<?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: No More Ponderous Usability Tests! Or&#8230;?</title>
	<atom:link href="http://usabilityworks.org/2007/06/23/no-more-ponderous-usability-tests-or/feed/" rel="self" type="application/rss+xml" />
	<link>http://usabilityworks.org/2007/06/23/no-more-ponderous-usability-tests-or/</link>
	<description>Making next year's Human-Computer family reunion a lot less uncomfortable.</description>
	<pubDate>Thu, 08 Jan 2009 23:01:33 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Robert Barlow-Busch</title>
		<link>http://usabilityworks.org/2007/06/23/no-more-ponderous-usability-tests-or/comment-page-1/#comment-40621</link>
		<dc:creator>Robert Barlow-Busch</dc:creator>
		<pubDate>Mon, 25 Jun 2007 05:06:38 +0000</pubDate>
		<guid isPermaLink="false">http://usabilityworks.org/2007/06/23/no-more-ponderous-usability-tests-or/#comment-40621</guid>
		<description>Hey Matthew, thanks for your comments on this video about design checkpoints. You're entirely right that what I talk about "is pretty basic" -- in fact, those three words more or less sum up the motivation behind design checkpoints. I began conducting these while a consultant at Quarry Integrated Communications, after noticing that clients tended to view usability tests as Special Events. When this happens, things tend to slow down. Perhaps this effect is worsened by the client/consultant effect? Hmm... Anyway, introducing design checkpoints often helped us to speed things back up again while shifting focus back to the purpose of usability: improving design! FYI that a brief commentary and slides are also available on my blog at &lt;a href="http://www.chopsticker.com/" rel="nofollow"&gt;www.chopsticker.com&lt;/a&gt;.</description>
		<content:encoded><![CDATA[<p>Hey Matthew, thanks for your comments on this video about design checkpoints. You&#8217;re entirely right that what I talk about &#8220;is pretty basic&#8221; &#8212; in fact, those three words more or less sum up the motivation behind design checkpoints. I began conducting these while a consultant at Quarry Integrated Communications, after noticing that clients tended to view usability tests as Special Events. When this happens, things tend to slow down. Perhaps this effect is worsened by the client/consultant effect? Hmm&#8230; Anyway, introducing design checkpoints often helped us to speed things back up again while shifting focus back to the purpose of usability: improving design! FYI that a brief commentary and slides are also available on my blog at <a href="http://www.chopsticker.com/" rel="nofollow">http://www.chopsticker.com</a>.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
