<?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: Consulting doesn&#8217;t work any more. We need to reinvent it.</title>
	<atom:link href="http://peter.evans-greenwood.com/2010/02/25/consulting-doesnt-work-any-more-we-need-to-reinvent-it/feed/" rel="self" type="application/rss+xml" />
	<link>http://peter.evans-greenwood.com/2010/02/25/consulting-doesnt-work-any-more-we-need-to-reinvent-it/</link>
	<description>Trying to understand the intersection between business and technology</description>
	<lastBuildDate>Thu, 01 Dec 2011 14:45:43 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Peter Evans-Greenwood</title>
		<link>http://peter.evans-greenwood.com/2010/02/25/consulting-doesnt-work-any-more-we-need-to-reinvent-it/comment-page-1/#comment-1006</link>
		<dc:creator>Peter Evans-Greenwood</dc:creator>
		<pubDate>Fri, 05 Mar 2010 09:57:34 +0000</pubDate>
		<guid isPermaLink="false">http://peter.evans-greenwood.com/?p=1313#comment-1006</guid>
		<description>I think we need to be careful about how we define that outcome, as it needs to be something meaningful to the business, not simply &quot;delivered project&quot;. What did the project do? Did it save money or created new capability? Or was it simply provisioning an infrastructure project which doesn&#039;t provide an direct business benefit? A good example is to make a percentage fee for providing a successful sale, rather than changing the client for bums on seats in the contact centre. I&#039;m seeing quite a few companies going down this road.&lt;br&gt;&lt;br&gt;Which brings us to the good point with the HP/EDS story; many people forget that moving to &quot;delivering shared business outcomes&quot; implies that the SI/consultancy also shares the risk with the client. If your outcome is to save money, and you don&#039;t (save money that is), then you didn&#039;t deliver the outcome so you don&#039;t make a profit. (In the worst case, you&#039;ll make a large loss.)&lt;br&gt;&lt;br&gt;I agree that for the large efforts (&quot;create a new mobility strategy&quot;) this will mean breaking the large problem down into streams of smaller projects, avoiding the monolithic projects of the past. Each step of the journey needs to create incremental value, as neither consultancy or client can tolerate the risk of a multi-year transformation.&lt;br&gt;&lt;br&gt;And finally, there will some money to be made from &quot;did it, done it&quot; stories of the past, at least in the mid term, as does positioning as a flex resource. However, as we know from the Sieble -&gt; Saleforce stories, demand for that sort of engagement is shrinking quite rapidly.</description>
		<content:encoded><![CDATA[<p>I think we need to be careful about how we define that outcome, as it needs to be something meaningful to the business, not simply &#8220;delivered project&#8221;. What did the project do? Did it save money or created new capability? Or was it simply provisioning an infrastructure project which doesn&#39;t provide an direct business benefit? A good example is to make a percentage fee for providing a successful sale, rather than changing the client for bums on seats in the contact centre. I&#39;m seeing quite a few companies going down this road.</p>
<p>Which brings us to the good point with the HP/EDS story; many people forget that moving to &#8220;delivering shared business outcomes&#8221; implies that the SI/consultancy also shares the risk with the client. If your outcome is to save money, and you don&#39;t (save money that is), then you didn&#39;t deliver the outcome so you don&#39;t make a profit. (In the worst case, you&#39;ll make a large loss.)</p>
<p>I agree that for the large efforts (&#8220;create a new mobility strategy&#8221;) this will mean breaking the large problem down into streams of smaller projects, avoiding the monolithic projects of the past. Each step of the journey needs to create incremental value, as neither consultancy or client can tolerate the risk of a multi-year transformation.</p>
<p>And finally, there will some money to be made from &#8220;did it, done it&#8221; stories of the past, at least in the mid term, as does positioning as a flex resource. However, as we know from the Sieble -&gt; Saleforce stories, demand for that sort of engagement is shrinking quite rapidly.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nigel Walsh</title>
		<link>http://peter.evans-greenwood.com/2010/02/25/consulting-doesnt-work-any-more-we-need-to-reinvent-it/comment-page-1/#comment-1005</link>
		<dc:creator>Nigel Walsh</dc:creator>
		<pubDate>Tue, 02 Mar 2010 02:16:50 +0000</pubDate>
		<guid isPermaLink="false">http://peter.evans-greenwood.com/?p=1313#comment-1005</guid>
		<description>Peter a great post as always.  I was of the opinion though people were already selling (and buying) outcomes.  I view people buying consultancy for a number of specific reasons.&lt;br&gt;&lt;br&gt;1. To augment or add to existing or specific skill sets internally&lt;br&gt;2. To run a specific project / deliverable(s)&lt;br&gt;3. To reduce cost, mitigate risk&lt;br&gt;&lt;br&gt;In most of these, the client is usually accountable/responsible for the underlying project, with specific deliverables being handled by the SI.&lt;br&gt;&lt;br&gt;Expanding on this, you would move to a BPO/BTO where you &#039;lift and shift&#039; or &#039;your mess for less&#039; type engagement.  In either of these the key difference is the SI taking ownership for bigger picture outcomes -  as opposed to smaller project based milestones. Additionally, the win for the SI is in being able to transform the stuff they now own. For example I work with an SI whos rule of thumb is for every 3 client employees, they can do it in 2.  Better processes, technology etc.&lt;br&gt;&lt;br&gt;The challenge they have this with is demonstrated by the recent case from HP/EDS against Murdoch and BSKYB – selling outcomes is costly when it goes wrong.  see here:  &lt;a href=&quot;http://www.ft.com/cms/s/0/e2bd88fe-0ae2-11df-8a26-00144feabdc0.html&quot; rel=&quot;nofollow&quot;&gt;http://www.ft.com/cms/s/0/e2bd88fe-0ae2-11df-8a...&lt;/a&gt;  But you also have to stick your neck out to win in the first place.&lt;br&gt;&lt;br&gt;In this, Sky have been awarded £200M in damages – a hefty fine.. I think the original contract was about £48m.&lt;br&gt;&lt;br&gt;&quot;Did it Done it&quot; now just allows you to be on the long list.  SaaS and other such approaches reduce some of the risk, but there has to be a new way.  SaaS still needs best practice consultancy - at the end of the day its just the same platform managed/hosted by someone else.  Even the best SW deployed badly is still not fit for purpose (sorry, I know preaching to the guy who wrote the book here).&lt;br&gt;&lt;br&gt;Maybe the answer is SI&#039;s do need a larger number of smaller projects – or they just take ownership of the bigger picture, innovate over 7/10 years through transformation &amp; Innovation and hand back a much neater environment should they need to.&lt;br&gt;&lt;br&gt;I’m not sure either of these are different than what they do today though.  Just my initial thoughts.  &lt;br&gt;&lt;br&gt;Nigel</description>
		<content:encoded><![CDATA[<p>Peter a great post as always.  I was of the opinion though people were already selling (and buying) outcomes.  I view people buying consultancy for a number of specific reasons.</p>
<p>1. To augment or add to existing or specific skill sets internally<br />2. To run a specific project / deliverable(s)<br />3. To reduce cost, mitigate risk</p>
<p>In most of these, the client is usually accountable/responsible for the underlying project, with specific deliverables being handled by the SI.</p>
<p>Expanding on this, you would move to a BPO/BTO where you &#39;lift and shift&#39; or &#39;your mess for less&#39; type engagement.  In either of these the key difference is the SI taking ownership for bigger picture outcomes &#8211;  as opposed to smaller project based milestones. Additionally, the win for the SI is in being able to transform the stuff they now own. For example I work with an SI whos rule of thumb is for every 3 client employees, they can do it in 2.  Better processes, technology etc.</p>
<p>The challenge they have this with is demonstrated by the recent case from HP/EDS against Murdoch and BSKYB – selling outcomes is costly when it goes wrong.  see here:  <a href="http://www.ft.com/cms/s/0/e2bd88fe-0ae2-11df-8a26-00144feabdc0.html" rel="nofollow">http://www.ft.com/cms/s/0/e2bd88fe-0ae2-11df-8a&#8230;</a>  But you also have to stick your neck out to win in the first place.</p>
<p>In this, Sky have been awarded £200M in damages – a hefty fine.. I think the original contract was about £48m.</p>
<p>&#8220;Did it Done it&#8221; now just allows you to be on the long list.  SaaS and other such approaches reduce some of the risk, but there has to be a new way.  SaaS still needs best practice consultancy &#8211; at the end of the day its just the same platform managed/hosted by someone else.  Even the best SW deployed badly is still not fit for purpose (sorry, I know preaching to the guy who wrote the book here).</p>
<p>Maybe the answer is SI&#39;s do need a larger number of smaller projects – or they just take ownership of the bigger picture, innovate over 7/10 years through transformation &#038; Innovation and hand back a much neater environment should they need to.</p>
<p>I’m not sure either of these are different than what they do today though.  Just my initial thoughts.  </p>
<p>Nigel</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Massimo</title>
		<link>http://peter.evans-greenwood.com/2010/02/25/consulting-doesnt-work-any-more-we-need-to-reinvent-it/comment-page-1/#comment-1003</link>
		<dc:creator>Massimo</dc:creator>
		<pubDate>Fri, 26 Feb 2010 01:51:35 +0000</pubDate>
		<guid isPermaLink="false">http://peter.evans-greenwood.com/?p=1313#comment-1003</guid>
		<description>Yes indeed, but in my opinion the &quot;cost variabilization&quot; role of consultancy is true in general not only for BPO / Outsourcing.&lt;br&gt;In general, consultancy usage is a strategic choice and depends on many factors not least company culture.</description>
		<content:encoded><![CDATA[<p>Yes indeed, but in my opinion the &#8220;cost variabilization&#8221; role of consultancy is true in general not only for BPO / Outsourcing.<br />In general, consultancy usage is a strategic choice and depends on many factors not least company culture.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Peter Evans-Greenwood</title>
		<link>http://peter.evans-greenwood.com/2010/02/25/consulting-doesnt-work-any-more-we-need-to-reinvent-it/comment-page-1/#comment-1002</link>
		<dc:creator>Peter Evans-Greenwood</dc:creator>
		<pubDate>Fri, 26 Feb 2010 01:11:28 +0000</pubDate>
		<guid isPermaLink="false">http://peter.evans-greenwood.com/?p=1313#comment-1002</guid>
		<description>I hinted at this in the post. SaaS is eroding the BPO and outsource businesses, replacing people (internal or external) with software.</description>
		<content:encoded><![CDATA[<p>I hinted at this in the post. SaaS is eroding the BPO and outsource businesses, replacing people (internal or external) with software.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Massimo</title>
		<link>http://peter.evans-greenwood.com/2010/02/25/consulting-doesnt-work-any-more-we-need-to-reinvent-it/comment-page-1/#comment-998</link>
		<dc:creator>Massimo</dc:creator>
		<pubDate>Thu, 25 Feb 2010 18:38:06 +0000</pubDate>
		<guid isPermaLink="false">http://peter.evans-greenwood.com/?p=1313#comment-998</guid>
		<description>Peter,&lt;br&gt;in the article you explained one half of che consultancy business: selling knowledge, but the other half (or more than that), is that consultancy moves company costs from internal to  external and from fixed (employee) to variable (consultant).</description>
		<content:encoded><![CDATA[<p>Peter,<br />in the article you explained one half of che consultancy business: selling knowledge, but the other half (or more than that), is that consultancy moves company costs from internal to  external and from fixed (employee) to variable (consultant).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: links for 2010-02-25 &#124; Don&#39;t mind Rick</title>
		<link>http://peter.evans-greenwood.com/2010/02/25/consulting-doesnt-work-any-more-we-need-to-reinvent-it/comment-page-1/#comment-1000</link>
		<dc:creator>links for 2010-02-25 &#124; Don&#39;t mind Rick</dc:creator>
		<pubDate>Thu, 25 Feb 2010 14:08:32 +0000</pubDate>
		<guid isPermaLink="false">http://peter.evans-greenwood.com/?p=1313#comment-1000</guid>
		<description>[...] Consulting doesn’t work any more. We need to reinvent it. (tags: innovation) [...]</description>
		<content:encoded><![CDATA[<p>[...] Consulting doesn’t work any more. We need to reinvent it. (tags: innovation) [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: links for 2010-02-25 &#171; burningCat</title>
		<link>http://peter.evans-greenwood.com/2010/02/25/consulting-doesnt-work-any-more-we-need-to-reinvent-it/comment-page-1/#comment-999</link>
		<dc:creator>links for 2010-02-25 &#171; burningCat</dc:creator>
		<pubDate>Thu, 25 Feb 2010 14:07:20 +0000</pubDate>
		<guid isPermaLink="false">http://peter.evans-greenwood.com/?p=1313#comment-999</guid>
		<description>[...] Consulting doesn’t work any more. We need to reinvent it. (tags: innovation) [...]</description>
		<content:encoded><![CDATA[<p>[...] Consulting doesn’t work any more. We need to reinvent it. (tags: innovation) [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Out Smart the Code Monkeys &#171; Diego&#39;s Brain Picks</title>
		<link>http://peter.evans-greenwood.com/2010/02/25/consulting-doesnt-work-any-more-we-need-to-reinvent-it/comment-page-1/#comment-996</link>
		<dc:creator>Out Smart the Code Monkeys &#171; Diego&#39;s Brain Picks</dc:creator>
		<pubDate>Thu, 25 Feb 2010 08:53:10 +0000</pubDate>
		<guid isPermaLink="false">http://peter.evans-greenwood.com/?p=1313#comment-996</guid>
		<description>[...] that come with an established sector competing in a global market. Competition is getting tougher, the &#8216;did it, done it&#8217; has become a weak argument to secure market position. How can IT companies provide value that differentiates their capabilities from the main stream ? [...]</description>
		<content:encoded><![CDATA[<p>[...] that come with an established sector competing in a global market. Competition is getting tougher, the &#8216;did it, done it&#8217; has become a weak argument to secure market position. How can IT companies provide value that differentiates their capabilities from the main stream ? [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

