<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" media="screen" href="/~d/styles/rss2full.xsl"?><?xml-stylesheet type="text/css" media="screen" href="http://feeds.feedburner.com/~d/styles/itemcontent.css"?><rss 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/" xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" version="2.0">

<channel>
	<title>readytext blog</title>
	
	<link>http://readytext.com/blog</link>
	<description>writing about reading and writing</description>
	<lastBuildDate>Wed, 14 Dec 2011 03:27:24 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.6</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="self" type="application/rss+xml" href="http://feeds.feedburner.com/ReadytextBlog" /><feedburner:info uri="readytextblog" /><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="hub" href="http://pubsubhubbub.appspot.com/" /><feedburner:emailServiceId>ReadytextBlog</feedburner:emailServiceId><feedburner:feedburnerHostname>http://feedburner.google.com</feedburner:feedburnerHostname><item>
		<title>Scrabble</title>
		<link>http://feedproxy.google.com/~r/ReadytextBlog/~3/Ixm56AmSRu4/</link>
		<comments>http://readytext.com/blog/2011/12/scrabble/#comments</comments>
		<pubDate>Wed, 14 Dec 2011 02:16:31 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[writing]]></category>

		<guid isPermaLink="false">http://readytext.com/blog/?p=492</guid>
		<description><![CDATA[Scrabble seems such a straightforward game on the face of it, doesn&#8217;t it? Get your letters on the board as quick as you can. A bit like a crossword, except you can make up the words yourself.

But Mr. Butts must have realized that a game as simple as that wouldn&#8217;t create the opportunities to grow [...]]]></description>
			<content:encoded><![CDATA[<p>Scrabble seems such a straightforward game on the face of it, doesn&#8217;t it? Get your letters on the board as quick as you can. A bit like a crossword, except you can make up the words yourself.
</p>
<p>But Mr. Butts must have realized that a game as simple as that wouldn&#8217;t create the opportunities to grow and develop skill that an enduring product requires. (Let&#8217;s not discuss the merits of Mousetrap here – who knows why it&#8217;s still around.)
</p>
<p>Experienced Scrabble players know that it&#8217;s not the words themselves that will win the game – how many letters they have managed to rid themselves of – but the compound interest provided by existing words on the board, and by the bonus spots that double and triple otherwise mediocre scores.
</p>
<p>In this respect, Scrabble provides a model for all us aspiring writers and communicators.  We approach a topic with a bagful of ideas that we need to mesh as productively as possible with existing published information.  All communication is subject to the assumptions around its medium and by other past and current work with which readers will be familiar. This is an opportunity that we can choose to ignore, or to exploit.
</p>
<p>There may be a few hot buttons that we can hit – the triple-word scores that will add extra interest; there are also explicit and implicit references we can make to connect to messages that are already out there, and borrow some of their value.
</p>
<p>A fresh news site can win by providing stories that complete gaps left by mainstream media, perhaps by offering a new or local angle on national and international events. Choices of form, structure, style and vocabulary can bring to mind a fresh point of view borrowed from an unexpected genre.  Writers can exploit the productive effects of intertextual references by engaging with and working against commentary and opinion that their readers are likely to recognize.
</p>
<p>For example, framing an otherwise dry comment on writing within the context of a familiar board game might just work for some. That&#8217;s one key to winning an audience or a Scrabble game: use the leverage provided by the context you&#8217;re working in to add value to your message.
</p>
<p><img src="http://readytext.com/blog/wp-content/uploads/2011/12/121411_0216_Scrabble12.png" alt=""/></p>
<!-- AdSense Now! V1.75 -->
<!-- Post[count: 2] -->
<div class="adsense adsense-leadout" style="float:right;margin: 12px;"><script type="text/javascript"><!--
google_ad_client = "pub-3321865564354735";
/* blogpages */
google_ad_slot = "7147521806";
google_ad_width = 125;
google_ad_height = 125;
//-->
</script>
<script type="text/javascript"
src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
</script></div><div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/ReadytextBlog?a=Ixm56AmSRu4:OqoTe2yS0PU:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/ReadytextBlog?d=yIl2AUoC8zA" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/ReadytextBlog?a=Ixm56AmSRu4:OqoTe2yS0PU:qj6IDK7rITs"><img src="http://feeds.feedburner.com/~ff/ReadytextBlog?d=qj6IDK7rITs" border="0"></img></a>
</div>]]></content:encoded>
			<wfw:commentRss>http://readytext.com/blog/2011/12/scrabble/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://readytext.com/blog/2011/12/scrabble/</feedburner:origLink></item>
		<item>
		<title>DITA: Too Much Information?</title>
		<link>http://feedproxy.google.com/~r/ReadytextBlog/~3/-eCNbfW3sdM/</link>
		<comments>http://readytext.com/blog/2010/08/dita-too-much-information/#comments</comments>
		<pubDate>Fri, 06 Aug 2010 21:05:34 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[technical writing]]></category>
		<category><![CDATA[writing]]></category>
		<category><![CDATA[writing tools]]></category>
		<category><![CDATA[effective writing]]></category>
		<category><![CDATA[writing project management]]></category>

		<guid isPermaLink="false">http://readytext.com/blog/?p=458</guid>
		<description><![CDATA[DITA (Darwin Information Typing Architecture) is IBM’s stab at producing standardized mechanisms for hoarding, or rather for “authoring, producing, and delivering technical information.” One thing DITA, and other information typing technologies cannot help with is the ranking of information in terms of likely relevance in future. This is likely to be specific to your particular topic domain or specialization, but in order to avoid hoarding and amassing too much undifferentiated information we need some standardization in the way we approach assigning value to topics.]]></description>
			<content:encoded><![CDATA[<p>There is a reality television program at the moment that follows hoarders, those poor folks who cannot help amassing stuff, either by collecting it or through their inability to throw anything away. The value of the stuff is immaterial; they just feel happier knowing that they have it, stored somewhere, even if it&#8217;s more or less inaccessible to them. The amount of stuff they have is often limited only by the space they have available to store it, and once they&#8217;ve filled their house they may go on to rent storage units so they can keep even more stuff.
</p>
<h2>DITA and Hoarding<br />
</h2>
<p>DITA (Darwin Information Typing Architecture) is IBM&#8217;s stab at producing standardized mechanisms for hoarding, or rather for &#8220;authoring, producing, and delivering technical information.&#8221; It needn&#8217;t be only technical information – the same principles can be applied to all sorts of written information, and the system is designed to be extensible. It basically refers to the process of storing information at a fairly granular level (individual information units or &#8220;topics&#8221;) along with meta-information that provides useful descriptions in case you want to re-use all or part of the information in future. It&#8217;s the foundation for content management and repurposing; other tools can then assemble and transform these topics as required for specific audiences, purposes, and output formats.
</p>
<p>There are a number of related efforts, all focused on the task of labeling and organizing information. So by now we&#8217;re starting to understand what it takes to hoard all the information an organization produces, and build software to help us identify and retrieve it in future. In that regard – managing and retrieving our data – we&#8217;re better off than the hoarders who have so much stuff they couldn&#8217;t tell you what they have or where it is. But we do have one major problem in common with them; it&#8217;s hard to distinguish between information that&#8217;s likely to be useful, and information that we will likely never reference again.
</p>
<h2>Information Assets and Liabilities<br />
</h2>
<p>Since storage is cheap, it&#8217;s tempting to keep all the information we produce. Every document, internal and external, every memo, e-mail message, meeting agenda and minutes – everything. And this gets more attractive as we develop DITA-related tools that help streamline the cataloguing and storing process. But this mass warehousing approach suggests that all our information is either of equal value, or of equally unknown value. And more is not always better, especially when it comes to rapid search and retrieval of information in future.
</p>
<p>One thing DITA, and other information typing technologies cannot help with is the ranking of information in terms of likely relevance. This is likely to be specific to your particular topic domain or specialization, but in order to avoid hoarding and amassing too much undifferentiated information we need some standardization in the way we approach assigning value to topics.
</p>
<h2>Imputed versus Apparent Relevance<br />
</h2>
<p>We can impute value, which pretty much means make a good guess when we produce information as to whether we might reference it again in future. Writers could do this based on the feedback they received from subject matter experts (SMEs) when they gathered the information; they can get a pretty good feel for how important or controversial topics were, and how much interest there was in them. They can also use reviewer comments to distinguish the hot topics from the less interesting ones, and assign the more debated information a higher relevance.
</p>
<p>There&#8217;s also the apparent value of information, which is well-known to those engaged in search engine optimization. This is indicated by how well linked the information is – how much other information references it or is referenced by it. Topics at the center of a web are more likely to have lasting relevance than those that attract less attention, and we can imagine automated tools to track and assign a dynamic relevance quota that represents this more measurable or  apparent value of a topic.
</p>
<p>Based on their likely relevance, then, topics can also be assigned a &#8220;time to live&#8221; number that determines how slowly or rapidly their likely relevance expires. This value ticks down to zero (or &#8220;irrelevant&#8221;) for as long as the topic remains untouched; at that point it might be removed from the system.
</p>
<h2>What&#8217;s the Payback?<br />
</h2>
<p>The payback for DITA and similar technologies is clear. If we don&#8217;t learn from past topics, decisions, meetings, and e-mail threads – then we are doomed to repeat them. Building a library of tried and tested, edited and legalized information topics has clear value. But we need to develop a hierarchy of information such that the likely most valuable is the most thoroughly tagged and categorized, and information that proves to be of little use can be quietly and efficiently sent to a &#8220;stack&#8221; or jettisoned for good. Only by doing this can we most efficiently use the time and expertise of writers, editors, and program managers who are tasked with maintaining that core company asset – information.
</p>
<h2>More Information<br />
</h2>
<p>This topic, and more, is further discussed in an upcoming issue of <a href="http://readytext.com/rewrite.html">rewrite</a>, where we provide short, immediately useful and engaging articles relating to obtaining, organizing, transforming and producing written information. Take a look and see if a subscription might be useful for you; in the meantime, thanks for your interest in the readytext blog.
</p>
<p>
 </p>
<p>
 </p>
<!-- AdSense Now! V1.75 -->
<!-- Post[count: 3] -->
<div class="adsense adsense-leadout" style="float:right;margin: 12px;"><script type="text/javascript"><!--
google_ad_client = "pub-3321865564354735";
/* blogpages */
google_ad_slot = "7147521806";
google_ad_width = 125;
google_ad_height = 125;
//-->
</script>
<script type="text/javascript"
src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
</script></div><div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/ReadytextBlog?a=-eCNbfW3sdM:zIpw8WbXzYw:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/ReadytextBlog?d=yIl2AUoC8zA" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/ReadytextBlog?a=-eCNbfW3sdM:zIpw8WbXzYw:qj6IDK7rITs"><img src="http://feeds.feedburner.com/~ff/ReadytextBlog?d=qj6IDK7rITs" border="0"></img></a>
</div>]]></content:encoded>
			<wfw:commentRss>http://readytext.com/blog/2010/08/dita-too-much-information/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://readytext.com/blog/2010/08/dita-too-much-information/</feedburner:origLink></item>
		<item>
		<title>Writing Programs</title>
		<link>http://feedproxy.google.com/~r/ReadytextBlog/~3/HOVl0d-E5XQ/</link>
		<comments>http://readytext.com/blog/2010/08/writing-programs/#comments</comments>
		<pubDate>Tue, 03 Aug 2010 20:00:45 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[technical writing]]></category>
		<category><![CDATA[writing]]></category>
		<category><![CDATA[writing tools]]></category>
		<category><![CDATA[content management]]></category>
		<category><![CDATA[effective writing]]></category>
		<category><![CDATA[writing project management]]></category>

		<guid isPermaLink="false">http://readytext.com/blog/?p=453</guid>
		<description><![CDATA['Literate programming', originated by Donald Knuth in the '80s, championed a style that turned programmers into essayists (Knuth's term) as much as they are engineers. 
</p><p>Our interest was piqued in case there was an opportunity for literate programmers to return the favor, and pass on news we could use to become "programming writers".
]]></description>
			<content:encoded><![CDATA[<p>An article in this month&#8217;s <a href="http://readytext.com/rewrite.html">rewrite</a> takes a look at the things writers know that have proven useful to programmers. Specifically, programmers who want to have more fun writing more efficient programs that other programmers can more readily understand. &#8216;Literate programming&#8217;, originated by Donald Knuth in the &#8217;80s, championed a style that turned programmers into essayists (Knuth&#8217;s term) as much as they are engineers.
</p>
<p>Our interest was piqued in case there was an opportunity for literate programmers to return the favor, and pass on news we could use to become &#8220;programming writers&#8221;.
</p>
<h2>What Writers Know<br />
</h2>
<p>Writers, some more than others, are good at sorting and presenting data, arranging argument, illustrating issues and, perhaps most significantly, making information interesting and accessible. They spend time figuring stuff out, so that readers don&#8217;t have to spend that time themselves. They try to avoid ambiguity, to ensure readers get what they need, and to convey messages clearly. They follow rules of grammar and style that are known to be effective, and they strive to make all this look as easy as possible to keep focus on the message rather than the medium.
</p>
<h2>What Programmers Know<br />
</h2>
<p>Programmers, some more than others, are good at solving complex problems as efficiently as possible. They spend time applying logical principles and tried and tested algorithms to seemingly disorganized and incoherent sets of functional requirements. They use languages, tools, and program development environments to produce program components designed to be read by humans, by machines, and by other programs.  They know different languages and styles of programming, and they use their experience to judge those best-suited for the task in hand. And they save time and effort by re-using components that have already been written and tested.
</p>
<h2>What Each Offers the Other<br />
</h2>
<p>The two are converging. Programmers know that one of the main costs of software development is supportability. So programmers see the value of languages and tools that help write programs that are readily decipherable, supported, and enhanced by others.
</p>
<p>Writers, particularly those involved in large projects written by teams, are learning to produce writing (or &#8220;content&#8221;) that is readily re-usable, and that can be readily transformed and repurposed for specific audiences and output devices. So these writers&#8217; documents must now contain additional information to enable humans and machines to understand something of their purpose and design.
</p>
<p>In short, programmers are programming a little more like writers, and writers are writing – and using computer-based tools and utilities – more like programmers.
</p>
<p>A literate programmer writes for humans first, and in the process will often write programs that are more efficient also for the machine. Programming writers are now working in a computerized environment that can transform their content into audience- and device-specific variants, and they write with that content development environment in mind.
</p>
<p>Documents today are not only written, edited and published; they are linked, they&#8217;re compiled, and they are shareable – all familiar features to programmers. And programs aren&#8217;t just highly structured and sparsely commented files full of computer language: literate programmers can write programs that disclose the decision processes and trains of thought that went into their design.
</p>
<h2>More Information<br />
</h2>
<p>This topic, and more, is further discussed in the August 2010 issue of <a href="http://readytext.com/rewrite.html">rewrite</a>, where we provide short, immediately useful and engaging articles relating to obtaining, organizing, transforming and producing written information. Take a look and see if a subscription might be useful for you; in the meantime, thanks for your interest in the readytext blog.</p>
<div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/ReadytextBlog?a=HOVl0d-E5XQ:RO10BAR78fc:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/ReadytextBlog?d=yIl2AUoC8zA" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/ReadytextBlog?a=HOVl0d-E5XQ:RO10BAR78fc:qj6IDK7rITs"><img src="http://feeds.feedburner.com/~ff/ReadytextBlog?d=qj6IDK7rITs" border="0"></img></a>
</div>]]></content:encoded>
			<wfw:commentRss>http://readytext.com/blog/2010/08/writing-programs/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://readytext.com/blog/2010/08/writing-programs/</feedburner:origLink></item>
		<item>
		<title>Last Minute Errors</title>
		<link>http://feedproxy.google.com/~r/ReadytextBlog/~3/OH_KoI1EG34/</link>
		<comments>http://readytext.com/blog/2010/06/last-minute-errors/#comments</comments>
		<pubDate>Tue, 29 Jun 2010 19:22:32 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[editing]]></category>
		<category><![CDATA[technical writing]]></category>
		<category><![CDATA[writing]]></category>
		<category><![CDATA[effective writing]]></category>

		<guid isPermaLink="false">http://readytext.com/blog/?p=261</guid>
		<description><![CDATA[A quick roundup of the most common issues that, if we're not careful, appear only after we've released the finished work. Check for these during final edit, and you can prevent that sinking feeling that happens when readers report a miss-spelled running header, or a table caption that somehow got pushed to the following page. ]]></description>
			<content:encoded><![CDATA[<p>The July issue of <a href="http://readytext.com/rewrite.html">rewrite</a> discusses electronic publishing and e-readers, and this brought to mind how the electronic word enables authors to stay &#8216;in touch&#8217; with their work after it&#8217;s initially published. The idea of successive editions of a work is a legacy of the printed book; now, writers have much more granular control over changes and enhancements to texts that can be readily re-published, lately to electronic readers (e-readers) that can be easily refreshed with the latest content.</p>
<p>But that doesn&#8217;t let the writer or editor off the hook with respect to producing clean, error-free writing. In particular, writing that&#8217;s free of those annoying errors that crop up at the last minute, just before publication, and often go unnoticed as the momentum to publish takes hold.</p>
<p>So here&#8217;s a quick roundup of the most common issues that, if we&#8217;re not careful, appear only after we&#8217;ve released the finished work. Check for these during final edit, and you can prevent that sinking feeling that happens when readers report a miss-spelled running header, or a table caption that somehow got pushed to the following page.</p>
<p>First, check the pages for the big picture. Often, you can spot formatting errors more easily when you step back a little and view the pages two-up. Check for missing headers and footers, wrong page numbers, and unusual looking gaps and white space. Make sure fonts look consistent, and paragraphs aren&#8217;t orphaned across page breaks (leaving just a few words at the top of a new page before a new paragraph). Do diagrams and tables sit correctly with regard to associated text? A common error is for changes in body text to push or pull a table across a page break, resulting in a table header with just one row beneath it, or illustrations with text flowed around them that now doesn&#8217;t flow quite as well.</p>
<p>Next, scan a little closer for missing or extra spaces between words, before and after punctuation, and even between paragraphs. When late additions or deletions are made, these sorts of errors are likely. Check that where possible diagrams, tables and figures are on the same page as the text that references them, and that associated captions are correctly attached. Check all numbering – for pages, headers, tables and so on &#8212; for consistency, sequence, and integrity.</p>
<p>Search for things like &#8216;above&#8217; and &#8216;below&#8217;. These terms shouldn&#8217;t be used to refer to the relative location of items in the text, and editors generally remove them; but where they are, make sure things haven&#8217;t been subsequently moved. Search for references to numbers; often, the number of items of one sort or another – list entries, subsections, even table entries – changes, but the text referring to them doesn&#8217;t (&#8221;There are five reasons to drink tea&#8221; followed by four reasons, for example).</p>
<p>It&#8217;s probably best to take the time to double-check any hyperlinks, both inside and outside the document. There&#8217;s nothing like dead links inside an online document to undermine its relevance and authority, and if a link is going to go away it will do so at the last minute, you can be sure. That includes those internal links in the table of contents, if necessary (you already checked that the page numbers in the TOC are correct, right? Forgetting to regenerate TOCs is a classic mistake made under stress).</p>
<p>A final check that headings remain parallel is useful. For example, someone added a new section and now six headings are imperatives (such as &#8220;Boil the Water&#8221;, &#8220;Measure the Tea&#8221;) and one contains a participle (&#8221;Warming the Pot&#8221;).</p>
<p>Finally, it&#8217;s surprisingly easy in a well-reviewed and heavily edited document to end up with chunks of material – paragraphs and more – that at the last minute either disappear, or are duplicated. Blame cut and paste. This is one of the few errors that a quick scan is more likely to catch than a detailed read-through.</p>
<p>More on this in future, and in particular how common writing tools often seem to conspire to make the late introduction of these sorts of errors almost automatic. We will also look at strategies to avoid having to deal with disgruntled customers who pushed for hasty production and skipped edit rounds, because they didn&#8217;t feel error-free text was important until they saw the published article.</p>
<div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/ReadytextBlog?a=OH_KoI1EG34:ievT6iZzj6s:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/ReadytextBlog?d=yIl2AUoC8zA" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/ReadytextBlog?a=OH_KoI1EG34:ievT6iZzj6s:qj6IDK7rITs"><img src="http://feeds.feedburner.com/~ff/ReadytextBlog?d=qj6IDK7rITs" border="0"></img></a>
</div>]]></content:encoded>
			<wfw:commentRss>http://readytext.com/blog/2010/06/last-minute-errors/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://readytext.com/blog/2010/06/last-minute-errors/</feedburner:origLink></item>
		<item>
		<title>Most of us Will Never Be Great Writers!</title>
		<link>http://feedproxy.google.com/~r/ReadytextBlog/~3/cfT-_FAeSaw/</link>
		<comments>http://readytext.com/blog/2010/05/most-of-us-will-never-be-great-writers/#comments</comments>
		<pubDate>Tue, 25 May 2010 18:55:21 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[reading]]></category>
		<category><![CDATA[technical writing]]></category>
		<category><![CDATA[writing]]></category>
		<category><![CDATA[effective writing]]></category>

		<guid isPermaLink="false">http://readytext.com/blog/?p=253</guid>
		<description><![CDATA[Why do some texts seem to carry us forward and propel us toward their messages, while others are like pushing rocks uphill? A related question is whether, given the tendency of texts, presentations and written communication in general to escape the control of the author, we can identify what it is that authors are doing when they produce "good" or even "great" writing. Because if teachers can't figure that out, they can't really coach others to be great writers. 
]]></description>
			<content:encoded><![CDATA[<p>The upcoming June edition of the <a href="http://readytext.com/rewrite.html">rewrite</a> newsletter deals with how meaning is conjured, apparently from nothing, when we write. And it looks at what readers bring to the meaning table when they begin to interpret what we write. A goal of the &#8216;meaning of meaning&#8217; theme is to examine to what extent meaning and the significance of a text can be controlled or developed by the writer, because writers tell us that they often feel like they are following rather than constructing as they write.</p>
<p>Novelists report that fictional characters and situations seem to independently take on threads of meaning that the author recognizes, follows, and explores. Non-fiction writers can find themselves in similar situations, when structural demands of the text, contextual resonances, and the unpredictable situations in which the text will be interpreted can lead to a sense that meaning is being corralled rather than created.</p>
<p>A related question is whether, given the tendency of texts, presentations and written communication in general to escape the control of the author, we can identify what it is that authors are doing when they produce &#8220;good&#8221; or even &#8220;great&#8221; writing. Because if teachers can&#8217;t figure that out, they can&#8217;t really coach others to be great writers.</p>
<p>Stephen King reckons it&#8217;s not possible to teach anyone to be a great writer. You can become a good writer, but his claim is that great writers – like people who are great at almost anything – have an aptitude at the outset that you either have or you don&#8217;t.</p>
<p>So it may be like great painting, or great musicianship; we know it when we see it or hear it, and we can go to great lengths to explain why we think one work stands out above the rest, but most of us don&#8217;t really expect to learn to write like Hemingway, paint like Van Gogh, or compose our own fifth symphony. But we do, often, feel compelled to ask why it reads well, looks interesting, or sounds so moving.</p>
<p>Common advice to would-be writers is to read as much as possible, presumably choosing among texts that are already judged well-written. And this we can all do, in the hope that some of that technique will rub off. In many endeavors, when we hang around successful people we raise the chances that we, too, will be successful; perhaps the same principal applies here.</p>
<p>So if Stephen King is right, what can a writing newsletter have to offer and what kind of articles can you expect in <a href="http://readytext.com/rewrite.html">rewrite</a>, which claims to deal with the &#8220;techniques and technologies of effective written communication&#8221;?</p>
<p>We do include a few purely pragmatic tips to help identify common stumbling-blocks that prevent writing from working for us. More in-depth articles look at practical tools such as single-sourcing and content management support systems that increase the efficiency of individual writers and writing teams.</p>
<p>But we also follow the idea of summoning success by standing closer to someone successful. We look at greater length at what makes great writing work; why it&#8217;s effective, why it&#8217;s a pleasure to read, and what makes it unusual. Why do some texts seem to carry us forward and propel us toward their messages, while others are like pushing rocks uphill? What features of the language are at play when writing achieves something remarkable, or what techniques make one presentation memorable while another is forgettable? By reading, by reflecting on what we read and by analyzing it when it strikes us that something unusual is happening, we may learn to at least better recognize the good and the bad, the resonant and the unreadable in our own work.</p>
<p>The intention is that in the process we may not become great writers, but we may become better writers and we may just have more fun writing.</p>
<div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/ReadytextBlog?a=cfT-_FAeSaw:rmmzDWXAHZs:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/ReadytextBlog?d=yIl2AUoC8zA" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/ReadytextBlog?a=cfT-_FAeSaw:rmmzDWXAHZs:qj6IDK7rITs"><img src="http://feeds.feedburner.com/~ff/ReadytextBlog?d=qj6IDK7rITs" border="0"></img></a>
</div>]]></content:encoded>
			<wfw:commentRss>http://readytext.com/blog/2010/05/most-of-us-will-never-be-great-writers/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://readytext.com/blog/2010/05/most-of-us-will-never-be-great-writers/</feedburner:origLink></item>
		<item>
		<title>Working with Subject Matter Experts</title>
		<link>http://feedproxy.google.com/~r/ReadytextBlog/~3/u01JHF33Y6k/</link>
		<comments>http://readytext.com/blog/2010/04/working-with-subject-matter-experts/#comments</comments>
		<pubDate>Mon, 19 Apr 2010 03:45:05 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[technical writing]]></category>
		<category><![CDATA[writing]]></category>
		<category><![CDATA[effective writing]]></category>
		<category><![CDATA[SME]]></category>
		<category><![CDATA[subject matter experts]]></category>

		<guid isPermaLink="false">http://readytext.com/blog/?p=240</guid>
		<description><![CDATA[How to make the most of your time with SMEs, and how to avoid some of the most common pitfalls when you work with them.]]></description>
			<content:encoded><![CDATA[<p>When you need to write about something you&#8217;re not completely familiar with – which is probably most of your writing that&#8217;s not either pure fiction or autobiography – you may well need to consult one or more Subject Matter Experts (SMEs).</p>
<p>This month in <a href="http://readytext.com/rewrite.html">rewrite</a> we look at how to make the most of your time with SMEs, and how to avoid some of the most common pitfalls when your work with them. In the meantime, here&#8217;s a few of the takeaways.</p>
<h2>Pre-SME</h2>
<p>Find out what your project is about. Sounds pretty basic, but until you&#8217;ve nailed down what you&#8217;re writing about, it&#8217;s hard to identify the best people to help you with it. You may need to review an outline with whoever is sponsoring or signing off on your work, before you can be sure where the required expertise lies.</p>
<p>As you identify SMEs, try to get a feel for how likely it is you will be able to get what you need from them within your schedule. An unavailable expert is no use, and an expert in another time zone may be less useful than someone down the hall. You may prefer experts who have bought into the project, or whose managers are committed to it, over those who are unaware or who work in a separate organization.</p>
<p>You perhaps don&#8217;t need all your experts on day 1 for draft 1. Line up SMEs with dates and drafts, and sequence them if necessary if you know you will need information from one before you are ready to interview another.</p>
<p>Pay special attention to the message inviting them to speak with you. Make clear why you need them, when you need them, and why it&#8217;s important that they give you their time. It&#8217;s important to be flexible, but you should bear in mind your schedule and respect your own as well as the SMEs&#8217; time. Always allow a potential SME who cannot meet your schedule to nominate someone else they feel is equipped to contribute.</p>
<h2>SME</h2>
<p>In general, SME interviews should be efficient. That means you end up with information you can use in the form of notes you can decipher, and the SME has given you information you couldn&#8217;t reasonably or easily have got elsewhere. They are experts, so they don&#8217;t enjoy spending time discussing topics outside their area of expertise, especially if their schedule is already tight. Interviews usually go well when you ask intelligent questions for which you are adequately prepared, so you can move on without spending too much time seeking clarifications.</p>
<p>However, don&#8217;t waste time taking notes on points you really don&#8217;t understand. Worse than asking for clarification during the interview, is having to come back to the SME later to ask the same questions again because you clearly didn&#8217;t follow the first time around.</p>
<p>Awkward interviews – when the SME is uninterested, distracted or otherwise unhelpful – can always be rescheduled. Sometimes the suggestion that they be rescheduled is enough to bring them back on track. If you know the SME finds it hard to blank out uninterrupted time for you, it may be best to schedule the interview somewhere you won&#8217;t be disturbed – a meeting room, your office, even the cafeteria or coffee bar – and avoid the SME&#8217;s office.</p>
<h2>Post-SME</h2>
<p>Follow up with thank you and next steps – especially if the SME will be on an interview loop later in the project. If possible, make sure everyone involved in the project sees progress; publish a timeline with major milestones checked off as they are achieved. Give everyone a sense that the project has momentum, that they&#8217;re all onboard and it&#8217;s too late to step off. Be prepared to be diplomatic when you have conflicting information from SMEs, or when their review comments appear to contradict one another. You must ensure you understand and can articulate your understanding of all arguments before you pit them against one another and seek resolution. The ego in the Expert part of SME can be easily bruised, and maintaining a good professional relationship with SMEs is important, especially if you feel you may be speaking with them again in future projects.</p>
<h2>More Information</h2>
<p>This topic, and more, is further discussed in the May 2010 issue of <a href="http://readytext.com/rewrite.html">rewrite</a>, where we provide short, immediately useful and engaging articles relating to obtaining, organizing, transforming and producing written information. Take a look and see if a subscription might be useful for you; in the meantime, thanks for your interest in the readytext blog.</p>
<div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/ReadytextBlog?a=u01JHF33Y6k:bsBXBBhuhfo:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/ReadytextBlog?d=yIl2AUoC8zA" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/ReadytextBlog?a=u01JHF33Y6k:bsBXBBhuhfo:qj6IDK7rITs"><img src="http://feeds.feedburner.com/~ff/ReadytextBlog?d=qj6IDK7rITs" border="0"></img></a>
</div>]]></content:encoded>
			<wfw:commentRss>http://readytext.com/blog/2010/04/working-with-subject-matter-experts/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://readytext.com/blog/2010/04/working-with-subject-matter-experts/</feedburner:origLink></item>
		<item>
		<title>Building Presentations: Taking Cues from Commercials</title>
		<link>http://feedproxy.google.com/~r/ReadytextBlog/~3/xH5VcWzeKR8/</link>
		<comments>http://readytext.com/blog/2010/04/building-presentations-taking-cues-from-commercials/#comments</comments>
		<pubDate>Thu, 15 Apr 2010 20:36:33 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[technical writing]]></category>
		<category><![CDATA[writing]]></category>
		<category><![CDATA[effective writing]]></category>

		<guid isPermaLink="false">http://readytext.com/blog/?p=229</guid>
		<description><![CDATA[Maybe we should treat presentations more like commercials than – well – presentations. We have a short time to make a lasting impression, and we need to focus on making our messaging stick.]]></description>
			<content:encoded><![CDATA[<p>Most presenters design their own slides, and their area of expertise is not PowerPoint or Keynote. To make matters worse, these tools don&#8217;t come with instructions on how to create memorable presentations.</p>
<h3>Slides as Notes</h3>
<p>Here&#8217;s a slide that might be designed to tell the audience about a new line of perfume.</p>
<p><img src="http://readytext.com/blog/wp-content/uploads/2010/04/041510_2036_BuildingPre1.png" alt="" /></p>
<p><span style="font-size:9pt"><em>Speaker notes: Designed for women. Will be called &#8216;rouge&#8217;. Reasonably exclusive. Testers say &#8220;hot&#8221;, &#8220;fiery&#8221;, &#8220;sophisticated&#8221;, &#8220;liberating&#8221;. Is one of our more expensive.<br />
</em></span></p>
<p>Many of us have endured countless tedious and forgettable slides like this. The speaker pushes the button, reads the slide, coughs, and shuffles on to the next one. The slides proceed more as a script or reference material that we should print out for later, and in fact often reappear, bound and filed, as &#8216;handouts&#8217;. This kind of slide is more like a précis than a presentation.</p>
<h3>Slides as Representations</h3>
<p>Of course, it&#8217;s fine for the speaker to say what&#8217;s on that slide. The bad part is that it&#8217;s also on the slide. Slides should illustrate or represent rather than slavishly repeat the messages of the presentation.</p>
<p>Dick Hardt, a Web identity specialist who is unafraid to use his remarkable name to help sell his message, has produced some great presentations. <em>Who Is the Dick on My Site</em>? (<a href="http://identity20.com/media/ETECH_2006/">http://identity20.com/media/ETECH_2006</a>) showcases his method of using slides to punctuate, not repeat, his words. His presentation is not sequential or rigidly structured (sequences of key slide, sub-slides); he builds his arguments, but the slides dart in and out of the discussion, highlighting, grabbing attention and sometimes intentionally and ironically undermining. Key words and phrases flash on the screen as he talks, adding pace and punch to his pretty much continuous speech. Pictures and graphics are repeated at various stages to reinforce fundamental points and create a sense of familiarity and closure. The applause at the end of his presentations is genuine, the audience sensing that they have covered a lot of ground, learned a lot, and will remember it long after the Danish pastries are gone and the coffee is cold.</p>
<p>And that&#8217;s the main point here: his presentations are memorable – or, rather, the presentation itself makes his arguments memorable and tie otherwise arcane issues to memorable images and events.</p>
<h3>Slides as Metaphors</h3>
<p>Dick&#8217;s slides, though, are still chiefly direct representations, in one form or another, of what he is saying. They&#8217;re by no means straight scripts, but they are literal in that they refer directly to one or more points in his speech. He also uses a less direct approach to reinforcing his words.</p>
<p>Slides can also be memorable when they are metaphorical, rather than literal. They provide images that are separate from the speaker&#8217;s words and they don&#8217;t refer directly to them at all. Instead, slides provide figural glue that helps the messaging to stick in the audience&#8217;s mind.</p>
<p>Our perfume presenter plodded through the inevitably impersonal features of the new perfume, and listed those features on a slide that doesn&#8217;t help tie them to the product or lend the new perfume any sort of unique identity. We could be talking about any perfume, really. How much more effective is an image to which the audience can associate on the one hand the stated features, and on the other, this specific product:</p>
<p><img src="http://readytext.com/blog/wp-content/uploads/2010/04/041510_2036_BuildingPre2.jpg" alt="" /></p>
<p><span style="font-size:9pt"><em>Speaker notes: Designed for women. Will be called &#8216;rouge&#8217;. Reasonably exclusive. Testers say &#8220;hot&#8221;, &#8220;fiery&#8221;, &#8220;sophisticated&#8221;, &#8220;liberating&#8221;. Is one of our more expensive.<br />
</em></span></p>
<p>In this way the speaker is able to use the power of metaphor to link dissimilar objects (product and message) within an image, made memorable by the overall experience.</p>
<h3>Presentations as Commercials</h3>
<p>Of course, the &#8220;product&#8221; here is whatever concept or argument that the presenter is trying to make. And the image could be anything that fires the imagination and adds stickiness to the messaging. This is a process familiar to people who make commercials, where they are intending to make as big an impression as possible, as immediately as possible. It&#8217;s even hard to imagine a commercial designed along the lines of the average corporate PowerPoint slide. Commercials don&#8217;t expect their audience to remember a series of facts, and they seldom punish us with bulleted lists. They engage us, they give us something to figure out, and they enable us to take part in creating a memorable experience by setting up the conditions for this to happen.</p>
<p><img src="http://readytext.com/blog/wp-content/uploads/2010/04/041510_2036_BuildingPre3.png" alt="" /></p>
<p>What do we achieve when we take on these techniques in our presentations? We exchange mere information redundancy for message reinforcement. Our audience gets an experience rather than a lecture, and instead of dying in their ring binders our messaging lives in their imagination.</p>
<p>Maybe we should treat presentations more like commercials than – well – presentations. We have a short time to make a lasting impression, and we need to focus on making our messaging stick. More on building effective presentations in the May 2010 edition of the <a href="http://readytext.com/rewrite.html">rewrite</a> newsletter.</p>
<div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/ReadytextBlog?a=xH5VcWzeKR8:hwl3XIkrJMw:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/ReadytextBlog?d=yIl2AUoC8zA" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/ReadytextBlog?a=xH5VcWzeKR8:hwl3XIkrJMw:qj6IDK7rITs"><img src="http://feeds.feedburner.com/~ff/ReadytextBlog?d=qj6IDK7rITs" border="0"></img></a>
</div>]]></content:encoded>
			<wfw:commentRss>http://readytext.com/blog/2010/04/building-presentations-taking-cues-from-commercials/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://readytext.com/blog/2010/04/building-presentations-taking-cues-from-commercials/</feedburner:origLink></item>
		<item>
		<title>Putting the ‘Corp’ in Corporate Communications</title>
		<link>http://feedproxy.google.com/~r/ReadytextBlog/~3/0jVkJ_80PXA/</link>
		<comments>http://readytext.com/blog/2010/01/putting-the-%e2%80%98corp%e2%80%99-in-corporate-communications/#comments</comments>
		<pubDate>Sun, 17 Jan 2010 19:16:55 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[technical writing]]></category>
		<category><![CDATA[writing]]></category>
		<category><![CDATA[effective writing]]></category>

		<guid isPermaLink="false">http://readytext.com/blog/?p=198</guid>
		<description><![CDATA[Effective and memorable corporate communications, and not only external ones, should feature a specific corporate identity or 'voice'. ]]></description>
			<content:encoded><![CDATA[<p>The latest Apple commercials are great examples of a company that places itself and its reputation at the center of its communications. They present themselves and their chief competitor, Microsoft, literally as people. The Apple person is likeable and the sort of person you might want to hang out with; friendly, confident, cool and relaxed. The Microsoft person is less impressive. He&#8217;s nervous, defensive and gives the impression he&#8217;d rather not be there at all.</p>
<p>The commercials give no real detail about Apple&#8217;s products or services. Instead, they promote a long-term message that Apple is good people, that we can feel good about keeping their company, and that the quality of their products goes without question. In contrast, their competitor has only the questionable quality of its products to offer, and those flaws are embodied by an actor who happens to remind us of Microsoft&#8217;s most famous employee. In this way one corporation becomes a flawed character we wouldn&#8217;t want to associate or be associated with, while we poke fun and share jokes about it with our friend, the other.</p>
<h3>Keeping the Brand &#8216;In Mind&#8217;</h3>
<p>Raw information, technical detail, rational argument – no matter how well reasoned and clearly presented – is by nature anonymous, characterless, utilitarian, orphaned from any source, and ultimately forgettable. It doesn&#8217;t help keep a company or its brand &#8216;in mind&#8217;.</p>
<p>What does help is when we think of Corporations as people, not entities. One relatively recent way to achieve this is to embrace social networking (<em>Facebook</em>,<em> Twitter</em>) in order to win the loyalty and forgiveness that&#8217;s reserved for our friends, and avoid the suspicion and distrust that may accompany an approach by strangers.</p>
<p>But expensive and infrequent commercials, perky tweets, or the camaraderie of a <em>Facebook</em> fan are not the only means available to add personality, stay in mind, and convince customers that they&#8217;re in good company.</p>
<h3>Voicing Communications</h3>
<p>Convention sometimes holds that the best writing model for conveying information is transparent, opinionless and apparently authorless – the perfect journalistic style.</p>
<p>I would argue instead that effective and memorable corporate communications, and not only external ones, should feature a specific corporate identity or &#8216;voice&#8217;. Key to developing and maintaining voice is making the notion of the character of the source, and the emotional appeal of the message, central principles. This not only helps customers &#8216;read&#8217; information, it makes their task easier, makes the company memorable, and helps associate that positive experience with a brand.</p>
<h3>Personality and Consistency</h3>
<p>The danger for a company is that it writes itself or its brand out of its communications, when its goal should be the opposite: to be recognized and recalled whenever it communicates.</p>
<p>Among those things that help determine a recognizable voice in corporate communications are:</p>
<ul>
<li><strong>Facts tempered with experiences</strong>. In a feature-list for a new notebook computer, it&#8217;s common to find a LED-backlit 1920*1080 pixel display. But in Apple&#8217;s case, the display is variously <em>brilliant</em>, <em>stunning</em>, <em>beautiful</em>, and <em>ideal for watching HD movies</em>. These are terms that may then come to mind when we see the computer or think of the brand.</li>
<li><strong>Elements imported from a conversational style</strong>. Writing that &#8217;speaks&#8217; to customers probably isn&#8217;t written by a lawyer, so communications should be more like conversations than legalese.</li>
<li><strong>Consistency</strong>. You may not recognize a person who looks completely different every time you see them. Publications need consistent cues too if readers are to recognize a common and unifying authorial voice.
<ul>
<li>Repetition of form, structure, and vocabulary helps too.</li>
</ul>
</li>
<li><strong>Resisted temptation to let the subject dictate the style</strong>. Complex subjects don&#8217;t need tougher prose; technical detail is not by necessity dry and anonymous.</li>
<li><strong>Efficiency sacrificed for readability</strong>. Casual chit-chat may be one of the least efficient means of communication; mathematical notation one of the most dense. Good communications aim for somewhere in between!
<ul>
<li>Fifteen pages of lists with a half dozen supporting tables may be &#8216;optimal&#8217;, but context-setting and a paragraph here and there reminds us that we&#8217;re in a conversation with the author, collaborating in the writing and reading process, and not merely taking instruction from a robot.</li>
</ul>
</li>
<li><strong>Strong editing</strong>, especially where communications are compiled from multiple sources.
<ul>
<li>Editing that refuses to allow topic complexity or audience specialization to excuse bland or incoherent voice.</li>
</ul>
</li>
<li><strong>Strong sense of &#8220;I&#8221; and &#8220;You&#8221;</strong>. Strong characters are self-aware, and strong writing is positive, active, and unafraid to identify who is speaking and who else is in the conversation. Not &#8220;The manufacturer will replace a defective widget&#8221;, but &#8220;Widgetmaster will promptly replace your failed widget.&#8221;</li>
</ul>
<h3>When Deadpan Rational is Still Best</h3>
<p>Of course, there are situations where a controlled style and vocabulary may be required. Air traffic control communications, drug administration instructions, and legal contracts are specifically intended to assume a single voice common to their specialized domain. These documents do not conjure the image of recognized and trusted friend. They are not intended to do anything but convey information as formally and accurately as the language will allow, and so use rigid conventions and contexts that must be understood before they are read.</p>
<p>But don&#8217;t write like that unless you have to.</p>
<p>Try to give readers of all types a memorable experience by developing a recognizable and repeatable authorial voice. Put the corp, not the corpse, back into corporate communications.</p>
<p>This article discusses corporate approaches to personalizing communications. But the same principles apply to individuals who are writing for colleagues, staff or managers within their organizations. There will be more on voice and narrative in non-fiction writing in an upcoming edition of the <a href="http://readytext.com/rewrite.html">rewrite</a> newsletter.</p>
<div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/ReadytextBlog?a=0jVkJ_80PXA:pBtlh5l7Mig:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/ReadytextBlog?d=yIl2AUoC8zA" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/ReadytextBlog?a=0jVkJ_80PXA:pBtlh5l7Mig:qj6IDK7rITs"><img src="http://feeds.feedburner.com/~ff/ReadytextBlog?d=qj6IDK7rITs" border="0"></img></a>
</div>]]></content:encoded>
			<wfw:commentRss>http://readytext.com/blog/2010/01/putting-the-%e2%80%98corp%e2%80%99-in-corporate-communications/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://readytext.com/blog/2010/01/putting-the-%e2%80%98corp%e2%80%99-in-corporate-communications/</feedburner:origLink></item>
		<item>
		<title>Product Information: Inconvenient Truths</title>
		<link>http://feedproxy.google.com/~r/ReadytextBlog/~3/HR_BXuCP1-A/</link>
		<comments>http://readytext.com/blog/2009/12/product-information-inconvenient-truths/#comments</comments>
		<pubDate>Mon, 28 Dec 2009 20:19:47 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[reading]]></category>
		<category><![CDATA[technical writing]]></category>
		<category><![CDATA[writing]]></category>
		<category><![CDATA[effective writing]]></category>

		<guid isPermaLink="false">http://readytext.com/blog/?p=188</guid>
		<description><![CDATA[As a manufacturer you are keen to bond with your consumers. You want to own a productive and long-term relationship with them. And nothing threatens that bond more than consumers who turn to strangers for information about your products, who are frustrated by them, or who are driven to indifference about you and your brand.]]></description>
			<content:encoded><![CDATA[<p>Anyone who&#8217;s gone online to find the answer to a question like &#8220;Why does my new mouse not work?&#8221; will be familiar with forums full of people who prefer not to read instruction manuals. Particularly, perhaps, when those manuals come on a CD and require you to install additional software just to read them. People have more or less specific questions, and thanks to internet search they can usually find someone who has provided the answers.
</p>
<h3>Top Five Convenience Requirements for Product Information<br />
</h3>
<p>Let&#8217;s face it: you don&#8217;t read most product documentation, because most product documentation is inconvenient. In order of convenience, you probably want:
</p>
<ol>
<li>To already know everything you need to know
</li>
<li>To have immediate answers to your questions
</li>
<li>To have readily available information on the thing you need to learn about
</li>
<li>To know that the information you need is available if only you can find it
</li>
<li>To be able to give up on whatever you are trying to do and feel ok about that
</li>
</ol>
<h4>Know Everything you Need to Know<br />
</h4>
<p>A great goal for every product, and certainly the claim of many. This happens sometimes, but usually with items like egg timers, pencils and batteries – items that we really don&#8217;t expect to have difficulty figuring out. Some still believe it of Apple computers.
</p>
<h4>Immediate Answers to your Questions<br />
</h4>
<p>Instruction manuals don&#8217;t cut it since they&#8217;re not immediate enough or we assume it will take too long to find our simple answer using the index, table of contents or whatever. Immediate answers come from the online forum, or the expert standing at your side. Again, Apple computer use this technique by way of a search feature that is intended to present the most likely useful answers to your queries. For printed documents, &#8216;Quick Start&#8217; and &#8216;Troubleshooting&#8217; sheets (often colorful and glossy) are supposed to anticipate your issues with in-your-face instructions in bold type and appealing graphics. But they usually fall short sooner or later.
</p>
<h4>Readily Available Information on the Thing you Need to Learn About<br />
</h4>
<p>This is the equivalent of the shelf-full of manuals that used to come with computers, or the substantial book that comes with a new car. The assumption here is that you may actually read these books, perhaps even from start to finish, in order to inwardly digest all the manufacturer feels you should know about the product. In fact you tend to turn to these as a last resort, relying on the probability that such a huge amount of information cannot possibly exclude the one thing you need to know.
</p>
<h4>The Information you Need is Available if Only you can Find it<br />
</h4>
<p>You know the feeling. You have such an obvious task that you know there must be a way your new widget can do it, but after a number of unsuccessful guesses you need to find some help somewhere. But no need to give up – after all, the widget manufacturer  wouldn&#8217;t be in business if the answer wasn&#8217;t there somewhere. Maybe try once more online…
</p>
<h4>Give Up on Whatever you are Trying to Do and Feel OK About That<br />
</h4>
<p>This is the least convenient aspect of owning your new widget, and perhaps the final chance it has for you to keep it despite the issue, rather than return it and write off the whole experience. The marketers&#8217; equivalent to the sin of despair, they have invoked in you the sin of indifference. They have produced a product whose feature is so hard to figure out, so frustratingly obvious yet inaccessible, that the consumer has simply lost interest and doesn&#8217;t care enough to complain. Classic example: programmable VCRs on which the only functions anyone uses are &#8216;play&#8217; and &#8217;stop&#8217;.
</p>
<h3>Why This Needs Fixing<br />
</h3>
<p>As a manufacturer you are keen to bond with your consumers. You want to own a productive and long-term relationship with them. And nothing threatens that bond more than consumers who turn to strangers for information about your products, who are frustrated by them, or who are driven to indifference about you and your brand.
</p>
<p>In the upcoming <a href="http://readytext.com/rewrite.html"><em>rewrite</em></a> newsletter we will be looking at how a blend of the first three conveniences seems to be optimal for consumers and manufacturers alike, why manufacturers need to own that blend rather than relinquish it to third-parties,  and the steps we can take to achieve it in the most simple and the most complex product documentation scenarios.
</p>
<p> In the meantime, for fun here are two examples of self-describing products.
</p>
<h4>The Self-Disclosing Appliance<br />
</h4>
<p>This is a knob. If you play with it you&#8217;ll find you can turn it and push it. You plug it into your computer and see what it does. It requires little or no documentation, and it&#8217;s an extreme manifestation of self-disclosure.  Trouble is, it&#8217;s correspondingly orphaned from its producer  (perhaps that&#8217;s why the manufacturer&#8217;s name alone is stamped so boldly on it).
</p>
<p>It looks like it dropped out of the sky.
</p>
<p><img src="http://readytext.com/blog/wp-content/uploads/2009/12/120309_1929_ProductInfo12.jpg" alt=""/>
	</p>
<p>
 </p>
<h4>The Self-Documenting Appliance<br />
</h4>
<p>Oh dear. A button for every function, and a label for every button.  We know it&#8217;s a &#8216;Bedroom Cordless Telephone/Clock Radio&#8217; because it says so, but with all those buttons we&#8217;re sure it must wash the dishes too.
</p>
<p><img src="http://readytext.com/blog/wp-content/uploads/2009/12/120309_1929_ProductInfo22.jpg" alt=""/>
	</p>
<p> If only we could figure out how to set the alarm.
</p>
<p>
 </p>
<div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/ReadytextBlog?a=HR_BXuCP1-A:ntKzu3tYos0:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/ReadytextBlog?d=yIl2AUoC8zA" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/ReadytextBlog?a=HR_BXuCP1-A:ntKzu3tYos0:qj6IDK7rITs"><img src="http://feeds.feedburner.com/~ff/ReadytextBlog?d=qj6IDK7rITs" border="0"></img></a>
</div>]]></content:encoded>
			<wfw:commentRss>http://readytext.com/blog/2009/12/product-information-inconvenient-truths/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://readytext.com/blog/2009/12/product-information-inconvenient-truths/</feedburner:origLink></item>
		<item>
		<title>Common Punctuation Problems</title>
		<link>http://feedproxy.google.com/~r/ReadytextBlog/~3/it7W9ffWlzc/</link>
		<comments>http://readytext.com/blog/2009/12/common-punctuation-problems/#comments</comments>
		<pubDate>Wed, 02 Dec 2009 20:24:22 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[writing]]></category>
		<category><![CDATA[effective writing]]></category>
		<category><![CDATA[technical writing]]></category>

		<guid isPermaLink="false">http://readytext.com/blog/?p=157</guid>
		<description><![CDATA[You know there's a rule about parentheses and period placement, but you're unsure about it. The result is you have to make a decision about this and other punctuation issues every time you're faced with them. It slows you down, interrupts your thought, wastes your effort, and makes it hard to write consistently. A quick reference this time for those annoying punctuation issues that commonly cause us to write inconsistently. 
]]></description>
			<content:encoded><![CDATA[<p>A quick reference this time for those annoying punctuation issues that commonly cause us to write inconsistently.</p>
<p>You know there&#8217;s a rule about parentheses and period placement, but you&#8217;re unsure about it. The result is you have to make a decision about this and other punctuation issues every time you&#8217;re faced with them. It slows you down, interrupts your thought, wastes your effort, and makes it hard to write consistently.</p>
<h3>Our Top Ten List</h3>
<p>Here&#8217;s a top ten list for punctuation problems (by no means exhaustive, but familiar to many of us).</p>
<ul>
<li><strong>Apostrophe</strong>. For the possessive of <em>it</em>, make sure you remove its apostrophe. But it&#8217;s a requirement for <em>it is</em> or <em>it has</em>. Dave Barry famously advised that an apostrophe is used to indicate that an <em>s</em> is coming; this is true in the case of pluralized words, where the <em>s</em> may otherwise be confused with the word itself (no <em>if</em>&#8217;s about it).</li>
<li><strong>Capitals</strong>. Capitalize sentences and quoted sentences; as our editor told us, &#8220;Remember that rule!&#8221; Capitalize proper nouns such as people, places and things. Don&#8217;t capitalize common nouns which are generic classes of things. Microsoft produces software called Office from its Redmond office. That reminds me; when you refer to something like Microsoft Online Services, follow the inventor or owner&#8217;s capitalization. As a general rule, use capitals in headers except for logistical words like articles (a, the) conjunctions (if, and) and prepositions (in, for).</li>
<li><strong>Dashes, Colons, and Semicolons</strong>. Dashes are almost as powerful as highlight pens, and so should generally be used just as sparingly. They can emphasize small things – words – or entire phrases – which might otherwise be overlooked. They can also mark a switch of emphasis – and I mean this most sincerely – or additional information – often too important to be enclosed in parentheses.
<ul>
<li><em>Colons</em> are much more straightforward: they mark examples, explanations such as this, and lists. The important thing is not to combine them with words or phrases that already provide that function, <span style="color:red">such as: this</span>.</li>
<li>Finally there are <em>semicolons</em>, which also link independent phrases or clauses, but less dramatically. Sometimes you can link two short sentences with a semicolon; this creates a single sentence that has a better rhythm. If your writing seems too staccato, maybe you need more semicolons.</li>
</ul>
</li>
<li><strong>Hyphenation</strong>. Simple rule: if in doubt, leave it out. Hyphens are often a historical waypoint in the migration of two words to one (for example<em>: touch line</em>, <em>touch-line</em>, <em>touchline</em>). So if you&#8217;re unsure then you&#8217;re better off ahead of this game rather than behind it; go straight to a single word. Hyphens are often introduced in an adjectival/adverbial role, where they modify a thing or an action. In these cases, eventually, the modifier and the modified are merged (I know I risk pigeonholing here).</li>
<li><strong>Inside or Outside?</strong> In general, punctuation accompanies the material quoted or parenthesized. Keep punctuation marks inside quotes and parentheses where it&#8217;s part of the quoted material. If the quoted or parenthesized material is inside a sentence, or at the end of a sentence, or if the punctuation is a colon or semicolon, place it outside the quotes or parentheses instead. &#8220;Why should I?&#8221; you may ask (because it&#8217;s a pain to remember all these rules).</li>
<li><strong>Italics</strong>. Use italics to indicate you&#8217;re referring, rather than directly using, words or names; for example, the word <em>italics</em> in this sentence or Keats&#8217; use of the word <em>fibble</em>.</li>
<li><strong>Numbers</strong>. Spell them out at the beginning of sentences, or if that&#8217;s too unwieldy, move them inside the sentence and use figures. Rule of thumb: within text, use figures for numbers above 99. Spell out ordinals (ranked numbers) like <em>first</em>, <em>sixth</em>, <em>eleventh</em> instead of using figures. Spell out percentages and use the word <em>percent</em>. Use all figures inside tables.</li>
<li><strong>Quotation</strong>. Quote titles of short works, articles, episodes, and blog entries like &#8220;Common Punctuation Problems&#8221;, but use italics to refer to major works, series titles or collections such as readytext&#8217;s <em>rewrite</em> newsletter or <em>Lambs Tales from Shakespeare</em>.</li>
<li><strong>Serial Commas</strong>. The most unassuming of punctuation marks, commas try to quietly order things without drawing any attention. In a list of three or more items, use a comma after each of them to help keep them separate. &#8220;My parents, Mother Theresa, and the Pope&#8221; is a common example that always raises a smile, a smirk, or a complaint.</li>
<li><strong>Spaces</strong>. Notorious for evading automated grammar checking, spaces should be avoided whenever you have to think about it, and double spaces are almost invariably optional. In general, don&#8217;t use spaces before punctuation marks of any sort (apart from parentheses and quotes). You don&#8217;t need a second space after a period.</li>
</ul>
<h3>The Importance of Being Consistent</h3>
<p>A good rule is that consistency is as important as accuracy. Even if they&#8217;re not familiar with the rules, readers are surprisingly good at picking up inconsistency in punctuation, and this can lead to a sense of uncertainty or lack of authority in your writing. And even if you make a mistake, if it&#8217;s consistently made then it&#8217;s easier for your editor to correct.</p>
<p>So pick a rule and stick with it until your editor successfully argues you out of it. And let me know when you spot the punctuation errors in this blog!</p>
<div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/ReadytextBlog?a=it7W9ffWlzc:-ErlF0DOHk8:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/ReadytextBlog?d=yIl2AUoC8zA" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/ReadytextBlog?a=it7W9ffWlzc:-ErlF0DOHk8:qj6IDK7rITs"><img src="http://feeds.feedburner.com/~ff/ReadytextBlog?d=qj6IDK7rITs" border="0"></img></a>
</div>]]></content:encoded>
			<wfw:commentRss>http://readytext.com/blog/2009/12/common-punctuation-problems/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://readytext.com/blog/2009/12/common-punctuation-problems/</feedburner:origLink></item>
	</channel>
</rss>

