<?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 are more important than potential users!</title>
	<atom:link href="http://compoundthinking.com/blog/index.php/2006/08/31/users-are-more-important-than-potential-users/feed/" rel="self" type="application/rss+xml" />
	<link>http://compoundthinking.com/blog/index.php/2006/08/31/users-are-more-important-than-potential-users/</link>
	<description>Thinking about programming in new ways</description>
	<lastBuildDate>Tue, 15 Mar 2011 02:30:01 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Mark Ramm</title>
		<link>http://compoundthinking.com/blog/index.php/2006/08/31/users-are-more-important-than-potential-users/#comment-3760</link>
		<dc:creator>Mark Ramm</dc:creator>
		<pubDate>Mon, 04 Sep 2006 00:26:06 +0000</pubDate>
		<guid isPermaLink="false">http://compoundthinking.com/blog/index.php/2006/08/31/users-are-more-important-than-potential-users/#comment-3760</guid>
		<description>Adam, 

We provide context sensitive help already, and it helps a lot when somebody is in the right area already.  The manual provides a overview of, and a structure for understanding, the process that the software is designed to facilitate.

A &quot;getting started&quot; guide, and perhaps a getting started screencast is something we&#039;ve talked about.  

Another thing we&#039;ve been talking about is trying to find a way to distribute paper versions of something like the getting started guide or the manual to our online users in an economical way.   People are still way more likely to read paper than PDF&#039;s .

--Mark</description>
		<content:encoded><![CDATA[<p>Adam, </p>
<p>We provide context sensitive help already, and it helps a lot when somebody is in the right area already.  The manual provides a overview of, and a structure for understanding, the process that the software is designed to facilitate.</p>
<p>A &#8220;getting started&#8221; guide, and perhaps a getting started screencast is something we&#8217;ve talked about.  </p>
<p>Another thing we&#8217;ve been talking about is trying to find a way to distribute paper versions of something like the getting started guide or the manual to our online users in an economical way.   People are still way more likely to read paper than PDF&#8217;s .</p>
<p>&#8211;Mark</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Adam Jones</title>
		<link>http://compoundthinking.com/blog/index.php/2006/08/31/users-are-more-important-than-potential-users/#comment-3759</link>
		<dc:creator>Adam Jones</dc:creator>
		<pubDate>Sun, 03 Sep 2006 23:57:56 +0000</pubDate>
		<guid isPermaLink="false">http://compoundthinking.com/blog/index.php/2006/08/31/users-are-more-important-than-potential-users/#comment-3759</guid>
		<description>How are you distributing these manuals? If they are available as a help file you could look into making it context-sensitive so people could just click a &quot;get help&quot; button and it opens the manal pages relevant to what they are doing.

If it isn&#039;t, consider doing that. Also put any &quot;getting started&quot; information in the front of the manual as well, and fill it with &quot;you can get more information about $X on page $Y&quot; where appropriate.</description>
		<content:encoded><![CDATA[<p>How are you distributing these manuals? If they are available as a help file you could look into making it context-sensitive so people could just click a &#8220;get help&#8221; button and it opens the manal pages relevant to what they are doing.</p>
<p>If it isn&#8217;t, consider doing that. Also put any &#8220;getting started&#8221; information in the front of the manual as well, and fill it with &#8220;you can get more information about $X on page $Y&#8221; where appropriate.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

