<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet href="/stylesheets/rss.css" type="text/css"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:trackback="http://madskills.com/public/xml/rss/module/trackback/">
  <channel>
    <title>Handwriting: Tag sxsw</title>
    <link>http://blog.handwire.com/articles/tag/sxsw?tag=sxsw</link>
    <language>en-us</language>
    <ttl>40</ttl>
    <description>A blog by Handwire</description>
    <item>
      <title>Saturation or Sense?</title>
      <description>&lt;p&gt;I just read a &lt;a href="http://www.jaredigital.com/article/154/sxsw-2006-day-1"&gt;good summary&lt;/a&gt; of the general message at &lt;span class="caps"&gt;SXSW&lt;/span&gt; Interactive (which echoed my own summary):&lt;/p&gt;


&lt;blockquote&gt;If there was one overarching message at this year’s conference, I think it was this: Businesses or services have customers, clients and/or users. And those are people. Human beings. The way of speaking to and otherwise communicating with those people is changing. The press release is boring. People would much rather read a blog. Corporate-speak is a thing of the past. There are ways to stay professional and better engage customers. Because no one is passionate or really excited about a company that they don’t relate to. The key is passionate users. With so many options for consuming services, it is key to incite passion in customers, clients and users. They should be proud to “buy your t-shirt”—believe in your culture, message and persona. It is the experience that sells. It is the experience that differentiates.&lt;/blockquote&gt;

	&lt;p&gt;It&amp;#8217;s that last sentence along with a question that we heard during the Fried / 
Coudal keynote that&amp;#8217;s got me thinking.&lt;/p&gt;&lt;p&gt;The question was basically:  how many subscription-based web apps will one person sign up to before it&amp;#8217;s just too much to think about?&lt;/p&gt;


	&lt;p&gt;Fried suggested that even if this new movement means a single person is signing up to ten $10/month (highly specific, simple, elegant) services, he himself would pay that $100 a month to get tools that are useful and compelling.&lt;/p&gt;


	&lt;p&gt;Sure, that might make sense.  We consumers pay monthly for services all the time:  cell phone, land-line, cable, broadband, magazine and newspaper subscriptions etc..  It does seem that the web is moving that way too &amp;#8211; rather than buying a box from a store with bloated software in it and buying the update a year later, the software landscape is turning into a more dynamic, web-based service style business.&lt;/p&gt;


	&lt;p&gt;This change in focus is valuable for everyone involved, especially consumers.  There&amp;#8217;s no denying that.  However, people only have so much passion to go around.  Passion is an extreme emotion, and if people ended up passionate about every product or service that they use they&amp;#8217;d get burnt out.  Similarly, building community is great, but there are only so many communities that one can be a part of.  If you&amp;#8217;re an avid Flickr user, and let&amp;#8217;s say you&amp;#8217;re also on Friendster or MySpace or something like that, plus you keep a blog and read others&amp;#8217; blogs&amp;#8230; when does it end?&lt;/p&gt;


	&lt;p&gt;More likely, people will never reach that saturation point.  A few great services and products will rise to the surface, and the rest will die away.&lt;/p&gt;


	&lt;p&gt;On the other hand, it’s not like one day all the products that to need to exist &lt;em&gt;will&lt;/em&gt; exist, and then we can all go home. Although there may be some limit to the number of products or services that a single person will pay for and get excited about, there are almost an infinite number of groups and subgroups of people with different needs and interests. So, we’ll probably see a trend toward highly focused applications that cater to very narrow market segments.&lt;/p&gt;</description>
      <pubDate>Thu, 16 Mar 2006 10:47:00 -0500</pubDate>
      <guid isPermaLink="false">urn:uuid:72387c45-e6a8-4991-97bc-e1611e74a324</guid>
      <author>Kristina B</author>
      <link>http://blog.handwire.com/articles/2006/03/16/saturation-or-sense</link>
      <category>sxsw06</category>
      <category>sxsw</category>
      <category>sxswi</category>
      <category>handwire</category>
      <category>marketing</category>
      <category>business</category>
      <trackback:ping>http://blog.handwire.com/articles/trackback/39</trackback:ping>
    </item>
    <item>
      <title>Handwire At The Conference</title>
      <description>&lt;p&gt;We’ve all been going to panels and parties, and though we are very close to achieving “plum tuckered” status, we’re keeping it alive for the rest of Interactive and then (gasp)... music.  And when I say “it” I mean “us”.  I, for one, both look forward to this time of year and dread it.  Being an Austinite takes endurance sometimes.&lt;/p&gt;


	&lt;p&gt;Anyway, a bit about the panels we’ve seen.  The general consensus in the office is that the &lt;a href="http://2006.sxsw.com/interactive/programming/panels/?action=show&amp;#38;id=IAP060014"&gt;Creating Passionate Users&lt;/a&gt; panel on Saturday was one of the best panels that any of us have seen so far.  It scored not only on content but delivery.  &lt;a href="http://headrush.typepad.com/creating_passionate_users/"&gt;Kathy Sierra&lt;/a&gt; really did a bang-up job at conveying useful, intelligent perspectives in an engaging way.&lt;/p&gt;&lt;p&gt;The panel focused on the psychology of people’s reactions to things, and how that can be used to build community, buzz and loyalty around a product.  I’m not a marketing person, and when I just reread that sentence it sounded like some kind of evil form of manipulation.  There was a bit about that, I suppose, but it was delivered in such a genuine and realistic way that it didn’t seem either evil or manipulative.  The reality is, for example, that people’s brains respond chemically to positive experiences and everything they are experiencing gets roped into that effect.  So, for example, if you show someone a picture of an attractive, scantily clad person along with your product they will respond positively even if their logical mind identifies it as a cheap marketing trick.   She really drove home the idea that, yes, there are cheap tricks you can use&amp;#8230; but using them effectively is an art form.&lt;/p&gt;


	&lt;p&gt;Cheap tricks aside, the strongest message in this panel was to focus on your customers rather than yourself.  Which, of course!  Duh!  Everyone knows that, right?  Still, look around the web and  you’ll find tons of marketing web sites that are really all about companies and products rather than their customers.  It’s an easy mistake to make.  This year really seems focused on creating &lt;a href="http://37signals.com/svn/"&gt;user-centric products&lt;/a&gt; and marketing them in a user-centric way.  Which is a good thing all around.&lt;/p&gt;


	&lt;p&gt;We sat around at lunch today talking about who the users of &lt;a href="http://www.bugwire.com"&gt;Bugwire&lt;/a&gt; really will be (people like us, no doubt), and what they might care about.  There was no shortage of jokes about putting svelte, naked people on the Bugwire home page.&lt;/p&gt;


	&lt;p&gt;With the &lt;a href="http://handwire.com/?request=21"&gt;wayfinding work&lt;/a&gt; we&amp;#8217;ve been doing recently, Steph was intrigued by the &lt;a href="http://2006.sxsw.com/interactive/programming/panels/?action=show&amp;#38;id=IAP060080"&gt;Online In Offline Spaces&lt;/a&gt; panel. The idea of tying web apps in to three dimensional spaces is exciting and &lt;a href="http://www.meetup.com/"&gt;Meetup&lt;/a&gt;, &lt;a href="http://dodgeball.com/"&gt;Dodgeball&lt;/a&gt;, and &lt;a href="http://socialight.com/"&gt;Socialite&lt;/a&gt; are brilliant examples of what can be done there. It&amp;#8217;ll be interesting to see if this idea can find more traction in applications that go beyond social networks.&lt;/p&gt;


	&lt;p&gt;More on panels coming soon.  If you missed the conference, some of the panels have been recorded as &lt;a href="http://2006.sxsw.com/coverage/podcasts/"&gt;podcasts&lt;/a&gt;.&lt;/p&gt;</description>
      <pubDate>Tue, 14 Mar 2006 21:57:00 -0500</pubDate>
      <guid isPermaLink="false">urn:uuid:88b8d0eb-230c-4396-8247-016cb24d91ae</guid>
      <author>Kristina B</author>
      <link>http://blog.handwire.com/articles/2006/03/14/handwire-at-the-conference</link>
      <category>sxsw06</category>
      <category>sxsw</category>
      <category>sxswi</category>
      <category>handwire</category>
      <category>bugwire</category>
      <category>austin</category>
      <category>kathysierra</category>
      <category>meetup</category>
      <category>dodgeball</category>
      <category>socialite</category>
      <trackback:ping>http://blog.handwire.com/articles/trackback/38</trackback:ping>
    </item>
    <item>
      <title>Big News At SXSWi</title>
      <description>&lt;p&gt;Handwire will be making an appearance at SXSWi with an exciting announcement.  We&amp;#8217;re finally going to follow the advice of numerous friends and partners and launch &lt;a href="http://www.bugwire.com"&gt;Bugwire&lt;/a&gt; as a product.&lt;/p&gt;


	&lt;p&gt;A while back, Handwire was casting about for bug tracking software that met our needs.  We wanted something that didn&amp;#8217;t include a thousand other features to crowd the interface and increase the bill. We wanted something simple, low cost and with minimal setup time/effort.  We looked and looked and found&amp;#8230; nothing quite right.&lt;/p&gt;


	&lt;p&gt;Around the same time, &lt;a href="http://www.rubyonrails.org/"&gt;Rails&lt;/a&gt; was gaining momentum and respect in the development community.   We were interested, but understandably wary of using a nascent platform on client projects.  We decided to apply our curiosity about Rails to the bug tracking problem, and Bugwire was born.&lt;/p&gt;


	&lt;p&gt;In designing the UI, we treated ourselves the way we would treat a client.  It was probably the easiest requirements gathering experience we&amp;#8217;ve ever had!  Quite simply, our software PMs, testers, tech leads and programmers needed a  system to queue up tasks and bugs.  It needed to be available to all parties in realtime.  We wanted each bug or task to allow file uploads.  It needed to be capable of handling a back and forth discussion about each task or bug.  Finally, it needed to allow clients to use it without showing them information about all the projects in the system.  Visually, we wanted a clear, uncrowded interface.&lt;/p&gt;


	&lt;p&gt;Within about a month, we had exactly what we needed.  Because we&amp;#8217;re good like that, and because Rails really is a &amp;#8220;rapid development platform&amp;#8221;.  We&amp;#8217;ve been using it, tweaking it and sharing it with our partners and contractors ever since.  The response has been resoundingly positive.  It&amp;#8217;s funny because Bugwire was truly meant to be an internal tool and experiment in Rails, but it&amp;#8217;s turned into something so useful for us that we might as well share it and find out if others like it as much as we do.&lt;/p&gt;


	&lt;p&gt;We still have some work to do to make it available online as a subscription service.  Keep an eye on this blog, as we&amp;#8217;ll post updates, screenshots and other information here in the coming weeks.  In the meantime, you can sign up for an invitation  to be an early tester at &lt;a href="http://bugwire.com"&gt;www.bugwire.com&lt;/a&gt;.  Sign up in the next 2 weeks for a special &lt;span class="caps"&gt;SXSW&lt;/span&gt; gift!&lt;/p&gt;</description>
      <pubDate>Sat, 11 Mar 2006 17:08:00 -0500</pubDate>
      <guid isPermaLink="false">urn:uuid:65b463b9-c089-42e7-be16-b3b41aa53638</guid>
      <author>Kristina B</author>
      <link>http://blog.handwire.com/articles/2006/03/11/big-news-at-sxswi</link>
      <category>bugwire</category>
      <category>handwire</category>
      <category>sxsw</category>
      <category>sxsw06</category>
      <category>rails</category>
      <trackback:ping>http://blog.handwire.com/articles/trackback/37</trackback:ping>
    </item>
  </channel>
</rss>
