I wrote previously about how disruptive technologies will save SAP. However, it’s worth understanding the large dilemma that SAP, and Oracle alike, are facing and why it’s important to understand how success is made with innovation. Let’s first start by stating the definition(s) of innovation as coined by Clay Christensen from the Innovator’s Dilemma.
Sustaining Innovations: What all sustaining technologies have in common is that they improve the performance of established products, along the dimensions of performance that mainstream customers in major markets have historically valued.
Disruptive Innovation: Disruptive technologies bring to a market a very different value proposition than had been available previously…Products based on disruptive technologies are typically cheaper, simpler, smaller, and, frequently, more convenient to use.
It’s clear – cloud computing has been disruptive to the enterprise space. As it’s popularity increases it will begin to “cross the chasm” and eventually become a clearly defined market. If you look at the early history of cloud computing (or actually really known as SaaS – Software as a Service) you’ll notice early adoption was quite low. No one understood why you would decide to use a CRM system hosted by someone else. Crazy right? It’s now starting to hit the bend in the hockey stick and is ripe for growth. In order to understand disruptive innovation, let’s look at first why this type of technology historically hasn’t been a sustaining innovation for Enterprise software houses:
- Both companies have not executed any real ability to create their own organic SaaS platform. SAP’s Business ByDesign has been around for about 5 years and hasn’t turned the corner yet. I believe the reason for ByDesign’s failures were largely due to adding too many features too soon, and not really understanding how companies would use the technology. Yes, what I’m saying is that they tried too hard to create a product.
- SAP recently bought SuccessFactors for $3.4bn and Oracle has now bought both Taleo and RightNow.
- Cloud/SaaS solutions have done nothing to improve the performance of any existing technologies in the markets that SAP and Oracle have traditionally served, which is mainly large enterprise using on-premise software. In fact SaaS is about to eat their lunch.
Now let’s lay out why cloud is so disruptive:
- There is a different value proposition (hosted software, maintained by the vendor)
- It’s cheaper (straight forward subscription model), simpler (doesn’t require an army of consultants), and more convenient to use (have a web browser on your computer?)
- SAP is hurrying to use it’s RDS (Rapid Deployment Solutions) to combat and milk it’s existing on-premise software while it can
- SAP and Oracle make a staggering 90% profit margin on enterprise support. Even more interestingly, SAP is now trying to tell the market that they will be the first company to make the cloud profitable. I’m confused as to what core competency SAP possesses that will make that true. Throwing money at a problem doesn’t increase a profit margin.
Ultimately, I’m scared largely for SAP, and less scared for Oracle. Why? First, SAP is really damn good at selling on-premise software. This is one of the most important aspects of Clay Christensen’s theory on innovation. The firms that are most successful at sustaining innovation are also the least likely to succeed in disruptive innovation. Second, from my talks with sales/pre-sales/etc people at Oracle, their products largely operate in silos and tend to compete with each other. Yes, this already happens between Hyperion, JD Edwards, PeopleSoft, etc. So culturally they will embrace an internally competing technology much easier than SAP can.
“We’re trying to manage disruption,” said Mike Eacrett, vice president of product management for SAP HANA at SAP Labs in Palo Alto, Calif. “It’s the innovator’s dilemma,” Eacrett said, “figuring out how to take advantage of new opportunities while managing change.”
I’m not so worried about the success of SAP HANA because the product was built largely out of a group within SAP (and from the Hasso Platner Institute) that has been known to be very autonomous from the rest of the business. This is exactly what Clay Christensen offers as a solution to the Innovator’s Dilemma – an autonomous group that acts solely without discretion of the overall firm. It could theoretically be seen as a sustained innovation in that is improves performance on an existing and established market (databases). The big question will be: if cloud consumes on-premise software, than where will HANA sit?
The truth is, SAP is in an identity crisis. It’s largely been seen as an organically growing giant. It’s now spent nearly $10bn+ over the last half decade on acquisitions and it simply cannot be the organic juggernaut it once was. This is largely due to the externally facing pressure from disruptive technologies. What’s worse is it still boasts it’s ability to innovate using its €1.7bn cost (2010) on R&D as justification. Again, the firms that are so certain about growing their portfolio of sustaining technologies in an existing market are largely in a worse position to support disruptive technology.
So what’s the solution? Simple. Well, simple for me to articulate, but not simple for SAP and Oracle to execute. As Christensen says:
“Survival depends on being able to disrupt yourself. Once you let others disrupt your business, you are heading down the path to death.”
In other words, SAP’s cloud computing division (led by Lars Dalgaard) has to aggressively compete against SAP’s own on-premise software. It has to act completely autonomously. Dalgaard is a visionary with some quirky and non-traditional management practices. Which is why I think he’s perfectly suited to lead the charge. But will SAP’s top Executives give in to the Street and become another software graveyard or take a short term hit for long term growth?
What do you think? I’m interested to hear others’ opinions on this.
EDIT: Changed some sentence structure in the second to last paragraph. Didn’t make sense before. EDIT2: Changed to ByDesign, not ByDemand. Good thing I don’t get paid to be a full time editor.