<?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: Don&#8217;t Make Me Think!: A Common Sense Approach to Web Usability</title>
	<atom:link href="http://www.teamrubber.com/blog/dont-make-me-think-a-common-sense-approach-to-web-usability/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.teamrubber.com/blog/dont-make-me-think-a-common-sense-approach-to-web-usability/</link>
	<description>Team Rubber talks on the Internet in a blog</description>
	<lastBuildDate>Thu, 08 Dec 2011 13:10:18 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1.1</generator>
	<item>
		<title>By: Book report: Don&#8217;t Make Me Think!: A Common Sense Approach to Web Usability</title>
		<link>http://www.teamrubber.com/blog/dont-make-me-think-a-common-sense-approach-to-web-usability/comment-page-1/#comment-2324</link>
		<dc:creator>Book report: Don&#8217;t Make Me Think!: A Common Sense Approach to Web Usability</dc:creator>
		<pubDate>Sun, 26 Apr 2009 00:42:03 +0000</pubDate>
		<guid isPermaLink="false">http://www.teamrubber.com/blog/?p=81#comment-2324</guid>
		<description>[...] book report originally appeared on the Team Rubber blog.  Cover of Don&#039;t Make Me [...]</description>
		<content:encoded><![CDATA[<p>[...] book report originally appeared on the Team Rubber blog.  Cover of Don&#8217;t Make Me [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andy</title>
		<link>http://www.teamrubber.com/blog/dont-make-me-think-a-common-sense-approach-to-web-usability/comment-page-1/#comment-44</link>
		<dc:creator>Andy</dc:creator>
		<pubDate>Fri, 08 Feb 2008 17:09:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.teamrubber.com/blog/?p=81#comment-44</guid>
		<description>Hi Lisa,

Hmm, writing for the web.  You&#039;ll have guessed, I&#039;m with Ogilvy and Claude Hopkins: when you have something detailed that you need to communicate, go long.  

Long works well, for example, when you need to answer questions people might have, or persuade them of something.  Use cases might be a product sales page: years of testing shows that typically, more detail will produce more conversions (although it must be relevant detail).  Similarly, a long job ad will communicate more of the company character and culture; it will also better explain the job role.

Where &quot;Don&#039;t make me think&quot; has it exactly right is in reducing pointless words.  Remove fluff and happy talk that doesn&#039;t communicate; be as long as necessary and no longer.  In that spirit, I&#039;ll end this here.</description>
		<content:encoded><![CDATA[<p>Hi Lisa,</p>
<p>Hmm, writing for the web.  You&#8217;ll have guessed, I&#8217;m with Ogilvy and Claude Hopkins: when you have something detailed that you need to communicate, go long.  </p>
<p>Long works well, for example, when you need to answer questions people might have, or persuade them of something.  Use cases might be a product sales page: years of testing shows that typically, more detail will produce more conversions (although it must be relevant detail).  Similarly, a long job ad will communicate more of the company character and culture; it will also better explain the job role.</p>
<p>Where &#8220;Don&#8217;t make me think&#8221; has it exactly right is in reducing pointless words.  Remove fluff and happy talk that doesn&#8217;t communicate; be as long as necessary and no longer.  In that spirit, I&#8217;ll end this here.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

