<?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: Which Comes First: the Crew or the CMS?</title>
	<atom:link href="http://jonontech.com/2009/04/12/which-comes-first-the-crew-or-the-cms/feed/" rel="self" type="application/rss+xml" />
	<link>http://jonontech.com/2009/04/12/which-comes-first-the-crew-or-the-cms/</link>
	<description>Confessions of a Digital Agency Nerd</description>
	<lastBuildDate>Wed, 10 Mar 2010 18:43:58 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: David Siedband</title>
		<link>http://jonontech.com/2009/04/12/which-comes-first-the-crew-or-the-cms/#comment-2204</link>
		<dc:creator>David Siedband</dc:creator>
		<pubDate>Tue, 04 Aug 2009 00:22:02 +0000</pubDate>
		<guid isPermaLink="false">http://jonontech.com/?p=473#comment-2204</guid>
		<description>Building a custom CMS implementation is a process; a conversation; a relationship.  The customer should have a list of criteria to start from, and good vendors will ask questions to the customer clarify their needs.  In this process some CMS options will fall out.  At that point, you probably have a short-list of vendors who you resonate with.  Often times vendors work in a specific CMS, so the vendor/CMS choice are often intertwined.  My recommendation is to perform your initial technology choice filtering based on clear criteria.  Based on those criteria you may be equally comfortable with multiple technology choices.  Once you&#039;re narrowed your technology choices make your vendor choice based on communications.  Which vendor listened better?  Who asked better questions?  Who was a better communicator in the scoping process.  That&#039;s the vendor to work with.</description>
		<content:encoded><![CDATA[<p>Building a custom CMS implementation is a process; a conversation; a relationship.  The customer should have a list of criteria to start from, and good vendors will ask questions to the customer clarify their needs.  In this process some CMS options will fall out.  At that point, you probably have a short-list of vendors who you resonate with.  Often times vendors work in a specific CMS, so the vendor/CMS choice are often intertwined.  My recommendation is to perform your initial technology choice filtering based on clear criteria.  Based on those criteria you may be equally comfortable with multiple technology choices.  Once you&#8217;re narrowed your technology choices make your vendor choice based on communications.  Which vendor listened better?  Who asked better questions?  Who was a better communicator in the scoping process.  That&#8217;s the vendor to work with.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jeff Cram</title>
		<link>http://jonontech.com/2009/04/12/which-comes-first-the-crew-or-the-cms/#comment-1142</link>
		<dc:creator>Jeff Cram</dc:creator>
		<pubDate>Thu, 04 Jun 2009 05:46:18 +0000</pubDate>
		<guid isPermaLink="false">http://jonontech.com/?p=473#comment-1142</guid>
		<description>This discussion is hard to have without specifics on the exact business case. However, I believe:

- Both CMS vendor and integrator bring their own biases. It&#039;s critical for the end client to understand these biases going in. An integrator can steer you just as astray as a CMS vendor.

- The biggest mistake organizations make is thinking a CMS project starts with the technology resulting in selecting both cms vendor and integrator based on tech competence alone.

- Having multiple partners is OK. A neutral strategic partner can help you select the right technology and an expert integrator can help you get it done right. This is often the approach that works the best.

- CMS aside, most organizations need a strategic web partner that is looking at the bigger picture. CMS is only a part of an overall web infrastructure and web strategy. You can do a textbook technical CMS implementation and still completely fail. This is something vendor pro services have a hard time understanding. 

We just wrote a post on CMS selection. Would love to hear any thoughts.
http://www.cmsmyth.com/blogs/cms_myth/archive/2009/05/30/does-your-cms-fit.aspx

Jeff Cram
CMS Myth
www.cmsmyth.com</description>
		<content:encoded><![CDATA[<p>This discussion is hard to have without specifics on the exact business case. However, I believe:</p>
<p>- Both CMS vendor and integrator bring their own biases. It&#8217;s critical for the end client to understand these biases going in. An integrator can steer you just as astray as a CMS vendor.</p>
<p>- The biggest mistake organizations make is thinking a CMS project starts with the technology resulting in selecting both cms vendor and integrator based on tech competence alone.</p>
<p>- Having multiple partners is OK. A neutral strategic partner can help you select the right technology and an expert integrator can help you get it done right. This is often the approach that works the best.</p>
<p>- CMS aside, most organizations need a strategic web partner that is looking at the bigger picture. CMS is only a part of an overall web infrastructure and web strategy. You can do a textbook technical CMS implementation and still completely fail. This is something vendor pro services have a hard time understanding. </p>
<p>We just wrote a post on CMS selection. Would love to hear any thoughts.<br />
<a href="http://www.cmsmyth.com/blogs/cms_myth/archive/2009/05/30/does-your-cms-fit.aspx" rel="nofollow">http://www.cmsmyth.com/blogs/cms_myth/archive/2009/05/30/does-your-cms-fit.aspx</a></p>
<p>Jeff Cram<br />
CMS Myth<br />
<a href="http://www.cmsmyth.com" rel="nofollow">http://www.cmsmyth.com</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Philippe Parker</title>
		<link>http://jonontech.com/2009/04/12/which-comes-first-the-crew-or-the-cms/#comment-842</link>
		<dc:creator>Philippe Parker</dc:creator>
		<pubDate>Mon, 18 May 2009 09:49:51 +0000</pubDate>
		<guid isPermaLink="false">http://jonontech.com/?p=473#comment-842</guid>
		<description>Jon,
I largely agree with your process, but I still remain unconvinced overall.
We&#039;ve all worked on projects that have been painful in extreme because the product didn&#039;t do what it was supposed to. That to me is a clear indication that you need to do some significant work selecting the right tool. And you can&#039;t always trust your supplier to do that for you, as they have a vested interest in more services.
Fundamentally, if you&#039;re trying to improve how you manage content you need to pick the right tool. If you care little about those operational aspects, then just pick an agency who&#039;ll build you a great website.
A few further thoughts here: &lt;a href=&quot;http://contentedmanagement.net/blog/people-or-software/&quot; rel=&quot;nofollow&quot;&gt;http://contentedmanagement.net/blog/people-or-software/&lt;/a&gt;.
Philippe</description>
		<content:encoded><![CDATA[<p>Jon,<br />
I largely agree with your process, but I still remain unconvinced overall.<br />
We&#8217;ve all worked on projects that have been painful in extreme because the product didn&#8217;t do what it was supposed to. That to me is a clear indication that you need to do some significant work selecting the right tool. And you can&#8217;t always trust your supplier to do that for you, as they have a vested interest in more services.<br />
Fundamentally, if you&#8217;re trying to improve how you manage content you need to pick the right tool. If you care little about those operational aspects, then just pick an agency who&#8217;ll build you a great website.<br />
A few further thoughts here: <a href="http://contentedmanagement.net/blog/people-or-software/" rel="nofollow">http://contentedmanagement.net/blog/people-or-software/</a>.<br />
Philippe</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jon Marks</title>
		<link>http://jonontech.com/2009/04/12/which-comes-first-the-crew-or-the-cms/#comment-820</link>
		<dc:creator>Jon Marks</dc:creator>
		<pubDate>Sun, 17 May 2009 09:12:49 +0000</pubDate>
		<guid isPermaLink="false">http://jonontech.com/?p=473#comment-820</guid>
		<description>John - I think you&#039;re right. I&#039;ll try to write a separate post outlining my views on Digital Agencies/Systems Integrators/Vendor PS and various hybrids. They&#039;re starting to merge and overlap, but defining them and agreeing a common definition will be useful for taking this forward, and writing a book ;-)

Anyone else want to write their views on it first. I&#039;ve got a raging hangover today ...</description>
		<content:encoded><![CDATA[<p>John &#8211; I think you&#8217;re right. I&#8217;ll try to write a separate post outlining my views on Digital Agencies/Systems Integrators/Vendor PS and various hybrids. They&#8217;re starting to merge and overlap, but defining them and agreeing a common definition will be useful for taking this forward, and writing a book <img src='http://jonontech.com/wp-includes/images/smilies/icon_wink.gif' alt=';-)' class='wp-smiley' /> </p>
<p>Anyone else want to write their views on it first. I&#8217;ve got a raging hangover today &#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ian Truscott</title>
		<link>http://jonontech.com/2009/04/12/which-comes-first-the-crew-or-the-cms/#comment-819</link>
		<dc:creator>Ian Truscott</dc:creator>
		<pubDate>Sun, 17 May 2009 08:56:00 +0000</pubDate>
		<guid isPermaLink="false">http://jonontech.com/?p=473#comment-819</guid>
		<description>@Jon Marks -My point was about when to get the vendor involved, not a partner like yourself, as you point out organizations really benefit from experienced help putting together requirements/wireframes and getting someone in to do that stuff and can cut through @John Goode&#039;s point about internal politics. After that it gets muddy, which I think is your point. 

@John Goode - I think for both end customers and vendor partners  there needs to be some model of proving that this relationship is more than a logo on a website, we used to see too much of &quot;partnerships&quot; being based on a couple of alliances guys having lunch. I am not sure I am qualified to comment beyond that really, I&#039;m a product guy that likes talking to people - the mechanics of the partner economy is probably a minefield I should be cautious of in this company!</description>
		<content:encoded><![CDATA[<p>@Jon Marks -My point was about when to get the vendor involved, not a partner like yourself, as you point out organizations really benefit from experienced help putting together requirements/wireframes and getting someone in to do that stuff and can cut through @John Goode&#8217;s point about internal politics. After that it gets muddy, which I think is your point. </p>
<p>@John Goode &#8211; I think for both end customers and vendor partners  there needs to be some model of proving that this relationship is more than a logo on a website, we used to see too much of &#8220;partnerships&#8221; being based on a couple of alliances guys having lunch. I am not sure I am qualified to comment beyond that really, I&#8217;m a product guy that likes talking to people &#8211; the mechanics of the partner economy is probably a minefield I should be cautious of in this company!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John Goode</title>
		<link>http://jonontech.com/2009/04/12/which-comes-first-the-crew-or-the-cms/#comment-814</link>
		<dc:creator>John Goode</dc:creator>
		<pubDate>Sun, 17 May 2009 07:08:21 +0000</pubDate>
		<guid isPermaLink="false">http://jonontech.com/?p=473#comment-814</guid>
		<description>@Ian Truscott, @Jon Marks. Can we discuss the difference in project delivery methods and style between Vendor PS team and Vendor Partner (Digital Agency)?

It&#039;s my experience that Vendor PS teams exist to facilitate sales. They don&#039;t usually offer UX as an intrinsic component of their delivery.

Are we clear about the difference? The reason I ask this is that as a digital agency we&#039;re often rated and categorised by WCMS vendors. Some just want to monitor, control and accredit competency. Others want to take it further. I wonder how well equipped vendors are in measuring and categorising their partner organisations?

I also worry about how many clients know the difference between a Digital Agency, an SI and a Vendor PS team etc and when to select one from this or any other list?

Many of the players in this space have smudged boundaries. Clarity helps to determine the importance of *crew* selection. Ordinary folk may appreciate your comments….</description>
		<content:encoded><![CDATA[<p>@Ian Truscott, @Jon Marks. Can we discuss the difference in project delivery methods and style between Vendor PS team and Vendor Partner (Digital Agency)?</p>
<p>It&#8217;s my experience that Vendor PS teams exist to facilitate sales. They don&#8217;t usually offer UX as an intrinsic component of their delivery.</p>
<p>Are we clear about the difference? The reason I ask this is that as a digital agency we&#8217;re often rated and categorised by WCMS vendors. Some just want to monitor, control and accredit competency. Others want to take it further. I wonder how well equipped vendors are in measuring and categorising their partner organisations?</p>
<p>I also worry about how many clients know the difference between a Digital Agency, an SI and a Vendor PS team etc and when to select one from this or any other list?</p>
<p>Many of the players in this space have smudged boundaries. Clarity helps to determine the importance of *crew* selection. Ordinary folk may appreciate your comments….</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jon Marks</title>
		<link>http://jonontech.com/2009/04/12/which-comes-first-the-crew-or-the-cms/#comment-790</link>
		<dc:creator>Jon Marks</dc:creator>
		<pubDate>Sat, 16 May 2009 14:21:56 +0000</pubDate>
		<guid isPermaLink="false">http://jonontech.com/?p=473#comment-790</guid>
		<description>Yep, all makes sense. Unless you&#039;re a full service agency like LBi. Half of the work we do is the user research, writing the requirements, doing the wireframes, clickable prototypes, testing these, iterating these, continually liaising with the technical teams to ensure the output of the wireframes and requirements make sense and reasonable within the implementation budget. If we get engaged after the wireframes have been done, it&#039;s too late for us. Hence the dilemma I was talking about towards the end of the post.

I also find that if we are engaged after the requirements and wireframes are complete, the focus is often far too front end, and the back end usability requirements and content model definition are sadly lacking. Which is sad as these are the areas that affect the CMS selection more to than the front end. I tried to explain this (badly) in the post &lt;a href=&quot;http://jonontech.com/2009/04/16/oh-cms-deliver-me/&quot; rel=&quot;nofollow&quot;&gt;Oh CMS, Deliver Me 
&lt;/a&gt;.

Referring back to my numbered steps, I am pretty convinced that the CMS vendors should only be engaged at Step 4 after the wireframes. That&#039;s almost the definition of our User Centered Design process. But which steps would you think an Agency like LBi (or Avenue A/Razorfish, Sapient, Conchango and our other competitors) would be involved in? Which, if any, of my 3 options are viable?</description>
		<content:encoded><![CDATA[<p>Yep, all makes sense. Unless you&#8217;re a full service agency like LBi. Half of the work we do is the user research, writing the requirements, doing the wireframes, clickable prototypes, testing these, iterating these, continually liaising with the technical teams to ensure the output of the wireframes and requirements make sense and reasonable within the implementation budget. If we get engaged after the wireframes have been done, it&#8217;s too late for us. Hence the dilemma I was talking about towards the end of the post.</p>
<p>I also find that if we are engaged after the requirements and wireframes are complete, the focus is often far too front end, and the back end usability requirements and content model definition are sadly lacking. Which is sad as these are the areas that affect the CMS selection more to than the front end. I tried to explain this (badly) in the post <a href="http://jonontech.com/2009/04/16/oh-cms-deliver-me/" rel="nofollow">Oh CMS, Deliver Me<br />
</a>.</p>
<p>Referring back to my numbered steps, I am pretty convinced that the CMS vendors should only be engaged at Step 4 after the wireframes. That&#8217;s almost the definition of our User Centered Design process. But which steps would you think an Agency like LBi (or Avenue A/Razorfish, Sapient, Conchango and our other competitors) would be involved in? Which, if any, of my 3 options are viable?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jon Marks</title>
		<link>http://jonontech.com/2009/04/12/which-comes-first-the-crew-or-the-cms/#comment-789</link>
		<dc:creator>Jon Marks</dc:creator>
		<pubDate>Sat, 16 May 2009 14:06:51 +0000</pubDate>
		<guid isPermaLink="false">http://jonontech.com/?p=473#comment-789</guid>
		<description>Maybe you are right. But then I&#039;m still unlucky. I&#039;m currently involved in 3 (all started in the last few months) where step 1 is to select the CMS. With a CMS vendor that is partner channel only, sometimes we then have to help by doing CMS demos, filling in matrices and more. Should the CMS we are pimping be selected, then we are fortunate enough to get an ITT to compete against other partners of the CMS vendor that haven&#039;t had to spend anything on the processes up to that point. Such is life, I guess.

It might be because most of our clients/prospects are quite large organisations and so their procument is very rigid. They have many procedures for product/vendor selections that kick in. The smaller companies often just let us pick the CMS.

I&#039;d love for us to just say no to this kind of process, but it seems we don&#039;t say no enough these days if the prize is juicy.</description>
		<content:encoded><![CDATA[<p>Maybe you are right. But then I&#8217;m still unlucky. I&#8217;m currently involved in 3 (all started in the last few months) where step 1 is to select the CMS. With a CMS vendor that is partner channel only, sometimes we then have to help by doing CMS demos, filling in matrices and more. Should the CMS we are pimping be selected, then we are fortunate enough to get an ITT to compete against other partners of the CMS vendor that haven&#8217;t had to spend anything on the processes up to that point. Such is life, I guess.</p>
<p>It might be because most of our clients/prospects are quite large organisations and so their procument is very rigid. They have many procedures for product/vendor selections that kick in. The smaller companies often just let us pick the CMS.</p>
<p>I&#8217;d love for us to just say no to this kind of process, but it seems we don&#8217;t say no enough these days if the prize is juicy.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Steph Gray</title>
		<link>http://jonontech.com/2009/04/12/which-comes-first-the-crew-or-the-cms/#comment-788</link>
		<dc:creator>Steph Gray</dc:creator>
		<pubDate>Sat, 16 May 2009 13:16:53 +0000</pubDate>
		<guid isPermaLink="false">http://jonontech.com/?p=473#comment-788</guid>
		<description>Jon - I think you may have been unlucky. Agency-side, I think most briefs we saw were open-minded about CMS except where the client already had an established site in place. Within govt (where my experience is more limited), I&#039;d say the two are often procured together. But there&#039;s still a big emphasis on the CMS and its functionality, which is probably excessive. As I said in my original tweet, bad implementation of a sophisticated tool probably lands you in a worse position than good implementation of something more basic (and probably cheaper). I know from working with good developers just what pain and negative motivation can come from fighting against a supposedly easy to use but badly engineered CMS.</description>
		<content:encoded><![CDATA[<p>Jon &#8211; I think you may have been unlucky. Agency-side, I think most briefs we saw were open-minded about CMS except where the client already had an established site in place. Within govt (where my experience is more limited), I&#8217;d say the two are often procured together. But there&#8217;s still a big emphasis on the CMS and its functionality, which is probably excessive. As I said in my original tweet, bad implementation of a sophisticated tool probably lands you in a worse position than good implementation of something more basic (and probably cheaper). I know from working with good developers just what pain and negative motivation can come from fighting against a supposedly easy to use but badly engineered CMS.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Twitter.com/Squizme</title>
		<link>http://jonontech.com/2009/04/12/which-comes-first-the-crew-or-the-cms/#comment-783</link>
		<dc:creator>Twitter.com/Squizme</dc:creator>
		<pubDate>Sat, 16 May 2009 11:53:38 +0000</pubDate>
		<guid isPermaLink="false">http://jonontech.com/?p=473#comment-783</guid>
		<description>We kinda sit right in the middle as we develop a supported open source platform called MySource Matrix and essentially provide professional services around this.

I dont understand why agencies need so many cms products and from feedback puts the living fear of god into the client when forced to engage with such a choice, ( cms overload totally ).

I would look at open source cms platforms and build your platform on a product that is constantly evolving &amp; take out a support / SLA agreement to provide your organization warranty / peace of mind with minimal costs with the archaic license models out there.

This debate is spot on and I would welcome any non agency / vendor individuals to come to a upcoming event to network with 150 of UK leading industry professionals on this very subject. 

There is a  free 1/2 day seminar / debate being held at Australia House July 2nd with networking event afterwards.

( sorry no agencies, vendors ) a panel hosted by Gartner,World Health Organization &amp; eConsultancy entitled &quot;The Future of Web Content Management&quot;.

To read more how to bring this topic to a wider audience feel free to register at:http://tinyurl.com/qsyne4


Great post 

D</description>
		<content:encoded><![CDATA[<p>We kinda sit right in the middle as we develop a supported open source platform called MySource Matrix and essentially provide professional services around this.</p>
<p>I dont understand why agencies need so many cms products and from feedback puts the living fear of god into the client when forced to engage with such a choice, ( cms overload totally ).</p>
<p>I would look at open source cms platforms and build your platform on a product that is constantly evolving &amp; take out a support / SLA agreement to provide your organization warranty / peace of mind with minimal costs with the archaic license models out there.</p>
<p>This debate is spot on and I would welcome any non agency / vendor individuals to come to a upcoming event to network with 150 of UK leading industry professionals on this very subject. </p>
<p>There is a  free 1/2 day seminar / debate being held at Australia House July 2nd with networking event afterwards.</p>
<p>( sorry no agencies, vendors ) a panel hosted by Gartner,World Health Organization &amp; eConsultancy entitled &#8220;The Future of Web Content Management&#8221;.</p>
<p>To read more how to bring this topic to a wider audience feel free to register at:http://tinyurl.com/qsyne4</p>
<p>Great post </p>
<p>D</p>
]]></content:encoded>
	</item>
</channel>
</rss>
