<?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 for The Content Strategy Noob</title>
	<atom:link href="http://contentstrategy.rsgracey.com/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://contentstrategy.rsgracey.com</link>
	<description>Content Strategy...Huh? (by @rsgracey)</description>
	<lastBuildDate>Mon, 28 Jun 2010 18:07:48 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>Comment on Taxonomy: A &#8220;Disambiguation&#8221; by rsgracey</title>
		<link>http://contentstrategy.rsgracey.com/2010/06/18/taxonomy-disambiguation/comment-page-1/#comment-499</link>
		<dc:creator>rsgracey</dc:creator>
		<pubDate>Mon, 28 Jun 2010 18:07:48 +0000</pubDate>
		<guid isPermaLink="false">http://contentstrategy.rsgracey.com/?p=183#comment-499</guid>
		<description>Hi, Laura! My colleague @paintingblue, who&#039;s a librarian, says that taxonomy is really only of interest to the information architect, as it lies behind the site. The user will never see it, and even the content authors have limited access to it: Done right, most of it is applied automatically. Therein lies that challenges: Because content owners can&#039;t see it, they have trouble understanding why it&#039;s there. Likewise, in one of my own horror stories, content owners assume that if there isn&#039;t primary navigation leading directly to a section of content, people won&#039;t find it. I maintain people find good content regardless of the site structure, and no amount of direct access will increase traffic to useless content.</description>
		<content:encoded><![CDATA[<p>Hi, Laura! My colleague @paintingblue, who&#8217;s a librarian, says that taxonomy is really only of interest to the information architect, as it lies behind the site. The user will never see it, and even the content authors have limited access to it: Done right, most of it is applied automatically. Therein lies that challenges: Because content owners can&#8217;t see it, they have trouble understanding why it&#8217;s there. Likewise, in one of my own horror stories, content owners assume that if there isn&#8217;t primary navigation leading directly to a section of content, people won&#8217;t find it. I maintain people find good content regardless of the site structure, and no amount of direct access will increase traffic to useless content.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Taxonomy: A &#8220;Disambiguation&#8221; by rsgracey</title>
		<link>http://contentstrategy.rsgracey.com/2010/06/18/taxonomy-disambiguation/comment-page-1/#comment-498</link>
		<dc:creator>rsgracey</dc:creator>
		<pubDate>Mon, 28 Jun 2010 18:02:49 +0000</pubDate>
		<guid isPermaLink="false">http://contentstrategy.rsgracey.com/?p=183#comment-498</guid>
		<description>Hey, Matt! Thanks sooooo much for reading and commenting! I&#039;ve been on vacation the last week, so please forgive the delay in responding. 

As I say, I&#039;m not really a taxonomist/ontologist. I try to simplify complex ideas so that they are more widely digestible. I think, though, that your last point (i.e., [paraphrase] that one should focus more on site structure and navigation than on taxonomy) can only take one so far. If you have a small site, then creating an ontology, I agree, is a lot of work for very little gain, but navigation and site organization quickly become too complex to reveal the site&#039;s content after a few areas and levels (across and down). Browsing becomes impossible at that point, and site search remains unreliable. 

In addition, I think it&#039;s impossible to talk about &quot;metadata&quot; on its own because the risk is too great to overlook the importance of defining a formal schema. Tagging becomes inconsistent without a solid mapping of terms. So in a particular content domain where people have many ways of finding what they need, the metadata must be applied consistently according to the structure to ensure that everything falls into its rightful &quot;place,&quot; regardless of how the visitor defines that &quot;place.&quot; My own goal for content is to have it arrange itself wherever the visitor expects to find it, rather than defining a website structure to hold it.

What do you think?

Stephen</description>
		<content:encoded><![CDATA[<p>Hey, Matt! Thanks sooooo much for reading and commenting! I&#8217;ve been on vacation the last week, so please forgive the delay in responding. </p>
<p>As I say, I&#8217;m not really a taxonomist/ontologist. I try to simplify complex ideas so that they are more widely digestible. I think, though, that your last point (i.e., [paraphrase] that one should focus more on site structure and navigation than on taxonomy) can only take one so far. If you have a small site, then creating an ontology, I agree, is a lot of work for very little gain, but navigation and site organization quickly become too complex to reveal the site&#8217;s content after a few areas and levels (across and down). Browsing becomes impossible at that point, and site search remains unreliable. </p>
<p>In addition, I think it&#8217;s impossible to talk about &#8220;metadata&#8221; on its own because the risk is too great to overlook the importance of defining a formal schema. Tagging becomes inconsistent without a solid mapping of terms. So in a particular content domain where people have many ways of finding what they need, the metadata must be applied consistently according to the structure to ensure that everything falls into its rightful &#8220;place,&#8221; regardless of how the visitor defines that &#8220;place.&#8221; My own goal for content is to have it arrange itself wherever the visitor expects to find it, rather than defining a website structure to hold it.</p>
<p>What do you think?</p>
<p>Stephen</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Taxonomy: A &#8220;Disambiguation&#8221; by Taxonomy: A “Disambiguation” &#124; UX Booth</title>
		<link>http://contentstrategy.rsgracey.com/2010/06/18/taxonomy-disambiguation/comment-page-1/#comment-497</link>
		<dc:creator>Taxonomy: A “Disambiguation” &#124; UX Booth</dc:creator>
		<pubDate>Sat, 26 Jun 2010 23:27:16 +0000</pubDate>
		<guid isPermaLink="false">http://contentstrategy.rsgracey.com/?p=183#comment-497</guid>
		<description>[...] A “Disambiguation” &#124; UX Booth     UX BoothTaxonomy: A “Disambiguation”Share This     Share Browse UX BoothPreviousNext Close This  function resizeIframe() { var height = [...]</description>
		<content:encoded><![CDATA[<p>[...] A “Disambiguation” | UX Booth     UX BoothTaxonomy: A “Disambiguation”Share This     Share Browse UX BoothPreviousNext Close This  function resizeIframe() { var height = [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Taxonomy: A &#8220;Disambiguation&#8221; by Laura Creekmore</title>
		<link>http://contentstrategy.rsgracey.com/2010/06/18/taxonomy-disambiguation/comment-page-1/#comment-496</link>
		<dc:creator>Laura Creekmore</dc:creator>
		<pubDate>Tue, 22 Jun 2010 17:23:31 +0000</pubDate>
		<guid isPermaLink="false">http://contentstrategy.rsgracey.com/?p=183#comment-496</guid>
		<description>This is a great post. Thanks for putting these details out there! I find that a lot of my clients do struggle with the difference between taxonomy, navigation and their org chart. It&#039;s always important to write taxonomy and navigation from the customer&#039;s viewpoint, and not from the org chart viewpoint. That&#039;s a challenge for some!</description>
		<content:encoded><![CDATA[<p>This is a great post. Thanks for putting these details out there! I find that a lot of my clients do struggle with the difference between taxonomy, navigation and their org chart. It&#8217;s always important to write taxonomy and navigation from the customer&#8217;s viewpoint, and not from the org chart viewpoint. That&#8217;s a challenge for some!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Taxonomy: A &#8220;Disambiguation&#8221; by Mathew Sanders</title>
		<link>http://contentstrategy.rsgracey.com/2010/06/18/taxonomy-disambiguation/comment-page-1/#comment-495</link>
		<dc:creator>Mathew Sanders</dc:creator>
		<pubDate>Sun, 20 Jun 2010 23:23:46 +0000</pubDate>
		<guid isPermaLink="false">http://contentstrategy.rsgracey.com/?p=183#comment-495</guid>
		<description>It’s fascinating, frustrating, and confusing when words take on new meanings.

In the case of taxonomy in the world of software or web design it’s more difficult because in some projects the traditional meaning and the new meaning will sometimes clash.

From conversations with people, it seems to me that most people see the hierarchal structure of content on a website they make the leap from hierarchy to taxonomy, but of course just because something is structured hierarchically doesn’t mean that it has been structured by the rules of a taxonomy. 

Because of this I’ve avoided using any new meanings for taxonomy, and instead discuss metadata or site structure.

Overall I think you’ve got a great article here, but there were a couple of points I think are important to discuss:

&gt;&gt; “…Amazon and other e-commerce giants have made such ubiquitous and successful use of taxonomy to sell related things, but it’s really quite difficult to establish those kinds of relationships in your content without taxonomy.”

I don’t (and have never) worked for Amazon, but my understanding of how their recommendations work are mostly based on customer buying behavior (so relations are made by patterns found between what users are browsing, purchasing or adding to wish lists).

&gt;&gt; “…Whereas in a biological taxonomy, we’re dealing with only one dimension of relationship, the ultimate relationship of one species to another through its name…”

Living species could be classified by any number of ways (habitat, colour, type of noise they make… ;) but like you mention earlier, the power of a taxonomy comes from it being widely adopted so that different groups of people can classify, analyze, share, discover and learn around a common set of information.

When more complex relationships start to form, instead of using multiple taxonomies, an easier approach is to create an ontology which has must more flexible classification rules (think of a network or a graph instead of a tree).

Traditionally, taxonomy has been a preferred approach to classification because in the past it was the only practical way to maintain a complex set of records (we were physically constrained in the past with paper based records – think back to the old stacks found in libraries).

The potential of developing and using a taxonomy (or ontology) in software design is huge. Especially in the area of search – but from my experience, unless you’re working in document/record management, or in the area of content governance then you probably don’t need to think about taxonomy at all.

Instead people should focus on a structure that allows people to find what they are looking for – a great place to start here might be some card sorting activities with people from your target audiences.</description>
		<content:encoded><![CDATA[<p>It’s fascinating, frustrating, and confusing when words take on new meanings.</p>
<p>In the case of taxonomy in the world of software or web design it’s more difficult because in some projects the traditional meaning and the new meaning will sometimes clash.</p>
<p>From conversations with people, it seems to me that most people see the hierarchal structure of content on a website they make the leap from hierarchy to taxonomy, but of course just because something is structured hierarchically doesn’t mean that it has been structured by the rules of a taxonomy. </p>
<p>Because of this I’ve avoided using any new meanings for taxonomy, and instead discuss metadata or site structure.</p>
<p>Overall I think you’ve got a great article here, but there were a couple of points I think are important to discuss:</p>
<p>&gt;&gt; “…Amazon and other e-commerce giants have made such ubiquitous and successful use of taxonomy to sell related things, but it’s really quite difficult to establish those kinds of relationships in your content without taxonomy.”</p>
<p>I don’t (and have never) worked for Amazon, but my understanding of how their recommendations work are mostly based on customer buying behavior (so relations are made by patterns found between what users are browsing, purchasing or adding to wish lists).</p>
<p>&gt;&gt; “…Whereas in a biological taxonomy, we’re dealing with only one dimension of relationship, the ultimate relationship of one species to another through its name…”</p>
<p>Living species could be classified by any number of ways (habitat, colour, type of noise they make… <img src='http://contentstrategy.rsgracey.com/wp-includes/images/smilies/icon_wink.gif' alt=';)' class='wp-smiley' />  but like you mention earlier, the power of a taxonomy comes from it being widely adopted so that different groups of people can classify, analyze, share, discover and learn around a common set of information.</p>
<p>When more complex relationships start to form, instead of using multiple taxonomies, an easier approach is to create an ontology which has must more flexible classification rules (think of a network or a graph instead of a tree).</p>
<p>Traditionally, taxonomy has been a preferred approach to classification because in the past it was the only practical way to maintain a complex set of records (we were physically constrained in the past with paper based records – think back to the old stacks found in libraries).</p>
<p>The potential of developing and using a taxonomy (or ontology) in software design is huge. Especially in the area of search – but from my experience, unless you’re working in document/record management, or in the area of content governance then you probably don’t need to think about taxonomy at all.</p>
<p>Instead people should focus on a structure that allows people to find what they are looking for – a great place to start here might be some card sorting activities with people from your target audiences.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Taxonomy: A &#8220;Disambiguation&#8221; by Tweets that mention The Content Strategy Noob » Taxonomy: A “Disambiguation” -- Topsy.com</title>
		<link>http://contentstrategy.rsgracey.com/2010/06/18/taxonomy-disambiguation/comment-page-1/#comment-494</link>
		<dc:creator>Tweets that mention The Content Strategy Noob » Taxonomy: A “Disambiguation” -- Topsy.com</dc:creator>
		<pubDate>Fri, 18 Jun 2010 14:30:25 +0000</pubDate>
		<guid isPermaLink="false">http://contentstrategy.rsgracey.com/?p=183#comment-494</guid>
		<description>[...] This post was mentioned on Twitter by Peter J. Bogaards, Bas Evers. Bas Evers said: warm aanbevolen, leesbare uitleg van taxonomieën en metadata RT @RSGracey: &quot;Taxonomy: A &#039;disabiguation&#039;&quot; http://bit.ly/922Wd1 [...]</description>
		<content:encoded><![CDATA[<p>[...] This post was mentioned on Twitter by Peter J. Bogaards, Bas Evers. Bas Evers said: warm aanbevolen, leesbare uitleg van taxonomieën en metadata RT @RSGracey: &quot;Taxonomy: A &#039;disabiguation&#039;&quot; <a href="http://bit.ly/922Wd1" rel="nofollow">http://bit.ly/922Wd1</a> [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Toward a taxonomy of content by Tweets that mention The Content Strategy Noob » Toward a taxonomy of content -- Topsy.com</title>
		<link>http://contentstrategy.rsgracey.com/2010/05/27/toward-a-taxonomy-of-content/comment-page-1/#comment-493</link>
		<dc:creator>Tweets that mention The Content Strategy Noob » Toward a taxonomy of content -- Topsy.com</dc:creator>
		<pubDate>Thu, 27 May 2010 23:59:10 +0000</pubDate>
		<guid isPermaLink="false">http://contentstrategy.rsgracey.com/?p=179#comment-493</guid>
		<description>[...] This post was mentioned on Twitter by GarrettFrench and R. Stephen Gracey, Denise Edwards. Denise Edwards said: Interesting post by @rsgracey on classifying content into classes with intentions - &#039;Toward a Taxonomy of Content:&#039; http://bit.ly/aFyd5r [...]</description>
		<content:encoded><![CDATA[<p>[...] This post was mentioned on Twitter by GarrettFrench and R. Stephen Gracey, Denise Edwards. Denise Edwards said: Interesting post by @rsgracey on classifying content into classes with intentions &#8211; &#39;Toward a Taxonomy of Content:&#39; <a href="http://bit.ly/aFyd5r" rel="nofollow">http://bit.ly/aFyd5r</a> [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Who’s not here? Diversity in community by Tweets that mention The Content Strategy Noob » Who’s not here? Diversity in community -- Topsy.com</title>
		<link>http://contentstrategy.rsgracey.com/2010/05/25/diversity-in-community/comment-page-1/#comment-492</link>
		<dc:creator>Tweets that mention The Content Strategy Noob » Who’s not here? Diversity in community -- Topsy.com</dc:creator>
		<pubDate>Tue, 25 May 2010 21:32:35 +0000</pubDate>
		<guid isPermaLink="false">http://contentstrategy.rsgracey.com/?p=176#comment-492</guid>
		<description>[...] This post was mentioned on Twitter by R. Stephen Gracey and Jonathan Kahn, Jonathan Kahn. Jonathan Kahn said: &quot;Inclusive diversity ensures.. there’s always someone new.. to shake things up &amp; make you revise your whole picture&quot; http://bit.ly/9cvYp4 [...]</description>
		<content:encoded><![CDATA[<p>[...] This post was mentioned on Twitter by R. Stephen Gracey and Jonathan Kahn, Jonathan Kahn. Jonathan Kahn said: &quot;Inclusive diversity ensures.. there’s always someone new.. to shake things up &amp; make you revise your whole picture&quot; <a href="http://bit.ly/9cvYp4" rel="nofollow">http://bit.ly/9cvYp4</a> [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Sophie’s choice: Well-crafted content or empowered content owners? by Tweets that mention Just Blogged: "Sophie's Choice: Well-Crafted Content or Empowered Content Owners?" #contentstrategy -- Topsy.com</title>
		<link>http://contentstrategy.rsgracey.com/2010/05/06/sophie%e2%80%99s-choice-well-crafted-content-or-empowered-content-owners/comment-page-1/#comment-491</link>
		<dc:creator>Tweets that mention Just Blogged: "Sophie's Choice: Well-Crafted Content or Empowered Content Owners?" #contentstrategy -- Topsy.com</dc:creator>
		<pubDate>Thu, 06 May 2010 20:30:44 +0000</pubDate>
		<guid isPermaLink="false">http://contentstrategy.rsgracey.com/?p=163#comment-491</guid>
		<description>[...] This post was mentioned on Twitter by R. Stephen Gracey, Bill Joseph. Bill Joseph said: RT @RSGracey: Just Blogged: &quot;Sophie&#039;s Choice: Well-Crafted Content or Empowered Content Owners?&quot; #contentstrategy http://bit.ly/blMumA [...]</description>
		<content:encoded><![CDATA[<p>[...] This post was mentioned on Twitter by R. Stephen Gracey, Bill Joseph. Bill Joseph said: RT @RSGracey: Just Blogged: &quot;Sophie&#39;s Choice: Well-Crafted Content or Empowered Content Owners?&quot; #contentstrategy <a href="http://bit.ly/blMumA" rel="nofollow">http://bit.ly/blMumA</a> [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on The Mythic Bestiary: Content Owners by uberVU - social comments</title>
		<link>http://contentstrategy.rsgracey.com/2010/03/29/the-mythic-bestiary-content-owners/comment-page-1/#comment-490</link>
		<dc:creator>uberVU - social comments</dc:creator>
		<pubDate>Thu, 01 Apr 2010 14:49:04 +0000</pubDate>
		<guid isPermaLink="false">http://contentstrategy.rsgracey.com/?p=132#comment-490</guid>
		<description>&lt;strong&gt;Social comments and analytics for this post...&lt;/strong&gt;

This post was mentioned on Twitter by everbass: content ownership is not content dictatorship RT @RSGracey: &quot;The Mythic Bestiary: Content Owners,&quot; #contentstrategy http://bit.ly/8XG6Wl...</description>
		<content:encoded><![CDATA[<p><strong>Social comments and analytics for this post&#8230;</strong></p>
<p>This post was mentioned on Twitter by everbass: content ownership is not content dictatorship RT @RSGracey: &#8220;The Mythic Bestiary: Content Owners,&#8221; #contentstrategy <a href="http://bit.ly/8XG6Wl.." rel="nofollow">http://bit.ly/8XG6Wl..</a>.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Content Transparency: Can you see me now? by Cocktail Hour: 5 at 5pm : Incisive.nu</title>
		<link>http://contentstrategy.rsgracey.com/2010/03/22/content-transparency-can-you-see-me-now/comment-page-1/#comment-489</link>
		<dc:creator>Cocktail Hour: 5 at 5pm : Incisive.nu</dc:creator>
		<pubDate>Fri, 26 Mar 2010 20:25:53 +0000</pubDate>
		<guid isPermaLink="false">http://contentstrategy.rsgracey.com/?p=126#comment-489</guid>
		<description>[...] Robert Gracey, &#8220;Content Transparency: Can You See Me Now?&#8221; [...]</description>
		<content:encoded><![CDATA[<p>[...] Robert Gracey, &#8220;Content Transparency: Can You See Me Now?&#8221; [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Content Transparency: Can you see me now? by uberVU - social comments</title>
		<link>http://contentstrategy.rsgracey.com/2010/03/22/content-transparency-can-you-see-me-now/comment-page-1/#comment-488</link>
		<dc:creator>uberVU - social comments</dc:creator>
		<pubDate>Fri, 26 Mar 2010 16:31:12 +0000</pubDate>
		<guid isPermaLink="false">http://contentstrategy.rsgracey.com/?p=126#comment-488</guid>
		<description>&lt;strong&gt;Social comments and analytics for this post...&lt;/strong&gt;

This post was mentioned on Twitter by RSGracey: Blogged: Content Transparency: Can your audience &quot;see through&quot; your content? #contentstrategy http://bit.ly/b9KiJv...</description>
		<content:encoded><![CDATA[<p><strong>Social comments and analytics for this post&#8230;</strong></p>
<p>This post was mentioned on Twitter by RSGracey: Blogged: Content Transparency: Can your audience &#8220;see through&#8221; your content? #contentstrategy <a href="http://bit.ly/b9KiJv.." rel="nofollow">http://bit.ly/b9KiJv..</a>.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Content Transparency: Can you see me now? by Tweets that mention The Content Strategy Noob » Content Transparency: Can you see me now? -- Topsy.com</title>
		<link>http://contentstrategy.rsgracey.com/2010/03/22/content-transparency-can-you-see-me-now/comment-page-1/#comment-487</link>
		<dc:creator>Tweets that mention The Content Strategy Noob » Content Transparency: Can you see me now? -- Topsy.com</dc:creator>
		<pubDate>Wed, 24 Mar 2010 17:14:37 +0000</pubDate>
		<guid isPermaLink="false">http://contentstrategy.rsgracey.com/?p=126#comment-487</guid>
		<description>[...] This post was mentioned on Twitter by DJ Francis and evanarsdall, R. Stephen Gracey. R. Stephen Gracey said: Content Transparency: Can your audience &quot;see through&quot; your content? #contentstrategy http://bit.ly/b9KiJv [...]</description>
		<content:encoded><![CDATA[<p>[...] This post was mentioned on Twitter by DJ Francis and evanarsdall, R. Stephen Gracey. R. Stephen Gracey said: Content Transparency: Can your audience &quot;see through&quot; your content? #contentstrategy <a href="http://bit.ly/b9KiJv" rel="nofollow">http://bit.ly/b9KiJv</a> [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Be Known For Your Content, Not Your Name! by 30 delicious content strategy and content marketing links &#171; new media mentality</title>
		<link>http://contentstrategy.rsgracey.com/2009/06/04/be-known-for-your-content-not-your-name%e2%80%a6/comment-page-1/#comment-187</link>
		<dc:creator>30 delicious content strategy and content marketing links &#171; new media mentality</dc:creator>
		<pubDate>Tue, 14 Jul 2009 07:38:15 +0000</pubDate>
		<guid isPermaLink="false">http://contentstrategy.rsgracey.com/?p=110#comment-187</guid>
		<description>[...] http://contentstrategy.rsgracey.com/2009/06/04/be-known-for-your-content-not-your-name%E2%80%A6/ [...]</description>
		<content:encoded><![CDATA[<p>[...] <a href="http://contentstrategy.rsgracey.com/2009/06/04/be-known-for-your-content-not-your-name%E2%80%A6/" rel="nofollow">http://contentstrategy.rsgracey.com/2009/06/04/be-known-for-your-content-not-your-name%E2%80%A6/</a> [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Content strategy is an act of love by 30 delicious content strategy and content marketing links &#171; new media mentality</title>
		<link>http://contentstrategy.rsgracey.com/2009/04/30/content-strategy-is-an-act-of-love/comment-page-1/#comment-186</link>
		<dc:creator>30 delicious content strategy and content marketing links &#171; new media mentality</dc:creator>
		<pubDate>Tue, 14 Jul 2009 07:37:49 +0000</pubDate>
		<guid isPermaLink="false">http://contentstrategy.rsgracey.com/?p=94#comment-186</guid>
		<description>[...] http://contentstrategy.rsgracey.com/2009/04/30/content-strategy-is-an-act-of-love/ [...]</description>
		<content:encoded><![CDATA[<p>[...] <a href="http://contentstrategy.rsgracey.com/2009/04/30/content-strategy-is-an-act-of-love/" rel="nofollow">http://contentstrategy.rsgracey.com/2009/04/30/content-strategy-is-an-act-of-love/</a> [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on You’ll Wish You’d Had a Content Strategy Before Implementing Content Management by Rahel Bailie</title>
		<link>http://contentstrategy.rsgracey.com/2009/05/28/you%e2%80%99ll-wish-you%e2%80%99d-had-a-content-strategy-before-implementing-content-management/comment-page-1/#comment-69</link>
		<dc:creator>Rahel Bailie</dc:creator>
		<pubDate>Fri, 29 May 2009 06:16:53 +0000</pubDate>
		<guid isPermaLink="false">http://contentstrategy.rsgracey.com/?p=105#comment-69</guid>
		<description>I do sympathize, and really think you got taken for a ride by your consultants. Asking &quot;what do you want the system to do&quot; is NOT the same as gathering requirements, and if they couldn&#039;t find a way to explain the pros and cons, within the context of your organization&#039;s framework, they didn&#039;t do their jobs. Period. I get so agitated when I see these things. There&#039;s a saying that the quality of your integrator can make or break a project. I would extend that to say that the quality of your consultants can determine whether your project will be successful. Requirements analysis, content analysis, and THEN technology analysis - the technology gets chosen to apply to what you need it to accomplish. OK, I&#039;m going back to my work here before I melt my keyboard!</description>
		<content:encoded><![CDATA[<p>I do sympathize, and really think you got taken for a ride by your consultants. Asking &#8220;what do you want the system to do&#8221; is NOT the same as gathering requirements, and if they couldn&#8217;t find a way to explain the pros and cons, within the context of your organization&#8217;s framework, they didn&#8217;t do their jobs. Period. I get so agitated when I see these things. There&#8217;s a saying that the quality of your integrator can make or break a project. I would extend that to say that the quality of your consultants can determine whether your project will be successful. Requirements analysis, content analysis, and THEN technology analysis &#8211; the technology gets chosen to apply to what you need it to accomplish. OK, I&#8217;m going back to my work here before I melt my keyboard!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on You’ll Wish You’d Had a Content Strategy Before Implementing Content Management by Cleve</title>
		<link>http://contentstrategy.rsgracey.com/2009/05/28/you%e2%80%99ll-wish-you%e2%80%99d-had-a-content-strategy-before-implementing-content-management/comment-page-1/#comment-68</link>
		<dc:creator>Cleve</dc:creator>
		<pubDate>Fri, 29 May 2009 05:54:41 +0000</pubDate>
		<guid isPermaLink="false">http://contentstrategy.rsgracey.com/?p=105#comment-68</guid>
		<description>I really feel for you here Stephen.  When starting a new project, with a new CMS, there is a lot of customer Fear, Uncertainty and Doubt. Then for consultants to bombard customers with question after question, is like you walking into a restaurant and the chef trotting out asking you what kinds of food you like and how do you prefer it cooked.  
Show us the menu already!  We&#039;ve paid for your experience. Build us prototypes!  Guide us to where we need to go.  Early access to tangible solutions, means more informed questions, that leads to real answers.  As a rule, for the larger projects, prototypes are part of the requirements gathering phase.  Oh, I&#039;m with Jeff on planning.  I subscribe to the 6 Ps (Prior Planning Prevents Piss Poor Performance).</description>
		<content:encoded><![CDATA[<p>I really feel for you here Stephen.  When starting a new project, with a new CMS, there is a lot of customer Fear, Uncertainty and Doubt. Then for consultants to bombard customers with question after question, is like you walking into a restaurant and the chef trotting out asking you what kinds of food you like and how do you prefer it cooked.<br />
Show us the menu already!  We&#8217;ve paid for your experience. Build us prototypes!  Guide us to where we need to go.  Early access to tangible solutions, means more informed questions, that leads to real answers.  As a rule, for the larger projects, prototypes are part of the requirements gathering phase.  Oh, I&#8217;m with Jeff on planning.  I subscribe to the 6 Ps (Prior Planning Prevents Piss Poor Performance).</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on You’ll Wish You’d Had a Content Strategy Before Implementing Content Management by Jeffrey MacIntyre</title>
		<link>http://contentstrategy.rsgracey.com/2009/05/28/you%e2%80%99ll-wish-you%e2%80%99d-had-a-content-strategy-before-implementing-content-management/comment-page-1/#comment-65</link>
		<dc:creator>Jeffrey MacIntyre</dc:creator>
		<pubDate>Thu, 28 May 2009 14:36:16 +0000</pubDate>
		<guid isPermaLink="false">http://contentstrategy.rsgracey.com/?p=105#comment-65</guid>
		<description>Grim is right, Stephen. And this lesson applies with equal force to any system tool implementation: you need to evaluate it and model it in advance according to set requirements. Next to CMS &quot;upgrades&quot;, I think content migrations are the next most common pain point where strategic planning should be absolutely prerequisite (but often isn&#039;t). Plan your work and work your plan, as the old saw goes.</description>
		<content:encoded><![CDATA[<p>Grim is right, Stephen. And this lesson applies with equal force to any system tool implementation: you need to evaluate it and model it in advance according to set requirements. Next to CMS &#8220;upgrades&#8221;, I think content migrations are the next most common pain point where strategic planning should be absolutely prerequisite (but often isn&#8217;t). Plan your work and work your plan, as the old saw goes.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on You’ll Wish You’d Had a Content Strategy Before Implementing Content Management by Ian Waugh</title>
		<link>http://contentstrategy.rsgracey.com/2009/05/28/you%e2%80%99ll-wish-you%e2%80%99d-had-a-content-strategy-before-implementing-content-management/comment-page-1/#comment-64</link>
		<dc:creator>Ian Waugh</dc:creator>
		<pubDate>Thu, 28 May 2009 14:14:05 +0000</pubDate>
		<guid isPermaLink="false">http://contentstrategy.rsgracey.com/?p=105#comment-64</guid>
		<description>Very true! It&#039;s so important to spend enough time deciding what the CMS needs to do. Also, people do forget that it is the web front end that also needs to be thought of... all a CMS does is store and deliver the content. I for one will never implement another CMS that does not include some ability to modify the user-facing parts of the website as well... or at least is partnered with a web platform that can be easily customised.

All of this comes from experience though, and vendors are notoriously unreliable when it comes to discovering the client&#039;s real needs... they are understandably led by the potential features of their product.</description>
		<content:encoded><![CDATA[<p>Very true! It&#8217;s so important to spend enough time deciding what the CMS needs to do. Also, people do forget that it is the web front end that also needs to be thought of&#8230; all a CMS does is store and deliver the content. I for one will never implement another CMS that does not include some ability to modify the user-facing parts of the website as well&#8230; or at least is partnered with a web platform that can be easily customised.</p>
<p>All of this comes from experience though, and vendors are notoriously unreliable when it comes to discovering the client&#8217;s real needs&#8230; they are understandably led by the potential features of their product.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Content Typology: Getting a Handle on Your Content Types by Content Modelling : Content for the Masses</title>
		<link>http://contentstrategy.rsgracey.com/2009/04/22/content-typology-the-way-to-get-a-handle-on-your-content/comment-page-1/#comment-46</link>
		<dc:creator>Content Modelling : Content for the Masses</dc:creator>
		<pubDate>Mon, 18 May 2009 19:14:03 +0000</pubDate>
		<guid isPermaLink="false">http://contentstrategy.rsgracey.com/?p=82#comment-46</guid>
		<description>[...] and mind meld them with what others working upstream of the build phase are thinking. For example, Stephen Gracey&#8217;s approaches content modelling from the strategists perspective. Again, an interesting [...]</description>
		<content:encoded><![CDATA[<p>[...] and mind meld them with what others working upstream of the build phase are thinking. For example, Stephen Gracey&#8217;s approaches content modelling from the strategists perspective. Again, an interesting [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
