<?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/"
		>
<channel>
	<title>Comments on: OJR&#039;s &#039;five guide&#039; to do-it-yourself website usability testing</title>
	<atom:link href="http://www.ojr.org/ojrs-five-guide-to-do-it-yourself-website-usability-testing/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.ojr.org/ojrs-five-guide-to-do-it-yourself-website-usability-testing/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=ojrs-five-guide-to-do-it-yourself-website-usability-testing</link>
	<description>Focusing on the future of digital journalism</description>
	<lastBuildDate>Mon, 15 Apr 2013 13:43:27 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.5.1</generator>
	<item>
		<title>By: Steve Yelvington</title>
		<link>http://www.ojr.org/ojrs-five-guide-to-do-it-yourself-website-usability-testing/#comment-883</link>
		<dc:creator>Steve Yelvington</dc:creator>
		<pubDate>Mon, 06 Aug 2007 10:30:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.ojr.org/?p=1341#comment-883</guid>
		<description><![CDATA[Find the most egregious mistakes. Fix them quickly. And then test again to find the next most egregious mistakes. Repeat the process until your website no longer makes your users cry.

The hard part isn&#039;t conducting the test, or identifying the errors, or even fixing them.

The hard part is resisting the temptation to turn the process into a Big Deal.

This &quot;five guide&quot; is a great step in the right direction.

But even this guide slips a bit into the analysis trap.

Beware of quantifying your data. Don&#039;t look for averages. Just look for screwups, and fix them fast. Don&#039;t write any reports longer than one page and make them bullet points of issues to be addressed.

I had to fill out a Skymiles form on Delta&#039;s website today. Apparently nobody ever tested the thing with real people, because I got stuck in a loop, bounced back to an error page whose messages did not match the actual &quot;error.&quot;

The web is rife with those kinds of design and implementation errors. You&#039;ll get the biggest return on your investment of time and energy by going after the low-hanging fruit of bad usability.
]]></description>
		<content:encoded><![CDATA[<p>Find the most egregious mistakes. Fix them quickly. And then test again to find the next most egregious mistakes. Repeat the process until your website no longer makes your users cry.</p>
<p>The hard part isn&#8217;t conducting the test, or identifying the errors, or even fixing them.</p>
<p>The hard part is resisting the temptation to turn the process into a Big Deal.</p>
<p>This &#8220;five guide&#8221; is a great step in the right direction.</p>
<p>But even this guide slips a bit into the analysis trap.</p>
<p>Beware of quantifying your data. Don&#8217;t look for averages. Just look for screwups, and fix them fast. Don&#8217;t write any reports longer than one page and make them bullet points of issues to be addressed.</p>
<p>I had to fill out a Skymiles form on Delta&#8217;s website today. Apparently nobody ever tested the thing with real people, because I got stuck in a loop, bounced back to an error page whose messages did not match the actual &#8220;error.&#8221;</p>
<p>The web is rife with those kinds of design and implementation errors. You&#8217;ll get the biggest return on your investment of time and energy by going after the low-hanging fruit of bad usability.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Robert Niles</title>
		<link>http://www.ojr.org/ojrs-five-guide-to-do-it-yourself-website-usability-testing/#comment-882</link>
		<dc:creator>Robert Niles</dc:creator>
		<pubDate>Fri, 03 Aug 2007 09:40:02 +0000</pubDate>
		<guid isPermaLink="false">http://www.ojr.org/?p=1341#comment-882</guid>
		<description><![CDATA[Since its our own CMS, we can make it do pretty much whatever we want... so long as there is reader demand. I&#039;m not quite sure exactly what functionality you&#039;re looking for here, but if you want to either comment again, or e-mail me via the link at the bottom of the page, with a little more detail, I&#039;d be happy to try to whip up something useful.]]></description>
		<content:encoded><![CDATA[<p>Since its our own CMS, we can make it do pretty much whatever we want&#8230; so long as there is reader demand. I&#8217;m not quite sure exactly what functionality you&#8217;re looking for here, but if you want to either comment again, or e-mail me via the link at the bottom of the page, with a little more detail, I&#8217;d be happy to try to whip up something useful.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tom Abate</title>
		<link>http://www.ojr.org/ojrs-five-guide-to-do-it-yourself-website-usability-testing/#comment-881</link>
		<dc:creator>Tom Abate</dc:creator>
		<pubDate>Fri, 03 Aug 2007 00:26:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.ojr.org/?p=1341#comment-881</guid>
		<description><![CDATA[Authors: awesome piece. Clear, terse, practical and authoritative. Thanks.

Editors: In future how-to pieces of this sort could you make it easy for readers who implement the instuctions to share any widgets or spreadsheets they might create? If that is difficult or risky than just accept thanks and encouragement for more nitty-gritty stuff of this caliber and tone.


 any  ]]></description>
		<content:encoded><![CDATA[<p>Authors: awesome piece. Clear, terse, practical and authoritative. Thanks.</p>
<p>Editors: In future how-to pieces of this sort could you make it easy for readers who implement the instuctions to share any widgets or spreadsheets they might create? If that is difficult or risky than just accept thanks and encouragement for more nitty-gritty stuff of this caliber and tone.</p>
<p> any  </p>
]]></content:encoded>
	</item>
</channel>
</rss>