What is the Real Story with SAP’s Run Simple?

Executive Summary

  • The Run Simple marketing program by SAP has been quite popular.
  • In this article, we review the accuracy of the Run Simple campaign.

Introduction

For several years now SAP has been using the term simple in its marketing and sales. There is Simple Finance, Simple Logistics, the term “Running Simple,” or “Run Simple,” that is used in many SAP presentations. So what does all this simple stuff mean? In this article, I will cover what is behind it and how the concept should be interpreted by buyers and those that study SAP.

I will begin by analyzing some the statements I was able to find about simplicity from SAP and determine the accuracy of these statements to come to a general conclusion about running simple.

The Effort Put Behind SAP Run Simple

At SAP conferences, SAP and partners drove the concept of SAP Run Simple into the ground. Each partner seemed to have simply worked into their catchphrase “Run Simple with E&Y.” “Let IBM Show You How to Run Simple.”

For a while, there everything was “SAP Run Simple” and a lot of people who had never worked with the software, or had but had forgotten how it worked, were running around saying how simple everything was going to be. SAP Run Simple was the catchphrase that was on SAP marketing literature and SAP Run Simple was woven into many different areas of SAP messaging. Of course, the SAP partners picked up SAP Run Simple with an uncountable number of consulting companies using different takes on SAP Run Simple in order to co-promote with SAP. With SAP Run Simple everything was supposed to now be simple in SAP.

In his book SAP Nation, Vinnie Mirchandani does a very thorough job of covering the history of SAP’s use of the term simple or proposing they will simplify going back to the 1990’s.

The High-Level Concept of SAP Run Simple

At the high level, SAP has been fighting the perception that it ‘s hard to use and that it is expensive. Problems are fighting those perceptions, as they are both true.

  • Is SAP is Difficult to Use?: If you want to produce a forecast, approve a PO, check on inventory, it will be more difficult than in other applications. SAP is known as the most complex of the enterprise software applications. I say this complexity is a perception — however, as a long time SAP consultant, I can say that it is true. One example of this is how long it takes to get things done in the user interface or the SAPGUI. Another is example is how SAP makes integration more difficult than other vendors by preventing the direct interrogation of its database. They are still the only vendor I know of that uses an intermediate document, a relic from the hierarchical data formats of the mainframe era for application integration. Now one might say the complexity is worth it. Whether something is worth its inherent complexity is really a separate discussion from whether something is complex. Interestingly, much of the marketing by SAP that promotes S/4 HANA is how much it simplifies what were complicated things in SAP. The problem though is that it relies upon simplistic platitudes regarding a simplified data model and on the use of Fiori. However, Fiori is not a user interface, it is a series of apps with a very hazy future. I cover this in the article What is in the Fiori Box? Also, is SAP agreeing that their software is very sophisticated right now?
  • Implementation Costs: SAP has the highest cost implementations in nearly any software category that you want to compare. I know this from working on many SAP projects and comparing them to non-SAP projects. Full TCO calculators on SAP and non-SAP applications show this research and allow people to calculate the TCO for their projects. It is precisely why so many consulting companies recommend SAP. No consulting company suggests lower cost SaaS solutions which they can’t make the most money on.

I am bringing up this information above as simply background as to why SAP is motivated to present their systems as easier to use.

Clearly, the “simple” campaign is part of changing the perception.

Understanding the Marketing of SAP Run Simple

Let us take a look of some of the marketing statements on Running Simple. Here is one that caught my eye.

If we simplify everything, we can do anything. SAP helps you streamline your processes, so you have the agility to create new growth opportunities for your business with the world’s most innovative platform.

There are a lot of statements like this on the SAP website. The first part of the paragraph is a platitude or a nursery rhyme. Much like the phrase “if you don’t stand for anything you will far for everything,” or “if the glove does not fit you must acquit.” It is a sentence designed to appeal to our reptilian brains. The last part of the paragraph is completely untrue.

SAP is not the world’s most innovative platform. Also, SAP is not a platform. Every single area of functionality that SAP internally developed it has copied from someplace else (I speak only of the applications SAP developed. I don’t know the acquired applications well enough to make that claim — but those are not SAP applications). That is not necessarily a bad thing, as long as it is credited, but saying you are the most innovative platform does not acknowledge where you obtained these ideas. Like Microsoft, SAP can say that it is big. It can say that it is successful. It can claim enormous monopoly power, that it has the most highly compensated consultants in IT.

However, it cannot claim innovation.

I can list of vendor after vendor that has participated in true innovation. I don’t want to just list them here, but I point out innovative functionality in software vendors at SCM Focus. Let us show some respect for the true innovators. This actually reminds me of a tension-filled interaction between Tywin Lannister and Joeffry on Game of Thrones. At one point Jeoffry, in an effort to establish his authority states “I am King!” Tywin Lanister responds “Any King who has to say “I am King!” is no true king.”

It is amusing. See the clip below:

[tube]https://www.youtube.com/watch?v=4sJY7BTIuPY[/tube] Wouldn’t Tywin say the same thing to SAP for saying they are the most innovative platform in enterprise software? I think he would.

In an article on the topic of making things simple by Frank Scavo, he presented the following areas where SAP was proposing it was more simple with its newer products.

  1. A Simpler Code Base
  2. A Simpler User Interface
  3. Simpler to Implement
  4. Cloud Deployment Simplifying Ongoing Support
  5. Making SAP Simple to Deal With

Let’s go through each of the quotations individually, and then analyze whether the information provided by SAP in each area is true or likely to be true.

A Simpler Code Base

Under HANA the applications can now simply record transactions and not have to create any summarized data fields for later reporting. With HANA, reporting always goes back to the source data in memory to build aggregated data fields on the fly. This shrinks the size of the programs, greatly reducing the number of lines of code, making them less error-prone and easier to debug. It also means that users can now drill down from summary data to details in any way they choose, without having to write special reports or customize the code.

True of False?: Some aspects of column based databases are more simple than row-based databases (what HANA proposes to replace). However, nothing definitive can be said either way. I cover this in Does S/4 HANA Have a Simplified Data Model? SAP has been like a dog with a bone on this one, and they are completely mistaken on this topic.

These are a second point that the code in the application layer has been cut down and simplified. This has repeatedly been referred to by SAP. However, this comment by an architect in the book SAP Nation 2.0 makes me question this proposal.

“What SAP has done with S/4 is simplify the underlying structure through database views in HANA. So it’s another layer on top of the database that compounds very granular underlying database tables into logical business constructs; something that has always been done by the application logic in SAP (the data in SAP is dumb — all the intelligence is in the logic) And since that SAP logic is all process driven in the “order to cash” or “procure to pay” themes, making business sense of that data can be a real bitch. What it is NOT is a material reduction in tables or a simplification of the data structure. Buy definition, it can’t be because those hundreds of million lines of ABAP code all point to those original tables in some way; so until the code is rewritten, the tables still need to exist. And that includes all the customer customizations…”

Additionally, I find this quotation very confusing, because my understanding was that all the ECC tables had been converted into columnar tables and all the code in S/4 in the application layer had been rewritten to address those column based tables.

This quotation calls this into question.

“It’s another layer on top of the layers that already exist. It is additive. And the more layers, the more issues with context and integrity — and the more challenges in maintaining relationships when the underlying tables change. Also, though the views are great for getting things out, but they really can’t put  things back. So it’s really analytics only. To put it back in SAP, you have to follow the old rules and it has to go to the original tables.”

If this architect is correct, then I was misled by several people from SAP that pitched S/4 HANA to a broader group over a year ago and me. Of course, they were just repeating a message they were told to repeat and probably did not know themselves.

Secondly, HANA will take longer to implement, and there is less in the way of skills to manage any HANA complexity compared to competing databases. This is because there are fewer HANA skills in the market than for the competing databases that could be used. This is similar to buying an uncommonly purchased car — it will mean less available mechanics to work on it.

So more likely that not, HANA is a more complex implementation than implementing without HANA. There may be some maintenance benefits from HANA versus more traditional databases, as there are fewer indexes, (which I cover in several articles here) but again HANA has other complexities that come along with it. Here are why SAP’s comments on HANA are so unreliable:

  • SAP misstates both the origin and advantages of column-based databases. None of the technological underpinnings to HANA are exclusive to SAP, and in fact, none of them were invented by SAP.
  • SAP routinely lists the advantages of HANA without listing the disadvantages.

That means any statement by SAP on HANA must be put through a reality blender, to get a balanced final output.

The Verdict? Most Likely Untrue.

A Simpler User Interface:

SAP Fiori provides the user interface for Simple Finance. Fiori apps operate across desktop and mobile devices to provide a simplified user interface for SAP’s applications. They are not just a new presentation layer but in many cases combine SAP transactions into a single user process. For example, entering a manual payment in Accounts Payable can now be done in a single screen instead of the multiple screens it previously required in SAP. On a side note, after much push-back from customers, SAP announced that Fiori apps will now be delivered at no charge to customers under maintenance, removing one barrier to adoption of Simple Finance.

True or False?: Fiori cannot be the user interface for Simple Finance, or what is now just “Finance.” It can’t be the user interface for all of S/4 HANA when it is eventually released in what now looks like next year. I explain why this is the case in the article What is in the Fiori Box?

The user interface for S/4 HANA will be the same (outside of some Fiori apps here and there) will be SAPGUI. Companies that want to get a modern interface need to seek out third parties that are far better at modifying and representing the SAPGUI than SAP is.

The Verdict? Untrue.

Simpler to implement?:

Implementation tools and methodologies are built right into the application, based on SAP’s previous work with its Rapid Deployment Services. These include wizard-like tools to guide and configure the applications. There are data migration tools to map data from existing systems into Simple Finance—whether from previous versions of SAP or from other systems. Implementation testing is also managed within the system itself. In addition, Simple Finance is integrated with SAP’s collaboration system, Jam, to encourage knowledge exchange. If a user runs into problems, for example, he or she can reach out to other users for help.

True or False?: The Rapid Deployment Services of RDSs are a hodgepodge of mostly already existing material that has been repackaged. For instance, it includes:

  • Best Practices documentation, which isn’t best practices. That is another topic which I cover in this article Evidence for SAP’s Best Practice Claims.
  • Configuration documentation
  • Some confusing flow charts
  • Various documents of different types depending upon the RDS in question.
  • Some demo data, again very much depending upon the RDS in question.

A lot of this has been around for quite some time, and is just repackaged into “RDSs.”

I can’t speak to the proposed data migration tools mentioned in the quote. It ‘s hard to see how implementation testing could be performed in the application.

Jam is an unknown quantity at this point, and it is not enough to hang your hat on. Overall, one would have to see new SAP applications installed more quickly than older applications before anything definitive can be said.

In November 30 2015, Hasso Plattner published How to Understand the Business Benefits of SAP S/4 HANA Better.

This article shows some clear frustration on the part of Hasso with the well documented fact that SAP’s customers are having a problem seeing the value in S/4 HANA.

Lets understand each of Hasso’s observations and see how they stack up. You can first read Hasso’s article, which I have provided the link above and then read this one as I have taken out what I think are the most important quotes. I have each of the quotes and my comments organized under the exact headings that are from Hasso’s article.

Hasso on The Reduction in Complexity from S/4 HANA

“For years our customers complained about the complexity of the business suite and asked for simplification. Now some fear they have to relearn a lot and that will cost time and money. The simplification of the UI is real and will save time with the first day of productive use. The business functionality of the transactions is still the same but comes in a much more efficient form.

The dramatic simplification of the data model, the fact that any field can be used as an index for selecting data and the unprecedented short response times are allowing for much faster development cycles of new applications. The deployment of extensions in SAP HANA Cloud Platform is an elegant way to enhance SAP S/4HANA systems or to build completely new applications. SAP S/4HANA combines the proven set of core business functionality, in many languages and for nearly all countries, with the ability to venture into completely new dimensions of applications. This capability is key when business processes are developing at an ever increasing speed and core enterprise systems cannot just be complemented by point solutions but have to also accommodate these changes.  This reduction in complexity also lowers the threshold for smaller companies to switch to SAP S/4HANA.”

Lets look into the detail in each area brought up by Hasso.

  • For Years Our Customers Complained About the Complexity of the Business Suite (ECC): Yes, this is true. However, most of the complaints did not have to do with what HANA is improving. Many of the companies did have to do with the SAPGUI. However, again SAP buyers cannot expect Fiori to cover many of the ECC screens for some time. So Fiori will be used along the same old SAPGUI. Therefore, complaints will continue.
  • The Dramatic Simplification of the Data Model: I cover in Getting Clear on S/4 HANA, that it is debatable whether HANA actually simplifies the data model.
  • ..The Ability to Venture into Completely New Dimensions of Applications: It is hard to see how this is true. S/4 has a (partially) new UI. And Fiori can be customized much more easily than SAPGUI, however, it is still a lot of work, and there is not really a consensus on Fiori yet in terms of whether it will actually stick longterm. The later part of this paragraph is sort of fanciful sales talk and its difficult to really address what Hasso is describing.

The Verdict? Some Things are Untrue; Others are Unknown.

Cloud Deployment Simplifying Ongoing Support

SAP also wants run simple in how customers keep their applications up-to-date. Like most traditional on-premises vendors, the majority of SAP customers are not on the latest releases of its products. The reason is that applying new versions (in SAP lingo, “enhancement packs”) is often a labor-intensive activity—testing the new code, retrofitting any customizations, regression testing to be sure nothing gets broken, and migrating data. SAP’s solution is to take over these responsibilities by hosting customers’ systems in SAP’s HANA Enterprise Cloud (HEC). This program, already rolled out to some early SAP customers, is essentially a managed services offering in which SAP takes all responsibility for day to day operation of the system in SAP’s own data centers. Notably, SAP also takes responsibility for keeping the customer’s system up to date with the latest enhancement packs and bug fixes. It even supports systems with custom modifications.

True or False?: This one is pretty easy. This quote is several years old, and this has not happened. Some of this may be related to price, and some to simply SAP trying to be good at something that it does not have experience in. However, there is no momentum for this year after the HEC was introduced. Everything at the beginning of this quotation above is still the case today.

The Verdict? Untrue.

Making SAP Simple to Deal With

Bill McDermott is always good for some major whoppers. I question how good McDermott is a spokesman at this point for SAP because he has built up a history of saying things that turn out not to be true. It is probably a good time for him to take is stock options and for SAP to bring in a new fresh face to pitch this crazy stuff.

He (McDermott) continued: “For customers, we’re committed to a beautiful user experience. We will make it simple to do business with SAP: simple pricing, pay-as-you-go in the cloud, simple web experience.”

Those are big promises. Anyone who has negotiated an acquisition of SAP software knows that SAP contracts are incredibly complex.  Pricing is opaque, with many various types of named users defined for each product. SAP’s terms and conditions around indirect access (when other systems access information from an SAP system) are onerous.

The result is that it is nearly impossible for an SAP customer to be fully compliant. When SAP does an audit of a customer’s use of SAP products—which it has the right to do—it will find problem, if it looks hard enough.

Even finding the right person in SAP’s organization to deal with is not a simple matter. Whether it is the result of having a worldwide organization or peculiarities of German corporate governance, it is difficult to understand who reports to whom, or who is responsible for what.

True?: I don’t think I need to add anything to what Frank Scavo said.

The Verdict? Untrue.

SAP Run Simple

SAP has huge media influence. The advantages of being big are real. SAP can simply reach out to most media outlets and find them compliant to most messages that SAP has to give them. SAP is a major advertiser so that combined with being big goes a long way to getting their message out.

If a media outlet presents this information without commentary, which they often do, and if SAP does this through a lot of media outlets, then it can seem that the media outlet is endorsing SAP’s marketing machine, when that may not be their real intent. However, if SAP quotations are provided without objective commentary from the article author, then it is very easy to create an echo chamber. That is a lot of pollyannish statements are made by SAP that becomes taken for granted.

Was SAP Run Simple Ever and Accurate Concept?

I have worked in SAP since 1997, and I don’t recall anything in SAP to be simple. SAP may be the standard. It may be robust. But it is not simple. I have noticed a strong correlation between people who propose SAP’s new simplicity and how far away they are from SAP applications, and i.e. how little they know. And of course, it’s much easier to believe something complex is simple — if you don’t have to do the work yourself to configure or setup said system.

Secondly, there was always a problem with using the term “simple” as part of a production name that SAP marketing never picked up on. The word “simple” is a superlative adjective, and adjectives don’t make a lot of sense as part of application names. And after a while, it makes more sense to just drop the adjective as it just becomes redundant. This would be like calling a system “handsome” or “fantastic.” Let us apply this to another application, say the SAS Forecast Server, would become the:

“SAS Outstanding Forecast Server”

See…it just does not work.

Secondly, S/4HANA is not simple. Parts of S/4 HANA can use the Fiori user interface, but quite a bit about S/4HANA is actually more complex. This includes all the changes that are a part of S/4HANA that need time to be understood and incorporated properly into companies.

What Happened to Run Simple?

Then just as quickly as SAP Run Simple had arrived on the scene, the term was removed from the SAP marketing literature. Simple Finance was rename to just Finance. Simple Logistics was renamed to a number of different items, but the word simple was no longer used. SAP Run Simple had run its course as a term to use.

ComputerWorld on SAP’s Run Simple

On August 25, 2014 ComputerWorld published the article SAP’s Simplicity Push Is Not So Simple.

In this article, we will review the article for accuracy.

Article Quotations

“SAP has long grappled with the side effects of its software being perceived as both sophisticated enough to meet the specific needs of almost any company but also complex, expensive and unwieldy.”

SAP’s Complexity is Merely a Perception

The beginning of this article is a problem because it implies that the software is perceived. However, this is not a perception. SAP being not only complex but unnecessarily complex. This pushes the article towards probably pushing SAP’s marketing message that SAP’s obvious complexity is simply a perception. ComputerWorld has some type of financial relationship with SAP that means ComputerWorld normally acts as simply a passive marketing channel for SAP.

HANA is Attached to Everything SAP Does?

“Under CEO Bill McDermott, SAP is pledging to make both its software and its customer-interaction processes simpler. At the Sapphire conference in June, McDermott unveiled Simple Finance, one of a planned series of Hana-powered ERP applications that use the Hana in-memory computing platform and other technologies to slim down the code base and make the user interface more appealing and productive.

Hana is attached to everything we have, McDermott said in a recent interview.”

Bill McDermott is an unreliable source of information on SAP. He is a lifelong salesman with a yearly compensation of $50 million. Previous statements made by Bill McDermott have mostly proven to be untrue. Once again, he is proven wrong when he says HANA is attached to everything SAP does. Six years after its introduction, it only works with a minority of SAP applications and only has penetration into one application for implementation, which is the SAP BW.

Oracle and SAP as Big Cloud Companies?

Like rival Oracle, SAP is in a transition period as its customers, who traditionally bought perpetual licenses for on-premise deployments, look to adopt cloud-based software that is sold by subscription.

Oracle also receives the vast majority of its revenues from on-premises software. Oracle over-reports a number of sales that come from the cloud, but it not very difficult to look under the covers to find out the reality.

SAP’s Run Simple Campaign Must be Fine Tuned?

SAP may need to fine-tune its pledge for more simplicity, says independent analyst Jon Reed. SAP used to sell so much software based on its completeness of functionality, Reed says.

This is a political way of saying that SAP has overstated the “Run Simple” marketing program. Jon Reed is framing it in positive terms, implying that SAP’s complexity is necessary because SAP’s functionality is so complete.

  1. SAP does not have completeness of functionality. SAP lacks functionality where other vendors do have functionality — process industry manufacturing is just one example, and secondly, some of SAP’s functionality that is in the release notes, does not work properly.
  2. Even if a company has “completeness of functionality,” which itself more a term of propaganda rather than a real statement (a more accurate statement would be that an application has a wide breadth of functionality), it does not necessarily follow that this means a great deal of complexity. For example, the vendor Arena Solutions has a wide breadth of functionality for BOM management but is software is easy to use.

One would have to really know close to nothing about SAP to actually believe that SAP is not all of a sudden simple. The entire Run Simple campaign is simply an example of counter-marketing. That is attempting to counter a valid negative perception by asserting the opposite.

It is not declared, but Reed is a co-founder of Diginomica, which counts SAP as a funding entity. Therefore, ComputerWorld, which receives funding from SAP and does not declare this, is obtaining a quote from what appears to be an independent source, in this case, Jon Reed, but there is also not declared of Jon Reed’s relationship to SAP. (Diginomica does declare SAP’s sponsorship on the Diginomica website.) But overall this article has both a biased publisher and then employed biased sources.

But a products sheer depth of features is declining in importance as enterprise software buyers adopt newer, more specialized cloud applications.

This is an interesting observation from Jon Reed. But what this means is that SAP is losing its grip on customers. This is consistent with our primary observation of the SAP market, which is covered at [Brightwork Research & Analysis.]

Customers Tell Jon Reed that SAP is Simple to Use?

The more crucial task for SAP is to make doing business with it easier, and that work is far from done, Reed says. SAP at Sapphire put out simplicity as a leadership mantra: Were going to lead you to a simple future, he says. Its a challenge for SAP to live up to. When I hear customers tell me how simple and easy it is to deal with SAP, Ill get on board.

It is hard to fathom who is telling Jon Reed that it’s simple to use SAP. I am a long term SAP consultant going back to 1997, and to do anything in SAP is always more difficult and complex than doing that same thing in any other competing application.

This is covered in the article [Is SAP’s Run Run Simple Real?]

DSAG on the Simple Story

“SAPs message of simplicity is a good story for customers, says Marco Lenck, chairman of DSAG, a German SAP user group. This is the right direction for customers, but it takes investment in terms of time, knowledge and money to get there.”

Marco Lenck’s quotation here is golden. Marco very nice puts the simplicity story in a box, by calling it what it is. He then basically says that SAP has a lot of work to do in the area.

DSAG is really the only SAP user group that does anything close to its mission of representing user interests to SAP. The only one that has the courage to actually stand up to SAP.

Simple is So Hard!

“One CIO of an SAP shop agrees. Simple is really hard, says David Wascom, CIO of Summit Electric Supply and a board member of the Americas SAP Users Group, because all the steps that have to take place in your business dont go away.”

This is more justifying SAP’s unnecessary complexity. What do “all the steps that have to take place not going away” have to do with SAP’s complexity? Complexity is primarily a feature of software design, and SAP designs extremely complex software, but not because the problem it is solving is particularly complex. A good example of this is the SNP optimizer. The SNP optimizer has a bad design. Other optimizers are far easier to use while SNP’s is essentially useless.

It seems that this article is commingling complexity with bad design. A good measure of software design is how something that is complex can be made simple to use. A good example of this is Airtable. Airtable makes relational databases almost as easy to use as a spreadsheet. The complexity is hidden from the user.

SAP Becoming More Simple?

“Wascom says that he is seeing some signs of improvement lately from SAP, but he’s hoping for more. One of the biggest challenges I have as a business executive is not how to get SAP to give me some particular piece of functionality, he says. The challenge is managing the risk of my SAP investment. To that end, SAP should improve customers visibility into its product road maps, Wascom says.”

This is actually a pretty severe dig at SAP, if you follow SAP. This is because SAP has probably the most confusing product roadmaps of any software vendor. The reason for this is SAP is constantly proposing things in their roadmaps that they are not able to deliver. They allow marketing to control the roadmap and more or less tell development what they will do and when they will do it rather than the other way around. This is because at SAP sales and marketing is far more powerful than development.

But that is actually a slightly different issue from the complexity of the software itself.

Does this Quotation Qualify as a Big Message?

“While committed to SAP technology, Wascom offered cautionary advice to any fellow CIOs who are considering the company’s products.

The big message is that SAP, among the platforms I’ve looked at, is the most powerful and most flexible to meet whatever your business needs are, he says. But with great power comes great complexity. Its not like installing Microsoft Word.”

This is a strange comparison. Microsoft employs no one to install Word, it self-installs. SAP projects fund millions of consultants worldwide and SAP projects can go on for years. This is a major driver of revenues for major multinational consulting companies.

At this point, it seems reasonable to assume that people reading this article would know that SAP does not self-install. This quotation seems designed to minimize expense and complexity and SAP.

And once again, the statement is that complexity is a trade-off for some virtue. But SAP is far too complicated for what it does, and its complexity is a hindrance to using it effectively. I can provide a long list of software vendors that cover the same areas as SAP, but which has far less complexity because they are simply better designed. The best software works this way.

SAP Needs Ombudspeople?

“SAP would benefit from having simplicity ombudspeople who would guide customers through difficult software migrations and improve the entire customer experience, says independent analyst China Martens.”

Isn’t that what large SAP consulting companies are supposed to do? Aren’t they supposed to be independent?

China Martens has to know that SAP gets very little revenue from consulting, and that SAP outsourced it’s consulting in return for being recommended decades ago. Secondly, the software must be designed better, putting consultants on the issue will really only do so much good. But secondly, SAP’s support has been greatly degraded, so now customers are far more frequently left to fend for themselves than in the past.

Also, SAP will never employ any person who supports the customer’s interests to SAP. That is not the way that SAP operates. Even the large consulting companies, who don’t technically report to SAP, behave as if they do, putting the interests of SAP ahead of those of their clients.

Conclusion

SAP Run Simple, which is supposed to apply to S/4HANA really makes no sense, particularly when SAP Run Simple is supposed to apply to just about everything from S/4 to Fiori to HANA, when all of these items are new and will require years of burn in to reach the stability of the products they are replacing.

It is no easy feat keeping up with SAP’s S/4HANA terminology. SAP went through a period where they invested mightily in what was essentially a false marketing construct — that the new applications were somehow simple.

Basically, for all of SAP’s emphasis on their Simple program, it ‘s hard to find any substance to any of it. That is there is no evidence that new SAP applications will be any simpler, in actually any dimension than previous applications.

  • SAP has made some proposals, but they are easily disproven and are designed to exploit those with little understanding of SAP.
  • Other proposals are unknown and depend upon seeing the results in the field. However, they are presented as if they are already proven. This is a consistent theme in SAP’s writing. Unproven conjecture and bragging are presented as if it is an academically researched and settled topic.

The “Run Simple” program was directed at people who are easily tricked. It was a major way that SAP sold HANA and S/4HANA as we cover in the article Does HANA Have a Simplified Data Model and Faster Reconciliation? However, within a few years, Run Simple was a dead marketing program at SAP.

The Necessity of Fact Checking

We ask a question that anyone working in enterprise software should ask.

Should decisions be made based on sales information from 100% financially biased parties like consulting firms, IT analysts, and vendors to companies that do not specialize in fact-checking?

If the answer is “No,” then perhaps there should be a change to the present approach to IT decision making.

In a market where inaccurate information is commonplace, our conclusion from our research is that software project problems and failures correlate to a lack of fact checking of the claims made by vendors and consulting firms. If you are worried that you don’t have the real story from your current sources, we offer the solution.

Financial Disclosure

Financial Bias Disclosure

Neither this article nor any other article on the Brightwork website is paid for by a software vendor, including Oracle, SAP or their competitors. As part of our commitment to publishing independent, unbiased research; no paid media placements, commissions or incentives of any nature are allowed.

Search Our Other HANA Simplification Content

References

https://www.computerworlduk.com/it-vendors/saps-simplicity-push-is-not-so-simple-3539591/

I cover how to interpret risk for IT projects in the following book.

The Risk Estimation Book

Rethinking Enterprise Software Risk: Controlling the Main Risk Factors on IT Projects

Better Managing Software Risk

The software implementation is risky business and success is not a certainty. But you can reduce risk with the strategies in this book. Undertaking software selection and implementation without approximating the project’s risk is a poor way to make decisions about either projects or software. But that’s the way many companies do business, even though 50 percent of IT implementations are deemed failures.

Finding What Works and What Doesn’t

In this book, you will review the strategies commonly used by most companies for mitigating software project risk–and learn why these plans don’t work–and then acquire practical and realistic strategies that will help you to maximize success on your software implementation.

Chapters

Chapter 1: Introduction
Chapter 2: Enterprise Software Risk Management
Chapter 3: The Basics of Enterprise Software Risk Management
Chapter 4: Understanding the Enterprise Software Market
Chapter 5: Software Sell-ability versus Implementability
Chapter 6: Selecting the Right IT Consultant
Chapter 7: How to Use the Reports of Analysts Like Gartner
Chapter 8: How to Interpret Vendor-Provided Information to Reduce Project Risk
Chapter 9: Evaluating Implementation Preparedness
Chapter 10: Using TCO for Decision Making
Chapter 11: The Software Decisions’ Risk Component Model