<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Technical Communication Professionals in Southwest Michigan &#124; Prima Communications, Inc. &#187; Reference Manual</title>
	<atom:link href="http://primacommunications.com/tag/reference-manual/feed/" rel="self" type="application/rss+xml" />
	<link>http://primacommunications.com</link>
	<description>Connecting information with the people who need it.</description>
	<lastBuildDate>Thu, 03 Nov 2011 20:34:16 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
		<item>
		<title>What Makes a Smart Doc Smart?</title>
		<link>http://primacommunications.com/2009/04/what-makes-a-smart-doc-smart/</link>
		<comments>http://primacommunications.com/2009/04/what-makes-a-smart-doc-smart/#comments</comments>
		<pubDate>Tue, 14 Apr 2009 11:48:04 +0000</pubDate>
		<dc:creator>Jeremy</dc:creator>
				<category><![CDATA[Documentation & Training]]></category>
		<category><![CDATA[Prima Communications Blog]]></category>
		<category><![CDATA[Checklist]]></category>
		<category><![CDATA[Procedures]]></category>
		<category><![CDATA[Reference Manual]]></category>
		<category><![CDATA[Reformatting]]></category>
		<category><![CDATA[Smart Docs]]></category>
		<category><![CDATA[White space]]></category>

		<guid isPermaLink="false">http://www.primacommunications.com/blog/2009/?p=89</guid>
		<description><![CDATA[I’m sure we can all take a tedious text procedure and make it look better by reformatting, adding graphics, or using white space better. Does that make it a smart doc? I don’t think so. Smart docs require some planning and a lot of thought because they aren’t single pretty documents but a system of [...]]]></description>
			<content:encoded><![CDATA[<p>I’m sure we can all take a tedious text procedure and <a href="http://mindmappingsoftwareblog.com/why-communicate-visually/" target="_blank">make it look better by reformatting, adding graphics, or using white space better</a>. Does that make it a smart doc? I don’t think so.</p>
<p>Smart docs require some planning and a lot of thought because they aren’t single pretty documents but a system of documentation that works together, <a href="http://www.janetswisher.com/?itemid=196" target="_blank">is easy to use, and is rigorously logical</a>. True smart docs can’t be developed in a silo but must be developed with the other documents in the system.</p>
<p>For instance, smart docs don’t repeat information in multiple places unless absolutely necessary. Information goes in the one most logical place. This sometimes requires some thinking about what that most logical place is and sometimes sparks some debate (which can be very healthy and lead to a better solution).</p>
<p>Smart docs also put similar information in similar documents. If information on how to operate a cartoner is in a reference manual, then information on how to operate a labeler is in a reference manual. If setup information is in a checklist on Line 2, then setup information is in a checklist for Line 6. This consistent documentation makes it easier for operators to find the information they need.</p>
<p>It’s not enough to have pretty documents. You need a system of smart docs.</p>
]]></content:encoded>
			<wfw:commentRss>http://primacommunications.com/2009/04/what-makes-a-smart-doc-smart/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

