<?xml version="1.0" encoding="utf-8"?>
<rss xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:pingback="http://madskills.com/public/xml/rss/module/pingback/" xmlns:trackback="http://madskills.com/public/xml/rss/module/trackback/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0">
  <channel>
    <title>Write Now ... in the world of Technical Communication - Composition</title>
    <link>http://writtendesigns.com/blog/</link>
    <description>Current Happenings in the World of Training and Technical Communication</description>
    <language>en-us</language>
    <copyright>Libby Craver dba Written Designs</copyright>
    <lastBuildDate>Thu, 14 May 2009 16:39:04 GMT</lastBuildDate>
    <generator>newtelligence dasBlog 2.1.8102.813</generator>
    <managingEditor>blog@writtendesigns.com</managingEditor>
    <webMaster>blog@writtendesigns.com</webMaster>
    <item>
      <trackback:ping>http://writtendesigns.com/blog/Trackback.aspx?guid=2a146edd-1d04-4421-8bab-67655cbf4f01</trackback:ping>
      <pingback:server>http://writtendesigns.com/blog/pingback.aspx</pingback:server>
      <pingback:target>http://writtendesigns.com/blog/PermaLink,guid,2a146edd-1d04-4421-8bab-67655cbf4f01.aspx</pingback:target>
      <dc:creator>Libby</dc:creator>
      <wfw:comment>http://writtendesigns.com/blog/CommentView,guid,2a146edd-1d04-4421-8bab-67655cbf4f01.aspx</wfw:comment>
      <wfw:commentRss>http://writtendesigns.com/blog/SyndicationService.asmx/GetEntryCommentsRss?guid=2a146edd-1d04-4421-8bab-67655cbf4f01</wfw:commentRss>
      <title>Discovering Your Product's Voice</title>
      <guid isPermaLink="false">http://writtendesigns.com/blog/PermaLink,guid,2a146edd-1d04-4421-8bab-67655cbf4f01.aspx</guid>
      <link>http://writtendesigns.com/blog/2009/05/14/DiscoveringYourProductsVoice.aspx</link>
      <pubDate>Thu, 14 May 2009 16:39:04 GMT</pubDate>
      <description>&lt;p&gt;
&lt;span lang=EN style="FONT-SIZE: 10pt; FONT-FAMILY: 'Verdana','sans-serif'; mso-ansi-language: EN"&gt;&lt;font color=#000000&gt;&lt;font face=Tahoma&gt;&lt;?xml:namespace prefix = o ns = "urn:schemas-microsoft-com:office:office" /&gt;Writers
often hear about “discovering your voice” when writing fiction. After all, the challenge
of fiction writers is to craft a story that is compelling, interesting, and dynamic.
Your characters must be likable; your readers must be able to relate to them or else
they will simply set your story aside for something more interesting. The voice in
fiction is often your character’s or narrator’s voice. It is that voice, the tone,
the choice of words, how those words are arranged into sentences, that convey the
deeper nuances within good fiction.&lt;o:p&gt;&lt;/o:p&gt;
&lt;/font&gt;&lt;/font&gt;&lt;/span&gt;
&lt;/p&gt;
&lt;p&gt;
&lt;span lang=EN style="FONT-SIZE: 10pt; FONT-FAMILY: 'Verdana','sans-serif'; mso-ansi-language: EN"&gt;&lt;font color=#000000&gt;&lt;font face=Tahoma&gt;I
am an avid reader. I revel in delightful, compelling fiction yet my attention can
be equally captured by the solid, thought-provoking prose in a non-fiction novel.
Good non-fiction has a compelling voice else there would be very few of us who continued
to buy non-fiction. 
&lt;o:p&gt;&lt;/o:p&gt;
&lt;/font&gt;&lt;/font&gt;&lt;/span&gt;
&lt;/p&gt;
&lt;p&gt;
&lt;span lang=EN style="FONT-SIZE: 10pt; FONT-FAMILY: 'Verdana','sans-serif'; mso-ansi-language: EN"&gt;&lt;font color=#000000&gt;&lt;font face=Tahoma&gt;Enter
technical writing. Technical writing is non-fiction writing, yet many people (both
companies and consumers alike) treat their technical documentation as an afterthought
-“&lt;em&gt;We have to document our product because we need to offer online help, user guides,
etc. But we know our customers rarely use them.”&lt;/em&gt; Why is it that customer’s shy
away from the technical documentation offered with products and services?&lt;o:p&gt;&lt;/o:p&gt;
&lt;/font&gt;&lt;/font&gt;&lt;/span&gt;
&lt;/p&gt;
&lt;p&gt;
&lt;span lang=EN style="FONT-SIZE: 10pt; FONT-FAMILY: 'Verdana','sans-serif'; mso-ansi-language: EN"&gt;&lt;font color=#000000&gt;&lt;font face=Tahoma&gt;I
think it comes down to voice. Let’s face it, most technical documents are boring.
We, as technical writers, try to spice things up, but there are only so many ways
you can say “Now, click Next.” Too often, companies are in a rush to get their documentation
out with their products. This causes writers to rush – they do their best at getting
the information down on paper but have little time to consider the voice of the whole
publication. They’re just happy when they meet the ever looming deadline. The documentation
gets out, hardly ever gets read, and customer service continues to receive the same
types of calls in spite of those issues being thoroughly documented.&lt;o:p&gt;&lt;/o:p&gt;
&lt;/font&gt;&lt;/font&gt;&lt;/span&gt;
&lt;/p&gt;
&lt;p&gt;
&lt;span lang=EN style="FONT-SIZE: 10pt; FONT-FAMILY: 'Verdana','sans-serif'; mso-ansi-language: EN"&gt;&lt;font color=#000000&gt;&lt;font face=Tahoma&gt;Now
imagine how things might change if the application or service suddenly became a character.
You’d still explain all the technical details about your product. You’d still include
all the screen shots, tables and instructions, but the tone would be different. Your
product would become the main character and, as such, it would have a distinctive
voice. Maybe the voice is more familiar and includes current technology slang if your
audience is of a younger generation. Perhaps the voice is more formal, but concise
and friendly, for a corporate business audience. Either way, the product takes on
its own persona. Your writers have the ability to include more details, tidbit, and
side bars about how the application works, its quirks, and, ultimately, its power.
The documentation becomes an extension of the product itself instead of simply an
afterthought. 
&lt;o:p&gt;&lt;/o:p&gt;
&lt;/font&gt;&lt;/font&gt;&lt;/span&gt;
&lt;/p&gt;
&lt;p&gt;
&lt;span lang=EN style="FONT-SIZE: 10pt; LINE-HEIGHT: 115%; FONT-FAMILY: 'Verdana','sans-serif'; mso-ansi-language: EN; mso-fareast-font-family: Calibri; mso-fareast-theme-font: minor-latin; mso-bidi-font-family: 'Times New Roman'; mso-bidi-theme-font: minor-bidi; mso-fareast-language: EN-US; mso-bidi-language: AR-SA"&gt;&lt;font face=Tahoma color=#000000&gt;Once
the documentation becomes an integral part of your product, you’ve opened up a whole
new realm of possibilities. High-quality, comprehensive documentation, tutorials,
and training materials can then become revenue-generating tools that could set you
apart in your industry. Your documentation becomes an integral part of your business,
driving sales and providing actual ROI to both you and your clients. Your customer
service related calls are reduced. Your clients have more successful implementations
and adoptions of your products. In short, you’ve reduced overhead while boosting sales
– all because you discovered your product’s voice.&lt;/font&gt;&lt;/span&gt;
&lt;/p&gt;
&lt;img width="0" height="0" src="http://writtendesigns.com/blog/aggbug.ashx?id=2a146edd-1d04-4421-8bab-67655cbf4f01" /&gt;</description>
      <comments>http://writtendesigns.com/blog/CommentView,guid,2a146edd-1d04-4421-8bab-67655cbf4f01.aspx</comments>
      <category>Composition</category>
      <category>Technical Writing</category>
    </item>
  </channel>
</rss>