Business Solutions with SAP

Competitive Pressures and Value Propositions, Is Lean the Answer?

November 10th, 2009 by

business and IT strategy

Modern technology has lowered the barrier to entry for new competitors by allowing international outsourcing, greater agility, quicker product design to market, and specialized focus on niche markets causing more market fragmentation and specialization. Customers have a wide variety of information from sellers and the Internet about products, design, services, options, pricing, and availability.  Things are more dynamic than ever.

Because of the pace of change, focusing on “best practices” and internal process improvement, or even extending processes is no longer enough. Business can rarely (if ever today) integrate, automate, and streamline to achieve marketplace success –, to one degree or another nearly every competitor is doing this or is quickly headed in that direction.

Business complexity and the breakneck pace of change turns yesterday’s breakthrough technology into today’s commodity; vendors are modestly integrated into the extended supply chain, all the way from raw materials to end customer delivery; customers are more sophisticated and have more options than ever through the Internet; competitors have worked to incorporate similar technology throughout their entire process chains by integrating, automating, and accelerating their processes.  As a result, business demand on technology simultaneously creates new opportunities and new struggles. 

For years SAP has been trying to encourage their customer base to focus on creating value as one way to address some of the changing business dynamics. SAP has developed major toolsets to focus on strategy and value for over a decade and often reference this need for a value and strategic focus in their literature:

Investing in technology is only half the game. Investing in IT without analogous improvements in the management practices around IT will lead only to a slight increase in productivity. Leading companies that invest in IT while enhancing management practices and governance have experienced sustainable results in increased value and improved productivity, in some instances as much as a 20% boost (reported in Stephen J. Dorgan and John J. Dowdy, “When IT Lifts Productivity,” The McKinsey Quarterly, November 2004)… [A]n IT project needs to be not only on time and on budget but also on value. Similar to any other capital investment, the project is not done when it goes live.

SAP Executive Insight Series. Accelerate Value Creation: The Virtuous Cycle of Using Technology to Maximize Business Value, pg. 3, September 7, 2009.

SAP built a multi-billion dollar business based on helping business succeed in strategy and value as critical components of their software implementation. So why isn’t it happening? 

What about “Lean”?

If you are embarking on “Lean” initiatives it indicates that your market space already is, or is rapidly headed for commoditization. The reason is that “Lean” processes are primarily another type of process improvement initiative that only addresses one of the three key areas of the “value proposition.” Lean focuses on the value proposition area of operational excellence but does very little in the other key arenas of customer focus or innovation. In turn, operational excellence addresses cost reduction through automation, cycle-time reduction, and operational efficiency.  But is that what you need?

Excess capacities, combined with the frequent layoffs that occur during economic downturns indicate that many enterprises are operating at or near optimal levels, maybe not perfect, but certainly efficient. Whatever backlog exists before any market downturn or disruption is low enough that those backlogs quickly dissolve. When market downturns occur, resources are adjusted relatively quickly in response. As market downturns point out, integration, automation, and streamlining are not the problem. The excess capacity, whether in products or services, demonstrates that processes are effective and efficient.

Do you need “Lean” or Six Sigma? Maybe, maybe not. There are two reasons your business or organization should consider this operational excellence proposition over the others–, 1) your competitors are beating you on price, or your market is already a commodity or is quickly becoming commoditized, or 2) if your product or service requires a significant amount of precision, Lean makes sense.  Otherwise why would your pour your company’s limited resources, time, and energy into these methodologies where the “last mile” of change has the highest cost but yields the smallest gains? 

If your competitors have a significant price point advantage then it may make sense. Otherwise your efforts and resources might be better spent focusing on competitive pressures, market dynamics, business strategy, IT strategy, and value propositions.  With Lean you may be running a dangerous race to the lowest price in the marketplace that will squeeze your profit margins, press your cash flows, and commoditize your products or services.  On top of all of this you may risk of stagnating or even declining stock prices unless you are able to capture significant market share.

Using “Lean” methodologies to squeeze out the “last mile” of very small efficiency gains is no longer enough to gain real competitive advantage in the marketplace. It might eliminate or streamline some of the bureaucracy, and it will help to minimally improve margins and improve cycle times, but it will not create breakthroughs that companies need to survive and thrive in today’s business environment. In a nutshell, process integration, automation, and streamlining is not the only issue to be addressed.

Is there an Answer to Competitive Pressures and Value Propositions?

If your organization approaches your SAP or IT investment from a business and IT strategy perspective you are far more likely to achieve the kind of benefits and results you are looking for. Unfortunately by the time you get to the RFP you are asking vendors to bid on a project where there is a built in emphasis on putting the system in.  Integrators are bidding on the IT work, not on business transformation, not on business benefit, not on business goals, not on addressing competitive pressures–, the RFP only addresses IT work. Before the vendor RFP is issued by your company you should be having key internal discussions about why you are doing the project.  What are your business drivers?  The direction of the company must be considered, the key goals and initiatives defined, and then your RFP should insist on vendors demonstrating their direct competence on delivering solutions that enable your key business drivers.

IT Directors, CIOs, CFOs, and other key decision makers who influence technology decisions find it difficult, if not impossible for their vendors to provide the innovation and guidance for this type of implementation. It is a creature of the business climate and the traditional RFP approach that these typical implementations occur in.  Some of the things that influence the RFP focus on delivering a technology solution rather than business solutions are:

1. ERP systems generally can be very costly to implement.

2. The marketplace has dictated lower implementation costs, which has in turn led to;
   a. Implementation “success” being defined down to “on time and on budget.”
   b. Many software vendors hire the least cost but acceptable application consultants to meet some cost and margin goals.

3. Few or no real entrance requirements to SAP consulting has led to a wholesale consultant cottage industry of frauds and fakes that are not well-vetted.

4. Of the actual SAP consultants with verifiable experience few have real business background outside of an SAP implementation (as a result they do not understand value propositions, business strategies, competitive markets, etc.).

5. Fewer consultants have real process integration experience to be able to cover an entire process from start to finish. For example, there are few genuine “Order to Cash” or “Requisition to Pay” or “Plan to Produce” consultants.

6. Implementation vendors have no incentive and no requirement to participate in or drive organization success. They have an incentive for project success, as defined by “on time and on budget” but no incentive or guidance on your organization’s success.

If you don’t see the spark of innovation, creativity, strategy, or marketplace understanding in an implementation vendor during the selection process it is unlikely to change once you sign the contract with them. If business expertise and strategy development appears lacking in the consultants being proposed for your project you won’t see it in your project; and it is even less likely you will see it in the SAP solution that is rolled out to the user community. If they don’t have it when they come to the table, they won’t have it when you start paying them! There are ways to change this frequent disappointment:

First, the business must drive the project right from the beginning–, and that beginning is before an RFP is created.

Second, an educational process is required which includes critical tools, resources, methods, and techniques to ensure you finally realize ROI and business benefit from your SAP implementation. And not just cost-focused benefit either, but real business transformation benefits and business focus on the IT investment.  This process must include some repeatable process for evaluating your competitive pressures, addressing your value proposition, and integrating your employees through collaboration.

Third, that new knowledge from the educational process must be incorporated into the entire implementation process, and ultimately in the entire organization–, from before the RFP is issued, to the vendor selection, through the Blueprint, into the Implementation, and throughout the organization once your SAP system is operational.

Today’s organizations need more than the old vendor implementation model, today’s organizations need consultants to deliver results. Previous consulting methods have produced consultants that are little more than expensive commodities that focus exclusively on the “better, faster, cheaper” method of project delivery. But they only deliver technology solutions, they rarely, if ever, deliver business solutions.  That same commodity is available to every organization everywhere. It does nothing to tailor the organization for today’s global competitive pressures or for enhancing their value propositions.

The client or customer who implements, upgrades, and adds on to their SAP landscape can no longer afford the commodity consultant. Because of the lack of genuine business knowledge and experience from application “technicians” there is consistent disappointment from C-level executives who want to see the promise of technology transform their business. These “technicians” are not able to assist in transforming the enterprise, or business, or an organization to compete in today’s marketplace. Your company must insist on more from consulting vendors and from placement firms or you will continue to be disappointed by the lack of results.

Additional Reading and Resources on Business and IT strategy:

The Real Reason Executive Participation Creates IT Project Success

CRM, ERP, BI, and IT Investment — Where Do You Find the Business Benefit?

Why SAP Projects Fail to Deliver ROI (and How to Change IT)

Related Posts:


November 5th, 2009 by

This site was started because of being disgusted with some of the improper, unethical, and potentially even criminal activities that take place in the IT arena. 

Far too often organizations that decide to engage in technology projects are misled and frankly, ripped off.  Our goal on this site is to provide solid content to help educate technology customers so that you become more aware of how to use technology as a lever for success.  We believe that educated, sophisticated, and knowledgeable technology customers are the best kind of customers and none of our consultants are threatened by these challenges. 


Practical Enterprise Transformation Using SAP’s ERP, CRM, SRM, BI, and other applications. The Source for SAP ROI, Business Process Improvement, Business and IT Strategy Integration, SAP Implementations or Upgrades, and Market-Oriented IT Solutions.

Insight from the trenches on how to get the most out of your SAP implementation. No fluff, no sales pitches, just real nuts and bolts on how to do IT and SAP projects the right way to achieve real ROI.

This site is focused on how to get the best SAP application consultants, or other key technology consultants–, the consultants and vendors you want business solutions from.

Related Posts:

ERP Business Case: Do You Really Need a New System?

November 1st, 2009 by

ERP Business Case - Make the Right IT Decision

In many cases those pushing for a new ERP system are comparing the worst of the current environment to an idealistic ERP concept that is all things to all people.

Sometimes the best way to avoid a train wreck is not to get on the train. In other words, do you really need a new ERP system and, if so, is now the right time to proceed? Performing an honest and thorough assessment of business needs and alternatives is an important part of taking ownership in the ERP business case, the decision not to do ERP or any alternative solutions. 

It is understandable this question is not always popular among the ERP zealots; but for the organization, it is a very necessary discussion. There is an old saying that certainly applies: “when you have a hammer in your hand everything can look like a nail”.  That is, believe it or not every organization does not need a new ERP system. 

The problem is when the ERP bandwagon starts to roll and no one in management is asking the right questions, those with legitimate business concerns get steam rolled. It is often not even a fair debate. After all, in many cases those pushing for a new system tend to compare the very worst of the current environment to an idealistic ERP concept that at this stage is all things to all people. Make no mistake; there are plenty of good reasons to implement ERP including many “no brainers”. However, in most organizations the decision is not so obvious and one must objectively evaluate the validity of the proposed business case, timing and not shoot the messengers that raise the red flag. 

Therefore, an executive running a business in the real world must ask the following questions before spending millions of dollars on ERP.  Again, the intention is not necessarily to rain on your ERP parade; but perhaps bring some sanity to the decision-making process.

1. Are the business strategies and assumptions that drive the perceived need for a new ERP system valid?

2. Would an ERP project be one of the top two priorities within the organization (given other internal and external projects, initiatives, or probable events)?

3. What is really broken, the current software or our business processes? (Don’t attempt to automated the mess you already have!)

4. Has the organization attempted to fix the things it can without new software? (The point is bad policies, procedures,  work flows,  controls, cultural issues and measurement systems typically have little or nothing to do with software, but a lot to do with poor business performance).

5. Will the availability of “better information” actually result in better decision-making or make lousy managers more effective?

6. Does anyone understand the data or capabilities of the current software (that are not utilized)?

7. Is the promise of “new technology” always a good reason to throw out application software?

8. Do we have bad software or just bad data (garbage in, garbage out)?

9. Is everything about the current software terrible (or are there areas where a major step backward is inevitable with new software)?

10. Can a few customizations or enhancements to the current software satisfy 80% of the important needs for a fraction of the time and cost? (I know mods are a no no but sometimes they make perfect business sense).

11. Can a few purchased (and integrated) “bolt-on” applications do the trick vs. buying an entirely new package (that likely has a few bolt-ons of its own under the covers)?

12. Is the current software really on the brink of “not supported” by any vendor(after all, they have been saying this for years) and, if so, what are the other support options?

13. Before spending a fortune on software to implement a new operating philosophy or paradigm, should we first “prove out” the idea with a limited pilot? (even when a few software work-arounds are necessary to complete the pilot).

14. Are the perceived operational benefits and cost savings of new software real or fluff? (The history of ERP states they might be fluff)

15. Have we considered ALL the implementation and support cost in the ROI? (Many are not so obvious).

Related Posts: