<?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: Users Read Help Manuals Like an Encyclopedia, Not a Novel</title>
	<atom:link href="http://www.idratherbewriting.com/2008/09/19/users-read-help-manuals-like-an-encyclopedia-not-a-novel/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.idratherbewriting.com/2008/09/19/users-read-help-manuals-like-an-encyclopedia-not-a-novel/</link>
	<description>Technical Communication Blog / Technical Writing Blog</description>
	<lastBuildDate>Mon, 22 Mar 2010 08:03:46 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Your Writing Dept Blog &#187; Do you read user manuals?</title>
		<link>http://www.idratherbewriting.com/2008/09/19/users-read-help-manuals-like-an-encyclopedia-not-a-novel/comment-page-1/#comment-134880</link>
		<dc:creator>Your Writing Dept Blog &#187; Do you read user manuals?</dc:creator>
		<pubDate>Wed, 01 Oct 2008 05:16:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.idratherbewriting.com/?p=2005#comment-134880</guid>
		<description>[...] More on this at the I&#8217;d Rather Be Writing Technical Communication Blog [...]</description>
		<content:encoded><![CDATA[<p>[...] More on this at the I&#8217;d Rather Be Writing Technical Communication Blog [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ron</title>
		<link>http://www.idratherbewriting.com/2008/09/19/users-read-help-manuals-like-an-encyclopedia-not-a-novel/comment-page-1/#comment-134872</link>
		<dc:creator>Ron</dc:creator>
		<pubDate>Tue, 30 Sep 2008 21:41:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.idratherbewriting.com/?p=2005#comment-134872</guid>
		<description>My original post on LinkedIn:

“I always look at the product manual to see how well it was written and how it was designed. When making a major purchase, I usually go to the company&#039;s web site to see if the manual is available as a download before I make the purchase. My opinion is that a well-written manual equates to a well built and supported product. I save manuals in a file for future use for what to do and what not to do when writing a user manual. Learn from the good and avoid what does not work.&quot;

But then I got to thinking about how product design plays an important role in the need, or lack of need, for documentation. A poorly designed product with difficult to understand functionality would require more detailed documentation before the user is competent with the product, while a well designed product would allow for the user to learn by using (or, at least we should be able to assume).

So, my answer would have to be based on the extent to which the product was designed with the user in mind.

Ron
www.YourWritingDept.com</description>
		<content:encoded><![CDATA[<p>My original post on LinkedIn:</p>
<p>“I always look at the product manual to see how well it was written and how it was designed. When making a major purchase, I usually go to the company&#8217;s web site to see if the manual is available as a download before I make the purchase. My opinion is that a well-written manual equates to a well built and supported product. I save manuals in a file for future use for what to do and what not to do when writing a user manual. Learn from the good and avoid what does not work.&#8221;</p>
<p>But then I got to thinking about how product design plays an important role in the need, or lack of need, for documentation. A poorly designed product with difficult to understand functionality would require more detailed documentation before the user is competent with the product, while a well designed product would allow for the user to learn by using (or, at least we should be able to assume).</p>
<p>So, my answer would have to be based on the extent to which the product was designed with the user in mind.</p>
<p>Ron<br />
<a href="http://www.YourWritingDept.com" rel="nofollow">http://www.YourWritingDept.com</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Decomposing the Handbook for the Recently Deceased &#171; ffeathers &#8212; a technical writer&#8217;s blog</title>
		<link>http://www.idratherbewriting.com/2008/09/19/users-read-help-manuals-like-an-encyclopedia-not-a-novel/comment-page-1/#comment-134734</link>
		<dc:creator>Decomposing the Handbook for the Recently Deceased &#171; ffeathers &#8212; a technical writer&#8217;s blog</dc:creator>
		<pubDate>Sat, 27 Sep 2008 07:13:35 +0000</pubDate>
		<guid isPermaLink="false">http://www.idratherbewriting.com/?p=2005#comment-134734</guid>
		<description>[...] &#8220;Users turn to the help  to look for a specific question, just as someone consults an encyclopedia for a specific question.&#8221; (From Tom Johnson, in his post Users Read Help Manuals Like an Encyclopedia, Not a Novel.) [...]</description>
		<content:encoded><![CDATA[<p>[...] &#8220;Users turn to the help  to look for a specific question, just as someone consults an encyclopedia for a specific question.&#8221; (From Tom Johnson, in his post Users Read Help Manuals Like an Encyclopedia, Not a Novel.) [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andrew</title>
		<link>http://www.idratherbewriting.com/2008/09/19/users-read-help-manuals-like-an-encyclopedia-not-a-novel/comment-page-1/#comment-134722</link>
		<dc:creator>Andrew</dc:creator>
		<pubDate>Fri, 26 Sep 2008 18:00:57 +0000</pubDate>
		<guid isPermaLink="false">http://www.idratherbewriting.com/?p=2005#comment-134722</guid>
		<description>This is a great discussion and a constant source of tension between myself and my clients. Thanks for the insight!</description>
		<content:encoded><![CDATA[<p>This is a great discussion and a constant source of tension between myself and my clients. Thanks for the insight!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
