<?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>Robby on Rails: Tag time</title>
    <link>http://www.robbyonrails.com/articles/tag/time</link>
    <language>en-us</language>
    <ttl>40</ttl>
    <description>thoughts.sort_by{|t| t[:topic]}.collect </description>
    <item>
      <title>Tip: Save your users 15+ seconds of their day</title>
      <description>&lt;p&gt;Since understanding the context is so important when designing interfaces, I wanted to point out one of those things that caused me to shake my head at.&lt;/p&gt;


	&lt;p&gt;When logging into our Basecamp account this afternoon (via openid)... I was presented the following helpful notice.&lt;/p&gt;


&lt;div class="thumbnail"&gt;&lt;a href="http://skitch.com/robbyrussell/fusw/know-your-user"&gt;&lt;img src="http://img.skitch.com/20080131-gqiir6xybre1cx7pp8ptbqrjjy.preview.jpg" alt="know your user" /&gt;&lt;/a&gt;&lt;br /&gt;&lt;span style="font-family: Lucida Grande, Trebuchet, sans-serif, Helvetica, Arial; font-size: 10px; color: #808080"&gt;Uploaded with &lt;a href="http://plasq.com/"&gt;plasq&lt;/a&gt;&amp;#8217;s &lt;a href="http://skitch.com"&gt;Skitch&lt;/a&gt;!&lt;/span&gt;&lt;/div&gt;

	&lt;p&gt;What&amp;#8217;s amusing in this scenario&amp;#8230; is that I&amp;#8217;m sure that Basecamp knows that I&amp;#8217;m logged in via openid and it is, in fact, displaying the OpenBar across the top of the page. Yet, it&amp;#8217;s making this helpful recommendation that I&amp;#8217;m obviously already aware of.&lt;/p&gt;


	&lt;p&gt;What harm is there? Well, in this scenario, I caught it and thought, &amp;#8220;wow, this isn&amp;#8217;t helpful or informative.&amp;#8221; Over time, it&amp;#8217;s these short-lived experiences that affect our overall perceptions of the product.&lt;/p&gt;


	&lt;p&gt;When we&amp;#8217;re designing and developing applications, we must be very consistent with how we communicate with our audience. We don&amp;#8217;t need to provide them information that isn&amp;#8217;t relevant to them.&lt;/p&gt;


	&lt;p&gt;I&amp;#8217;m not picking on Basecamp here, I&amp;#8217;m sure that they have great intentions with this, but as a developer, I know that it doesn&amp;#8217;t take a whole lot of extra work to avoid small problems like this, which could lead your people to feel like you&amp;#8217;re not being respectful of their time.&lt;/p&gt;


	&lt;p&gt;Saving customers 15-30 seconds is something that we can quantify.&lt;/p&gt;


	&lt;ul&gt;
	&lt;li&gt;100 customers = 25-50 minutes &lt;/li&gt;
		&lt;li&gt;1,000 customers = ~4-8 hours&lt;/li&gt;
		&lt;li&gt;10,000 customers = 40-80 hours&lt;/li&gt;
		&lt;li&gt;etc&amp;#8230;&lt;/li&gt;
	&lt;/ul&gt;


	&lt;p&gt;Just a little reminder that it&amp;#8217;s easy for us to overlook things like that can make a difference.&lt;/p&gt;
</description>
      <pubDate>Thu, 31 Jan 2008 12:42:00 -0600</pubDate>
      <guid isPermaLink="false">urn:uuid:e23e3e9a-7633-4e55-a272-93f058148ba3</guid>
      <author>Robby Russell</author>
      <link>http://www.robbyonrails.com/articles/2008/01/31/tip-save-your-users-15-seconds-of-their-day</link>
      <category>interaction</category>
      <category>ixda</category>
      <category>ui</category>
      <category>communication</category>
      <category>users</category>
      <category>people</category>
      <category>time</category>
      <category>tip</category>
    </item>
  </channel>
</rss>
