<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
	
	>
<channel>
	<title>Comments on: Breaking more than just news</title>
	<atom:link href="http://www.richardingram.co.uk/2010/02/breaking-more-than-just-news/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.richardingram.co.uk/2010/02/breaking-more-than-just-news/</link>
	<description>Richard Ingram&#039;s blog about content strategy, information design, and web accessibility</description>
	<lastBuildDate>Tue, 04 Jun 2013 11:22:19 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>https://wordpress.org/?v=4.1.42</generator>
	<item>
		<title>By: The content strategy advocate &#124; Richard Ingram &#124; Shut the door on your way out Cicero…</title>
		<link>http://www.richardingram.co.uk/2010/02/breaking-more-than-just-news/comment-page-1/#comment-188</link>
		<dc:creator><![CDATA[The content strategy advocate &#124; Richard Ingram &#124; Shut the door on your way out Cicero…]]></dc:creator>
		<pubDate>Thu, 18 Feb 2010 20:40:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.richardingram.co.uk/?p=335#comment-188</guid>
		<description><![CDATA[[...] helping to anticipate future content types and allowing everyone to cope better with periods of high publishing intensity. An organisation-wide web style guide will also help to develop and sustain a controlled message [...]]]></description>
		<content:encoded><![CDATA[<p>[&#8230;] helping to anticipate future content types and allowing everyone to cope better with periods of high publishing intensity. An organisation-wide web style guide will also help to develop and sustain a controlled message [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: How to Ensure Content Quality on the Fly &#124; Future Changes</title>
		<link>http://www.richardingram.co.uk/2010/02/breaking-more-than-just-news/comment-page-1/#comment-155</link>
		<dc:creator><![CDATA[How to Ensure Content Quality on the Fly &#124; Future Changes]]></dc:creator>
		<pubDate>Wed, 03 Feb 2010 20:17:15 +0000</pubDate>
		<guid isPermaLink="false">http://www.richardingram.co.uk/?p=335#comment-155</guid>
		<description><![CDATA[[...] Breaking More Than Just News, Richard Ingram says it&#8217;s more important than ever to check and recheck your content before [...]]]></description>
		<content:encoded><![CDATA[<p>[&#8230;] Breaking More Than Just News, Richard Ingram says it&#8217;s more important than ever to check and recheck your content before [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Richard</title>
		<link>http://www.richardingram.co.uk/2010/02/breaking-more-than-just-news/comment-page-1/#comment-154</link>
		<dc:creator><![CDATA[Richard]]></dc:creator>
		<pubDate>Wed, 03 Feb 2010 12:13:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.richardingram.co.uk/?p=335#comment-154</guid>
		<description><![CDATA[Hi Carl-Magnus,

I can understand how content that is moulded and shaped by several departments may have lost some of its initial verve when published. But errors like misspelling a name, listing the wrong phone number, or misquoting someone to such a degree that the information they&#039;ve divulged can only be misinterpreted can easily be snuffed out with even a simple set of quality control filters.

These filters exist in any sizeable organisation, but when the heat&#039;s on (when isn&#039;t it?) they can be disregarded and that&#039;s when common errors creep in.

There was a story over here recently about a British soldier&#039;s grieving mother who was upset that the Prime Minister had misspelt her son&#039;s name in a handwritten letter of condolence. One of the national papers decided to make a huge fuss over the issue and then went on to make a similar error on their own website. Needless to say an apology was swiftly issued.]]></description>
		<content:encoded><![CDATA[<p>Hi Carl-Magnus,</p>
<p>I can understand how content that is moulded and shaped by several departments may have lost some of its initial verve when published. But errors like misspelling a name, listing the wrong phone number, or misquoting someone to such a degree that the information they&#8217;ve divulged can only be misinterpreted can easily be snuffed out with even a simple set of quality control filters.</p>
<p>These filters exist in any sizeable organisation, but when the heat&#8217;s on (when isn&#8217;t it?) they can be disregarded and that&#8217;s when common errors creep in.</p>
<p>There was a story over here recently about a British soldier&#8217;s grieving mother who was upset that the Prime Minister had misspelt her son&#8217;s name in a handwritten letter of condolence. One of the national papers decided to make a huge fuss over the issue and then went on to make a similar error on their own website. Needless to say an apology was swiftly issued.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Carl-Magnus Löfström</title>
		<link>http://www.richardingram.co.uk/2010/02/breaking-more-than-just-news/comment-page-1/#comment-153</link>
		<dc:creator><![CDATA[Carl-Magnus Löfström]]></dc:creator>
		<pubDate>Wed, 03 Feb 2010 09:55:41 +0000</pubDate>
		<guid isPermaLink="false">http://www.richardingram.co.uk/?p=335#comment-153</guid>
		<description><![CDATA[As a journalist the woes of getting published were a big issue in the beginning of my career. 

The only possible antidote is usually a healthy contempt of knowledge =). How would otherwise any journalist be able to interview a scientist for 30 minutes (who has worked 10 years on a project), write it down in 2 hours and then send it to print?

Ok, that is an extreme and not correct when it comes to organisation communication. But it has some valid correlations. One of the biggest problems with getting stuff on the corporate site is that too many (read legal department and product experts) wants the information to be so correct that it is impossible to misinterpret. That usually needs advanced technobabble or 2 page legal document.]]></description>
		<content:encoded><![CDATA[<p>As a journalist the woes of getting published were a big issue in the beginning of my career. </p>
<p>The only possible antidote is usually a healthy contempt of knowledge =). How would otherwise any journalist be able to interview a scientist for 30 minutes (who has worked 10 years on a project), write it down in 2 hours and then send it to print?</p>
<p>Ok, that is an extreme and not correct when it comes to organisation communication. But it has some valid correlations. One of the biggest problems with getting stuff on the corporate site is that too many (read legal department and product experts) wants the information to be so correct that it is impossible to misinterpret. That usually needs advanced technobabble or 2 page legal document.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: uberVU - social comments</title>
		<link>http://www.richardingram.co.uk/2010/02/breaking-more-than-just-news/comment-page-1/#comment-152</link>
		<dc:creator><![CDATA[uberVU - social comments]]></dc:creator>
		<pubDate>Tue, 02 Feb 2010 19:29:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.richardingram.co.uk/?p=335#comment-152</guid>
		<description><![CDATA[&lt;strong&gt;Social comments and analytics for this post...&lt;/strong&gt;

This post was mentioned on Twitter by richardjingram: New blog post: Don&#039;t compromise the quality of your content by rushing to publish http://bit.ly/caAb27 #contentstrategy...]]></description>
		<content:encoded><![CDATA[<p><strong>Social comments and analytics for this post&#8230;</strong></p>
<p>This post was mentioned on Twitter by richardjingram: New blog post: Don&#8217;t compromise the quality of your content by rushing to publish <a href="http://bit.ly/caAb27" rel="nofollow">http://bit.ly/caAb27</a> #contentstrategy&#8230;</p>
]]></content:encoded>
	</item>
</channel>
</rss>
