<?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:series="http://unfoldingneurons.com/"
		>
<channel>
	<title>Comments on: How Google Does Help</title>
	<atom:link href="http://idratherbewriting.com/2009/06/27/how-google-does-help/feed/" rel="self" type="application/rss+xml" />
	<link>http://idratherbewriting.com/2009/06/27/how-google-does-help/</link>
	<description>The Latest Trends in Technical Communication</description>
	<lastBuildDate>Mon, 13 Feb 2012 21:02:51 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Susan Wu</title>
		<link>http://idratherbewriting.com/2009/06/27/how-google-does-help/comment-page-1/#comment-142576</link>
		<dc:creator>Susan Wu</dc:creator>
		<pubDate>Tue, 28 Jul 2009 14:11:46 +0000</pubDate>
		<guid isPermaLink="false">http://www.idratherbewriting.com/?p=3916#comment-142576</guid>
		<description>I don&#039;t think quick reference is necessary for all online apps. A quick reference guide for apps with more features and buttons is useful, but something like Twitter where there&#039;s really only one or two things you do (write an update with less than 140 characters) really does not need a quick reference. 

I tend to think of quick reference guides as a something that you refer to frequently when you can&#039;t remember which keys or buttons or shortcuts to use. If a new user wants to learn to use something for the first time, I think short video tutorials (like what Google Voice and Chrome did) tend to be more effective (for quick starts) than a step-by-step procedural help, but that&#039;s just my personal opinion. 

If Twitter had a short video demoing how to use Twitter, that should be sufficient (again, my opinion). That&#039;s not to stay that video tutorials should replace text-based documentation. There&#039;s a need for both, but I do think that the general trend for providing more &quot;useful&quot; documentation, especially for online apps should be more contextualized rather than linear. 

When Gmail changed how users can label their emails (drag and drop as if labels were &quot;folders&quot;), the first time I saw the change, I saw a text box that hovered over the labels explaining the change. It wasn&#039;t annoying like a pop-up box and disappeared when I moved the mouse away. I never saw the context help box again, but I thought that was an interesting and effective way of showing me a new feature/change.</description>
		<content:encoded><![CDATA[<p>I don&#8217;t think quick reference is necessary for all online apps. A quick reference guide for apps with more features and buttons is useful, but something like Twitter where there&#8217;s really only one or two things you do (write an update with less than 140 characters) really does not need a quick reference. </p>
<p>I tend to think of quick reference guides as a something that you refer to frequently when you can&#8217;t remember which keys or buttons or shortcuts to use. If a new user wants to learn to use something for the first time, I think short video tutorials (like what Google Voice and Chrome did) tend to be more effective (for quick starts) than a step-by-step procedural help, but that&#8217;s just my personal opinion. </p>
<p>If Twitter had a short video demoing how to use Twitter, that should be sufficient (again, my opinion). That&#8217;s not to stay that video tutorials should replace text-based documentation. There&#8217;s a need for both, but I do think that the general trend for providing more &#8220;useful&#8221; documentation, especially for online apps should be more contextualized rather than linear. </p>
<p>When Gmail changed how users can label their emails (drag and drop as if labels were &#8220;folders&#8221;), the first time I saw the change, I saw a text box that hovered over the labels explaining the change. It wasn&#8217;t annoying like a pop-up box and disappeared when I moved the mouse away. I never saw the context help box again, but I thought that was an interesting and effective way of showing me a new feature/change.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tom</title>
		<link>http://idratherbewriting.com/2009/06/27/how-google-does-help/comment-page-1/#comment-142565</link>
		<dc:creator>Tom</dc:creator>
		<pubDate>Tue, 28 Jul 2009 05:09:16 +0000</pubDate>
		<guid isPermaLink="false">http://www.idratherbewriting.com/?p=3916#comment-142565</guid>
		<description>Susan, thanks for sharing your feedback and thoughts on Google&#039;s help. It&#039;s nice to see someone concur with some of my points. I think the quick reference guides for online apps should be a must-have deliverable for every app, no matter how seemingly simple. My father recently joined Twitter. After signing up, he said Now what? He wasn&#039;t sure where to go. I can hardly believe that a service like that doesn&#039;t have a clear quick reference guide. A tech writer who wanted to create volunteer quick reference guides to fill in the gaps could gain a lot of visibility doing this sort of thing.</description>
		<content:encoded><![CDATA[<p>Susan, thanks for sharing your feedback and thoughts on Google&#8217;s help. It&#8217;s nice to see someone concur with some of my points. I think the quick reference guides for online apps should be a must-have deliverable for every app, no matter how seemingly simple. My father recently joined Twitter. After signing up, he said Now what? He wasn&#8217;t sure where to go. I can hardly believe that a service like that doesn&#8217;t have a clear quick reference guide. A tech writer who wanted to create volunteer quick reference guides to fill in the gaps could gain a lot of visibility doing this sort of thing.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Susan Wu</title>
		<link>http://idratherbewriting.com/2009/06/27/how-google-does-help/comment-page-1/#comment-142533</link>
		<dc:creator>Susan Wu</dc:creator>
		<pubDate>Mon, 27 Jul 2009 08:18:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.idratherbewriting.com/?p=3916#comment-142533</guid>
		<description>Google Voice documentation is very different from &lt;a href=&quot;http://www.shanghaitechwriter.com/2008/09/09/technical-writing-at-google/&quot;&gt;Chrome documentation&lt;/a&gt; which I wrote about last year.

I got my Google Voice number several few weeks ago and was going through Google Voice page to learn the basics. I also found it strange that all the videos are housed in the &quot;About&quot; page while text help is in a different location altogether (without any videos). 

Also, previously, I didn&#039;t think Google needed any documentation in print format because all its products are web-based. Most Google applications have intuitive UIs and are pretty user-friendly. Google&#039;s online help systems are usually organized by topic/task, which I think is sufficient enough for most users. There&#039;s really no need for a printed/linear manual.

However, after using Google Voice, I find that I keep forgetting which buttons and numbers to push to perform certain tasks. I have to go online to search the help system. It would be great if there was a printed quick reference guide that I can keep near the phone.</description>
		<content:encoded><![CDATA[<p>Google Voice documentation is very different from <a href="http://www.shanghaitechwriter.com/2008/09/09/technical-writing-at-google/">Chrome documentation</a> which I wrote about last year.</p>
<p>I got my Google Voice number several few weeks ago and was going through Google Voice page to learn the basics. I also found it strange that all the videos are housed in the &#8220;About&#8221; page while text help is in a different location altogether (without any videos). </p>
<p>Also, previously, I didn&#8217;t think Google needed any documentation in print format because all its products are web-based. Most Google applications have intuitive UIs and are pretty user-friendly. Google&#8217;s online help systems are usually organized by topic/task, which I think is sufficient enough for most users. There&#8217;s really no need for a printed/linear manual.</p>
<p>However, after using Google Voice, I find that I keep forgetting which buttons and numbers to push to perform certain tasks. I have to go online to search the help system. It would be great if there was a printed quick reference guide that I can keep near the phone.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ellis Pratt</title>
		<link>http://idratherbewriting.com/2009/06/27/how-google-does-help/comment-page-1/#comment-141933</link>
		<dc:creator>Ellis Pratt</dc:creator>
		<pubDate>Fri, 03 Jul 2009 07:38:33 +0000</pubDate>
		<guid isPermaLink="false">http://www.idratherbewriting.com/?p=3916#comment-141933</guid>
		<description>This is very much in the style of the CommonCraft videos. CommonCraft has created a number of videos for various applications (such as on Twitter and on wikis). I think CommonCraft&#039;s Lee LeFever has written some articles on the strength and weaknesses of this approach - might be worth a look.</description>
		<content:encoded><![CDATA[<p>This is very much in the style of the CommonCraft videos. CommonCraft has created a number of videos for various applications (such as on Twitter and on wikis). I think CommonCraft&#8217;s Lee LeFever has written some articles on the strength and weaknesses of this approach &#8211; might be worth a look.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: hair extensions london</title>
		<link>http://idratherbewriting.com/2009/06/27/how-google-does-help/comment-page-1/#comment-141779</link>
		<dc:creator>hair extensions london</dc:creator>
		<pubDate>Sun, 28 Jun 2009 18:09:20 +0000</pubDate>
		<guid isPermaLink="false">http://www.idratherbewriting.com/?p=3916#comment-141779</guid>
		<description>if only their were more quality websites like yours on the internet, please keep up the good work.</description>
		<content:encoded><![CDATA[<p>if only their were more quality websites like yours on the internet, please keep up the good work.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: scottnesbitt's status on Sunday, 28-Jun-09 13:29:28 UTC - Identi.ca</title>
		<link>http://idratherbewriting.com/2009/06/27/how-google-does-help/comment-page-1/#comment-141774</link>
		<dc:creator>scottnesbitt's status on Sunday, 28-Jun-09 13:29:28 UTC - Identi.ca</dc:creator>
		<pubDate>Sun, 28 Jun 2009 13:29:36 +0000</pubDate>
		<guid isPermaLink="false">http://www.idratherbewriting.com/?p=3916#comment-141774</guid>
		<description>[...] Google does help - http://is.gd/1gYfw [...]</description>
		<content:encoded><![CDATA[<p>[...] Google does help &#8211; <a href="http://is.gd/1gYfw" rel="nofollow">http://is.gd/1gYfw</a> [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anna H.</title>
		<link>http://idratherbewriting.com/2009/06/27/how-google-does-help/comment-page-1/#comment-141771</link>
		<dc:creator>Anna H.</dc:creator>
		<pubDate>Sun, 28 Jun 2009 10:16:20 +0000</pubDate>
		<guid isPermaLink="false">http://www.idratherbewriting.com/?p=3916#comment-141771</guid>
		<description>Hey Tom, 
Great post. 
Seems strange that they would be so inconsistent. I would say it&#039;s may actually be a part of their strategy. 
Did you ever see the Google Chrome comic (http://www.google.com/googlebooks/chrome/). I recently had a discussion with my team about this, and we decided such a thing works well for them as an overview/intro type of thing. 
Similarily, I think you have concluded their Voice help - intro is neat, and eye-catching while the rest is sort of unrelated and secondary. 
Plus, it&#039;s all on-line, not really printer friendly.
Do the apps&#039; usability make up for that?
Cheers, 
A.</description>
		<content:encoded><![CDATA[<p>Hey Tom,<br />
Great post.<br />
Seems strange that they would be so inconsistent. I would say it&#8217;s may actually be a part of their strategy.<br />
Did you ever see the Google Chrome comic (<a href="http://www.google.com/googlebooks/chrome/" rel="nofollow">http://www.google.com/googlebooks/chrome/</a>). I recently had a discussion with my team about this, and we decided such a thing works well for them as an overview/intro type of thing.<br />
Similarily, I think you have concluded their Voice help &#8211; intro is neat, and eye-catching while the rest is sort of unrelated and secondary.<br />
Plus, it&#8217;s all on-line, not really printer friendly.<br />
Do the apps&#8217; usability make up for that?<br />
Cheers,<br />
A.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

