<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>WebSan Solutions Blog &#187; project failure</title>
	<atom:link href="http://www.websan.com/blog/index.php/tag/project-failure/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.websan.com/blog</link>
	<description>Unlock Your Potential!</description>
	<lastBuildDate>Thu, 02 Feb 2012 14:18:00 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.6</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Why do so many technology projects fail? &#8211; Part II</title>
		<link>http://www.websan.com/blog/index.php/2009/09/why-do-so-many-technology-projects-fail-part-ii/</link>
		<comments>http://www.websan.com/blog/index.php/2009/09/why-do-so-many-technology-projects-fail-part-ii/#comments</comments>
		<pubDate>Thu, 10 Sep 2009 13:00:12 +0000</pubDate>
		<dc:creator>aking</dc:creator>
				<category><![CDATA[Dynamics GP]]></category>
		<category><![CDATA[executive sponsorship]]></category>
		<category><![CDATA[project failure]]></category>
		<category><![CDATA[project success]]></category>
		<category><![CDATA[steering committee]]></category>
		<category><![CDATA[Unlock Your Potential]]></category>

		<guid isPermaLink="false">http://www.websan.com/blog/?p=39</guid>
		<description><![CDATA[I&#8217;ve been involved in IT and Supply Chain projects all over the world. I&#8217;ve seen projects achieve all of the objectives, come in under budget and ahead of schedule. I&#8217;ve also seen projects fail to achieve the benefits they set out to, or even outright fail to even work.
And what&#8217;s the #1 difference between success [...]]]></description>
			<content:encoded><![CDATA[<p>I&#8217;ve been involved in IT and Supply Chain projects all over the world. I&#8217;ve seen projects achieve all of the objectives, come in under budget and ahead of schedule. I&#8217;ve also seen projects fail to achieve the benefits they set out to, or even outright fail to even work.</p>
<p>And what&#8217;s the #1 difference between success and failure?</p>
<h3><span style="color: #0000ff;"><strong>Executive Sponsorship</strong></span></h3>
<p>When I am contacted by a prospective client to discuss a new ERP system, I always make sure that the first meeting includes <em><strong>key decision makers</strong>.</em> You may say, &#8220;well of course! You don&#8217;t want to sell to someone who isn&#8217;t authorized to make the purchase.&#8221; And you&#8217;d only be 1/2 right&#8230;</p>
<p>The real reason that the key decision maker needs to be <strong><em>in the very first meeting</em></strong> is because if they aren&#8217;t &#8220;driving the bus&#8221;, then everyone will end up under it. What I mean is that technology projects are complicated and fraught with challenges just by their very nature. If someone at the top of the organization isn&#8217;t driving the success of the project, then it will not work. It may finish, albeit over budget and over schedule, but I can almost guarantee that it won&#8217;t meet the business objectives set at the beginning.</p>
<p>Sometimes a CFO or CEO looks at me funny during the first sales meeting because I&#8217;ve refused to meet with the &#8220;IT guy&#8221; and insist on meeting with them as well. After I explain the reasoning behind it and start the Q&amp;A session that is outlined in the <strong>&#8220;Unlock Your Potential&#8221;</strong> program, they are always heavily engaged and demand to be significant contributors along the way. This is because we <em><strong>create value</strong></em> right at the very first meeting and if there is no significant ROI demonstrated right at the beginning for them, then it ends right there. No one is wasting time.</p>
<p>When the senior leadership is engaged at the beginning of the sales process, they can have a vision of the solution and understand the objectives right at the outset. We always make sure that when we publish the <em>Project Charter</em>, it states clearly what the objectives of the project are; not in &#8220;subjective terms&#8221;, but in real, tangible benefits.</p>
<p>This way, when the project hits a couple of bumps along the way (they always do), the senior management team is aligned to the goals and objectives and the project is put right back on the tracks.</p>
<p>Depending on the complexity of the project, I also sometimes recommend a <strong><span style="text-decoration: underline;">steering committee</span></strong> or <strong>program office</strong> be formed to manage the project along the way.</p>
<p>I&#8217;ll get into those details in the next post&#8230;</p>
]]></content:encoded>
			<wfw:commentRss>http://www.websan.com/blog/index.php/2009/09/why-do-so-many-technology-projects-fail-part-ii/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

