<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd"
xmlns:rawvoice="http://www.rawvoice.com/rawvoiceRssModule/"
	>
<channel>
	<title>Comments on: UIEtips: Quick &amp; Dirty Usability Testing: Step Away from the Book</title>
	<atom:link href="http://www.uie.com/brainsparks/2008/10/20/uietips-usabilitytesting_dc/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.uie.com/brainsparks/2008/10/20/uietips-usabilitytesting_dc/</link>
	<description>UIE\'s latest insights on the world of design</description>
	<lastBuildDate>Wed, 19 Jun 2013 09:10:37 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.4.1</generator>
	<item>
		<title>By: dış cephe</title>
		<link>http://www.uie.com/brainsparks/2008/10/20/uietips-usabilitytesting_dc/comment-page-1/#comment-144314</link>
		<dc:creator>dış cephe</dc:creator>
		<pubDate>Thu, 20 Nov 2008 17:14:09 +0000</pubDate>
		<guid isPermaLink="false">http://www.uie.com/brainsparks/?p=741#comment-144314</guid>
		<description>Thanks Dana.I agree.</description>
		<content:encoded><![CDATA[<p>Thanks Dana.I agree.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dana Chisnell</title>
		<link>http://www.uie.com/brainsparks/2008/10/20/uietips-usabilitytesting_dc/comment-page-1/#comment-144149</link>
		<dc:creator>Dana Chisnell</dc:creator>
		<pubDate>Thu, 23 Oct 2008 23:04:03 +0000</pubDate>
		<guid isPermaLink="false">http://www.uie.com/brainsparks/?p=741#comment-144149</guid>
		<description>Hey Bev, 

  I&#039;m totally projecting here, but there have got to be users -- or people who are like your users -- somewhere nearby. Even though your sites are business to business, there&#039;s a human there somewhere. There might be someone just down the hall from you who fits, or comes close. Can you give us an example?

Dana</description>
		<content:encoded><![CDATA[<p>Hey Bev, </p>
<p>  I&#8217;m totally projecting here, but there have got to be users &#8212; or people who are like your users &#8212; somewhere nearby. Even though your sites are business to business, there&#8217;s a human there somewhere. There might be someone just down the hall from you who fits, or comes close. Can you give us an example?</p>
<p>Dana</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Samantha LeVan</title>
		<link>http://www.uie.com/brainsparks/2008/10/20/uietips-usabilitytesting_dc/comment-page-1/#comment-144148</link>
		<dc:creator>Samantha LeVan</dc:creator>
		<pubDate>Thu, 23 Oct 2008 17:36:49 +0000</pubDate>
		<guid isPermaLink="false">http://www.uie.com/brainsparks/?p=741#comment-144148</guid>
		<description>Bev,

Do the participants need to be familiar with the website? For usability testing, as opposed to contextual research, you could try people who are business professionals from other fields to get a sense of the navigation and &quot;findability&quot; of information. Coffee shops are a great place to find business people, particularly at lunch or just before work. For quick and dirty, the perfect user isn&#039;t necessary. Closely related backgrounds and level of PC/Internet experience will still give you results to inspire design solutions.

Samantha</description>
		<content:encoded><![CDATA[<p>Bev,</p>
<p>Do the participants need to be familiar with the website? For usability testing, as opposed to contextual research, you could try people who are business professionals from other fields to get a sense of the navigation and &#8220;findability&#8221; of information. Coffee shops are a great place to find business people, particularly at lunch or just before work. For quick and dirty, the perfect user isn&#8217;t necessary. Closely related backgrounds and level of PC/Internet experience will still give you results to inspire design solutions.</p>
<p>Samantha</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bev</title>
		<link>http://www.uie.com/brainsparks/2008/10/20/uietips-usabilitytesting_dc/comment-page-1/#comment-144147</link>
		<dc:creator>Bev</dc:creator>
		<pubDate>Thu, 23 Oct 2008 15:21:16 +0000</pubDate>
		<guid isPermaLink="false">http://www.uie.com/brainsparks/?p=741#comment-144147</guid>
		<description>I am very interested in the method Dana proposes, but I&#039;m unsure how I can relate it to the type of client sites I design, which are mainly B2B (Business to Business) sites in areas like Telecommunications. These sites are aimed at business customers. Apart from trade shows, I&#039;m unsure how I could quickly and easily find suitable participants for the type of sites I&#039;m working on. Any suggestions?</description>
		<content:encoded><![CDATA[<p>I am very interested in the method Dana proposes, but I&#8217;m unsure how I can relate it to the type of client sites I design, which are mainly B2B (Business to Business) sites in areas like Telecommunications. These sites are aimed at business customers. Apart from trade shows, I&#8217;m unsure how I could quickly and easily find suitable participants for the type of sites I&#8217;m working on. Any suggestions?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Samantha LeVan</title>
		<link>http://www.uie.com/brainsparks/2008/10/20/uietips-usabilitytesting_dc/comment-page-1/#comment-144133</link>
		<dc:creator>Samantha LeVan</dc:creator>
		<pubDate>Tue, 21 Oct 2008 16:26:07 +0000</pubDate>
		<guid isPermaLink="false">http://www.uie.com/brainsparks/?p=741#comment-144133</guid>
		<description>When I have the time, I work on pet projects where I will take weeks or months to do formal research and usability testing. But on a regular basis, most everything I do is quick &amp; dirty. I&#039;d rather make sure some research is done, no matter the project schedule constraints, than say &quot;sorry, I&#039;d need at least a month&quot;. It was hard for me to learn this outside of school, but once I realized my results were similar, although maybe less detailed, it&#039;s become my favorite way to conduct user research. What&#039;s more thrilling is that my clients are just as happy with quick and dirty results.

I generally try to shoot for five users per round of usability testing, but if I see the first three all have exactly the same issues and I&#039;m under pressure to return the results quickly, I&#039;ll stop there and collect my thoughts, make a quick PowerPoint or Word doc and be done with it.

One of my favorite ways to present data is in Visio. Just thought bubbles right where the problems are... works well when there are many detail issues to resolve, as opposed to wholistic design changes.</description>
		<content:encoded><![CDATA[<p>When I have the time, I work on pet projects where I will take weeks or months to do formal research and usability testing. But on a regular basis, most everything I do is quick &amp; dirty. I&#8217;d rather make sure some research is done, no matter the project schedule constraints, than say &#8220;sorry, I&#8217;d need at least a month&#8221;. It was hard for me to learn this outside of school, but once I realized my results were similar, although maybe less detailed, it&#8217;s become my favorite way to conduct user research. What&#8217;s more thrilling is that my clients are just as happy with quick and dirty results.</p>
<p>I generally try to shoot for five users per round of usability testing, but if I see the first three all have exactly the same issues and I&#8217;m under pressure to return the results quickly, I&#8217;ll stop there and collect my thoughts, make a quick PowerPoint or Word doc and be done with it.</p>
<p>One of my favorite ways to present data is in Visio. Just thought bubbles right where the problems are&#8230; works well when there are many detail issues to resolve, as opposed to wholistic design changes.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mark Pawson</title>
		<link>http://www.uie.com/brainsparks/2008/10/20/uietips-usabilitytesting_dc/comment-page-1/#comment-144132</link>
		<dc:creator>Mark Pawson</dc:creator>
		<pubDate>Tue, 21 Oct 2008 15:04:49 +0000</pubDate>
		<guid isPermaLink="false">http://www.uie.com/brainsparks/?p=741#comment-144132</guid>
		<description>Run Tests at Tradeshows. There was two posts on this at IXDA.org
 http://www.ixda.org/discuss.php?post=23564
 http://www.ixda.org/discuss.php?post=18865

Saul Greenberg and I just finished submitting a paper to the Journal of Usability Studies on a technique I used successfully with a colleague at a major Photographic show. Here&#039;s hoping it gets accepted because when I did the research on this I found almost nothing for published material, even though based on the two links above, others have successfully done it.</description>
		<content:encoded><![CDATA[<p>Run Tests at Tradeshows. There was two posts on this at IXDA.org<br />
 <a href="http://www.ixda.org/discuss.php?post=23564" rel="nofollow">http://www.ixda.org/discuss.php?post=23564</a><br />
 <a href="http://www.ixda.org/discuss.php?post=18865" rel="nofollow">http://www.ixda.org/discuss.php?post=18865</a></p>
<p>Saul Greenberg and I just finished submitting a paper to the Journal of Usability Studies on a technique I used successfully with a colleague at a major Photographic show. Here&#8217;s hoping it gets accepted because when I did the research on this I found almost nothing for published material, even though based on the two links above, others have successfully done it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tara Schnaible</title>
		<link>http://www.uie.com/brainsparks/2008/10/20/uietips-usabilitytesting_dc/comment-page-1/#comment-144129</link>
		<dc:creator>Tara Schnaible</dc:creator>
		<pubDate>Tue, 21 Oct 2008 14:27:38 +0000</pubDate>
		<guid isPermaLink="false">http://www.uie.com/brainsparks/?p=741#comment-144129</guid>
		<description>Working for a non-profit, we rarely have the luxury of time or formalized equipment for testing.  Some aspects of formalized testing have made their way into our process, but our &lt;b&gt;average recruit/test/result-presentation time-frame&lt;/b&gt; is about &lt;b&gt;1.5 weeks&lt;/b&gt;.  We make certain to maintain tester anonymity (even when showing developers/team members video), we record mouse movements (and manually tally patterns), we formally present results via spreadsheets that breaks results down into &quot;overarching issues&quot; that have fixed severity/repeats/timing measures.
Formality aside, where that testing deviates:
 @ We&#039;ve found ways to use low-cost applications/sites to test (Webex sessions through Nethope, they can be recorded and as a member of Nethope we have free access to Webex)  We use Adobe Acrobat/Axure models/early-dev websites/Paper-Prototypes, whatever we can, to get ANY INFO about basic ideas about terminology/navigation/etc as early as we can.
 @ We do not create formal/elaborate Word reports, our teams have to trudge through an Excel results sheet
 @ We test with 5-7 users, tests are oftentimes conducted remotely (see Webex/Skype) and we spend weeks at the onset of the project recruiting appropriate users from the project team/other representative people from local offices/etc.
 @ Due to remote testing and a need to make users feel at-ease (they are often strangers to the tester) - we are informal, friendly and chatty without leading answers/questions.
 @ Smallish tests of terms/one page can be done by walking around the office asking people 1 question that tests an interface feature we think might be challenging.  Even tiny, impromptu tests can help provide guidance on whether a feature/widget/phrasing will work.

The underlying theme here is that you don&#039;t need great tools to eye-track, record mouse-clicks, etc.  E.g. If you see a 20-something lean in to a screen on a website to read text, signs are pretty good your fonts are way too small.  You can find out basic, valuable information in 5 minutes of questions and no budget.</description>
		<content:encoded><![CDATA[<p>Working for a non-profit, we rarely have the luxury of time or formalized equipment for testing.  Some aspects of formalized testing have made their way into our process, but our <b>average recruit/test/result-presentation time-frame</b> is about <b>1.5 weeks</b>.  We make certain to maintain tester anonymity (even when showing developers/team members video), we record mouse movements (and manually tally patterns), we formally present results via spreadsheets that breaks results down into &#8220;overarching issues&#8221; that have fixed severity/repeats/timing measures.<br />
Formality aside, where that testing deviates:<br />
 @ We&#8217;ve found ways to use low-cost applications/sites to test (Webex sessions through Nethope, they can be recorded and as a member of Nethope we have free access to Webex)  We use Adobe Acrobat/Axure models/early-dev websites/Paper-Prototypes, whatever we can, to get ANY INFO about basic ideas about terminology/navigation/etc as early as we can.<br />
 @ We do not create formal/elaborate Word reports, our teams have to trudge through an Excel results sheet<br />
 @ We test with 5-7 users, tests are oftentimes conducted remotely (see Webex/Skype) and we spend weeks at the onset of the project recruiting appropriate users from the project team/other representative people from local offices/etc.<br />
 @ Due to remote testing and a need to make users feel at-ease (they are often strangers to the tester) &#8211; we are informal, friendly and chatty without leading answers/questions.<br />
 @ Smallish tests of terms/one page can be done by walking around the office asking people 1 question that tests an interface feature we think might be challenging.  Even tiny, impromptu tests can help provide guidance on whether a feature/widget/phrasing will work.</p>
<p>The underlying theme here is that you don&#8217;t need great tools to eye-track, record mouse-clicks, etc.  E.g. If you see a 20-something lean in to a screen on a website to read text, signs are pretty good your fonts are way too small.  You can find out basic, valuable information in 5 minutes of questions and no budget.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dana Chisnell</title>
		<link>http://www.uie.com/brainsparks/2008/10/20/uietips-usabilitytesting_dc/comment-page-1/#comment-144125</link>
		<dc:creator>Dana Chisnell</dc:creator>
		<pubDate>Tue, 21 Oct 2008 02:33:26 +0000</pubDate>
		<guid isPermaLink="false">http://www.uie.com/brainsparks/?p=741#comment-144125</guid>
		<description>Max, 

There are lots of ways to find participants for studies. If you&#039;re sure you want current customers (rather than people who might be new to the site), you can try some things that I&#039;ve seen work for my clients: 

- Request that a link be put on the site that invites people to sign up to take part in user research (it might send them to an email that goes to you or to a small questionnaire that gathers contact information and then you can call them later). This has the advantage that people have opted in. If it&#039;s in a place on the site that people have to log in to use, you know they are already customers. 

- Hang out at a large branch (if your bank has branches) and ask people who are standing in line if they would like to participate in a short research session that will help the bank serve them better. Work with the bank manager to make sure he or she is comfortable with you doing this. You could even do short sessions right there in the branch if everyone is good with that. 

- Ask bankers in branches to help you recruit people who are opening accounts. Take the bankers out for coffee to thank them. 

If you have a couple of weeks before conducting your usability test, you might think about using personal and professional networks to help you find participants. Posting to craigslist.org might also work well, if you word the ad carefully. 

I don&#039;t recommend getting customer lists from the client for two reasons. First, most banks have privacy policies that customers have agreed to that prevent customers from being contacted for anything but doing specific business. Second, the contact information -- even at banks! -- can be woefully out of date.</description>
		<content:encoded><![CDATA[<p>Max, </p>
<p>There are lots of ways to find participants for studies. If you&#8217;re sure you want current customers (rather than people who might be new to the site), you can try some things that I&#8217;ve seen work for my clients: </p>
<p>- Request that a link be put on the site that invites people to sign up to take part in user research (it might send them to an email that goes to you or to a small questionnaire that gathers contact information and then you can call them later). This has the advantage that people have opted in. If it&#8217;s in a place on the site that people have to log in to use, you know they are already customers. </p>
<p>- Hang out at a large branch (if your bank has branches) and ask people who are standing in line if they would like to participate in a short research session that will help the bank serve them better. Work with the bank manager to make sure he or she is comfortable with you doing this. You could even do short sessions right there in the branch if everyone is good with that. </p>
<p>- Ask bankers in branches to help you recruit people who are opening accounts. Take the bankers out for coffee to thank them. </p>
<p>If you have a couple of weeks before conducting your usability test, you might think about using personal and professional networks to help you find participants. Posting to craigslist.org might also work well, if you word the ad carefully. </p>
<p>I don&#8217;t recommend getting customer lists from the client for two reasons. First, most banks have privacy policies that customers have agreed to that prevent customers from being contacted for anything but doing specific business. Second, the contact information &#8212; even at banks! &#8212; can be woefully out of date.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Max Soe</title>
		<link>http://www.uie.com/brainsparks/2008/10/20/uietips-usabilitytesting_dc/comment-page-1/#comment-144124</link>
		<dc:creator>Max Soe</dc:creator>
		<pubDate>Tue, 21 Oct 2008 00:00:08 +0000</pubDate>
		<guid isPermaLink="false">http://www.uie.com/brainsparks/?p=741#comment-144124</guid>
		<description>How do you actually acquire users for a client who is a corporate? For example, I may be working to improve a feature on an online banking site. How do I go about recruiting the client&#039;s users?</description>
		<content:encoded><![CDATA[<p>How do you actually acquire users for a client who is a corporate? For example, I may be working to improve a feature on an online banking site. How do I go about recruiting the client&#8217;s users?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
