<?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"
	>
<channel>
	<title>Comments on: Levis blames SAP for falling profitability</title>
	<atom:link href="http://itknowledgeexchange.techtarget.com/sap-watch/levis-blames-sap-for-falling-profitability/feed/" rel="self" type="application/rss+xml" />
	<link>http://itknowledgeexchange.techtarget.com/sap-watch/levis-blames-sap-for-falling-profitability/</link>
	<description>A SearchSAP.com blog</description>
	<pubDate>Fri, 27 Nov 2009 15:08:37 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.2</generator>
		<item>
		<title>By: Leviemployee</title>
		<link>http://itknowledgeexchange.techtarget.com/sap-watch/levis-blames-sap-for-falling-profitability/#comment-881</link>
		<dc:creator>Leviemployee</dc:creator>
		<pubDate>Sat, 07 Feb 2009 18:59:16 +0000</pubDate>
		<guid isPermaLink="false">http://sap.blogs.techtarget.com/2008/07/16/levis-blames-sap-for-falling-profitability/#comment-881</guid>
		<description>This was not an SAP issue. As a current employee of Levi's, they had many successes with SAP in Asia.  Do not blame the CIO or the IT function. We have serious business issues in that company that extend way behind this project.  David Bergen quit Levi's and then all hell broke loose. The major issue was that the IT function (outsourced contractor) made a technical mistake after going live that brought the system down. To blame David Bergen is a mistake. We would have been much worse without a David Bergen.  

Deloitte was the integration partner and could have done a better job in ensuring these types of human mistakes do not happen.  Our business continues not to want to change the processes and the business leadership is not forcing the change. How this becomes an IT issue is amazing. 

All that being said, the system is working fine and we are preparing to continue the project into the new countries.</description>
		<content:encoded><![CDATA[<p>This was not an SAP issue. As a current employee of Levi&#8217;s, they had many successes with SAP in Asia.  Do not blame the CIO or the IT function. We have serious business issues in that company that extend way behind this project.  David Bergen quit Levi&#8217;s and then all hell broke loose. The major issue was that the IT function (outsourced contractor) made a technical mistake after going live that brought the system down. To blame David Bergen is a mistake. We would have been much worse without a David Bergen.  </p>
<p>Deloitte was the integration partner and could have done a better job in ensuring these types of human mistakes do not happen.  Our business continues not to want to change the processes and the business leadership is not forcing the change. How this becomes an IT issue is amazing. </p>
<p>All that being said, the system is working fine and we are preparing to continue the project into the new countries.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: BIG4Guy</title>
		<link>http://itknowledgeexchange.techtarget.com/sap-watch/levis-blames-sap-for-falling-profitability/#comment-810</link>
		<dc:creator>BIG4Guy</dc:creator>
		<pubDate>Wed, 06 Aug 2008 01:23:24 +0000</pubDate>
		<guid isPermaLink="false">http://sap.blogs.techtarget.com/2008/07/16/levis-blames-sap-for-falling-profitability/#comment-810</guid>
		<description>@SAPMAN
B*S*ting doesn't help. So, don't blame the Deloittes or the Capgeminis or the Accentures of the world. Bet, you are one of those people who work for a SAP shop(Levi, et al), one with pre-conceived ideas about Big 4. Our job can be as good as the information provided to us(remember, the cliche "Garbage in Garbage out" - Yeah, that's how the consulting world works). I would be more interested to know what was Levi's key stakeholders'committment to the project like.</description>
		<content:encoded><![CDATA[<p>@SAPMAN<br />
B*S*ting doesn&#8217;t help. So, don&#8217;t blame the Deloittes or the Capgeminis or the Accentures of the world. Bet, you are one of those people who work for a SAP shop(Levi, et al), one with pre-conceived ideas about Big 4. Our job can be as good as the information provided to us(remember, the cliche &#8220;Garbage in Garbage out&#8221; - Yeah, that&#8217;s how the consulting world works). I would be more interested to know what was Levi&#8217;s key stakeholders&#8217;committment to the project like.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: DUNBLAMEBIG3</title>
		<link>http://itknowledgeexchange.techtarget.com/sap-watch/levis-blames-sap-for-falling-profitability/#comment-809</link>
		<dc:creator>DUNBLAMEBIG3</dc:creator>
		<pubDate>Tue, 05 Aug 2008 07:03:28 +0000</pubDate>
		<guid isPermaLink="false">http://sap.blogs.techtarget.com/2008/07/16/levis-blames-sap-for-falling-profitability/#comment-809</guid>
		<description>Do not blame the consulting partners for that.  I was involved in a good implementation by Deloitte in APD.  It was a well-budgeted project.  You pay peanuts you get monkeys!  The consulting partners' act on getting the cheap staff are actually being pressurised from the price squeeze from the customers.  Howevre, consulting firms should uphold their professionality.</description>
		<content:encoded><![CDATA[<p>Do not blame the consulting partners for that.  I was involved in a good implementation by Deloitte in APD.  It was a well-budgeted project.  You pay peanuts you get monkeys!  The consulting partners&#8217; act on getting the cheap staff are actually being pressurised from the price squeeze from the customers.  Howevre, consulting firms should uphold their professionality.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: SAPMAN</title>
		<link>http://itknowledgeexchange.techtarget.com/sap-watch/levis-blames-sap-for-falling-profitability/#comment-808</link>
		<dc:creator>SAPMAN</dc:creator>
		<pubDate>Fri, 01 Aug 2008 07:48:49 +0000</pubDate>
		<guid isPermaLink="false">http://sap.blogs.techtarget.com/2008/07/16/levis-blames-sap-for-falling-profitability/#comment-808</guid>
		<description>It's a well known fact on the market that Deloitte led the implementation at Levi. I have never seen a successful Deloitte implementation - or any other Big 4 (or 3?) for that matter. 

All the Big 3, bring an army of right-out-of-college (and some without college education) kids with zero experience, full of arogance, paying misery salaries and billing them to the customer anywhere from $200 to $500 per hour - I have seen invoices!! 

At one project I saw a Cap Gemini employee on his very first project as a "MANAGER", whose previous job 6 months earlier was a WAITER at PF Changs!!!! and another whose previous job was selling T-Shirts at Planet Hollywood. 

This is what customers are paying for!! Then they blame it on SAP. yeah right...</description>
		<content:encoded><![CDATA[<p>It&#8217;s a well known fact on the market that Deloitte led the implementation at Levi. I have never seen a successful Deloitte implementation - or any other Big 4 (or 3?) for that matter. </p>
<p>All the Big 3, bring an army of right-out-of-college (and some without college education) kids with zero experience, full of arogance, paying misery salaries and billing them to the customer anywhere from $200 to $500 per hour - I have seen invoices!! </p>
<p>At one project I saw a Cap Gemini employee on his very first project as a &#8220;MANAGER&#8221;, whose previous job 6 months earlier was a WAITER at PF Changs!!!! and another whose previous job was selling T-Shirts at Planet Hollywood. </p>
<p>This is what customers are paying for!! Then they blame it on SAP. yeah right&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rabih Charara</title>
		<link>http://itknowledgeexchange.techtarget.com/sap-watch/levis-blames-sap-for-falling-profitability/#comment-807</link>
		<dc:creator>Rabih Charara</dc:creator>
		<pubDate>Sun, 27 Jul 2008 05:05:41 +0000</pubDate>
		<guid isPermaLink="false">http://sap.blogs.techtarget.com/2008/07/16/levis-blames-sap-for-falling-profitability/#comment-807</guid>
		<description>The article says:"The subsequent SAP project in the U.S. may have been rushed." This is the key to failure:"Haste makes waste." Inadequate employee training is linked to the rush. Hershey's rushed its implementation (2.5 years instead of 5 years) and had a spectuclar failure too. Remember it's people who make or break the system not SAP.</description>
		<content:encoded><![CDATA[<p>The article says:&#8221;The subsequent SAP project in the U.S. may have been rushed.&#8221; This is the key to failure:&#8221;Haste makes waste.&#8221; Inadequate employee training is linked to the rush. Hershey&#8217;s rushed its implementation (2.5 years instead of 5 years) and had a spectuclar failure too. Remember it&#8217;s people who make or break the system not SAP.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: SAP Buck</title>
		<link>http://itknowledgeexchange.techtarget.com/sap-watch/levis-blames-sap-for-falling-profitability/#comment-806</link>
		<dc:creator>SAP Buck</dc:creator>
		<pubDate>Fri, 25 Jul 2008 14:20:33 +0000</pubDate>
		<guid isPermaLink="false">http://sap.blogs.techtarget.com/2008/07/16/levis-blames-sap-for-falling-profitability/#comment-806</guid>
		<description>It couldn't be that the business refused to change business processes and tried to get the implementation partner to modify SAP to match the way they did things on the mainframe, could it?</description>
		<content:encoded><![CDATA[<p>It couldn&#8217;t be that the business refused to change business processes and tried to get the implementation partner to modify SAP to match the way they did things on the mainframe, could it?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Razmataz</title>
		<link>http://itknowledgeexchange.techtarget.com/sap-watch/levis-blames-sap-for-falling-profitability/#comment-805</link>
		<dc:creator>Razmataz</dc:creator>
		<pubDate>Thu, 24 Jul 2008 19:27:59 +0000</pubDate>
		<guid isPermaLink="false">http://sap.blogs.techtarget.com/2008/07/16/levis-blames-sap-for-falling-profitability/#comment-805</guid>
		<description>In the information age its not only how but also what you do with the information and that makes or break the organization. Levi's cannot be an exception.</description>
		<content:encoded><![CDATA[<p>In the information age its not only how but also what you do with the information and that makes or break the organization. Levi&#8217;s cannot be an exception.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: SAP Pro in Naperville</title>
		<link>http://itknowledgeexchange.techtarget.com/sap-watch/levis-blames-sap-for-falling-profitability/#comment-804</link>
		<dc:creator>SAP Pro in Naperville</dc:creator>
		<pubDate>Thu, 17 Jul 2008 20:19:32 +0000</pubDate>
		<guid isPermaLink="false">http://sap.blogs.techtarget.com/2008/07/16/levis-blames-sap-for-falling-profitability/#comment-804</guid>
		<description>Hmm, so those companies that have SAP and do well should credit also be crediting SAP for their success? Blaming SAP is a ridiculous excuse on Levi's part. Thousands of companies use SAP successfully.

Having used Levi's website to try and order jeans, I find this article amusing.  You can't even order something in size 34x31. And they wonder why the are getting their a***s kicked in the marketplace?

Give it a try yourself:

http://us.levi.com/product/index.jsp?productId=2072838&#38;cp=2068573.2075200.2075204&#38;parentPage=family

I contacted them about this several times and got zippo for an adequate response.  A blind monkey could do better. I just took my business someplace else.
If Levi's wants to know why their business is off, I would be happy to tell them. They have taken a great brand and ruined it with their lack of focus on the customer.

This is their REAL problem, not SAP.</description>
		<content:encoded><![CDATA[<p>Hmm, so those companies that have SAP and do well should credit also be crediting SAP for their success? Blaming SAP is a ridiculous excuse on Levi&#8217;s part. Thousands of companies use SAP successfully.</p>
<p>Having used Levi&#8217;s website to try and order jeans, I find this article amusing.  You can&#8217;t even order something in size 34&#215;31. And they wonder why the are getting their a***s kicked in the marketplace?</p>
<p>Give it a try yourself:<br />
&nbsp;&lt;a href="http://us.levi.com/product/index.jsp?productId=2072838&amp;cp=2068573.2075200.2075204&amp;parentPage=family" title="http://us.levi.com/product/index.jsp?productId=2072838&amp;cp=2068573.2075200.2075204&amp;parentPage=family" target="_blank"&gt;http://us.levi.com/product/index.jsp?pro&#8230;&lt;/a&gt;</p>
<p>I contacted them about this several times and got zippo for an adequate response.  A blind monkey could do better. I just took my business someplace else.<br />
If Levi&#8217;s wants to know why their business is off, I would be happy to tell them. They have taken a great brand and ruined it with their lack of focus on the customer.</p>
<p>This is their REAL problem, not SAP.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joe SAP</title>
		<link>http://itknowledgeexchange.techtarget.com/sap-watch/levis-blames-sap-for-falling-profitability/#comment-803</link>
		<dc:creator>Joe SAP</dc:creator>
		<pubDate>Thu, 17 Jul 2008 15:24:06 +0000</pubDate>
		<guid isPermaLink="false">http://sap.blogs.techtarget.com/2008/07/16/levis-blames-sap-for-falling-profitability/#comment-803</guid>
		<description>I'm under the impression that a majority of clothing manufacturers are using SAP. SAP as a solution is not the issue here and most likely the blame should fall on the project managers, business process owners and whoever was brought in to facilitate those teams. Do we know who was the implementation partner/s were?</description>
		<content:encoded><![CDATA[<p>I&#8217;m under the impression that a majority of clothing manufacturers are using SAP. SAP as a solution is not the issue here and most likely the blame should fall on the project managers, business process owners and whoever was brought in to facilitate those teams. Do we know who was the implementation partner/s were?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
<!-- dynamic -->