<?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>Writeclick</title>
	
	<link>http://www.writeclick.co.nz</link>
	<description>Content strategy, web writing &amp; website optimisation - Wellington &amp; Auckland New Zealand</description>
	<lastBuildDate>Sat, 05 May 2012 01:05:23 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
		<atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="self" type="application/rss+xml" href="http://feeds.feedburner.com/writeclicknz" /><feedburner:info uri="writeclicknz" /><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="hub" href="http://pubsubhubbub.appspot.com/" /><item>
		<title>UXAustralia here we come!</title>
		<link>http://feedproxy.google.com/~r/writeclicknz/~3/v1bW8kL0DUw/</link>
		<comments>http://www.writeclick.co.nz/blog/uxaustralia-here-we-come/#comments</comments>
		<pubDate>Sat, 05 May 2012 00:57:55 +0000</pubDate>
		<dc:creator>Melua</dc:creator>
				<category><![CDATA[Blog]]></category>
		<category><![CDATA[Web content strategy]]></category>

		<guid isPermaLink="false">http://www.writeclick.co.nz/?p=1328</guid>
		<description><![CDATA[We will be launching our new content strategy workshop - Content Clinic: Making Content Priority One - at UXAustralia,  Brisbane, on 28 August. It's a one-day hands-on workshop to help you solve your organisation's content conundrums and streamline content development. ]]></description>
			<content:encoded><![CDATA[<p>We will be launching our new content strategy workshop &#8211; Content Clinic: Making Content Priority One &#8211; at UXAustralia,  Brisbane, on 28 August. It&#8217;s a one-day hands-on workshop to help you solve your organisation&#8217;s content conundrums and streamline content development.</p>
<p>The workshop &#8211; hosted in collaboration with Martin Bulmer from Optimal Usability &#8211; will join the dots between UX and content strategy, and help you put a proven content strategy process to work on real projects.</p>
<p>The day will be particularly useful for people about to start content development for a large new website or redesign. Get a head-start here!</p>
<p><a title="Content Clinic at UXAustralia 2012" href="http://www.uxaustralia.com.au/uxaustralia-2012/content-clinic" target="_blank">Content Clinic: Making Content Priority One &#8211; UXAustralia 28 August 2012 </a></p>
<img src="http://feeds.feedburner.com/~r/writeclicknz/~4/v1bW8kL0DUw" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://www.writeclick.co.nz/blog/uxaustralia-here-we-come/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		<feedburner:origLink>http://www.writeclick.co.nz/blog/uxaustralia-here-we-come/</feedburner:origLink></item>
		<item>
		<title>Writing for mobile and apps</title>
		<link>http://feedproxy.google.com/~r/writeclicknz/~3/KF7aCbSkMf4/</link>
		<comments>http://www.writeclick.co.nz/blog/writing-for-mobile-and-apps/#comments</comments>
		<pubDate>Mon, 23 Apr 2012 21:41:32 +0000</pubDate>
		<dc:creator>Duncan</dc:creator>
				<category><![CDATA[Blog]]></category>
		<category><![CDATA[Mobile content]]></category>

		<guid isPermaLink="false">http://www.writeclick.co.nz/?p=1323</guid>
		<description><![CDATA[When we read online we’re impatient, often with a job to do, and constantly enticed to click away. So to quickly give people what they want online, web writing is brief, task focused, structured for ‘skimmers’ and optimised for search engines. 

All this is true of mobile writing but more so. The smaller the screen, the sharper the copy.]]></description>
			<content:encoded><![CDATA[<p>Anyone who has done web writing training will know a few things set web writing apart from print. Most importantly, it’s how we behave: we read differently online to the way we read print.</p>
<p>When we read online we’re impatient, often with a job to do, and constantly enticed to click away. So to quickly give people what they want online, web writing is brief, task focused, structured for ‘skimmers’ and optimised for search engines.</p>
<p>All this is true of mobile writing but more so. The smaller the screen, the sharper the copy.</p>
<h3>Mobile content characteristics</h3>
<p>Ryan Matzner on Mashable did a great job of summarising how we use mobile content and how it needs to be presented. Mobile use is defined by ‘pockets of use’ – dipping in and out when you have just a moment to spare. Like when you’re waiting at traffic lights (is that legal?), standing in a queue, or waiting for your kid’s turn at ballet recitals.</p>
<p>Then there’s the constant offline distractions, like that nattily dressed person passing you in the street or sale signs in shop windows. Mobile content needs to be precise, concise and designed to grab attention.</p>
<h3>How to write content for mobile</h3>
<p>Matzner lists a few salient points for those of us charged with creating mobile content. Again, many of these apply to web writing but are amplified when the screen size is minimised.</p>
<p>It’s the usual good stuff: task-focused copy, re–tweetable headings, and ‘frontloaded’ content. Wellington writer Rachel McAlpine popularised this term years ago and it’s more relevant than ever today. Twitter is an ideal training ground for mobile writers!</p>
<p>Matzner’s blog provides a great summary of the demands placed on content strategists and copywriters in a mobile world.</p>
<p>Read the full article on <a href="http://mashable.com/2011/06/14/optimize-mobile-marketing/">Mashable</a></p>
<img src="http://feeds.feedburner.com/~r/writeclicknz/~4/KF7aCbSkMf4" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://www.writeclick.co.nz/blog/writing-for-mobile-and-apps/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://www.writeclick.co.nz/blog/writing-for-mobile-and-apps/</feedburner:origLink></item>
		<item>
		<title>Content strategy makes Sorted more sorted</title>
		<link>http://feedproxy.google.com/~r/writeclicknz/~3/m5z0-aTClWM/</link>
		<comments>http://www.writeclick.co.nz/blog/content-strategy-makes-sorted-more-sorted/#comments</comments>
		<pubDate>Tue, 20 Mar 2012 20:50:44 +0000</pubDate>
		<dc:creator>Melua</dc:creator>
				<category><![CDATA[Blog]]></category>
		<category><![CDATA[Web content strategy]]></category>

		<guid isPermaLink="false">http://www.writeclick.co.nz/?p=1294</guid>
		<description><![CDATA[With the shiny new Sorted website up and running we thought it was a good time to talk to the brains behind the redesign about why he chose a content strategy approach - and how it paid off. ]]></description>
			<content:encoded><![CDATA[<p>We recently had the pleasure of helping the Commission for Financial Literacy &amp; Retirement Income (formerly the Retirement Commission) develop content for their hugely popular Sorted website.</p>
<p>The project was user-centred and content-focused from the get-go. Content development was a breeze, thanks to the strategic approach of the Commission’s Content Manager Peter Johnston.</p>
<p>As the new Sorted (designed by <a href="http://www.chrometoaster.com/" target="_blank">Chrometoaster</a>) has just been launched we thought it was a good time to pick Peter’s brains about the value of a content strategy approach on this project.</p>
<h3><strong>What role did content strategy play in the redesign of the Sorted website?</strong></h3>
<p><strong> </strong><em>&#8220;It was all about taking a planned approach to things, making sure what the site was trying to do matched the Commission’s general business and marketing plans.</em></p>
<p><em>Content strategy came out of our marketing and business planning and the Content Strategy document itself reflects that. The Think, Shrink, Grow concept also came out of that planning. I think the planning process we went through as a team was the key – the strategy document just captured our thinking.</em></p>
<p><em> </em></p>
<p><em> </em></p>
<p><em>The Sorted project was focused on the redevelopment so the strategy wasn’t so much focused on ongoing maintenance, it was more high-level.&#8221; </em></p>
<h3><strong>What was involved in developing the strategy?</strong></h3>
<p>&#8220;<em>A lot of research, looking at our analytics and looking at overseas examples. We looked at what pages [on the old site] were most visited, what search terms were being used to find them.</em></p>
<p><em> </em></p>
<p><em>Any organisation that’s been around for a while has legacy content so it was a case of identifying what content was most used, and what content would be most useful.</em></p>
<p><em> </em></p>
<p><em>On the new site we made more use of links to authoritative sources rather than hosting it ourselves. It was all part of achieving content that was more sustainable.&#8221;<br />
</em></p>
<h3><strong>How did your content strategy influence the design and development process?</strong></h3>
<p><strong> </strong><em>&#8220;In terms of the IA process it was more a case of coming up with a high-level site structure. We decided we didn’t need card sorting and the like. We had feedback from users, examples from overseas, and evidence that people come looking for financial information when they need to – so, for example, it was important for the new ‘life events’ content stream to be there.</em></p>
<p><em>Previously the site was structured into categories like Debt and Investing but people don’t necessarily think that way. So we adopted a twin channel approach – A-Z guides, an open alphabetical listing of financial topics, and life events.</em></p>
<p><em> </em></p>
<p><em> </em></p>
<p><em>There’s also a more guided ‘Get sorted’ section for people who don’t know where to start. That’s where the Think, Shrink and Grow concept fits in.&#8221;<br />
</em></p>
<h3><strong>Content strategy is an emerging approach in New Zealand web development. How did you go about it?</strong></h3>
<p>&#8220;<strong> </strong><em>It’s all about taking a planned approach to content. Kristina Halvorson talks about the importance of governance and the need to think beyond launch date. You don’t want to create a huge amount of work down the track if you don’t have the resource to manage it. It’s about being realistic and sustainable.&#8221;<br />
</em></p>
<h3><strong>Did your content strategy make it easier to communicate what you wanted to your designers and web writers?</strong></h3>
<p>&#8220;<strong> </strong><em>In the old days content development would be crammed into the two weeks just before launching a new site. In the Sorted situation content planning was happening alongside the design planning and development thinking.</em></p>
<p><em>As soon as we had wireframes we engaged writers and got content organised. So when designs were signed off, content was ready for loading. So content was a year-long project.&#8221;</em></p>
<p><em> </em></p>
<p><em> </em></p>
<h3><strong>Why did you decide to take this approach? </strong></h3>
<p><em>&#8220;It was always our intent to do a content strategy. Professionally it was important to me, part of my professional development. I’d been to the Web Content 2010 conference in Chicago and read the books. If you’re the only person working on the content you may not need a strategy but if you’re getting others involved it’s very important.&#8221;<br />
</em></p>
<h3><strong>Do you think having a content strategy saved the Commission time, money, hassle or risk?</strong></h3>
<p>&#8220;<strong> </strong><em>Yes, it definitely saves risk for an organisation. It identified early on that certain resource was required and enabled us to plan for peer review processes so when the site went live we were confident everything had been reviewed.&#8221;<br />
</em></p>
<h3><strong>The Sorted Content Strategy was relatively brief – only three or four pages. We thought that was great!</strong></h3>
<p>&#8220;<strong> </strong><em>I’m a ‘less is more’ person and don’t have a big attention span for documents! I struggled initially with what a content strategy should look like. I tried to nut it down to key headings, what it needed to cover.</em></p>
<p><em>It didn’t need to cover everything because it sat alongside the content plan, where we mapped out each page, and a style guide which expanded on the key [content strategy] points. So the strategy gave an overview of structure but not the detail of the content plan.</em></p>
<p><em> </em></p>
<p><em> </em></p>
<p><em>And Chrometoaster had a detailed development plan, including numbering requirements and the like, and I didn’t want the Content Strategy to compete with that. Too much detail [in the Content Strategy] could have mucked that up.&#8221;<br />
</em></p>
<h3><strong>Do you think the project achieved what you wanted it to?</strong></h3>
<p>&#8220;<strong> </strong><em>Yes, everything went to plan. The content on the new site looks like it said it would on the tin – the content plan and page tables we created. And so far the feedback has been great!&#8221;</em></p>
<p><em> </em></p>
<h3><em> </em></h3>
<p>Post script: Peter has recently started a new position at Gareth Morgan Investments.</p>
<p>Check out the new <a href="https://www.sorted.org.nz/" target="_blank">Sorted</a></p>
<div id="_mcePaste" style="position: absolute; left: -10000px; top: 0px; width: 1px; height: 1px; overflow: hidden;"><!--[if gte mso 9]><xml> <w:WordDocument> <w:View>Normal</w:View> <w:Zoom>0</w:Zoom> <w:TrackMoves /> <w:TrackFormatting /> <w:PunctuationKerning /> <w:ValidateAgainstSchemas /> <w:SaveIfXMLInvalid>false</w:SaveIfXMLInvalid> <w:IgnoreMixedContent>false</w:IgnoreMixedContent> <w:AlwaysShowPlaceholderText>false</w:AlwaysShowPlaceholderText> <w:DoNotPromoteQF /> <w:LidThemeOther>EN-NZ</w:LidThemeOther> <w:LidThemeAsian>X-NONE</w:LidThemeAsian> <w:LidThemeComplexScript>X-NONE</w:LidThemeComplexScript> <w:Compatibility> <w:BreakWrappedTables /> <w:SnapToGridInCell /> <w:WrapTextWithPunct /> <w:UseAsianBreakRules /> <w:DontGrowAutofit /> <w:SplitPgBreakAndParaMark /> <w:DontVertAlignCellWithSp /> <w:DontBreakConstrainedForcedTables /> <w:DontVertAlignInTxbx /> <w:Word11KerningPairs /> <w:CachedColBalance /> </w:Compatibility> <w:BrowserLevel>MicrosoftInternetExplorer4</w:BrowserLevel> <m:mathPr> <m:mathFont m:val="Cambria Math" /> <m:brkBin m:val="before" /> <m:brkBinSub m:val=" " /> <m:smallFrac m:val="off" /> <m:dispDef /> <m:lMargin m:val="0" /> <m:rMargin m:val="0" /> <m:defJc m:val="centerGroup" /> <m:wrapIndent m:val="1440" /> <m:intLim m:val="subSup" /> <m:naryLim m:val="undOvr" /> </m:mathPr></w:WordDocument> </xml><![endif]--><!--[if gte mso 9]><xml> <w:LatentStyles DefLockedState="false" DefUnhideWhenUsed="true"   DefSemiHidden="true" DefQFormat="false" DefPriority="99"   LatentStyleCount="267"> <w:LsdException Locked="false" Priority="0" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Normal" /> <w:LsdException Locked="false" Priority="9" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="heading 1" /> <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 2" /> <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 3" /> <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 4" /> <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 5" /> <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 6" /> <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 7" /> <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 8" /> <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 9" /> <w:LsdException Locked="false" Priority="39" Name="toc 1" /> <w:LsdException Locked="false" Priority="39" Name="toc 2" /> <w:LsdException Locked="false" Priority="39" Name="toc 3" /> <w:LsdException Locked="false" Priority="39" Name="toc 4" /> <w:LsdException Locked="false" Priority="39" Name="toc 5" /> <w:LsdException Locked="false" Priority="39" Name="toc 6" /> <w:LsdException Locked="false" Priority="39" Name="toc 7" /> <w:LsdException Locked="false" Priority="39" Name="toc 8" /> <w:LsdException Locked="false" Priority="39" Name="toc 9" /> <w:LsdException Locked="false" Priority="35" QFormat="true" Name="caption" /> <w:LsdException Locked="false" Priority="10" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Title" /> <w:LsdException Locked="false" Priority="1" Name="Default Paragraph Font" /> <w:LsdException Locked="false" Priority="11" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Subtitle" /> <w:LsdException Locked="false" Priority="22" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Strong" /> <w:LsdException Locked="false" Priority="20" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Emphasis" /> <w:LsdException Locked="false" Priority="59" SemiHidden="false"    UnhideWhenUsed="false" Name="Table Grid" /> <w:LsdException Locked="false" UnhideWhenUsed="false" Name="Placeholder Text" /> <w:LsdException Locked="false" Priority="1" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="No Spacing" /> <w:LsdException Locked="false" Priority="60" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Shading" /> <w:LsdException Locked="false" Priority="61" SemiHidden="false"    UnhideWhenUsed="false" Name="Light List" /> <w:LsdException Locked="false" Priority="62" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Grid" /> <w:LsdException Locked="false" Priority="63" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 1" /> <w:LsdException Locked="false" Priority="64" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 2" /> <w:LsdException Locked="false" Priority="65" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 1" /> <w:LsdException Locked="false" Priority="66" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 2" /> <w:LsdException Locked="false" Priority="67" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 1" /> <w:LsdException Locked="false" Priority="68" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 2" /> <w:LsdException Locked="false" Priority="69" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 3" /> <w:LsdException Locked="false" Priority="70" SemiHidden="false"    UnhideWhenUsed="false" Name="Dark List" /> <w:LsdException Locked="false" Priority="71" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Shading" /> <w:LsdException Locked="false" Priority="72" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful List" /> <w:LsdException Locked="false" Priority="73" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Grid" /> <w:LsdException Locked="false" Priority="60" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Shading Accent 1" /> <w:LsdException Locked="false" Priority="61" SemiHidden="false"    UnhideWhenUsed="false" Name="Light List Accent 1" /> <w:LsdException Locked="false" Priority="62" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Grid Accent 1" /> <w:LsdException Locked="false" Priority="63" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 1 Accent 1" /> <w:LsdException Locked="false" Priority="64" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 2 Accent 1" /> <w:LsdException Locked="false" Priority="65" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 1 Accent 1" /> <w:LsdException Locked="false" UnhideWhenUsed="false" Name="Revision" /> <w:LsdException Locked="false" Priority="34" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="List Paragraph" /> <w:LsdException Locked="false" Priority="29" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Quote" /> <w:LsdException Locked="false" Priority="30" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Intense Quote" /> <w:LsdException Locked="false" Priority="66" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 2 Accent 1" /> <w:LsdException Locked="false" Priority="67" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 1 Accent 1" /> <w:LsdException Locked="false" Priority="68" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 2 Accent 1" /> <w:LsdException Locked="false" Priority="69" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 3 Accent 1" /> <w:LsdException Locked="false" Priority="70" SemiHidden="false"    UnhideWhenUsed="false" Name="Dark List Accent 1" /> <w:LsdException Locked="false" Priority="71" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Shading Accent 1" /> <w:LsdException Locked="false" Priority="72" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful List Accent 1" /> <w:LsdException Locked="false" Priority="73" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Grid Accent 1" /> <w:LsdException Locked="false" Priority="60" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Shading Accent 2" /> <w:LsdException Locked="false" Priority="61" SemiHidden="false"    UnhideWhenUsed="false" Name="Light List Accent 2" /> <w:LsdException Locked="false" Priority="62" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Grid Accent 2" /> <w:LsdException Locked="false" Priority="63" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 1 Accent 2" /> <w:LsdException Locked="false" Priority="64" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 2 Accent 2" /> <w:LsdException Locked="false" Priority="65" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 1 Accent 2" /> <w:LsdException Locked="false" Priority="66" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 2 Accent 2" /> <w:LsdException Locked="false" Priority="67" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 1 Accent 2" /> <w:LsdException Locked="false" Priority="68" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 2 Accent 2" /> <w:LsdException Locked="false" Priority="69" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 3 Accent 2" /> <w:LsdException Locked="false" Priority="70" SemiHidden="false"    UnhideWhenUsed="false" Name="Dark List Accent 2" /> <w:LsdException Locked="false" Priority="71" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Shading Accent 2" /> <w:LsdException Locked="false" Priority="72" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful List Accent 2" /> <w:LsdException Locked="false" Priority="73" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Grid Accent 2" /> <w:LsdException Locked="false" Priority="60" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Shading Accent 3" /> <w:LsdException Locked="false" Priority="61" SemiHidden="false"    UnhideWhenUsed="false" Name="Light List Accent 3" /> <w:LsdException Locked="false" Priority="62" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Grid Accent 3" /> <w:LsdException Locked="false" Priority="63" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 1 Accent 3" /> <w:LsdException Locked="false" Priority="64" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 2 Accent 3" /> <w:LsdException Locked="false" Priority="65" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 1 Accent 3" /> <w:LsdException Locked="false" Priority="66" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 2 Accent 3" /> <w:LsdException Locked="false" Priority="67" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 1 Accent 3" /> <w:LsdException Locked="false" Priority="68" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 2 Accent 3" /> <w:LsdException Locked="false" Priority="69" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 3 Accent 3" /> <w:LsdException Locked="false" Priority="70" SemiHidden="false"    UnhideWhenUsed="false" Name="Dark List Accent 3" /> <w:LsdException Locked="false" Priority="71" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Shading Accent 3" /> <w:LsdException Locked="false" Priority="72" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful List Accent 3" /> <w:LsdException Locked="false" Priority="73" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Grid Accent 3" /> <w:LsdException Locked="false" Priority="60" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Shading Accent 4" /> <w:LsdException Locked="false" Priority="61" SemiHidden="false"    UnhideWhenUsed="false" Name="Light List Accent 4" /> <w:LsdException Locked="false" Priority="62" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Grid Accent 4" /> <w:LsdException Locked="false" Priority="63" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 1 Accent 4" /> <w:LsdException Locked="false" Priority="64" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 2 Accent 4" /> <w:LsdException Locked="false" Priority="65" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 1 Accent 4" /> <w:LsdException Locked="false" Priority="66" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 2 Accent 4" /> <w:LsdException Locked="false" Priority="67" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 1 Accent 4" /> <w:LsdException Locked="false" Priority="68" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 2 Accent 4" /> <w:LsdException Locked="false" Priority="69" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 3 Accent 4" /> <w:LsdException Locked="false" Priority="70" SemiHidden="false"    UnhideWhenUsed="false" Name="Dark List Accent 4" /> <w:LsdException Locked="false" Priority="71" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Shading Accent 4" /> <w:LsdException Locked="false" Priority="72" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful List Accent 4" /> <w:LsdException Locked="false" Priority="73" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Grid Accent 4" /> <w:LsdException Locked="false" Priority="60" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Shading Accent 5" /> <w:LsdException Locked="false" Priority="61" SemiHidden="false"    UnhideWhenUsed="false" Name="Light List Accent 5" /> <w:LsdException Locked="false" Priority="62" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Grid Accent 5" /> <w:LsdException Locked="false" Priority="63" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 1 Accent 5" /> <w:LsdException Locked="false" Priority="64" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 2 Accent 5" /> <w:LsdException Locked="false" Priority="65" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 1 Accent 5" /> <w:LsdException Locked="false" Priority="66" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 2 Accent 5" /> <w:LsdException Locked="false" Priority="67" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 1 Accent 5" /> <w:LsdException Locked="false" Priority="68" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 2 Accent 5" /> <w:LsdException Locked="false" Priority="69" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 3 Accent 5" /> <w:LsdException Locked="false" Priority="70" SemiHidden="false"    UnhideWhenUsed="false" Name="Dark List Accent 5" /> <w:LsdException Locked="false" Priority="71" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Shading Accent 5" /> <w:LsdException Locked="false" Priority="72" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful List Accent 5" /> <w:LsdException Locked="false" Priority="73" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Grid Accent 5" /> <w:LsdException Locked="false" Priority="60" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Shading Accent 6" /> <w:LsdException Locked="false" Priority="61" SemiHidden="false"    UnhideWhenUsed="false" Name="Light List Accent 6" /> <w:LsdException Locked="false" Priority="62" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Grid Accent 6" /> <w:LsdException Locked="false" Priority="63" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 1 Accent 6" /> <w:LsdException Locked="false" Priority="64" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 2 Accent 6" /> <w:LsdException Locked="false" Priority="65" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 1 Accent 6" /> <w:LsdException Locked="false" Priority="66" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 2 Accent 6" /> <w:LsdException Locked="false" Priority="67" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 1 Accent 6" /> <w:LsdException Locked="false" Priority="68" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 2 Accent 6" /> <w:LsdException Locked="false" Priority="69" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 3 Accent 6" /> <w:LsdException Locked="false" Priority="70" SemiHidden="false"    UnhideWhenUsed="false" Name="Dark List Accent 6" /> <w:LsdException Locked="false" Priority="71" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Shading Accent 6" /> <w:LsdException Locked="false" Priority="72" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful List Accent 6" /> <w:LsdException Locked="false" Priority="73" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Grid Accent 6" /> <w:LsdException Locked="false" Priority="19" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Subtle Emphasis" /> <w:LsdException Locked="false" Priority="21" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Intense Emphasis" /> <w:LsdException Locked="false" Priority="31" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Subtle Reference" /> <w:LsdException Locked="false" Priority="32" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Intense Reference" /> <w:LsdException Locked="false" Priority="33" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Book Title" /> <w:LsdException Locked="false" Priority="37" Name="Bibliography" /> <w:LsdException Locked="false" Priority="39" QFormat="true" Name="TOC Heading" /> </w:LatentStyles> </xml><![endif]--><!--[if gte mso 10]> <mce:style><!   /* Style Definitions */  table.MsoNormalTable 	{mso-style-name:"Table Normal"; 	mso-tstyle-rowband-size:0; 	mso-tstyle-colband-size:0; 	mso-style-noshow:yes; 	mso-style-priority:99; 	mso-style-qformat:yes; 	mso-style-parent:""; 	mso-padding-alt:0cm 5.4pt 0cm 5.4pt; 	mso-para-margin:0cm; 	mso-para-margin-bottom:.0001pt; 	mso-pagination:widow-orphan; 	font-size:11.0pt; 	font-family:"Calibri","sans-serif"; 	mso-ascii-font-family:Calibri; 	mso-ascii-theme-font:minor-latin; 	mso-fareast-font-family:"Times New Roman"; 	mso-fareast-theme-font:minor-fareast; 	mso-hansi-font-family:Calibri; 	mso-hansi-theme-font:minor-latin; 	mso-bidi-font-family:"Times New Roman"; 	mso-bidi-theme-font:minor-bidi;} --> <!--[endif] --></p>
<p class="MsoNormal">We recently had the pleasure of helping the Commission for Financial Literacy &amp; Retirement Income (formerly the Retirement Commission) develop content for their hugely popular Sorted website.</p>
<p class="MsoNormal">The project was user-centred and content-focused from the get-go. Content development was a joy on this project, thanks to the strategic approach of the Commission’s Content Manager Peter Johnston.</p>
<p class="MsoNormal">The new Sorted site (designed by Chrometoaster) has just been launched so we thought it was a good time to pick Peter’s brains about the value of a content strategy approach.</p>
<p class="MsoNormal"><strong style="mso-bidi-font-weight:normal">What role did content strategy play in the redesign of the Sorted website?</strong></p>
<p class="MsoNormal"><em style="mso-bidi-font-style:normal">It was all about taking a planned approach to things, making sure what the site was trying to do matched the Commission’s general business and marketing plans.</em></p>
<p><em style="mso-bidi-font-style:normal"> </em><em style="mso-bidi-font-style:normal">Content strategy came out of our marketing and business planning and the Content Strategy document itself reflects that. The Think, Shrink, Grow concept also came out of that planning. </em></p>
<p class="MsoNormal"><em style="mso-bidi-font-style:normal">I think the planning process we went through as a team was the key – the strategy document just captured our thinking. </em></p>
<p class="MsoNormal"><em style="mso-bidi-font-style:normal">The Sorted project was focused on the redevelopment so the strategy wasn’t so much focused on ongoing maintenance, it was more high-level. </em></p>
<p class="MsoNormal"><strong style="mso-bidi-font-weight:normal">What was involved in developing the strategy?</strong></p>
<p class="MsoNormal"><em style="mso-bidi-font-style:normal">A lot of research, looking at our analytics and looking at overseas examples. We looked at what pages [on the old site] were most visited, what search terms were being used to find them. </em></p>
<p class="MsoNormal"><em style="mso-bidi-font-style:normal">Any organisation that’s been around for a while has legacy content so it was a case of identifying what content was most used, and what content would be most useful. </em></p>
<p class="MsoNormal"><em style="mso-bidi-font-style:normal">On the new site we made more use of links to authoritative sources rather than hosting it ourselves. It was all part of achieving content that was more sustainable. </em></p>
<p class="MsoNormal"><strong style="mso-bidi-font-weight:normal">How did your content strategy influence the design and development process?</strong></p>
<p class="MsoNormal"><em style="mso-bidi-font-style:normal">In terms of the IA process it was more a case of coming up with a high-level site structure. We decided we didn’t need card sorting and the like. We had feedback from users, examples from overseas, and evidence that people come looking for financial information when they need to – so, for example, it was important for the new ‘life events’ content stream to be there. </em></p>
<p class="MsoNormal"><em style="mso-bidi-font-style:normal">Previously the site was structured into categories like Debt and Investing but people don’t necessarily think that way. So we adopted a twin channel approach – A-Z guides, an open alphabetical listing of financial topics, and life events. There’s also a more guided ‘Get sorted’ section for people who don’t know where to start. That’s where the Think, Shrink and Grow concept fits in.</em></p>
<p class="MsoNormal"><strong style="mso-bidi-font-weight:normal">Content strategy is an emerging approach in New Zealand web development. How did you go about it?</strong></p>
<p class="MsoNormal"><em style="mso-bidi-font-style:normal">It’s all about taking a planned approach to content. Kristina Halvorson talks about the importance of governance and the need to think beyond launch date. You don’t want to create a huge amount of work down the track if you don’t have the resource to manage it. It’s about being realistic and sustainable. </em></p>
<p class="MsoNormal"><strong style="mso-bidi-font-weight:normal">Did your content strategy make it easier to communicate what you wanted to your designers and web writers?</strong></p>
<p class="MsoNormal"><em style="mso-bidi-font-style:normal">In the old days content development would be crammed into the two weeks just before launching a new site. In the Sorted situation content planning was happening alongside the design planning and development thinking. </em></p>
<p class="MsoNormal"><em style="mso-bidi-font-style:normal">As soon as we had wireframes we engaged writers and got content organised. So when designs were signed off, content was ready for loading. So content was a year-long project. </em></p>
<p class="MsoNormal"><strong style="mso-bidi-font-weight:normal">Why did you decide to take this approach? </strong></p>
<p class="MsoNormal"><em style="mso-bidi-font-style:normal">It was always our intent to do a content strategy. Professionally it was important to me, part of my professional development. I’d been to the Web Content 2010 conference in Chicago and read the books. If you’re the only person working on the content you may not need a strategy but if you’re getting others involved it’s very important. </em></p>
<p class="MsoNormal"><strong style="mso-bidi-font-weight:normal">Do you think having a content strategy saved the Commission time, money, hassle or risk? </strong></p>
<p class="MsoNormal"><em style="mso-bidi-font-style:normal">Yes, it definitely saves risk for an organisation. It identified early on that certain resource was required and enabled us to plan for peer review processes so when the site went live we were confident everything had been reviewed.</em></p>
<p class="MsoNormal"><strong style="mso-bidi-font-weight:normal">The Sorted Content Strategy was relatively brief – only three or four pages. We thought that was great!</strong></p>
<p class="MsoNormal"><em style="mso-bidi-font-style:normal">I’m a ‘less is more’ person and don’t have a big attention span for documents! I struggled initially with what a content strategy should look like. I tried to nut it down to key headings, what it needed to cover. And it didn’t need to cover everything because it sat alongside the content plan, where we mapped out each page, and a style guide which expanded on the key [content strategy] points. So the strategy gave an overview of structure but not the detail of the content plan. </em></p>
<p class="MsoNormal"><em style="mso-bidi-font-style:normal">And Chrometoaster had a detailed development plan, including numbering requirements and the like, and I didn’t want the Content Strategy to compete with that. Too much detail [in the Content Strategy] could have mucked that up. </em></p>
<p class="MsoNormal"><strong style="mso-bidi-font-weight:normal">Do you think the project achieved what you wanted it to? </strong></p>
<p class="MsoNormal"><em style="mso-bidi-font-style:normal">Yes, everything went to plan. The content on the new site looks like it said it would on the tin – the content plan and page tables we created. And so far the feedback has been great! </em></p>
<p class="MsoNormal"><strong style="mso-bidi-font-weight:normal">Thanks for your time. </strong></p>
<p class="MsoNormal"><em style="mso-bidi-font-style:normal">Post script: Peter has recently started a new position at Gareth Morgan Investments. <span style="mso-spacerun:yes"> </span></em></p>
</div>
<img src="http://feeds.feedburner.com/~r/writeclicknz/~4/m5z0-aTClWM" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://www.writeclick.co.nz/blog/content-strategy-makes-sorted-more-sorted/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://www.writeclick.co.nz/blog/content-strategy-makes-sorted-more-sorted/</feedburner:origLink></item>
		<item>
		<title>Sorted</title>
		<link>http://feedproxy.google.com/~r/writeclicknz/~3/fA6D3LPLkAM/</link>
		<comments>http://www.writeclick.co.nz/our-work/government/sorted/#comments</comments>
		<pubDate>Tue, 13 Mar 2012 21:24:55 +0000</pubDate>
		<dc:creator>Melua</dc:creator>
				<category><![CDATA[Government]]></category>

		<guid isPermaLink="false">http://www.writeclick.co.nz/?p=1284</guid>
		<description><![CDATA[Sorted, the hugely popular independent money guide, is now even better. Working with the Commission for Financial Literacy and Retirement Income we wrote financial guides in plain English to help Kiwis of all ages and stages get sorted. Sorted]]></description>
			<content:encoded><![CDATA[<p><img class="aligncenter size-full wp-image-1285" title="Sorted" src="http://www.writeclick.co.nz/wp-content/uploads/2012/03/Sorted_Mouse1.png" alt="Sorted" width="116" height="140" /><br />
Sorted, the hugely popular independent money guide, is now even better. Working with the Commission for Financial Literacy and Retirement Income we wrote financial guides in plain English to help Kiwis of all ages and stages get sorted.</p>
<p><a href="https://www.sorted.org.nz/" target="_blank">Sorted </a></p>
<img src="http://feeds.feedburner.com/~r/writeclicknz/~4/fA6D3LPLkAM" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://www.writeclick.co.nz/our-work/government/sorted/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://www.writeclick.co.nz/our-work/government/sorted/</feedburner:origLink></item>
		<item>
		<title>Call it what you will – content strategy is legit</title>
		<link>http://feedproxy.google.com/~r/writeclicknz/~3/4o-HLf8Hae4/</link>
		<comments>http://www.writeclick.co.nz/blog/call-it-what-you-will-content-strategy-is-legit/#comments</comments>
		<pubDate>Wed, 29 Feb 2012 00:49:05 +0000</pubDate>
		<dc:creator>Melua</dc:creator>
				<category><![CDATA[Blog]]></category>
		<category><![CDATA[Web content strategy]]></category>

		<guid isPermaLink="false">http://www.writeclick.co.nz/?p=1266</guid>
		<description><![CDATA[Gerry McGovern posted an interesting blog this week suggesting that if you want to be taken seriously by senior managers, don’t talk about content.]]></description>
			<content:encoded><![CDATA[<p>Gerry McGovern posted an interesting blog this week suggesting that if you want to be taken seriously by senior managers, don’t talk about content.</p>
<p>‘Content strategy’ in his view is a red herring, a distraction from the real business of helping clients with their online business. It also, he says, encourages silos within the digital production world. I kinda agree.</p>
<p>Yes we should be focusing on strategic content &#8211; if it&#8217;s not strategic what are we doing? &#8211; and if you’re talking to a senior manager by all means talk their language.</p>
<p>But the tag serves a useful purpose for all the web designers, developers, UX people and writers that make websites.</p>
<p>‘Content strategy’ is short-hand for a way of working towards happy businesses and happy web users. And the constant conversation amongst the people who ‘do’ content strategy every day is evidence of the need for a label, because a lot of the time it’s about process.</p>
<p>What is the best way to give people what they want online, within your client’s budget and timeframe? If you can answer this for a client they will take you seriously, whether you call it content strategy or not.</p>
<p>Content strategy deserves all the focus and attention right now because it is changing the way web design and communication projects happen. Can&#8217;t wait to see what Kristina Halvorson et al have to say!</p>
<p><a href="http://www.gerrymcgovern.com/nt/2012/nt-2012-02-27-Content-strategy.htm" target="_blank">Gerry McGovern&#8217;s blog </a></p>
<img src="http://feeds.feedburner.com/~r/writeclicknz/~4/4o-HLf8Hae4" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://www.writeclick.co.nz/blog/call-it-what-you-will-content-strategy-is-legit/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://www.writeclick.co.nz/blog/call-it-what-you-will-content-strategy-is-legit/</feedburner:origLink></item>
		<item>
		<title>Medsyn</title>
		<link>http://feedproxy.google.com/~r/writeclicknz/~3/UmCbT5k_k_M/</link>
		<comments>http://www.writeclick.co.nz/our-work/business/medsyn/#comments</comments>
		<pubDate>Tue, 21 Feb 2012 03:27:43 +0000</pubDate>
		<dc:creator>Melua</dc:creator>
				<category><![CDATA[Business]]></category>

		<guid isPermaLink="false">http://www.writeclick.co.nz/?p=1227</guid>
		<description><![CDATA[&#8220;Writeclick did a great job on the copy for our newly branded website. From a home-grown website, we now have a professional looking one. Fast turnaround was part of the service, thanks.&#8221; Craig Evans. Medsyn]]></description>
			<content:encoded><![CDATA[<p><img class="aligncenter size-full wp-image-1228" title="Medsyn" src="http://www.writeclick.co.nz/wp-content/uploads/2012/02/Medsyn_logo.jpg" alt="Medsyn" width="150" height="185" /></p>
<p>&#8220;Writeclick did a great job on the copy for our newly branded website. From a home-grown website, we now have a professional looking one. Fast turnaround was part of the service, thanks.&#8221; Craig Evans.</p>
<p><a href="http://www.medsyn.co/" target="_blank">Medsyn</a></p>
<img src="http://feeds.feedburner.com/~r/writeclicknz/~4/UmCbT5k_k_M" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://www.writeclick.co.nz/our-work/business/medsyn/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://www.writeclick.co.nz/our-work/business/medsyn/</feedburner:origLink></item>
		<item>
		<title>PKABOO</title>
		<link>http://feedproxy.google.com/~r/writeclicknz/~3/yzkC5k9s4XQ/</link>
		<comments>http://www.writeclick.co.nz/our-work/business/pkaboo/#comments</comments>
		<pubDate>Wed, 01 Feb 2012 23:03:06 +0000</pubDate>
		<dc:creator>Melua</dc:creator>
				<category><![CDATA[Business]]></category>

		<guid isPermaLink="false">http://www.writeclick.co.nz/?p=1205</guid>
		<description><![CDATA[PKABOO is an innovative line of child safety alarms to help keep kids safe around water. We wrote copy for PKABOO&#8217;s new website and optimised it for maximum exposure. PKABOO]]></description>
			<content:encoded><![CDATA[<p><img class="aligncenter size-full wp-image-1206" title="PKABOO Water Safety Alarms " src="http://www.writeclick.co.nz/wp-content/uploads/2012/02/Pkaboo2.jpg" alt="PKABOO Water Safety Alarms " width="246" height="155" /><br />
PKABOO is an innovative line of child safety alarms to help keep kids safe around water. We wrote copy for PKABOO&#8217;s new website and optimised it for maximum exposure.</p>
<p><a href="http://www.pkaboo.co.nz/" target="_blank">PKABOO </a></p>
<img src="http://feeds.feedburner.com/~r/writeclicknz/~4/yzkC5k9s4XQ" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://www.writeclick.co.nz/our-work/business/pkaboo/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://www.writeclick.co.nz/our-work/business/pkaboo/</feedburner:origLink></item>
		<item>
		<title>2012 ClearMark Awards</title>
		<link>http://feedproxy.google.com/~r/writeclicknz/~3/CC-W3_5E1kM/</link>
		<comments>http://www.writeclick.co.nz/blog/2012-clearmark-awards/#comments</comments>
		<pubDate>Wed, 18 Jan 2012 01:33:24 +0000</pubDate>
		<dc:creator>Melua</dc:creator>
				<category><![CDATA[Blog]]></category>
		<category><![CDATA[Plain English]]></category>

		<guid isPermaLink="false">http://www.writeclick.co.nz/?p=1200</guid>
		<description><![CDATA[I’ve spent my whole working life helping people to keep their writing clear and simple, so it was an honour to be asked to help judge the 2012 Centre for Plain Language ClearMark Awards.]]></description>
			<content:encoded><![CDATA[<p>I’ve spent my whole working life helping people to keep their writing clear and simple, so it was an honour to be asked to help judge the 2012 Centre for Plain Language ClearMark Awards.</p>
<p>This March a panel of plain language specialists from all over the world will be going through nominated websites and print documents with a fine-tooth comb. Or is that fine-toothed comb? There’s nothing like the judging process to keep you on your toes &#8211; as I&#8217;ve found through being involved with New Zealand&#8217;s own WriteMark Plain English Awards.</p>
<p>One thing I like about being part of a judging  panel is it really challenges your assumptions and habits. It&#8217;s also a great opportunity to stand back and take a good look at what&#8217;s happening in your industry. There is much cross-checking, discussion, and questioning – and utter delight when you come across an entry that clearly nails it. I can’t wait.</p>
<p>Find out more about the <a href="http://centerforplainlanguage.org/awards/" target="_blank">ClearMark Awards</a></p>
<img src="http://feeds.feedburner.com/~r/writeclicknz/~4/CC-W3_5E1kM" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://www.writeclick.co.nz/blog/2012-clearmark-awards/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://www.writeclick.co.nz/blog/2012-clearmark-awards/</feedburner:origLink></item>
		<item>
		<title>Peak Performance International</title>
		<link>http://feedproxy.google.com/~r/writeclicknz/~3/E7jncLXbEzA/</link>
		<comments>http://www.writeclick.co.nz/our-work/business/peak-performance-international/#comments</comments>
		<pubDate>Mon, 16 Jan 2012 21:40:00 +0000</pubDate>
		<dc:creator>Melua</dc:creator>
				<category><![CDATA[Business]]></category>

		<guid isPermaLink="false">http://www.writeclick.co.nz/?p=1192</guid>
		<description><![CDATA[Peak Performance International is a leading Australasian culture change and culture integration company. We helped them to tell their story with engaging content  designed to resonate with blue chip Australian and New Zealand organisations. Peak Performance International]]></description>
			<content:encoded><![CDATA[<p><img class="aligncenter size-full wp-image-1193" title="Peak Performance International" src="http://www.writeclick.co.nz/wp-content/uploads/2012/01/PPI.png" alt="Peak Performance International" width="247" height="129" /></p>
<p>Peak Performance International is a leading Australasian culture change and culture integration company. We helped them to tell their story with engaging content  designed to resonate with blue chip Australian and New Zealand organisations.</p>
<p><a href="http://www.peakperformance.com.au/">Peak Performance International </a></p>
<img src="http://feeds.feedburner.com/~r/writeclicknz/~4/E7jncLXbEzA" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://www.writeclick.co.nz/our-work/business/peak-performance-international/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://www.writeclick.co.nz/our-work/business/peak-performance-international/</feedburner:origLink></item>
		<item>
		<title>Kensington Swan</title>
		<link>http://feedproxy.google.com/~r/writeclicknz/~3/RM6yMD3Ruzo/</link>
		<comments>http://www.writeclick.co.nz/our-work/business/kensington-swan/#comments</comments>
		<pubDate>Tue, 20 Dec 2011 01:14:22 +0000</pubDate>
		<dc:creator>Melua</dc:creator>
				<category><![CDATA[Business]]></category>

		<guid isPermaLink="false">http://www.writeclick.co.nz/?p=1185</guid>
		<description><![CDATA[&#8220;Writeclick took about 90 legal service descriptions drafted by our in-house experts and gave them a consistent style and tone that captured our brand and worked well with our new site design. &#8220;They also brought to the project an invaluable knowledge of search engine optimisation: within two months of launching our new site we were [...]]]></description>
			<content:encoded><![CDATA[<div class="mceTemp mceIEcenter">
<dl id="attachment_1186" class="wp-caption aligncenter" style="width: 165px;">
<dt class="wp-caption-dt"><img class="size-full wp-image-1186" title="Kensington Swan " src="http://www.writeclick.co.nz/wp-content/uploads/2011/12/KSwan_lawyers1.JPG" alt="Kensington Swan" width="155" height="155" /></dt>
</dl>
</div>
<p>&#8220;Writeclick took about 90 legal service descriptions drafted by our in-house experts and gave them a consistent style and tone that captured our brand and worked well with our new site design.</p>
<p>&#8220;They also brought to the project an invaluable knowledge of search engine optimisation: within two months of launching our new site we were ranking well in Google for a wide range of key search terms for which we had previously been invisible.&#8221; Joe Owen, Kensington Swan.</p>
<p><a href="http://www.kensingtonswan.com/" target="_blank">Kensington Swan</a></p>
<img src="http://feeds.feedburner.com/~r/writeclicknz/~4/RM6yMD3Ruzo" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://www.writeclick.co.nz/our-work/business/kensington-swan/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://www.writeclick.co.nz/our-work/business/kensington-swan/</feedburner:origLink></item>
	</channel>
</rss>

