<?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>Johnny Holland &#187; Colleen Jones</title>
	<atom:link href="http://johnnyholland.org/author/colleen-jones/feed/" rel="self" type="application/rss+xml" />
	<link>http://johnnyholland.org</link>
	<description>It&#039;s all about interaction</description>
	<lastBuildDate>Mon, 11 Mar 2013 23:07:51 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3</generator>
		<item>
		<title>Johnny proudly presents: Content Strategy Week</title>
		<link>http://johnnyholland.org/2010/10/johnny-proudly-presents-content-strategy-week/</link>
		<comments>http://johnnyholland.org/2010/10/johnny-proudly-presents-content-strategy-week/#comments</comments>
		<pubDate>Mon, 11 Oct 2010 11:55:43 +0000</pubDate>
		<dc:creator>Colleen Jones</dc:creator>
				<category><![CDATA[Methods & theory]]></category>

		<guid isPermaLink="false">http://johnnyholland.org/?p=9016</guid>
		<description><![CDATA[<img width="220" height="160" src="http://johnnyholland.org/wp-content/uploads/2011/12/cs0.jpg" class="attachment-index-categories wp-post-image" alt="cs0" title="cs0" />We love content strategy. Why? Because content strategy solves problems. Lots of problems. And during this week five leading content [...]]]></description>
			<content:encoded><![CDATA[<img width="220" height="160" src="http://johnnyholland.org/wp-content/uploads/2011/12/cs0.jpg" class="attachment-index-categories wp-post-image" alt="cs0" title="cs0" /><p><img class="alignnone size-full wp-image-9022" title="Content Strategy Week" src="http://johnnyholland.org/wp-content/uploads/csw-0.png" alt="" width="416" height="160" /><br />
We love content strategy. Why? Because <em>content strategy solves problems</em>. Lots of problems. And during this week five leading content strategists from four countries will tackle a different set of challenges, just for you.<span id="more-9016"></span></p>
<p>So what type of articles can you expect? Let&#8217;s check out what each day will bring:</p>
<h2>Monday: <a href="http://johnnyholland.org/2010/10/11/4-web-project-problems-content-strategy-can-solve/">Problems with Owning and Organizing Content</a></h2>
<p>Today, Meghan Casey of <a href="http://www.braintraffic.com/">Brain Traffic</a> explains how content strategy fixes immediate problems from breaking designs to showing your corporate &#8220;underpants.&#8221;</p>
<p><em>&#8220;I get this question a lot: How do content strategists work with IAs/designers/writers? Truthfully, they often don’t. But, they can and they should. Not only should they work together, they should do away with the typical web project process that leaves content until last, resulting in a mad scramble. People don’t muck up web projects. Bad processes do.&#8221;</em></p>
<h2>Tuesday: <a href="http://johnnyholland.org/2010/10/12/producing-quality-content-with-multiple-contributors/">Problems with Creating Consistent Content</a></h2>
<p>On Tuesday, Sally Bagshaw of <a href="http://www.snappysentences.com/">Snappy Sentences</a> shares how to create good content consistently, even when you have many cooks in your content kitchen.</p>
<p><em>&#8220;You’ve probably heard the saying “too many cooks spoil the broth.”  It implies that having lots of people involved in the production of any one outcome isn’t a good thing. The same can be said for managing large websites. In fact, “too many authors spoil the content” is a much more pertinent issue in today’s digital world. Unfortunately it’s one that’s hard to escape.&#8221;</em></p>
<h2>Wednesday: <a href="http://johnnyholland.org/2010/10/13/supporting-comprehension-for-everyone/">Problems with Understanding Content</a></h2>
<p><strong> </strong>On<strong> </strong>Wednesday, Richard Ingram of <a href="http://www.ingserv.com/">ingserv</a> explains how content strategy solves the problem of accessible but incomprehensible content, a critical consideration for universal design.</p>
<p><em>&#8220;The process of publishing content, particularly when it includes content destined for the web, continues to be a mysterious process for corporate stakeholders, and sometimes for those involved in the process of publishing.&#8221;</em></p>
<h2>Thursday: <a href="http://johnnyholland.org/2010/10/14/content-lifecycle-closing-the-loop-in-content-strategy/">Problems with Strategic Planning for Content</a></h2>
<p>On Thursday, Rahel Bailie of <a href="http://intentionaldesign.ca/">Intentional Design</a> addresses the problem of underplanning for content by walking us through the content lifecycle.</p>
<h2>Friday: <a href="http://johnnyholland.org/2010/10/15/using-numbers-to-plan-content/">Problems with Evaluating Content</a></h2>
<p>On Friday, Clare O&#8217;Brien of <a href="http://www.webwordsworking.co.uk/">CDA</a> helps us understand what the numbers mean with her contextual approach to content evaluation.</p>
<p><em>&#8220;Something that’s fascinated me about online metrics since I started working in online (quite a long time ago in internet terms) is their immediacy. In fact, it’s their instancy&#8230; this real-time sense you get from actually watching people move in and out of a website or email or mobile platform—that really mesmerises. The numbers create a kind of certainty about the clicks, impressions, traffic volume&#8230; and based on those numbers we believe we can know what worked (or didn’t work). On the basis of these metrics we do more or less of the same.&#8221;</em></p>
<p>Special thanks to Jeroen van Geel for inviting this useful and international look at content strategy.</p>
]]></content:encoded>
			<wfw:commentRss>http://johnnyholland.org/2010/10/johnny-proudly-presents-content-strategy-week/feed/</wfw:commentRss>
		<slash:comments>15</slash:comments>
		</item>
	</channel>
</rss>
