<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>Boxes and Arrows: Comments by Etan Lightstone</title>
    <link>http://www.boxesandarrows.com/person/25305</link>
    <pubDate>Fri, 07 Jan 2011 19:48:51 GMT</pubDate>
    <description>Comments by Etan Lightstone</description>
    <item>
      <description>&lt;p&gt;Great article!&lt;br /&gt;A lot of people out there (as Andrew Maier pointed out) think that a usability study has to take weeks, involve expensive equipment and an interrogation room. I&amp;#8217;m glad you&amp;#8217;re getting the message out :)&lt;/p&gt;

	&lt;p&gt;A few comments of my own:&lt;/p&gt;

	&lt;p&gt;Regardless of how tight your deadline, I think it is an absolute must to at least run one or two pilot tests on internal users. The panic you describe, and the likelihood of having to change tasks (which could compromise your metric data) could be greatly reduced. More importantly, you lower the risk of potentially wasting a participants time (a big nono if you are testing an executive / VP user).&lt;/p&gt;

	&lt;p&gt;I very much liked the whiteboard strategy, I&amp;#8217;ve found that when running a study of my own, stakeholders often run into the room after a session has ended and bounce a million ideas off of me&amp;#8230; perhaps I&amp;#8217;ll try maintaining a living storyboard throughout the process.&lt;/p&gt;

	&lt;p&gt;One other thing is, if you find that this is going to be the kind of usability study where developers are likely going to make changes between days of testing, and tasks are likely going to be altered&amp;#8230; consider doing a &lt;a href="http://echouser.com/services.php" rel="nofollow" rel="nofollow"&gt; rapid Iterative style usability test &lt;/a&gt;. In this kind of test, metrics are charted out in iterations based on changes that happen to the UI that affect specific tasks. My company found this technique to be a powerful tool which blends nicely with a team&amp;#8217;s agile development style. Our site has some PDFs on the topic.&lt;/p&gt;

	&lt;p&gt;&amp;#8212;Etan&lt;br /&gt;UX engineer&lt;br /&gt;&lt;a href="http://www.echouser.com" rel="nofollow" rel="nofollow"&gt;EchoUser Inc&lt;/a&gt;&lt;/p&gt;</description>
      <link>http://www.boxesandarrows.com/view/quick-turnaround12#content_31594</link>
      <guid>http://www.boxesandarrows.com/view/quick-turnaround12#content_31594</guid>
      <pubDate>Fri, 07 Jan 2011 19:48:51 GMT</pubDate>
      <author>Etan Lightstone</author>
    </item>
  </channel>
</rss>

