Big Data. Big Decisions
InformationWeek
Special Coverage Series

Commentary

Bob Evans

Global CIO: An Open Letter To SAP CEO Leo Apotheker

SAP's plans to connect its operations and priorities more intimately with its customers are great signs, but they're also just the first steps in what's sure to be a long journey.

Earlier this year, Bob Evans wrote an open letter about software maintenance fees to Oracle's Larry Ellison. Now he's turning his attention to SAP CEO Leo Apotheker.

Dear Leo:

Congratulations on your recently announced commitment to work more closely with customers on not only lean application development but also some terms involving your annual maintenance fees. You've clearly had to think hard about these issues because, as my brainy colleague Mary Hayes Weier has pointed out in her insightful coverage of SAP, you've got to balance the demands of two very different but very insistent constituents: customers whose businesses and IT budgets have been hammered in the global economic downturn, and stockholders who expect you to find a way to fight your way through the downturn without cutting profits.

With regard to the shareholder group, I can't really speak to that issue except to ask this: Please name for me one company whose shareholders are happy but whose customers are not. That is, without ongoing and increasing customer value, you cannot maintain and increase shareholder value. But you're the CEO and you surely know that.

Global CIO
Global CIOs: A Site Just For You
Visit InformationWeek's Global CIO -- our new online community and information resource for CIOs operating in the global economy.

So let me focus more on the customer side of the equation. Again, I'm aware of the recent moves SAP has made to soften the big maintenance-fee increase announced late last year, and you and your company are to be applauded for that open-mindedness. But look at the overall context surrounding that message as perceived by your customers: In a huge InformationWeek cover story by Weier published in January and seen in print and online by more than 1 million IT executives and managers, here's how SAP positioned its decision to jack up maintenance fees by 30% on cash-strapped customers around the globe, from a 17% annual fee to matching Oracle at 22%:

Bill McDermott, president of global field operations at SAP, makes no excuses for moving all of SAP's customers to a 22% maintenance contract within the next few years. "The real criticism you can make is, 'Gee, Bill, why did it take you guys so long to increase the cost of customer support, because you were five points below the industry benchmark of 22% all that time, and giving up shareholder value?' " McDermott says. "That's a fair criticism I'll accept with open arms."

Now, Bill McDermott is an outstanding executive and his accomplishments and leadership at SAP speak for themselves. But, were it not for an equally stunning comment made by a counterpart at Oracle at almost exactly the same time (which I'll get to in a moment), McDermott's ham-handed rationale of "we shoulda hammered our customers a long time ago" would have won him the Tin Ear of the Year award by a landslide. Again, think about that comment from the perspective of the hundreds of thousands of customers and prospects who read it, and tell me if this hypothetical reaction from a CIO is unreasonable: "Hmm -- McDermott is saying that my job as an SAP customer is to keep the his shareholders fed, watered, and happy regardless of how brutally this economy is treating me and my company. And he says he's kicking himself for failing to raise our maintenance fees a long time ago not because we customers would be getting more value in return, but because that would have given SAP's shareholders more value. Is that really how SAP thinks of me?"

 1 | 23  | Next Page »


Related Reading


More Insights




Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

BYTE encourages readers to engage in spirited, healthy debate, including taking us to task. However, BYTE moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. BYTE further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.

Follow InformationWeek

By The Numbers

What Are Your Primary Concerns About Using Big Data Software?

Base: 417 respondents at organizations using or planning to deploy data analytics, BI or statistical analysis software
Data: InformationWeek 2013 Analytics, Business Intelligence and Information Management Survey of 541 business technology professionals, October 2012

What Do You Think?

What's your attitude about SQL analysis on top of Hadoop?
We want fast, standard SQL analysis capabilities on Hadoop ASAP
Hadoop is for unstructured data; SQL is for relational databases
We'll give SQL on Hadoop a try, but relational DBs will remain the mainstay
Given strong SQL support on Hadoop, we'd nix the data warehouse
We're not interested in Hadoop
No opinion



Related Content

From Our Sponsor

Five Big Data Challenges and How to Overcome Them with Visual Analytics

Five Big Data Challenges and How to Overcome Them with Visual Analytics

Business leaders often need a visual snapshot of data to quickly grasp and use it. This paper identifies five challenges in presenting data and how visual analytics can resolve them. Solutions are suggested to overcome the challenges of: speed, data clarity, data quality, displaying meaningful results, and dealing with outliers.

Game-Changing Analytics: How IT Executives Can Use Analytics to Create Innovation and Business Success

Game-Changing Analytics: How IT Executives Can Use Analytics to Create Innovation and Business Success

Today's competitive advantage requires a deeper understanding of your business, your market and your customers. As an IT executive, you can drive that knowledge transformation. In this white paper, learn how to make decisions as a strategic business leader and three steps to begin an analytics initiative within your enterprise.

Data Visualization Techniques: From Basics to Big Data with SAS Visual Analytics

Data Visualization Techniques: From Basics to Big Data with SAS Visual Analytics

High-performance data visualization turns sophisticated analyses into meaningful graphics, leading to faster and smarter decision making. In this white paper, learn how visual analytics can transform big data, with additional features such as real-time functionality, mobile compatibility, robust applications for technical groups and accessibility for nontechnical users.

Big Data: Lessons from the Leaders

Big Data: Lessons from the Leaders

Financial performance, competitive advantage, operational efficiency, strategic decision making - every business goal can extract value from big data, and the time for doubt or inaction has long passed. In this Economist Intelligence Unit report, in-depth interviews with data pioneers reveal the link between the effective use of big data and the bottom line among other results.

Decision-Driven Data Management: A Strategy for Better Decisions with Better Data

Decision-Driven Data Management: A Strategy for Better Decisions with Better Data

Which came first, the data or the decision? This white paper makes the case for having a decision in mind, then tailoring big data's volume, variety and velocity to achieve business results such as overcoming customer dissatisfaction or creating well-informed strategies in real time.

Informationweek Reports

Research: The Big Data Management Challenge

Research: The Big Data Management Challenge

The challenge of big data is real, but most organizations don't differentiate 'big data' from traditional data, and nearly 90% of respondents to our survey use conventional databases as the primary means of handling data. We'll help you understand what constitutes big data (it's not just size) and the numerous management challenges it poses.