My new book is now available to buy here in print version, and in the Kindle eBook version. As with my earlier books, I am excerpting roughly 10% of the 400 page book in a series of posts on my two blogs.
In chapter 8, I covered the final category in the four customer types in the book - Risk-takers, Modernizers, Diversifiers and Bystanders.
"So, it is not surprising that only a small fraction of SAP’s 400,000+ customers have migrated from ECC, Business One,BusinessObjects and other products to its more modern S/4, SuccessFactors, ByD, HANA and SCP.
In fairness, Oracle, Infor, Microsoft, IFS, Unit4 and other vendors have the same issue with their legacy customer bases. You also have to ask why after 20 years Salesforce, NetSuite and other SaaS vendors have still not converted millions of customers from the on-premise world."
I interviewed several analysts about these Bystanders
Holger Mueller of Constellation
"Now they’re in a similar situation. I think SAP pulled a fast one, saying, ’Oh, don’t worry. We copied all the code. S/4 is not a new system. S/4 is just a new implementation where we simplify things and get rid of old things.’ To some extent, it was a technical argument as you got rid of these non relevant tables. The simplification ran the system better, and you got better business intelligence because there was no need for a data warehouse.
However, for SAP, just copying the code wasn’t that easy. Technically, you had to examine the code and truly simplify it to make it work. Besides, the public cloud is not offering the dramatic TCO advantages that R/3 did relative to R/2.
Importantly, I don’t see the functional equivalency. When SAP was started, Hasso has said, he went to ICI, the launch customer, and met a person in the finance department. ‘He showed me how he worked, and I rebuilt that in software. It took us a few months, and then we had that.’
Today, you cannot go to a finance department and ask, ‘How do you use machine learning? What do you do with data science? How do you use the cloud? What are your FP&A best practices?’ These practices are still being distilled. We’re in the era of experimentation."
"To be fair to many of the European CIOs, the vendors also have not done a good job bringing data centers across the ocean. Germany is the largest European economy. Where else should your data center be? There have been so many ones opened in the UK, which makes sense for banking and financial services vendors, but Paris and Frankfurt are much bigger than London. That’s not even an argument."
Cindy Jutras of Mint Jutras
"Anecdotally, the biggest thing that stops them is the perception that they need all their previous customizations. I would argue they probably don’t, partly because new solutions today do more than they did back when they implemented. Plus, they have more ability to con- figure without invasive custom code changes. Partly, it’s because they just didn’t need those customizations. They did it because that’s the way they always did it, and they weren’t willing to bite the bullet and do something even better or different.
I was at a Unit4 conference last year, and I was in a session meant to collect information from customers to help them move to cloud. It was almost like a focus group with product management. The big resistance to moving to cloud is customization, because for so many years Unit4 had the BLINC message — an acronym for “Businesses Living IN Change.” With their SDKs, they actually encouraged code changes, but code changes that would move with upgrades. Now, in a multitenant SaaS solution, even those kinds of code changes are discouraged. But those customers are all sitting on those kinds of code changes, which is making them very resistant to moving into the cloud. I have asked Steve Miranda at Oracle a similar question. Basically, what he said was, ‘I strongly encourage customers not to inventory their customizations and to move forward.’
But I really think it is inertia. People have bad tastes in their mouths from having gone through the blood, sweat and tears of an ERP implementation years ago. I don’t think it needs to be like that today, but that’s the perception."
Frank Scavo of Strativa
"Vendors like Infor and Oracle have tried to move legacy customers to the cloud with initiatives called UpgradeX and SOAR, respectively. The reason you don’t have very many SOAR and Upgrade X customers to talk to is because there are not that many of them. Existing customers do not make that cloud conversion routinely."
"Some of these companies are running on operating systems that aren’t even supported anymore, so they’re running patched versions. They’re not getting vendor support, and they are running in emulation mode. A “last legs” kind of thing — and still, they will try not to make a conversion.
What are the kinds of events that finally force a company to go to a new ERP? There are several:
- We did an acquisition and we’re now on two ERP systems and this is just not tenable for the long term. We’ve got to standardize on one.
- We expanded our business into Asia and this ERP system is not double-byte or doesn’t support localizations.
- We went into a new line of business that has subscription billing. The [current] system doesn’t do this."
The joys of book reviews
I saw an article aimed at authors and publishers on how to handle critical reviews. And I chuckled to myself "I could have written that myself"
I took most heat for the first volume of SAP Nation - mostly from SAP fans and partners. It was actually a generous history of SAP as it grew from small German vendor to global powerhouse. What I drew attention to was its poor handling of partners and the massive costs and project failures in the ecosystem. Five years later, I can say with some pride that it had a significant impact. The strategies I highlighted in the book like ring fencing with cloud, two-tier ERP and third party maintenance have gone mainstream. Also, in writing volume 3.0 I saw customers have become cautious in their use of large SIs, they are minimizing change as they move to S/4 etc. That to me is gratifying. I was talking to the customer audience and many of them have benefited from the book.
I was criticized for not being alarmist enough with Silicon Collar. The book came out when prominent Oxford profs and Gartner analysts were screaming about catastrophic job losses from automation. Mine was a tone of optimism - automation makes us safer, smarter, speedier workers. Machines typically impact repetitive tasks not complete jobs. Automation takes time to mature, it is not cheap. History has proved me right so far. Very few job losses from machines. We are pushing back dates for autonomous vehicles, for payback from machine learning. Two disappointments from the book- I had hoped SIs and outsourcers would automate their own operations - but they are mostly sticking to labor intensive models. The other was software vendors would reshape processes to reflect growing drones and telematics in logistics, sensors, 3D printing and wearables on the shop floor, robotics everywhere but it may take a wave of greenfield vendors to come along to do that.
I am starting to hear criticism I am "too nice" to SAP in the latest, volume 3.0 of SAP Nation. I am actually pretty tough on SAP in a number of chapters. What I do point out is how little its competition has evolved in the last 5 years. So many missed opportunities. Some of the criticism is coming from them for highlighting their performance. To me, again, that is background noise. The book gave me a chance to highlight 200+ pages of case studies talking about a slew of new SAP products. Hopefully, the customer audience benefits from that and sees that this is not "your Dad's SAP". And the competitors realize the clock is reset and they can show much more progress by the time I start to write volume 4.0 in the series.
I tend to be a tough critic myself. The New Polymath was one of my best reviewed books and it was gratifying to get a number of comments about people wanting to expand their own skillsets. What I had hoped in addition was it would spur Polymath organizations like the GE Global Research Center I described in the book "Conversations in the cafeteria, in the hallways, and at the 40 - room lodge attached to the center effortlessly drift from pathology to holography, from one “ aha ” to another. The Global Research ethos is “ Innovation occurs at the intersection of disciplines. ” So, put chemists, mathematicians, engineers of all stripes, and biologists in close proximity and who knows where the conversations will lead."
The New Technology Elite was about smart products (analog products made digital with software, sensors and satellite support) and covered design, IP issues, the application of Moore's Law, a need to plan multiple releases, product documentation and training and a number of other dimensions. I see so many smart products launched in the last decade which could have used that advice. You wonder, for example, how things would have worked out if Boeing had provided better documentation and training around the MCAS software and the Angle of Attack sensor on the 737 MAX.
I write books to stay in touch with practitioners - my case study heavy style makes me reach out to over a hundred for each book. They provide me the reality checks and validations for the themes of each book. They also provide fodder for our advisory work. The ultimate compliments and criticism also comes from them, not from social media. Nothing is more pleasant than a note from a client which says "thank you from saving us from a $50 million mistake" or "you forced us to consider couple more scenarios we had not factored"
Having said all that, I happily sign my books, and enjoy presenting on themes from my books especially to audiences on campuses. See you at an event soon.
April 18, 2019 in Industry Commentary, SAP Nation, the book | Permalink | Comments (0)