<?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: For content problems, technology is not the thing.</title>
	<atom:link href="http://blog.braintraffic.com/2009/08/for-content-problems-technology-is-not-the-thing/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.braintraffic.com/2009/08/for-content-problems-technology-is-not-the-thing/</link>
	<description>Just another WordPress weblog</description>
	<lastBuildDate>Sat, 13 Mar 2010 06:35:13 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Tormod Guldvog</title>
		<link>http://blog.braintraffic.com/2009/08/for-content-problems-technology-is-not-the-thing/comment-page-1/#comment-728</link>
		<dc:creator>Tormod Guldvog</dc:creator>
		<pubDate>Thu, 15 Oct 2009 15:24:48 +0000</pubDate>
		<guid isPermaLink="false">http://blog.braintraffic.com/?p=568#comment-728</guid>
		<description>Spot on. Choosing one technology over another in order to solve obscure, poorly documented needs, quickly turns into a more or less relevant shouting contest over who thinks which features are most important, and which tool shines best.&lt;br&gt;&lt;br&gt;The question people should ask is &quot;why are we on the web&quot; and &quot;what do we want to achieve there&quot;. Then make a plan.&lt;br&gt;&lt;br&gt;If only..&lt;br&gt;&lt;br&gt;That said, changing platform simply to get away from something else *can* be a good thing, as long as you don&#039;t marry the new platform. It might help us solve critical issues while letting us move on with our content work. It&#039;s not all bad.</description>
		<content:encoded><![CDATA[<p>Spot on. Choosing one technology over another in order to solve obscure, poorly documented needs, quickly turns into a more or less relevant shouting contest over who thinks which features are most important, and which tool shines best.</p>
<p>The question people should ask is &#8220;why are we on the web&#8221; and &#8220;what do we want to achieve there&#8221;. Then make a plan.</p>
<p>If only..</p>
<p>That said, changing platform simply to get away from something else *can* be a good thing, as long as you don&#39;t marry the new platform. It might help us solve critical issues while letting us move on with our content work. It&#39;s not all bad.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tormod Guldvog</title>
		<link>http://blog.braintraffic.com/2009/08/for-content-problems-technology-is-not-the-thing/comment-page-1/#comment-567</link>
		<dc:creator>Tormod Guldvog</dc:creator>
		<pubDate>Thu, 15 Oct 2009 08:24:48 +0000</pubDate>
		<guid isPermaLink="false">http://blog.braintraffic.com/?p=568#comment-567</guid>
		<description>Spot on. Choosing one technology over another in order to solve obscure, poorly documented needs, quickly turns into a more or less relevant shouting contest over who thinks which features are most important, and which tool shines best.&lt;br&gt;&lt;br&gt;The question people should ask is &quot;why are we on the web&quot; and &quot;what do we want to achieve there&quot;. Then make a plan.&lt;br&gt;&lt;br&gt;If only..&lt;br&gt;&lt;br&gt;That said, changing platform simply to get away from something else *can* be a good thing, as long as you don&#039;t marry the new platform. It might help us solve critical issues while letting us move on with our content work. It&#039;s not all bad.</description>
		<content:encoded><![CDATA[<p>Spot on. Choosing one technology over another in order to solve obscure, poorly documented needs, quickly turns into a more or less relevant shouting contest over who thinks which features are most important, and which tool shines best.</p>
<p>The question people should ask is &#8220;why are we on the web&#8221; and &#8220;what do we want to achieve there&#8221;. Then make a plan.</p>
<p>If only..</p>
<p>That said, changing platform simply to get away from something else *can* be a good thing, as long as you don&#39;t marry the new platform. It might help us solve critical issues while letting us move on with our content work. It&#39;s not all bad.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Just fill in the blank? &#171; Brain Traffic Blog</title>
		<link>http://blog.braintraffic.com/2009/08/for-content-problems-technology-is-not-the-thing/comment-page-1/#comment-545</link>
		<dc:creator>Just fill in the blank? &#171; Brain Traffic Blog</dc:creator>
		<pubDate>Wed, 16 Sep 2009 14:27:31 +0000</pubDate>
		<guid isPermaLink="false">http://blog.braintraffic.com/?p=568#comment-545</guid>
		<description>[...] while ago, our fearless leader blogged about how technology can&#8217;t fix your content problems. Of course, I [...]</description>
		<content:encoded><![CDATA[<p>[...] while ago, our fearless leader blogged about how technology can&#8217;t fix your content problems. Of course, I [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kristina Halvorson</title>
		<link>http://blog.braintraffic.com/2009/08/for-content-problems-technology-is-not-the-thing/comment-page-1/#comment-529</link>
		<dc:creator>Kristina Halvorson</dc:creator>
		<pubDate>Mon, 24 Aug 2009 15:27:48 +0000</pubDate>
		<guid isPermaLink="false">http://blog.braintraffic.com/?p=568#comment-529</guid>
		<description>Thanks for your comments, Old Friend. &lt;br&gt;&lt;br&gt;I re-read my post, and I see where I didn&#039;t choose my words carefully. Of course a CMS can help folks who struggle with the logistics of content creation, delivery, and governance. Thanks for catching me on that. What I should have said is that, without a governing strategy that is built on people and process, it&#039;s not going to fix their problems. &lt;br&gt;&lt;br&gt;Right on!</description>
		<content:encoded><![CDATA[<p>Thanks for your comments, Old Friend. </p>
<p>I re-read my post, and I see where I didn&#39;t choose my words carefully. Of course a CMS can help folks who struggle with the logistics of content creation, delivery, and governance. Thanks for catching me on that. What I should have said is that, without a governing strategy that is built on people and process, it&#39;s not going to fix their problems. </p>
<p>Right on!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: An Old Friend</title>
		<link>http://blog.braintraffic.com/2009/08/for-content-problems-technology-is-not-the-thing/comment-page-1/#comment-525</link>
		<dc:creator>An Old Friend</dc:creator>
		<pubDate>Thu, 20 Aug 2009 11:25:48 +0000</pubDate>
		<guid isPermaLink="false">http://blog.braintraffic.com/?p=568#comment-525</guid>
		<description>Good post, but I would suggest that your claim is overstated. It can&#039;t solve *anything* related to delivery and governance? If your content development process is humming along just fine, but you can&#039;t get content published in a timely, regular fashion because an antiquated IT release process? Most any CMS can help you with that, as long as your users can use it. Or by the same token, if you need to able to frequently update your site with small but important changes...say interest rates, for example. I&#039;m talking about things that can be filed under site maintenance. A CMS will pay immediate dividends, whether your internal processes are screwed up or not.&lt;br&gt;&lt;br&gt;I like your overall point, though. A CMS is not a salve for process or staffing problems within an organization.</description>
		<content:encoded><![CDATA[<p>Good post, but I would suggest that your claim is overstated. It can&#39;t solve *anything* related to delivery and governance? If your content development process is humming along just fine, but you can&#39;t get content published in a timely, regular fashion because an antiquated IT release process? Most any CMS can help you with that, as long as your users can use it. Or by the same token, if you need to able to frequently update your site with small but important changes&#8230;say interest rates, for example. I&#39;m talking about things that can be filed under site maintenance. A CMS will pay immediate dividends, whether your internal processes are screwed up or not.</p>
<p>I like your overall point, though. A CMS is not a salve for process or staffing problems within an organization.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jeffcram</title>
		<link>http://blog.braintraffic.com/2009/08/for-content-problems-technology-is-not-the-thing/comment-page-1/#comment-524</link>
		<dc:creator>jeffcram</dc:creator>
		<pubDate>Thu, 20 Aug 2009 01:31:05 +0000</pubDate>
		<guid isPermaLink="false">http://blog.braintraffic.com/?p=568#comment-524</guid>
		<description>Amen! Great post and thanks for the shout out to the CMS Myth (and the kick in the rear to start writing more often!).  :-)&lt;br&gt;&lt;br&gt;Jeff Cram</description>
		<content:encoded><![CDATA[<p>Amen! Great post and thanks for the shout out to the CMS Myth (and the kick in the rear to start writing more often!).  <img src='http://blog.braintraffic.com/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /> </p>
<p>Jeff Cram</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dwayne Fishel</title>
		<link>http://blog.braintraffic.com/2009/08/for-content-problems-technology-is-not-the-thing/comment-page-1/#comment-523</link>
		<dc:creator>Dwayne Fishel</dc:creator>
		<pubDate>Wed, 19 Aug 2009 22:42:28 +0000</pubDate>
		<guid isPermaLink="false">http://blog.braintraffic.com/?p=568#comment-523</guid>
		<description>Great post...</description>
		<content:encoded><![CDATA[<p>Great post&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: joebachana</title>
		<link>http://blog.braintraffic.com/2009/08/for-content-problems-technology-is-not-the-thing/comment-page-1/#comment-522</link>
		<dc:creator>joebachana</dc:creator>
		<pubDate>Wed, 19 Aug 2009 16:39:24 +0000</pubDate>
		<guid isPermaLink="false">http://blog.braintraffic.com/?p=568#comment-522</guid>
		<description>Great post, Kristina!</description>
		<content:encoded><![CDATA[<p>Great post, Kristina!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
