<?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>Writing to Get Things Done (WGTD)</title>
	<atom:link href="http://wgtdblog.com/feed/" rel="self" type="application/rss+xml" />
	<link>http://wgtdblog.com</link>
	<description>Solve Problems, Meet Deadlines, Keep Projects on Target</description>
	<lastBuildDate>Thu, 07 Oct 2010 15:52:51 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
		<item>
		<title>The Hidden Value of Writing Lists in Parallel Structure</title>
		<link>http://wgtdblog.com/the-hidden-value-of-writing-lists-in-parallel-structure/</link>
		<comments>http://wgtdblog.com/the-hidden-value-of-writing-lists-in-parallel-structure/#comments</comments>
		<pubDate>Wed, 01 Sep 2010 19:02:25 +0000</pubDate>
		<dc:creator>Stu Tanquist</dc:creator>
				<category><![CDATA[Present Your Thoughts]]></category>
		<category><![CDATA[grammatical structure]]></category>
		<category><![CDATA[lists]]></category>
		<category><![CDATA[parallel structure]]></category>

		<guid isPermaLink="false">http://wgtdblog.com/?p=806</guid>
		<description><![CDATA[<p>Why Parallel Structure Matters You’re unlikely to be praised for writing lists using parallel structure. Yet fail to do so, and people will take note. It’s easy to recognize lists that are not parallel because they don’t make sense or sound right. As a result, your writing will come across as sloppy and confusing. <span style="color:#777"> . . . &#8594; Read More: <a href="http://wgtdblog.com/the-hidden-value-of-writing-lists-in-parallel-structure/">The Hidden Value of Writing Lists in Parallel Structure</a></span>]]></description>
			<content:encoded><![CDATA[<p><strong>Why Parallel Structure Matters</strong><br />
You’re unlikely to be praised for writing lists using parallel structure. Yet fail to do so, and people will take note. It’s easy to recognize lists that are not parallel because they don’t make sense or sound right. As a result, your writing will come across as sloppy and confusing. Conversely, when each item in your list follows the same grammatical structure, your writing will be easier to read and understand.</p>
<p><strong>An Obvious Example </strong><br />
Consider this list of work responsibilities from a job resume:</p>
<ul>
<li>Designed and developed promotional materials</li>
<li>Processed customer orders</li>
<li>Documented customer complaints</li>
<li>Good team member</li>
</ul>
<p>Notice how the last item in the list breaks the pattern of beginning each statement with an action verb. The problem quickly becomes apparent if you read just the first word of each statement:</p>
<ul>
<li>Designed …</li>
<li>Processed …</li>
<li>Documented …</li>
<li>Good …</li>
</ul>
<p>The last item disrupts the flow of the list and feels out of place. This seemingly subtle inconsistency can detract readers from the importance of your message.</p>
<p><strong>The Impact on You</strong><br />
Though your readers may not recognize a job well done, they’ll be quick to notice irregularities in your writing, which can reflect on you and your professionalism. When writing lists, ensure that each item follows the same grammatical form. This small change can make a big difference in how you’re perceived by others.</p>
]]></content:encoded>
			<wfw:commentRss>http://wgtdblog.com/the-hidden-value-of-writing-lists-in-parallel-structure/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Never Assume Knowledge</title>
		<link>http://wgtdblog.com/never-assume-knowledge/</link>
		<comments>http://wgtdblog.com/never-assume-knowledge/#comments</comments>
		<pubDate>Sun, 22 Aug 2010 13:34:13 +0000</pubDate>
		<dc:creator>Stu Tanquist</dc:creator>
				<category><![CDATA[Present Your Thoughts]]></category>
		<category><![CDATA[multi-step activities]]></category>
		<category><![CDATA[procedure writing]]></category>
		<category><![CDATA[writing procedures]]></category>

		<guid isPermaLink="false">http://wgtdblog.com/?p=789</guid>
		<description><![CDATA[<p>The Problem When writing procedures, a surefire way to create confusion is to assume that your readers can complete multi-step activities without explicit instructions. When you make this assumption, you risk creating confusion, frustration, and inaction. You’ll also burden other employees, subject matter experts, and/or help desk workers with unnecessary questions. This defeats the <span style="color:#777"> . . . &#8594; Read More: <a href="http://wgtdblog.com/never-assume-knowledge/">Never Assume Knowledge</a></span>]]></description>
			<content:encoded><![CDATA[<p><strong>The Problem</strong><br />
When writing procedures, a surefire way to create confusion is to assume that your readers can complete multi-step activities without explicit instructions. When you make this assumption, you risk creating confusion, frustration, and inaction. You’ll also burden other employees, subject matter experts, and/or help desk workers with unnecessary questions. This defeats the purpose of writing procedures. </p>
<p>Consider the following example:<br />
<a href="http://wgtdblog.com/wp-content/uploads/2010/08/never-assume-knowledge.gif"><img src="http://wgtdblog.com/wp-content/uploads/2010/08/never-assume-knowledge.gif" alt="Procedure that illustrates the problem of assuming knowledge" title="Never Assume Knowledge" width="487" height="236" class="aligncenter size-full wp-image-799" /></a><br />
Notice how the last step in this sequence is really a whole bunch of steps. When you consolidate steps, readers tend to become paralyzed with confusion and are therefore unable to continue</p>
<p><strong>Rationale</strong><br />
The key word here is <em>assume</em>. If you know that everyone who will <em>ever </em>follow the procedure can complete a multi-step activity, e.g., every reader is a skilled Access database programmer, you can then consolidate steps. Procedure writers often make unfounded assumptions about the knowledge of their audience. </p>
<p><strong>The Solution</strong><br />
When in doubt, assume that your readers need explicit instructions to complete multi-step activities. Though you’ll invest additional effort on the front-end, your procedure will offer greater long term productivity gains. </p>
]]></content:encoded>
			<wfw:commentRss>http://wgtdblog.com/never-assume-knowledge/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>A Tribute to the Gregg Reference Manual—the gatekeeper of business grammar since the 1950s</title>
		<link>http://wgtdblog.com/a-tribute-to-the-gregg-reference-manual/</link>
		<comments>http://wgtdblog.com/a-tribute-to-the-gregg-reference-manual/#comments</comments>
		<pubDate>Thu, 19 Aug 2010 21:18:55 +0000</pubDate>
		<dc:creator>Stan Berry</dc:creator>
				<category><![CDATA[Miscellaneous]]></category>
		<category><![CDATA[grammar]]></category>
		<category><![CDATA[Gregg Reference Manual]]></category>
		<category><![CDATA[Tribute Edition]]></category>
		<category><![CDATA[William A. Sabin]]></category>

		<guid isPermaLink="false">http://wgtdblog.com/?p=778</guid>
		<description><![CDATA[<p>This is a “hurrah, we’ve been waiting for you” tribute to the new and final edition of The Gregg Reference Manual: A Manual of Style, Grammar, Usage, and Formatting Tribute Edition published in March of 2010. Its coming is bittersweet.</p> <p>William A. Sabin (1931-2009) devoted his life to editing The Gregg Reference Manual (GRM). <span style="color:#777"> . . . &#8594; Read More: <a href="http://wgtdblog.com/a-tribute-to-the-gregg-reference-manual/">A Tribute to the Gregg Reference Manual—the gatekeeper of business grammar since the 1950s</a></span>]]></description>
			<content:encoded><![CDATA[<p>This is a “hurrah, we’ve been waiting for you” tribute to the new and final edition of <em>The Gregg Reference Manual:</em> A Manual of Style, Grammar, Usage, and Formatting Tribute Edition published in March of 2010. Its coming is bittersweet.</p>
<p><a href="http://wgtdblog.com/wp-content/uploads/2010/08/william-a-sabin.jpg"><img src="http://wgtdblog.com/wp-content/uploads/2010/08/william-a-sabin.jpg" alt="William A. Sabin, 1931-2009" title="William A. Sabin, 1931-2009" width="184" height="276" class="alignright size-full wp-image-779" /></a>William A. Sabin (1931-2009) devoted his life to editing <em>The Gregg Reference Manual (GRM)</em>. He finished reviewing the 11th Edition with his daughter, Margaret, from his hospital bed on December 29 and died two days later. </p>
<p>GRM has been the gatekeeper of business grammar for over 50 years. First published by John Robert Gregg in 1893 as <em>Gregg Shorthand</em> and later published as the <em>Reference Manual for Stenographers and Typists</em> in 1951, it became the choice of grammar reference used by typing pools—the last guard at the gate of correct business grammar—in corporate word processing departments. Bill Sabin became the sole author in the early 70s and changed the name to <em>The Gregg Reference Manual</em>, 5th Edition, in 1977.</p>
<p>As business professionals began using computers to type their own documents, <em>The Gregg Reference Manual </em>was passed from word processing departments to workstations across America. It has provided thoughtful analysis and clear direction on grammar usage ever since.</p>
<p>There are many good reasons for its popularity over the years: </p>
<ul>
<li>It’s current with revised editions published every 5-6 years. </li>
<li>The Table of Contents, Index and page layout make it easy to use. </li>
<li>It’s clearly written with many examples as backup. </li>
<li>It’s a joy to read. Sabin made GRM his life-long, daily expression of love for grammar and usage. You can easily see this love in his prose throughout the book, but it’s especially visible in his passionate <em>Essays on the Nature of Style</em>. My favorites are “The Comma Trauma,” “The Plight of the Compound Adjective&#8211;Or Where Have All the Hyphens Gone?” and “The Semicolon; And Other Myths.”</li>
<li>It’s honest.  Bill’s famous posture in matters of grammar: “It’s correct, lady, but it ain’t  right.”  While earning two degrees in English from Yale University, Bill was no pedantic follower of esoteric rules.  He was great for laying out the rules and then encouraging writers to follow their instincts. What is more brilliant, beautiful and right?</li>
</ul>
<p>I was not surprised to learn that Marie, his beloved wife of 50+ years, found one of Bill’s passwords soon after his death: “I love GRM.”  How fitting!  Millions of us have used GRM as a password into a world of succinct answers to sometimes confusing or controversial grammar issues. </p>
<p>Thank you, Mr. Sabin, for sharing your love of language and being a guiding light for all these years! We love you, too.<br />
<a href="http://wgtdblog.com/wp-content/uploads/2010/08/gregg-reference-manual.jpg"><img src="http://wgtdblog.com/wp-content/uploads/2010/08/gregg-reference-manual.jpg" alt="Gregg Reference Manual Book Covers" title="Gregg Reference Manual Book Covers" width="553" height="246" class="aligncenter size-full wp-image-780" /></a></p>
]]></content:encoded>
			<wfw:commentRss>http://wgtdblog.com/a-tribute-to-the-gregg-reference-manual/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>White Space – How to Make Something from Nothing</title>
		<link>http://wgtdblog.com/white-space-%e2%80%93-make-something-from-nothing/</link>
		<comments>http://wgtdblog.com/white-space-%e2%80%93-make-something-from-nothing/#comments</comments>
		<pubDate>Wed, 18 Aug 2010 20:51:43 +0000</pubDate>
		<dc:creator>Stu Tanquist</dc:creator>
				<category><![CDATA[Present Your Thoughts]]></category>
		<category><![CDATA[confusion]]></category>
		<category><![CDATA[procedures]]></category>
		<category><![CDATA[productivity]]></category>
		<category><![CDATA[readability]]></category>
		<category><![CDATA[white space]]></category>

		<guid isPermaLink="false">http://wgtdblog.com/?p=765</guid>
		<description><![CDATA[<p>It Works Like Magic When writing procedures, an ample use of white space can transform a cluttered confusing mess into a beautiful set of instructions. By increasing the readability (reading ease) of your procedures, you reduce confusion which helps your readers be more productive. The simple step of adding nothing (empty space) can magically <span style="color:#777"> . . . &#8594; Read More: <a href="http://wgtdblog.com/white-space-%e2%80%93-make-something-from-nothing/">White Space – How to Make Something from Nothing</a></span>]]></description>
			<content:encoded><![CDATA[<p><strong>It Works Like Magic</strong><br />
When writing procedures, an ample use of white space can transform a cluttered confusing mess into a beautiful set of instructions. By increasing the readability (reading ease) of your procedures, you reduce confusion which helps your readers be more productive. The simple step of adding nothing (empty space) can magically create something (greater productivity).  </p>
<p><a href="http://wgtdblog.com/wp-content/uploads/2010/08/procedures-confusion-productivity.jpg"><img src="http://wgtdblog.com/wp-content/uploads/2010/08/procedures-confusion-productivity.jpg" alt="Procedures - Confusion vs. Productivity" title="Procedures - Confusion vs. Productivity" width="500" height="286" class="aligncenter size-full wp-image-768" /></a><br />
<strong>White Space is Not Wasted Space</strong><br />
White space is like a pause in conversation – it gives your eyes a place to rest. As in conversation, it’s good to take a breath now and then. White space makes the page inviting and pleasurable to the eye so readers don’t become overwhelmed. As a result, your instructions will be easier to understand, remember, and apply. </p>
<p>Consider the following examples:</p>
<div style="padding-left: 35px;">
<strong><em>Before</em></strong><br />
Here’s how to use keyboard shortcuts to copy and paste text within or between documents (Windows computers). First, position your cursor at the beginning of the text that you want to copy. Next, highlight a block of text by holding down the <em>Shift </em>key while pressing the <em>Down </em>and/or <em>Right Arrow </em>keys. You can then copy the highlighted text to the Windows clipboard by holding down the Control key while pressing the letter <em>C</em> (there will be <em>no</em> indication that anything happened). Next, position your cursor where you would like to copy the text. Finally, paste the copied text by holding down the <em>Control </em>key while pressing the letter <em>V</em>. </p>
<p><strong><em>After</em></strong><br />
Here’s how to use keyboard shortcuts to copy and paste text within or between documents (Windows computers):</p>
<ol>
<li>Position your cursor at the beginning of the text that you want to copy</li>
<li>Highlight a block of text by holding down the <em>Shift </em>key while pressing the <em>Down </em>and/or <em>Right Arrow </em>keys</li>
<li>Copy the highlighted text to the Windows clipboard by holding down the <em>Control </em>key while pressing the letter <em>C</em> (there will be <em>no</em> indication that anything happened)</li>
<li>Position your cursor where you want to copy the text</li>
<li>Paste the copied text by holding down the <em>Control </em>key while pressing the letter <em>V</em></li>
</ol>
</div>
<p>Notice how ordering this procedure under a forecasting sentence adds white space to the left margin and gives your eyes a welcome rest after each step. Though commonly used, a procedure in paragraph format is hard to follow. Which would you rather read? </p>
<p><strong>Make it Easy for Your Readers</strong><br />
Remembering that we read from left to right and top to bottom, you can help your readers by adding white space in both directions. Ample side margins and indents make it easier to read left to right, while spacing between lines and paragraphs creates a comfortable flow from top to bottom. Don’t feel constrained by standard margin and paragraph settings. Procedures need more white space—often much more. </p>
<p><strong>It’s All About Balance</strong><br />
The key to the effective use of white space is balance. Too little white space makes a page look busy and uninviting. Add too much and your page will appear desolate with questionable value. </p>
<p>When in doubt, add more white space and then step back to view the page as a whole. If it looks clean and inviting, you may just have made something from nothing.  </p>
]]></content:encoded>
			<wfw:commentRss>http://wgtdblog.com/white-space-%e2%80%93-make-something-from-nothing/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Free Practical Grammar Resource</title>
		<link>http://wgtdblog.com/free-practical-grammar-resource/</link>
		<comments>http://wgtdblog.com/free-practical-grammar-resource/#comments</comments>
		<pubDate>Tue, 17 Aug 2010 16:51:00 +0000</pubDate>
		<dc:creator>Stu Tanquist</dc:creator>
				<category><![CDATA[Use the Language of WGTD]]></category>
		<category><![CDATA[grammar]]></category>
		<category><![CDATA[grammar resource]]></category>

		<guid isPermaLink="false">http://wgtdblog.com/?p=758</guid>
		<description><![CDATA[<p>Getting quick answers to grammar-related questions can be a challenge. Here’s a great free online resource called Common Errors in English Usage by Paul Brians. Brians is an Emeritus Professor of English at Washington State University- http://www.wsu.edu/~brians/errors/errors.html </p> <p>Many grammar guides offer lengthy convoluted descriptions of grammar rules. I especially like this one because <span style="color:#777"> . . . &#8594; Read More: <a href="http://wgtdblog.com/free-practical-grammar-resource/">Free Practical Grammar Resource</a></span>]]></description>
			<content:encoded><![CDATA[<p>Getting quick answers to grammar-related questions can be a challenge. Here’s a great free online resource called <em>Common Errors in English Usage</em> by Paul Brians. Brians is an Emeritus Professor of English at Washington State University- <a href="http://www.wsu.edu/~brians/errors/errors.html">http://www.wsu.edu/~brians/errors/errors.html</a> </p>
<p><a href="http://wgtdblog.com/wp-content/uploads/2010/08/common-errors-website.gif"><img src="http://wgtdblog.com/wp-content/uploads/2010/08/common-errors-website.gif" alt="Common Errors in English Usage - Screenshot" title="Common Errors in English Usage - Screenshot" width="500" height="185" class="aligncenter size-full wp-image-804" /></a>Many grammar guides offer lengthy convoluted descriptions of grammar rules. I especially like this one because of its practical nature. If you have a question about, say, using semicolons, use the search engine or click the letter “S” and you’ll find a concise explanation of how and when to use semicolons. </p>
<p>This is a helpful link for times when grammar questions arise. Near the bottom of the home page are links to additional online grammar resources recommended by the author. </p>
]]></content:encoded>
			<wfw:commentRss>http://wgtdblog.com/free-practical-grammar-resource/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Choosing Who or Whom with Confidence is as Easy as 1, 2, 3.</title>
		<link>http://wgtdblog.com/choosing-who-or-whom-with-confidence/</link>
		<comments>http://wgtdblog.com/choosing-who-or-whom-with-confidence/#comments</comments>
		<pubDate>Tue, 10 Aug 2010 19:09:12 +0000</pubDate>
		<dc:creator>Stan Berry</dc:creator>
				<category><![CDATA[Use the Language of WGTD]]></category>
		<category><![CDATA[grammar]]></category>
		<category><![CDATA[who]]></category>
		<category><![CDATA[whom]]></category>

		<guid isPermaLink="false">http://wgtdblog.com/?p=744</guid>
		<description><![CDATA[<p>The Hard Way The correct use of who and whom, like all personal pronouns, depends on how the pronoun functions in the sentence. Pronouns either function as the subject of the verb or the object of the verb. The difficulty of who and whom, unlike other personal pronouns, is that it’s not easy to <span style="color:#777"> . . . &#8594; Read More: <a href="http://wgtdblog.com/choosing-who-or-whom-with-confidence/">Choosing Who or Whom with Confidence is as Easy as 1, 2, 3.</a></span>]]></description>
			<content:encoded><![CDATA[<p><strong>The Hard Way</strong><br />
The correct use of <em>who </em>and <em>whom</em>, like all personal pronouns, depends on how the pronoun functions in the sentence.  Pronouns either function as the subject of the verb or the object of the verb.  The difficulty of who and whom, unlike other personal pronouns, is that it’s not easy to see how who or whom functions.</p>
<p><strong>The Easy Way</strong><br />
By using a three-step process you can avoid the need to understand all this grammar jargon in the previous paragraph.  Let’s use this example to see how this process works:</p>
<p><em>Intelligent citizens will vote for whoever they think is best qualified.</em></p>
<div style="padding-left: 20px;">
<strong><em>Here are the three simple steps:</em></strong></p>
<div style="padding-left: 20px;">
<em>Step 1. </em>Begin with the words that follow who or whom to find the gap. With our example, we’d be left with:</p>
<p style="display: block;">
<div style="padding-left: 35px;">
they think is best qualified.
</div>
<p><em>Step 2. </em>Plug the gap with either he/she or him/her, whichever one makes sense, and we get:</p>
<div style="padding-left: 35px;">
they think he is best qualified.
</div>
<p><em>Step 3. </em>Use a simple substitution:</p>
<div style="padding-left: 35px;">
he/she = who<br />
him/her = whom
</div>
</div>
</div>
]]></content:encoded>
			<wfw:commentRss>http://wgtdblog.com/choosing-who-or-whom-with-confidence/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Cumulative Return on Investment (ROI)</title>
		<link>http://wgtdblog.com/cumulative-return-on-investment/</link>
		<comments>http://wgtdblog.com/cumulative-return-on-investment/#comments</comments>
		<pubDate>Thu, 05 Aug 2010 10:10:53 +0000</pubDate>
		<dc:creator>Stu Tanquist</dc:creator>
				<category><![CDATA[Present Your Thoughts]]></category>
		<category><![CDATA[easy-to-follow instructions]]></category>
		<category><![CDATA[procedure writing]]></category>
		<category><![CDATA[return on investment]]></category>
		<category><![CDATA[ROI]]></category>
		<category><![CDATA[writing procedures]]></category>

		<guid isPermaLink="false">http://wgtdblog.com/?p=704</guid>
		<description><![CDATA[<p>A Small Investment Now Well written procedures (instructions) are worth their weight in gold, so to speak. Think about it. A single set of instructions can be used over and over by dozens, hundreds, or even thousands of employees (or customers) over a period of many years, with no additional effort or expense. By <span style="color:#777"> . . . &#8594; Read More: <a href="http://wgtdblog.com/cumulative-return-on-investment/">Cumulative Return on Investment (ROI)</a></span>]]></description>
			<content:encoded><![CDATA[<p><strong>A Small Investment Now</strong><br />
Well written procedures (instructions) are worth their weight in gold, so to speak. Think about it. A single set of instructions can be used over and over by dozens, hundreds, or even thousands of employees (or customers) over a period of many years, with no additional effort or expense. By quickly and efficiently completing the task at hand, they can then focus on other priorities, i.e., get things done. </p>
<p>Writing clear easy-to-follow instructions is a skill that anyone can learn and master. Few activities offer such a spectacular Return on Investment (ROI). </p>
<div id="attachment_705" class="wp-caption aligncenter" style="width: 520px"><a href="http://wgtdblog.com/wp-content/uploads/2010/08/procedure-writing-roi.jpg"><img src="http://wgtdblog.com/wp-content/uploads/2010/08/procedure-writing-roi.jpg" alt="Procedure Writing is a Wise Investment (ROI)" title="Procedure Writing is a Wise Investment (ROI)" width="510" height="318" class="size-full wp-image-705" /></a><p class="wp-caption-text">Photo used under Creative Commons from <a href="http://www.flickr.com/photos/neilt/75212042/" target="_blank">Neil T</a></p></div>
<p><strong>The Hidden Cost of Confusion</strong><br />
Conversely, poorly written procedures create a huge drain on productivity. Confused readers waste time through trial and error, searching online for better instructions, and troubling other busy employees, subject matter experts, and help desks. Though cumulative productivity losses can be staggering, they are often hidden and difficult to quantify.  </p>
<p><strong>Great Things to Come</strong><br />
In the coming weeks we’ll provide a number of instructional posts on how to write clear, easy-to-follow instructions, using key principles from our <a href="http://wgtdblog.com/procedure-writing-seminar/">Writing and Polishing Effective Procedures</a> seminar. Become skilled in the art of writing effective procedures and you’ll generate an impressive ROI every time.  </p>
]]></content:encoded>
			<wfw:commentRss>http://wgtdblog.com/cumulative-return-on-investment/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>With Procedure Writing, Point of View is Everything</title>
		<link>http://wgtdblog.com/procedure-writing-point-of-view-is-everything/</link>
		<comments>http://wgtdblog.com/procedure-writing-point-of-view-is-everything/#comments</comments>
		<pubDate>Tue, 03 Aug 2010 16:34:54 +0000</pubDate>
		<dc:creator>Stan Berry</dc:creator>
				<category><![CDATA[Present Your Thoughts]]></category>
		<category><![CDATA[procedure writing]]></category>
		<category><![CDATA[reading as I work]]></category>
		<category><![CDATA[reading for knowledge]]></category>
		<category><![CDATA[writing instructions]]></category>

		<guid isPermaLink="false">http://wgtdblog.com/?p=697</guid>
		<description><![CDATA[<p>An engineer at the United States Norfolk Naval Base asked, “Why are so many procedure manuals impossible to read?”</p> <p>The answer is two-fold. First, most instructions are written from the wrong point of view:</p> Users want a reading as I work viewpoint that answers the simple question, “What do I do next?” (Think recipe <span style="color:#777"> . . . &#8594; Read More: <a href="http://wgtdblog.com/procedure-writing-point-of-view-is-everything/">With Procedure Writing, Point of View is Everything</a></span>]]></description>
			<content:encoded><![CDATA[<p>An engineer at the United States Norfolk Naval Base asked, “Why are so many procedure manuals impossible to read?”</p>
<p>The answer is two-fold.  First, most instructions are written from the wrong point of view:</p>
<ul>
<li>Users want a <em>reading as I work </em>viewpoint that answers the simple question, “What do I do next?”  (Think <em>recipe </em>for making bread.)</li>
<li>Content experts, and their wannabes, write from a <em>reading for knowledge </em>viewpoint.  This answers the complex question, “How does this system work?”  (Think <em>explanation </em>for how yeast interacts with flour.)</li>
</ul>
<p><a href="http://wgtdblog.com/wp-content/uploads/2010/08/reading-for-knowledge-reading-as-work.gif"><img class="aligncenter size-full wp-image-698" title="Reading for Knowledge vs. Reading as I Work" src="http://wgtdblog.com/wp-content/uploads/2010/08/reading-for-knowledge-reading-as-work.gif" alt="Reading for Knowledge vs. Reading as I Work" width="408" height="225" /></a><em>When writing instructions, reading for knowledge </em>viewpoint is the wrong kind of information.  Take this example of motorcycle safety training. Instead of instructing a rider on how to manage the risk of road hazards, the content expert explains the combustion mechanics of a Harley Davidson engine.  This will explain what creates the percussion-rumbling sound, but it won’t help save the rider’s life.</p>
<p>Second, <em>reading for knowledge </em>viewpoint also lends itself into displaying procedures in a paragraph format, like what you find in a textbook. This in turn promotes:</p>
<div style="padding-left: 35px;">passive voice<br />
sequencing errors<br />
missing steps<br />
confusing conditions<br />
ambiguous doers<br />
verbose, technical language.</div>
<p>In short, this document only makes sense to other content experts who can recognize the process buried in the prose!</p>
<p><em>Reading as I work </em>viewpoint makes the organization of the procedure visually apparent to the users. The writer chooses the appropriate format based on the whether the process is linear or non-linear and the juxtaposition of four factors: how many steps, conditions, doers, and screens/forms are interacting within the procedure.</p>
<p><strong>A “reading for knowledge” viewpoint</strong>—not a good idea if you want to get things done!</p>
]]></content:encoded>
			<wfw:commentRss>http://wgtdblog.com/procedure-writing-point-of-view-is-everything/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>How to Write from the Readers’ Perspective</title>
		<link>http://wgtdblog.com/how-to-write-from-the-readers-perspective/</link>
		<comments>http://wgtdblog.com/how-to-write-from-the-readers-perspective/#comments</comments>
		<pubDate>Mon, 02 Aug 2010 06:39:03 +0000</pubDate>
		<dc:creator>Stu Tanquist</dc:creator>
				<category><![CDATA[Present Your Thoughts]]></category>
		<category><![CDATA[effective business writing]]></category>
		<category><![CDATA[the academic model]]></category>
		<category><![CDATA[the readers perspective]]></category>
		<category><![CDATA[WGTD]]></category>

		<guid isPermaLink="false">http://wgtdblog.com/?p=668</guid>
		<description><![CDATA[<p>A Sure Way to Confuse Your Readers In school and throughout our lives, we’ve learned to write using the academic model, i.e., introduction, body, and conclusion. In business writing, this approach greatly limits our ability to get things done.</p> <p>We can think of the academic model as a movie, where the plot gradually builds <span style="color:#777"> . . . &#8594; Read More: <a href="http://wgtdblog.com/how-to-write-from-the-readers-perspective/">How to Write from the Readers’ Perspective</a></span>]]></description>
			<content:encoded><![CDATA[<p><strong>A Sure Way to Confuse Your Readers</strong><br />
In school and throughout our lives, we’ve learned to write using the academic model, i.e., introduction, body, and conclusion. In business writing, this approach greatly limits our ability to get things done.</p>
<p>We can think of the academic model as a movie, where the plot gradually builds before reaching the exciting final conclusion. Communicating background information first works well in the entertainment industry (and in academia). In the fast-paced world of business, it creates confusion, frustration, and inaction.</p>
<h2 style="text-align: center;">The Academic Model</h2>
<div id="attachment_678" class="wp-caption aligncenter" style="width: 528px"><a href="http://wgtdblog.com/wp-content/uploads/2010/08/intro-body-conclusion.jpg"><img class="size-full wp-image-678" title="The Opposite of Effective Business Writing" src="http://wgtdblog.com/wp-content/uploads/2010/08/intro-body-conclusion.jpg" alt="Old Class Photo - The Academic Model: Introduction, Body, Conclusion" width="518" height="378" /></a><p class="wp-caption-text">Photo used under Creative Commons from <a href="http://www.flickr.com/photos/crabchick/2679400373" target="_blank">crabchick</a></p></div>
<p><strong>The Readers’ Perspective</strong><br />
Busy employees don’t have time to wade through background information to uncover your important action item. They have many other pressing priorities, which means they immediately want to know how your email affects them, and whether they have to do anything. The more difficult it is to answer these vital questions, the greater the risk of inaction.</p>
<h2 style="text-align: center;">Writing to Get Things Done (WGTD)</h2>
<p style="text-align: center;"><a href="http://wgtdblog.com/wp-content/uploads/2010/08/academic-model-vs-wgtd.gif"><img class="size-full wp-image-687  aligncenter" title="Writing to Get Things Done (WGTD)" src="http://wgtdblog.com/wp-content/uploads/2010/08/academic-model-vs-wgtd.gif" alt="The Academic Model vs. Writing to Get Things Done (WGTD)" width="511" height="205" /></a></p>
<p><strong>How to Give Your Readers What They Want</strong><br />
When you make it easy for your readers to find the most important part of your message, you do them, and yourself, a favor. Effective business writing is written from the readers’ perspective. To quickly answer their questions, “How does this affect me? Do I have to do anything?” <a href="http://wgtdblog.com/what-you-want-to-get-done-paragraph-one/">put what you want to get done in paragraph one</a>. They’ll love you for it—and you’ll love the results.</p>
]]></content:encoded>
			<wfw:commentRss>http://wgtdblog.com/how-to-write-from-the-readers-perspective/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Get Things Done by Communicating a Sense of Urgency</title>
		<link>http://wgtdblog.com/get-things-done-by-communicating-a-sense-of-urgency/</link>
		<comments>http://wgtdblog.com/get-things-done-by-communicating-a-sense-of-urgency/#comments</comments>
		<pubDate>Fri, 30 Jul 2010 13:23:26 +0000</pubDate>
		<dc:creator>Stu Tanquist</dc:creator>
				<category><![CDATA[Present Your Thoughts]]></category>
		<category><![CDATA[deadline]]></category>
		<category><![CDATA[get things done]]></category>
		<category><![CDATA[sense of urgency]]></category>
		<category><![CDATA[vague closings]]></category>

		<guid isPermaLink="false">http://wgtdblog.com/?p=636</guid>
		<description><![CDATA[<p>Vague Niceties Lead to Inaction When a friend ends an email with a vague statement like, “We should get together sometime.” what happens? Nothing! Until someone offers a more specific suggestion, e.g., “Are you free on Saturday?” any talk about getting together is just a nicety.</p> <p> Business Writing is No Different The same <span style="color:#777"> . . . &#8594; Read More: <a href="http://wgtdblog.com/get-things-done-by-communicating-a-sense-of-urgency/">Get Things Done by Communicating a Sense of Urgency</a></span>]]></description>
			<content:encoded><![CDATA[<p><strong>Vague Niceties Lead to Inaction</strong><br />
When a friend ends an email with a vague statement like, “We should get together sometime.” what happens? Nothing! Until someone offers a more specific suggestion, e.g., “Are you free on Saturday?” any talk about getting together is just a nicety.</p>
<p><a href="http://wgtdblog.com/wp-content/uploads/2010/07/why-most-emails-dont-get-things-done.jpg"><img src="http://wgtdblog.com/wp-content/uploads/2010/07/why-most-emails-dont-get-things-done.jpg" alt="Why Most Emails Don&#039;t Get Things Done" title="Why Most Emails Don&#039;t Get Things Done" width="294" height="276" class="alignright size-full wp-image-650" /></a><br />
<strong>Business Writing is No Different</strong><br />
The same is true in business writing, where <a href="http://wgtdblog.com/avoid-cliches-in-closing-sentence/">vague closings are the norm</a>. For example, if you end an email with the phrase, “Please advise at your earliest convenience.” you&#8217;re asking to have your message placed in their good intention pile. Instead, offer a sense of urgency and a reason for the urgency, using a <a href="http://wgtdblog.com/finesse-with-tone/">tone that encourages cooperation</a>. Consider this example:</p>
<div style="padding-left: 35px;">“Would it be possible to provide your data results by Friday? That will allow the development team enough time to complete their recommendation for senior management.”</div>
<p><strong>A Sense of Urgency Leads to Action</strong><br />
Busy employees are constantly juggling priorities. Vague closings inherently communicate a low priority, and, therefore, offer little hope of meaningful action. Instead, try this: Tactfully suggest a deadline, timeline, or sense of urgency. This one simple change will make a huge difference in your ability to get things done.</p>
]]></content:encoded>
			<wfw:commentRss>http://wgtdblog.com/get-things-done-by-communicating-a-sense-of-urgency/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
