<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0"><channel><title>The Content Management Blog - Latest Comments</title><link xmlns="http://www.w3.org/2005/Atom" rel="http://api.friendfeed.com/2008/03#sup" href="http://disqus.com/sup/all.sup#forumcomments-9c3c1b7c" type="application/json"/><link>http://theecmblog.disqus.com/</link><description></description><language>en</language><lastBuildDate>Wed, 15 Jul 2009 16:19:47 -0000</lastBuildDate><item><title>Re: Strategy? Do you need one?</title><link>http://www.releasefive.com/?p=106#comment-12712968</link><description>It is Vivek Pandey. My user id is ciaovivek :)</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">ciaovivek</dc:creator><pubDate>Wed, 15 Jul 2009 16:19:47 -0000</pubDate></item><item><title>Re: Strategy? Do you need one?</title><link>http://www.releasefive.com/?p=106#comment-12706352</link><description>Ciaovivek,&lt;br&gt;&lt;br&gt;Thanks for the comment, and boiling my post down to an eloquent one line comment :)&lt;br&gt;&lt;br&gt;Tim</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">timfives</dc:creator><pubDate>Wed, 15 Jul 2009 13:32:41 -0000</pubDate></item><item><title>Re: Strategy? Do you need one?</title><link>http://www.releasefive.com/?p=106#comment-12695183</link><description>If you fail to plan, you plan to fail :)</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">ciaovivek</dc:creator><pubDate>Wed, 15 Jul 2009 10:58:13 -0000</pubDate></item><item><title>Re: How vs. Why</title><link>http://www.releasefive.com/?p=103#comment-12040325</link><description>So true. Why is more important than how as former will pave way to latter.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">ciaovivek</dc:creator><pubDate>Thu, 02 Jul 2009 13:57:44 -0000</pubDate></item><item><title>Re: Change Management &amp;#8211;  (Best Practices)</title><link>http://www.releasefive.com/?p=94#comment-11574909</link><description>Matt, &lt;br&gt;&lt;br&gt;Welcome to the blog.  Your insight is exactly the problem, This is not a focus of technology, it is the application of that technology to solve a business problem, improve a business process or the like.&lt;br&gt;&lt;br&gt;Without representation from the business during the analysis phase, I have yet seen one of these projects be successful.  It is also when the change management starts, you can not start the change management process after the project is completed.&lt;br&gt;&lt;br&gt;Great insights!  Thanks!&lt;br&gt;&lt;br&gt;Tim</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">timfives</dc:creator><pubDate>Mon, 22 Jun 2009 14:51:08 -0000</pubDate></item><item><title>Re: Change Management &amp;#8211;  (Best Practices)</title><link>http://www.releasefive.com/?p=94#comment-11570771</link><description>I worked in publishing as an editor for 19 years, and was involved in a number of ECM implementations. The trick with publishing was that content was the lifeblood of the organization, but most of the tech vendors just did not GET this. They treated our content just like any other content in any other business: healthcare, accounting, legal. They didn't realize our content was a living, breathing thing that needed to be handled as such. They just looked at our content as various files.&lt;br&gt;&lt;br&gt;My point here is that tech vendors fall down because they fail to involve end users at the very inception of change management. If, as a tech vendor, you are making a presentation to a prospect and your only talking to the IT execs, stop the meeting and ask for end users in the business group to be involved. Get their input immediately and up front. I cannot tell you how many times I went into a meeting with a tech vendor and asked them to automate a certain process only to be told, "We can't do that. Your tech guys purchased the X version of our software, which doesn't have that capability. Maybe in the next rev, or for a fee we can customize it for you in 8 weeks." Argh.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Matt</dc:creator><pubDate>Mon, 22 Jun 2009 14:10:21 -0000</pubDate></item><item><title>Re: Program Management for ECM &amp;#8211; (Best Practices)</title><link>http://www.releasefive.com/?p=66#comment-11446748</link><description>Thanks for the reply, it is absolutely true to every IT project!</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">timfives</dc:creator><pubDate>Fri, 19 Jun 2009 09:52:00 -0000</pubDate></item><item><title>Re: Program Management for ECM &amp;#8211; (Best Practices)</title><link>http://www.releasefive.com/?p=66#comment-11438306</link><description>Correct! I’ve had seen it my self. What you put into preparation and proper program management is coming back ten fold when you’re deploying and anchoring the solution in the business. And it’s probably the same for all type of IT project not only ECM implementations…!!!</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">MiBTvede</dc:creator><pubDate>Fri, 19 Jun 2009 02:56:04 -0000</pubDate></item></channel></rss>