<?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: Documentation: the user assistance of last resort?</title>
	<atom:link href="http://www.itauthor.com/2010/01/23/documentation-the-user-assistance-of-last-resort/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.itauthor.com/2010/01/23/documentation-the-user-assistance-of-last-resort/</link>
	<description>Stuff about technical writing and software</description>
	<lastBuildDate>Sat, 04 Feb 2012 23:42:54 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: itauthor</title>
		<link>http://www.itauthor.com/2010/01/23/documentation-the-user-assistance-of-last-resort/comment-page-1/#comment-7182</link>
		<dc:creator>itauthor</dc:creator>
		<pubDate>Mon, 15 Mar 2010 22:43:20 +0000</pubDate>
		<guid isPermaLink="false">http://www.itauthor.com/2010/01/23/documentation-the-user-assistance-of-last-resort/#comment-7182</guid>
		<description>Thanks for commenting Rhonda. 
 
&quot;ask the Twitterverse&quot; - that&#039;s an interesting one. I&#039;ve tried that a couple of times and not found it effective (maybe I don&#039;t have enough followers), but I think that, or something similar, is how we&#039;ll increasingly do things in future: throw out a question and someone, somewhere will come back with an answer. The Stackoverflow question/answer site is proof that people love being able to answer questions for other people! </description>
		<content:encoded><![CDATA[<p>Thanks for commenting Rhonda. </p>
<p>&quot;ask the Twitterverse&quot; - that&#039;s an interesting one. I&#039;ve tried that a couple of times and not found it effective (maybe I don&#039;t have enough followers), but I think that, or something similar, is how we&#039;ll increasingly do things in future: throw out a question and someone, somewhere will come back with an answer. The Stackoverflow question/answer site is proof that people love being able to answer questions for other people!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rhonda</title>
		<link>http://www.itauthor.com/2010/01/23/documentation-the-user-assistance-of-last-resort/comment-page-1/#comment-7174</link>
		<dc:creator>Rhonda</dc:creator>
		<pubDate>Sun, 14 Feb 2010 22:20:55 +0000</pubDate>
		<guid isPermaLink="false">http://www.itauthor.com/2010/01/23/documentation-the-user-assistance-of-last-resort/#comment-7174</guid>
		<description>Hi Alistair 
 
Nice post! I like how you&#039;ve expanded on my question about whether we&#039;re programmed to learn by &#039;trial and error&#039;.  
 
These days I work from home, so when I have a problem I can&#039;t just pop my head over the cubicle and ask a colleague. My strategies for finding out how to do something will involve any or all of these: Google, phone call/email/IM to a colleague, consult the Help, consult product forums, ask the Twitterverse. I *do* consult the Help, but as I said in my article, early success is CRITICAL as to whether or not I&#039;ll use that method with that product again. If I have difficulty finding what I need in the Help the first time (think Microsoft Word!), I&#039;m less likely to try it when I have later problems -- at that point Google is my friend ;-) 
 
I had another experience recently. We&#039;re in the process of moving to another house and the previous owners didn&#039;t leave the manuals for the oven and cooktop. I needed to reprogram the oven&#039;s clock and to learn a bit about how to operate this fancy oven, so I went to the manufacturer&#039;s website, downloaded the manuals, printed them out and now have them as a permanent reference for when I need to try something new with the oven. And yes, I&#039;ve read parts of them already (even before we&#039;ve moved in!), and was able to reprogram the clock successfully. Now for operating the fan-forced this and that.... I *will* read the manual before I try these things, but may never touch it again once I&#039;ve gained some mastery of the techniques. 
 </description>
		<content:encoded><![CDATA[<p>Hi Alistair </p>
<p>Nice post! I like how you&#039;ve expanded on my question about whether we&#039;re programmed to learn by &#039;trial and error&#039;.  </p>
<p>These days I work from home, so when I have a problem I can&#039;t just pop my head over the cubicle and ask a colleague. My strategies for finding out how to do something will involve any or all of these: Google, phone call/email/IM to a colleague, consult the Help, consult product forums, ask the Twitterverse. I *do* consult the Help, but as I said in my article, early success is CRITICAL as to whether or not I&#039;ll use that method with that product again. If I have difficulty finding what I need in the Help the first time (think Microsoft Word!), I&#039;m less likely to try it when I have later problems -- at that point Google is my friend ;-) </p>
<p>I had another experience recently. We&#039;re in the process of moving to another house and the previous owners didn&#039;t leave the manuals for the oven and cooktop. I needed to reprogram the oven&#039;s clock and to learn a bit about how to operate this fancy oven, so I went to the manufacturer&#039;s website, downloaded the manuals, printed them out and now have them as a permanent reference for when I need to try something new with the oven. And yes, I&#039;ve read parts of them already (even before we&#039;ve moved in!), and was able to reprogram the clock successfully. Now for operating the fan-forced this and that.... I *will* read the manual before I try these things, but may never touch it again once I&#039;ve gained some mastery of the techniques.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

