<?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: Universal Challenge: Aligning Processes and Systems (Part 1)	</title>
	<atom:link href="https://cporising.com/2010/06/16/universal-challenges-aligning-processes-and-systems-part-1/feed/" rel="self" type="application/rss+xml" />
	<link>https://cporising.com/2010/06/16/universal-challenges-aligning-processes-and-systems-part-1/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=universal-challenges-aligning-processes-and-systems-part-1</link>
	<description>Analyst-led research and intelligence for the procurement community.</description>
	<lastBuildDate>Sat, 13 Jul 2024 01:06:46 +0000</lastBuildDate>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	
	<item>
		<title>
		By: Howard Richman		</title>
		<link>https://cporising.com/2010/06/16/universal-challenges-aligning-processes-and-systems-part-1/comment-page-1/#comment-85</link>

		<dc:creator><![CDATA[Howard Richman]]></dc:creator>
		<pubDate>Thu, 17 Jun 2010 21:20:29 +0000</pubDate>
		<guid isPermaLink="false">https://cporising.com/?p=1415#comment-85</guid>

					<description><![CDATA[Most large IT/process projects are doomed to fail in one (or all) of three ways - they don&#039;t deliver the promised functionality, don&#039;t meet the timeline, and don&#039;t meet the budget.  The solution to this is simple - don&#039;t do large projects!!
I feel that 95% of people use only about 5% of the functionality of the tools and systems that they work with (i.e. their laptops). Knowing this, I feel it it much better to take a series of smaller steps.  
What stops this?  For one, software providers give you a great deal if you buy the whole bundle (and then you end up paying license maintenance fees on non-productive applications that sit on the shelf).
Another reason for biting of more than you can chew is the drive for transformational change. Unfortunately, transformational change is not driven by systems, it is driven by culture. Without the cultural shift, the system is bound to fail, as t is only a tool.]]></description>
			<content:encoded><![CDATA[<p>Most large IT/process projects are doomed to fail in one (or all) of three ways &#8211; they don&#8217;t deliver the promised functionality, don&#8217;t meet the timeline, and don&#8217;t meet the budget.  The solution to this is simple &#8211; don&#8217;t do large projects!!<br />
I feel that 95% of people use only about 5% of the functionality of the tools and systems that they work with (i.e. their laptops). Knowing this, I feel it it much better to take a series of smaller steps.<br />
What stops this?  For one, software providers give you a great deal if you buy the whole bundle (and then you end up paying license maintenance fees on non-productive applications that sit on the shelf).<br />
Another reason for biting of more than you can chew is the drive for transformational change. Unfortunately, transformational change is not driven by systems, it is driven by culture. Without the cultural shift, the system is bound to fail, as t is only a tool.</p>
]]></content:encoded>
		
			</item>
	</channel>
</rss>
