In time for Labor Day weekend reading, Amazon is launching 2.0 on Kindle today. It is starting to show up in book stores (print on demand at CreateSpace ). As with previous books, I will be excerpting 10% of the contents over the next few weeks.
2.0 looks at the prospects of S/4HANA which SAP launched in February of this year. Chapter 1 looks over 10 pages on the SAP landscape in which S/4 was introduced
- SAP’s runaway success in the ‘90s came about because its R/3 product dramatically reduced enterprise sprawl…Today, SAP’s cloud competitors are using that very argument against it. Dave Duffield, co-founder of Workday likes to describe having customers on a common code base as the “power of one”. Zach Nelson, CEO of NetSuite touts “one product for many industries”.
- SAP’s product portfolio has exploded, and in the last decade there have been nearly 50, seemingly disconnected acquisitions. That has led Mark Hurd, CEO of competitor Oracle (itself very acquisitive), to sarcastically observe,”I guess we could buy a Dairy Queen.”
- Next, there is the sprawl around SAP’s core applications at its customers. According to Panaya a tool vendor “More than 50% of SAP shops have 40+ satellite applications. Of these less than 10 are SAP applications.” CAST Research Labs has analyzed customizations at several major SAP customers and found most of the customizations were sizable, with many of them high-risk, according to its benchmarks.
- Finally, there is significant growth in the partner ecosystem. At its Global Partner Summit this year, SAP announced it now has 13,000 partners—a five-fold increase in the last decade
- The wide diversity in SAP’s portfolio and its customer base is vividly on display in its advertising budget. This runs the gamut from radio spots promoting the Concur product to small businesses, SuccessFactors billboards at competitor events, corporate branding at hockey stadiums, three-page spreads in The Wall Street journal, hot air balloons and HANA commercials which ask “Can a business have a mind, a spirit, a soul?” It would appear every taxi driver, sports fan and New Age practitioner who can influence software decisions is being targeted. This marketing carries over to social media where SAP executives and fans rave about individual products as if they represent the whole SAP economy
- On this side of the pond, in a patriotic July 4 (U.S Independence Day) guest column titled, “A nation of underdogs,” McDermott wrote:
“From equal tights activists to entrepreneurs, our nation’s history is rife with stories of people who believed the impossible was possible. Indeed, a notion that an underdog can win—whatever his definition of winning may
be—is part of our country’s DNA. It’s a truism I know firsthand.”
- McDermott could inspire the “underdogs” in SAP Nation to tackle the sprawl challenge. With his sales background, he has proven his ability to generate new revenue. The SAP economy, however, does not need more selling. The economy needs "un-selling”—delivering on previous promises, lowering prices to reflect new market realities, and more predictable results. If McDermott can pull that off it could be his lasting legacy at SAP. Dr. Plattner has certainly raised expectations with his own “end of history” statement. After introducing the next-gen product, S/4HANA in early 2015, he told a journalist, “If this doesn’t work, we’re dead. Flat-out dead.”
Bruce J. Rogow on SAP Nation
Bruce J. Rogow is the closest to a Yoda in the IT Industry. With his background at Nolan, Norton, then Gartner, now as principal at IT Odyssey (where he crisscrosses the country in his car visiting CIOs and cataloging their successes and challenges) and ICEX (which facilitates knowledge exchange programs for Enterprise Architects and Data Center Executives from large, mainly global firms), he has seen just about everything in our industry.
He kindly took the time to read SAP Nation and over a nice dinner gave me plenty of feedback. The book has been fortunate to get plenty of media and Amazon reader reviews, but this was one of the most comprehensive - he showed me his dog eared copy.
I invited him to write it up and share the review. Whether you have read the book or not, I encourage you to read his commentary as it is one on the state of CIOs – in SAP world and beyond.
“Overall, I found the book very informative related to many of the aspects of what has been one of the two or three most dominant Information Technology Master Platforms of the past twenty plus years. Vinnie has put a number of issues and questions on the table.
As I read the SAP Nation the following thoughts developed:
1.Soft Factors: I have found from my experience that most of the challenges and failures with SAP (and other ERPs) relate to soft factors of behavior, culture, cultural resistance, lack of detail thinking, politics & ownership, inability to adjust to the nuances of the business and CEOs who are quick to agree to an ERP but wouldn't understand or force the change required. Much of the blame for this should be laid at the feet of the 3rd parties, pundits and CEOs who ignored or paid lip service to these issues and blindly pushed their self-serving agendas forward. The book brought out many other technical aspects I hadn't been privy to. The comments in the book by John Dean (former CIO of Steelcase) absolutely resonate with my experience.
2.True Management Consultancies: Where are they when we needed or need them? There used to be real, objective, independent Management Consultancies that saw an ethical barrier between evaluation/risk management/making recommendations and being the “doacy”. Unlike management consultancies, “Doacies” are firms whose primary revenue driver is the large project work of design, implementation or ongoing operations. These “Doacies” masqueraded as management consultancies that would benefit far more from the gigantic implementation project than an objective analysis of client need and capability. If the companies who hired doacies to do the evaluations were naïve enough to not realize the conflict of interest, they deserved the problems they encountered. Business in general suffers from the current “consultancies”.
3.Why Hasn't the Market Worked?: I agree with your premises, but it makes one wonder…if SAP is so widespread, over resourced, under efficient and prone to failure/problems….. Why hasn't the market worked to bring forth successful alternatives? If this huge, lethargic, self-serving SAP Nation is focused on feeding at the trough, why haven’t other alternatives emerged over 20+ years? Not even the supposed “IBM monopoly” lasted this long?
4.Another Estimation Approach to Size SAP Nation: Start with the total overall spend Globally Total IT Spend (GTITS)? This would include the failures, write-offs, etc. CIOs tell me that 25-40% of their total IT spend is associated with their ERPs (ERP%). What % of ERPs is SAP (%SAP)? So, it becomes a rather simple equation= GTITS x ERP% x %SAP. Then add #5 below.
5.Your Estimate of SAP Nation is Conservative: Folks who have implemented or tried to implement an ERP tell me that the costs of internal business resources are equal to or more than the cost of outside or IT resources and software. SAP Nation doesn’t include these costs.
6.Prisoner of Their EgoSystem: It is not just SAP that becomes a prisoner of their own EgoSystem. It has happened to almost every major vendor as I said in my contribution to SAP Nation. It is amazing that Lou Gerstner was able to pull a Lazarus with IBM.
7.Assimilation & Organizational Change: Deploying an ERP or HANA or whatever does not equate to use, assimilation, adoption, benefiting from or the obtaining the change associated with a major system. These are the major failings to me. Failure to get material benefit is far more concerning than a cost or time overrun. The doacies, SAP, pundits and others don’t seem to be concerned with use, assimilation, adoption, benefiting from or obtaining the change associated with a major system other than the opportunity for follow-on work. Vinnie could have written an entire book on this.
8.The Guys in the Cloud are Great, but What Does that Have to Do With Legacy Firms?: I keep hearing about all of these spinoffs or green fields that are able to totally use a cloud based ERP approach. Great. However, these green fields or fresh starts have little relevance to the issues of a legacy, established firm. Given, there are examples of legacy firms being able to convert a portion of their ERP to a Workday or other cloud based approach, but has anyone done a forklift, total migration?
9. Demand Chains: As you mention in the book, the focus of IT is now expanding to include the front office and revenue generation & business development as well as the Internet of Things (IoT). Over the next decade we are likely to see platforms emerge for the generation of revenue or the demand chain much as we have seen the evolution of ERP for Supply Chain and back office administration.
10.Nokia: It is a Finnish and Norwegian company. This is the one factual error I could find in the book.
11.Moore’s Law vs. Rogow’s Rule: The world moves ahead in a balance between Moore’s Law (along with Newton and others) and my Rule which is: Despite Moore’s Law, things can’t move faster than civilization, culture and behavior can buy and assimilate stuff.
12. Asset & Financial Management: IT is and has been an Asset Management game as you allude to in the book. However, the players don’t seem to know the game, hire the right players, get the right tools or even develop the right game plan.
13. Falling for The Pundit/Consultant/Vendor Self-Serving But Irresponsible Demagogue Mantra: “You fools are spending 80%+ to keep the lights on!!! Shame on you!” As stated in #12, IT is an Asset Management game. The basic management economics are depicted in this graphic that is a derivative of what Nolan, Norton & Company developed with clients many, many years ago.
You must start with the non-discretionary expense related to running and properly maintaining, supporting and enhancing existing applications. Prudent IT stewards start with what it costs to run their IT portfolio (Production Cost) of current & previous IT investments. Proper Maintenance, Enhancement & Support are a % of the production cost and are a must to preserve the value and contribution of the previous IT investments. Then, separate funding analysis is required to refresh or replace what you have and for new IT investments. Those NEW IT investments and some replacement investments result in an increase (drop down) of future Production and Maintenance/Enhancement/Support costs. Would you want to fly on an airline that did not know their M+E+S/Prod and shifted it to so they could only buy new planes…BTW, you get to fly on one of the old ones. This does not mean you don’t do all possible to have the most efficient production as well as M+E+S approaches. However, robbing Peter (P, M+E+S) to pay Paul (New Development) may make the current CIO look good, but beware what is left in their wake.
14. Getting Beyond the Procurement: Too much time and energy is spent on the procurement of an ERP by folks who in many cases do not have to live with it and are clueless. They do the wedding and the prenuptial, but others have to live with the marriage.
15. SAP Nation May Be Small Potatoes Compared to Outsourced Nation: The damage, loss of internal critical skills or lack of innovation being experienced in many firms by poor outsourcing is far more costly and impactful than SAP Nation. Perhaps Vinnie will look at that in the future. “
March 16, 2015 in Industry Commentary, SAP Nation Book | Permalink | Comments (3) | TrackBack (0)