March 28, 2007

Shai Agassi – a contrarian view

Shai Agassi is leaving SAP because, in essence, the old guard didn’t want to turn over the reins to him as fast as he would have liked.* Often, this kind of departure is a bad thing (e.g., Ray Lane at Oracle). But I suspect that SAP may actually be improved by Shai’s leaving.

*His other stated reasons include two very good and highly admirable ones – working on energy technologies and improving matters in Israel.

SAP’s technical strategy has three core elements:

  1. Automate business processes.
  2. Provide the technical infrastructure for automating business processes.
  3. Encapsulate process and data at the object/process level.

This strategy has been heavily developed and refined on Shai’s watch, with major contributions from lots of other folks. The issue isn’t vision any more. What SAP needs to do better is execute on the vision.

The problem hasn’t exactly been technology implementation. Rather, it’s been technology implementation anybody cares about. SAP has a huge potential advantage in analytics due to its ability to integrate operational and analytical business processes. But has that gotten past the “potential” stage? Dennis Moore’s’ composite apps strategy is brilliant. But has it much affected anybody’s life? Meanwhile, application functionality is so mature that added development may have diminishing practical returns. So I have to ask: Just where exactly does SAP still have a significant product advantage?

SAP is doing plenty of things well enough to mine its massive installed base. But preserving and increasing the size of the base? For that, vision needs to be turned into more substance. And of senior SAP execs I’ve talked with and listened to — in Shai’s case mainly the latter — Shai wasn’t necessarily at the top of the substance list. Indeed, he’s the only one who routinely left me shaking my head about a gap between rhetoric and actual technological fact.

Bottom line: SAP may do better getting out from underneath Shai’s overarching decision-making.

Links:

Comments

3 Responses to “Shai Agassi – a contrarian view”

  1. Shai Leaves SAP « Getting Technical on March 29th, 2007 4:06 am

    [...] Here is some of the coverage. [...]

  2. The Monash Report»Blog Archive » More on Shai Agassi and SAP on March 29th, 2007 8:04 pm

    [...] Sramana Mitra has a little bit of a different take on Shai Agassi’s departure than mine. At first blush, it’s a distinction almost without a difference. In essence, she argues that Shai was frustrated because he couldn’t make big needed changes fast enough. That’s pretty close to my view that change simply wasn’t happening quickly or completely enough. [...]

  3. The Monash Report»Blog Archive » Some quick thoughts on SAP acquiring Business Objects on October 8th, 2007 2:23 pm

    [...] 2.  The NetWeaver strategy has been failing.  Does anybody care about NetWeaver any more?  The whole thing includes some great ideas, but implementation has been lacking. [...]

Leave a Reply




Feed including blog about enterprise technology strategy and public policy Subscribe to the Monash Research feed via RSS or email:

Login

Search our blogs and white papers

Monash Research blogs

User consulting

Building a short list? Refining your strategic plan? We can help.

Vendor advisory

We tell vendors what's happening -- and, more important, what they should do about it.

Monash Research highlights

Learn about white papers, webcasts, and blog highlights, by RSS or email.