<?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: Lessons Learned with Quick Reference Guides: Timing and Truth</title>
	<atom:link href="http://idratherbewriting.com/2009/02/26/lessons-learned-with-quick-reference-guides-timing-and-information-flux/feed/" rel="self" type="application/rss+xml" />
	<link>http://idratherbewriting.com/2009/02/26/lessons-learned-with-quick-reference-guides-timing-and-information-flux/</link>
	<description>The Latest Trends in Technical Communication</description>
	<lastBuildDate>Sat, 26 May 2012 12:14:26 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
	<item>
		<title>By: Jonn</title>
		<link>http://idratherbewriting.com/2009/02/26/lessons-learned-with-quick-reference-guides-timing-and-information-flux/comment-page-1/#comment-147928</link>
		<dc:creator>Jonn</dc:creator>
		<pubDate>Tue, 12 Jan 2010 21:02:59 +0000</pubDate>
		<guid isPermaLink="false">http://www.idratherbewriting.com/?p=3042#comment-147928</guid>
		<description>Tom,

Thanks for this article, as well as all the others relating to Quick Reference materials. I would love to see a technical writing book from you as well, you&#039;ve helped me quite a bit!

Cheers!</description>
		<content:encoded><![CDATA[<p>Tom,</p>
<p>Thanks for this article, as well as all the others relating to Quick Reference materials. I would love to see a technical writing book from you as well, you&#8217;ve helped me quite a bit!</p>
<p>Cheers!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ben</title>
		<link>http://idratherbewriting.com/2009/02/26/lessons-learned-with-quick-reference-guides-timing-and-information-flux/comment-page-1/#comment-138101</link>
		<dc:creator>Ben</dc:creator>
		<pubDate>Wed, 04 Mar 2009 16:05:03 +0000</pubDate>
		<guid isPermaLink="false">http://www.idratherbewriting.com/?p=3042#comment-138101</guid>
		<description>I think the issues you discussed also speak to the importance of not relying solely on the designers and prototypes, but to also get into test versions of the system yourself and exercise it so that you know firsthand what the app actually does, not just what it was designed to do. The users are concerned with what it does, not what the designer wanted it to do, anyway.</description>
		<content:encoded><![CDATA[<p>I think the issues you discussed also speak to the importance of not relying solely on the designers and prototypes, but to also get into test versions of the system yourself and exercise it so that you know firsthand what the app actually does, not just what it was designed to do. The users are concerned with what it does, not what the designer wanted it to do, anyway.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tom</title>
		<link>http://idratherbewriting.com/2009/02/26/lessons-learned-with-quick-reference-guides-timing-and-information-flux/comment-page-1/#comment-138083</link>
		<dc:creator>Tom</dc:creator>
		<pubDate>Wed, 04 Mar 2009 07:24:36 +0000</pubDate>
		<guid isPermaLink="false">http://www.idratherbewriting.com/?p=3042#comment-138083</guid>
		<description>Josh, thanks for dropping by my site and leaving a comment. I was thinking about your suggestion to write a textbook. It would be a great idea, if I could either find the time or land a really cushy book deal with an advance to make it worthwhile. With the quick reference guide format, I&#039;m still learning quite a bit. There&#039;s a lot to know about information design. Overall, though, for students who want to learn some design skills, this is an excellent assignment for them because it&#039;s relatively short and you can easily tell good quick reference guides from poor ones. I usually flip through magazines looking for designs that catch my eye. The people who lay out magazines usually know what they&#039;re doing. 

Also, thanks for commenting on the jane-frustration video. We do have plans to go out this Friday.</description>
		<content:encoded><![CDATA[<p>Josh, thanks for dropping by my site and leaving a comment. I was thinking about your suggestion to write a textbook. It would be a great idea, if I could either find the time or land a really cushy book deal with an advance to make it worthwhile. With the quick reference guide format, I&#8217;m still learning quite a bit. There&#8217;s a lot to know about information design. Overall, though, for students who want to learn some design skills, this is an excellent assignment for them because it&#8217;s relatively short and you can easily tell good quick reference guides from poor ones. I usually flip through magazines looking for designs that catch my eye. The people who lay out magazines usually know what they&#8217;re doing. </p>
<p>Also, thanks for commenting on the jane-frustration video. We do have plans to go out this Friday.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Josh</title>
		<link>http://idratherbewriting.com/2009/02/26/lessons-learned-with-quick-reference-guides-timing-and-information-flux/comment-page-1/#comment-138063</link>
		<dc:creator>Josh</dc:creator>
		<pubDate>Tue, 03 Mar 2009 16:11:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.idratherbewriting.com/?p=3042#comment-138063</guid>
		<description>Tom - today in my technical writing class, I&#039;m introducing quick reference guides.  I&#039;m making the above post as well as &quot;Quick Reference Guide Formats — Tips for Finding Attractive Layouts&quot; and &quot;Quick Reference Guides: The Poetry of Technical Writing&quot; assigned reading.  

Have you considered writing a technical writing textbook?  Most of the ones on the market address non-English majors who are taking some kind of advanced composition class, not aspiring technical writers who plan on writing as a career.  

Most of today&#039;s technical writing textbooks won&#039;t even mention quick reference guides, usability testing, or the progression of documents through a department.  I&#039;ve been teaching college technical writing for five years, and I&#039;ve yet to find a textbook that addresses future technical writers as its primary audience.  Instead, they all seem to address nursing majors and business majors and construction management majors who might have to do a little writing someday.

I, along with hundreds of technical writing teachers, would jump all over a decent textbook for future technical writers.</description>
		<content:encoded><![CDATA[<p>Tom &#8211; today in my technical writing class, I&#8217;m introducing quick reference guides.  I&#8217;m making the above post as well as &#8220;Quick Reference Guide Formats — Tips for Finding Attractive Layouts&#8221; and &#8220;Quick Reference Guides: The Poetry of Technical Writing&#8221; assigned reading.  </p>
<p>Have you considered writing a technical writing textbook?  Most of the ones on the market address non-English majors who are taking some kind of advanced composition class, not aspiring technical writers who plan on writing as a career.  </p>
<p>Most of today&#8217;s technical writing textbooks won&#8217;t even mention quick reference guides, usability testing, or the progression of documents through a department.  I&#8217;ve been teaching college technical writing for five years, and I&#8217;ve yet to find a textbook that addresses future technical writers as its primary audience.  Instead, they all seem to address nursing majors and business majors and construction management majors who might have to do a little writing someday.</p>
<p>I, along with hundreds of technical writing teachers, would jump all over a decent textbook for future technical writers.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tip for technical writers: do the &#8216;designy&#8217; stuff last &#124; Orion Spur</title>
		<link>http://idratherbewriting.com/2009/02/26/lessons-learned-with-quick-reference-guides-timing-and-information-flux/comment-page-1/#comment-138034</link>
		<dc:creator>Tip for technical writers: do the &#8216;designy&#8217; stuff last &#124; Orion Spur</dc:creator>
		<pubDate>Mon, 02 Mar 2009 16:00:18 +0000</pubDate>
		<guid isPermaLink="false">http://www.idratherbewriting.com/?p=3042#comment-138034</guid>
		<description>[...] Lessons Learned with Quick Reference Guides: Timing and Truth &#124; I&#8217;d Rather Be Writing - Tom Jo... [...]</description>
		<content:encoded><![CDATA[<p>[...] Lessons Learned with Quick Reference Guides: Timing and Truth | I&#8217;d Rather Be Writing &#8211; Tom Jo&#8230; [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Links am Montag - Doku-Hotline - Birgit Grossmann über Texte, Technik und technische Dokumentation</title>
		<link>http://idratherbewriting.com/2009/02/26/lessons-learned-with-quick-reference-guides-timing-and-information-flux/comment-page-1/#comment-138024</link>
		<dc:creator>Links am Montag - Doku-Hotline - Birgit Grossmann über Texte, Technik und technische Dokumentation</dc:creator>
		<pubDate>Mon, 02 Mar 2009 06:36:33 +0000</pubDate>
		<guid isPermaLink="false">http://www.idratherbewriting.com/?p=3042#comment-138024</guid>
		<description>[...] Aus dem Leben eines Techwriters: Lessons Learned with Quick Reference Guides: Timing and Truth [...]</description>
		<content:encoded><![CDATA[<p>[...] Aus dem Leben eines Techwriters: Lessons Learned with Quick Reference Guides: Timing and Truth [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tom</title>
		<link>http://idratherbewriting.com/2009/02/26/lessons-learned-with-quick-reference-guides-timing-and-information-flux/comment-page-1/#comment-138009</link>
		<dc:creator>Tom</dc:creator>
		<pubDate>Sun, 01 Mar 2009 21:58:49 +0000</pubDate>
		<guid isPermaLink="false">http://www.idratherbewriting.com/?p=3042#comment-138009</guid>
		<description>Thanks for commenting, Ed. I usually do single source my content when I start in Flare. The problem is, the layout for the two-page content in Indesign is usually so highly formatted and visual that it&#039;s hard to use the same content as the online help, but that&#039;s something I&#039;m definitely moving towards. Thanks.</description>
		<content:encoded><![CDATA[<p>Thanks for commenting, Ed. I usually do single source my content when I start in Flare. The problem is, the layout for the two-page content in Indesign is usually so highly formatted and visual that it&#8217;s hard to use the same content as the online help, but that&#8217;s something I&#8217;m definitely moving towards. Thanks.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ed</title>
		<link>http://idratherbewriting.com/2009/02/26/lessons-learned-with-quick-reference-guides-timing-and-information-flux/comment-page-1/#comment-137983</link>
		<dc:creator>Ed</dc:creator>
		<pubDate>Sun, 01 Mar 2009 00:32:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.idratherbewriting.com/?p=3042#comment-137983</guid>
		<description>Sounds like a lot of work (and long hours). Next time, consider single-sourcing. Then, when the content changes (and we all know it will), at least you&#039;ll only have to update it in one place. I&#039;ve never used Indesign, so I don&#039;t know off the top of my head how it would work in a single-sourcing workflow, but you don&#039;t have to use anything expensive and complex to do it--a simple Access database and a few Word files would do the trick, depending on your needs and resources.

Right now at work, we&#039;re producing technical manuals and associated quick-reference cards for two products. We use FrameMaker and a few utilities for ouput into different formats. We maintain one set of source files for each product and we&#039;ve set up the topics that will appear in both the technical manuals and the quick-reference cards as text insets. When we need to produce each output, we just switch templates and produce output in whichever format we need. Easy cheesy.</description>
		<content:encoded><![CDATA[<p>Sounds like a lot of work (and long hours). Next time, consider single-sourcing. Then, when the content changes (and we all know it will), at least you&#8217;ll only have to update it in one place. I&#8217;ve never used Indesign, so I don&#8217;t know off the top of my head how it would work in a single-sourcing workflow, but you don&#8217;t have to use anything expensive and complex to do it&#8211;a simple Access database and a few Word files would do the trick, depending on your needs and resources.</p>
<p>Right now at work, we&#8217;re producing technical manuals and associated quick-reference cards for two products. We use FrameMaker and a few utilities for ouput into different formats. We maintain one set of source files for each product and we&#8217;ve set up the topics that will appear in both the technical manuals and the quick-reference cards as text insets. When we need to produce each output, we just switch templates and produce output in whichever format we need. Easy cheesy.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Craig</title>
		<link>http://idratherbewriting.com/2009/02/26/lessons-learned-with-quick-reference-guides-timing-and-information-flux/comment-page-1/#comment-137966</link>
		<dc:creator>Craig</dc:creator>
		<pubDate>Fri, 27 Feb 2009 16:13:22 +0000</pubDate>
		<guid isPermaLink="false">http://www.idratherbewriting.com/?p=3042#comment-137966</guid>
		<description>I&#039;m still in the middle of creating my first quick start guide. It hasn&#039;t been that quick, which nullifies the first word right away! I&#039;ll let you know how it turns out.</description>
		<content:encoded><![CDATA[<p>I&#8217;m still in the middle of creating my first quick start guide. It hasn&#8217;t been that quick, which nullifies the first word right away! I&#8217;ll let you know how it turns out.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Troy</title>
		<link>http://idratherbewriting.com/2009/02/26/lessons-learned-with-quick-reference-guides-timing-and-information-flux/comment-page-1/#comment-137965</link>
		<dc:creator>Troy</dc:creator>
		<pubDate>Fri, 27 Feb 2009 16:09:51 +0000</pubDate>
		<guid isPermaLink="false">http://www.idratherbewriting.com/?p=3042#comment-137965</guid>
		<description>I&#039;d say that another important lesson I&#039;ve learned from quick start guides is always, always, discuss scope at the beginning. I&#039;ve had a number of quick start guides turn into to actual help files because each stakeholder wanted their own stuff in the document.

On another note, did you consider a video tutorial/screencast for this type of information?</description>
		<content:encoded><![CDATA[<p>I&#8217;d say that another important lesson I&#8217;ve learned from quick start guides is always, always, discuss scope at the beginning. I&#8217;ve had a number of quick start guides turn into to actual help files because each stakeholder wanted their own stuff in the document.</p>
<p>On another note, did you consider a video tutorial/screencast for this type of information?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

