<?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: Goal-Driven Documentation</title>
	<atom:link href="http://tynerblain.com/blog/2006/10/09/goal-driven-documentation/feed/" rel="self" type="application/rss+xml" />
	<link>http://tynerblain.com/blog/2006/10/09/goal-driven-documentation/</link>
	<description>Software product success.</description>
	<lastBuildDate>Tue, 22 May 2012 20:46:27 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.4</generator>
	<item>
		<title>By: Laura Harley</title>
		<link>http://tynerblain.com/blog/2006/10/09/goal-driven-documentation/comment-page-1/#comment-141950</link>
		<dc:creator>Laura Harley</dc:creator>
		<pubDate>Fri, 31 Aug 2007 20:45:01 +0000</pubDate>
		<guid isPermaLink="false">http://tynerblain.com/blog/2006/10/09/goal-driven-documentation/#comment-141950</guid>
		<description>Your articles is right on target. I couldn&#039;t agree with you more. Unfortunately, the principle in software is to write only about the tool, and not the job, because we in software can&#039;t really know what the actual job in a company might be. Somewhere, software requirements folks determined this was the correct approach. I argue with this all the time in developing help for software systems. So I agree with you. However, your article lacks research or specific information about users preferences for help, what works and what doesn&#039;t. Your logic, however clear to me, won&#039;t convince my managers.</description>
		<content:encoded><![CDATA[<p>Your articles is right on target. I couldn&#8217;t agree with you more. Unfortunately, the principle in software is to write only about the tool, and not the job, because we in software can&#8217;t really know what the actual job in a company might be. Somewhere, software requirements folks determined this was the correct approach. I argue with this all the time in developing help for software systems. So I agree with you. However, your article lacks research or specific information about users preferences for help, what works and what doesn&#8217;t. Your logic, however clear to me, won&#8217;t convince my managers.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Scott Sehlhorst</title>
		<link>http://tynerblain.com/blog/2006/10/09/goal-driven-documentation/comment-page-1/#comment-55647</link>
		<dc:creator>Scott Sehlhorst</dc:creator>
		<pubDate>Thu, 19 Oct 2006 14:09:19 +0000</pubDate>
		<guid isPermaLink="false">http://tynerblain.com/blog/2006/10/09/goal-driven-documentation/#comment-55647</guid>
		<description>Hooray!

Thanks Nils, you&#039;ve made my day!

And good luck with the doc, I think you&#039;re right - it will help a ton.  Did you also check out the &lt;a href=&quot;http://tynerblain.com/blog/2006/10/10/use-case-driven-documentation/&quot; title=&quot;Use Case Driven Doc&quot; rel=&quot;nofollow&quot;&gt;Use Case Driven Documentation&lt;/a&gt; article?</description>
		<content:encoded><![CDATA[<p>Hooray!</p>
<p>Thanks Nils, you&#8217;ve made my day!</p>
<p>And good luck with the doc, I think you&#8217;re right &#8211; it will help a ton.  Did you also check out the <a href="http://tynerblain.com/blog/2006/10/10/use-case-driven-documentation/" title="Use Case Driven Doc" rel="nofollow">Use Case Driven Documentation</a> article?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nils</title>
		<link>http://tynerblain.com/blog/2006/10/09/goal-driven-documentation/comment-page-1/#comment-55634</link>
		<dc:creator>Nils</dc:creator>
		<pubDate>Wed, 18 Oct 2006 20:57:53 +0000</pubDate>
		<guid isPermaLink="false">http://tynerblain.com/blog/2006/10/09/goal-driven-documentation/#comment-55634</guid>
		<description>Scott - This post is so timely for me! I&#039;m currently reworking the doc set for our product (Accept 360°) with these goals (and a lot of Kathy Sierra&#039;s ideas) in mind. It&#039;s a big change, and somewhat scary - not much of the current docs will be left by the time I&#039;m finished, so it&#039;s all new work -- but I know it will provide a lot of value for customers and prospects evaluating the product.</description>
		<content:encoded><![CDATA[<p>Scott &#8211; This post is so timely for me! I&#8217;m currently reworking the doc set for our product (Accept 360°) with these goals (and a lot of Kathy Sierra&#8217;s ideas) in mind. It&#8217;s a big change, and somewhat scary &#8211; not much of the current docs will be left by the time I&#8217;m finished, so it&#8217;s all new work &#8212; but I know it will provide a lot of value for customers and prospects evaluating the product.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

