<?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>Brain Traffic Blog &#187; Add new tag</title>
	<atom:link href="http://blog.braintraffic.com/tag/add-new-tag/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.braintraffic.com</link>
	<description>Just another WordPress weblog</description>
	<lastBuildDate>Thu, 29 Jul 2010 22:05:04 +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>5 Tips on Working with a Style Guide</title>
		<link>http://blog.braintraffic.com/2009/07/5-tips-on-working-with-a-style-guide/</link>
		<comments>http://blog.braintraffic.com/2009/07/5-tips-on-working-with-a-style-guide/#comments</comments>
		<pubDate>Fri, 31 Jul 2009 17:07:40 +0000</pubDate>
		<dc:creator>Elizabeth Saloka</dc:creator>
				<category><![CDATA[Content Strategy]]></category>
		<category><![CDATA[Editorial Strategy]]></category>
		<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[Web Writing]]></category>
		<category><![CDATA[Add new tag]]></category>

		<guid isPermaLink="false">http://blog.braintraffic.com/?p=520</guid>
		<description><![CDATA[Don't let your style guide derail your sane train. Bone up on these tried-and-true tips.]]></description>
			<content:encoded><![CDATA[<p>When used correctly, your style guide can be a helpful tool.&nbsp; When used incorrectly, it can cause confusion and suck up time.</p>
<p>Don&rsquo;t let your style guide derail your sane train! Bone up on these tried-and-true tips:</p>
<p><strong>1.&nbsp;&nbsp;&nbsp; Don&rsquo;t put it off.</strong> Always have your style guide set before you start writing.&nbsp; A style guide will help you establish, guide and rein in all stakeholder expectations over the course of the project.</p>
<p>Whatever you do, don&rsquo;t fool yourself into believing you can write now and create your style guide later. You probably won&rsquo;t. And if you do, rest assured, it&rsquo;ll be a painful and messy process.</p>
<p><strong>Tip: </strong>If you already have a style guide, give it a good once-over. What should change, if anything? What should remain the same? If you&rsquo;ve found yourself ignoring major sections of the style guide in the past, consider updating it. A tight, clean style guide is a happy style guide!</p>
<p><strong>2.&nbsp;&nbsp;&nbsp; Make sure you &ldquo;get it&rdquo; get it.</strong> Don&rsquo;t make assumptions about your style guide. If anything seems wonky, illogical, or even just &ldquo;off,&rdquo; clarify it. That goes double if other people are going to be using it, too.</p>
<p><strong>Tip: </strong>Everything&rsquo;s relative. Words especially. Nail down slippery terms by defining what each one means to you. If you&rsquo;re going for a &ldquo;conversational&rdquo; tone, put together a comparison chart:</p>
<p><!--[if gte mso 9]&gt;--></p>
<p style="text-align: center;">&nbsp;<strong>Conversational is &#8230;</strong></p>
<table width="300" cellspacing="1" cellpadding="1" border="1" align="center">
<tbody>
<tr>
<td><strong>More Like<br />
            </strong></td>
<td><strong>Less Like</strong></td>
</tr>
<tr>
<td>For reals.</td>
<td>In all seriousness.</td>
</tr>
<tr>
<td>It&#8217;s off the hook.</td>
<td>It&#8217;s extraordinary.</td>
</tr>
<tr>
<td>Cool it.</td>
<td>Patience is a virtue.</td>
</tr>
<tr>
<td>Give a shout.</td>
<td>Contact customer service.</td>
</tr>
</tbody>
</table>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p><strong>3.&nbsp;&nbsp;&nbsp; Bob for phrases.</strong> Okay, so, you&rsquo;ve nailed down the definition of conversational. Great. Now, go a step further.&nbsp; Hunt down real-world examples of conversational copy. Websites, blogs, Twitter feeds&mdash;they&rsquo;re all easily accessible content mines. When you see a turn of phrase you like, copy and paste that baby into a spreadsheet.</p>
<p>In a nutshell, build out the left-hand column of the diagram above.</p>
<p>&nbsp;</p>
<table width="300" cellspacing="1" cellpadding="1" border="1" align="center">
<tbody>
<tr>
<td><strong>Word Bank</strong></td>
</tr>
<tr>
<td>For reals</td>
</tr>
<tr>
<td>It&#8217;s off the hook.</td>
</tr>
<tr>
<td>Cool it.</td>
</tr>
<tr>
<td>Give a shout.</td>
</tr>
<tr>
<td>Raise the roof.</td>
</tr>
<tr>
<td>Don&#8217;t sweat the small stuff.</td>
</tr>
<tr>
<td>Sandwich is &quot;wow&quot; spelled incorrectly.</td>
</tr>
</tbody>
</table>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p><!--[if gte mso 9]&gt;--><!--[if gte mso 10]&gt;--><strong>Tip: </strong>The word bank is supposed to serve as inspiration. You should not copy phrases verbatim from your word bank into your content. In other words, don&rsquo;t plagiarize.</p>
<p><strong><br />
4.&nbsp;&nbsp;&nbsp; Check in. </strong>After you&rsquo;ve revised your style guide, run through it again. Make sure you&rsquo;re on board before proceeding. This might seem tedious. And time-consuming. That&rsquo;s because it is.&nbsp; But, it&rsquo;s the only, only, only way to stay on point.</p>
<p><strong>Tip:</strong> When revising a style guide (especially if you&rsquo;re not the person who created it) give justifications for your changes. This can be a short intro paragraph, or comments in the word document. Or, it could simply be verbal. Whatever you do, though, justify. <br />
<strong><br />
5.&nbsp;&nbsp;&nbsp; Honor and obey your style guide. </strong>Inevitably, maybe after a few happy years with your style guide, you will see another one. It will appear fancy and wonderful. And you will think, &ldquo;Hey, no fair! I want a fancy and wonderful style guide.&rdquo;</p>
<p>You will be tempted to stray. DON&rsquo;T. Stay the course. Ditching your style guide mid-project, or&mdash;dread of all dreads!&mdash;near the end of a project, will only lead to heartbreak.&nbsp;</p>
<p><strong>Tip: </strong>If you&rsquo;re working on an ongoing project, and you&rsquo;re not happy with the style guide, consider revising your style guide for the next major content rollout.&nbsp;</p>
<p>&nbsp;</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.braintraffic.com/2009/07/5-tips-on-working-with-a-style-guide/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
	</channel>
</rss>
