What This Article Covers
- Case Studies
- What is a Conference Monkey
- How Individuals Lie to For Personal Gain
In many conferences, it is customary to think that consulting companies and software vendors will tell lies in order to increase their sales. But what is surprising to many is that many customers also will lie. I can recall when I worked for Deloitte, I was in many meetings with individuals from my client Lockheed Martin. The Senior Manager from Deloitte was trying to get the members from Lockheed Martin to present at SAPPHIRE. I presented at SAPPHIRE that year as well. When the member from Lockheed Martin presented, I observed him completely mislead the audience about how much progress had been made on the project. This is interesting because the Lockheed Martin representative was one of the more honest people I have worked with on a project. But the pressure he was under was evidently too great. Much of this was while being pressured by the Senior Manager to do so. The Senior Manager needed to sell his own project if he was going to be promoted to Partner, and to do that effectively, he needed to get Lockheed Martin to lie about the progress of the SAP project.
Since that time I have witnessed all manner of people at conferences clearly lying about how quickly they implemented SAP software, what they implemented, etc.
In the Brightwork Research & Analysis study on S/4HANA Implementation Study, there were numerous public case studies where the customer representative clearly lied about what occurred on the S/4HANA implementation. The following are examples:
- Florida Crystals: The CIO stated that Florida Crystals upgraded to S/4HANA in 3 weeks.
- New York Life: New York Life presented the idea that they implemented S/4HANA in order to use S/4HANA’s ledger. The representative for New York Life stated that they moved to S/4HANA to consolidated many different ledgers. However, one could have consolidated the ledgers to a single ledger. However, that could have been done with ECC.
- Hillary’s Blinds: The representative for Hillary’s Blinds has told all manner of incorrect statements, not only related to S/4HANA but to quite a few other applications, including pretending that moving CRM to HANA made a great improvement in CRM.
SAP has a number of customers where the members of the customers have the incentive or receive the incentive to lie about the status of S/4HANA. This is a problem that extends to all SAP products.
A conference monkey is a high ranking individual from a customer that is willing to lie about the functionality, the speed of the implementation, etc. A conference monkey may receive the benefit from SAP of being placed at a new position and a better position by SAP when a position opens up. A conference monkey lies on command, with the expectation of receiving something in return. They are critical in providing misinformation to the market, and therefore reducing the quality of information in the market. Just about all the conference monkeys are CIOs or out of the IT department. This gets into the topic of to whom does the IT department owe its allegiance which is covered in the following article.
- Sales people lie all the time to get deals.
- Consulting companies lie all the time to get consulting contracts.
- Senior members of companies lie on everything from the budgets to the successfulness of their implementations. In this case, they are simply lying for career reasons. This means that much of the information at SAP conferences is unreliable.
Financial Bias Disclosure
This article and no other article on the Brightwork website is paid for by a software vendor, including Oracle and SAP. Brightwork does offer competitive intelligence work to vendors as part of its business, but no published research or articles are written with any financial consideration. As part of Brightwork’s commitment to publishing independent, unbiased research, the company’s business model is driven by consulting services; no paid media placements are accepted.
Enterprise Software Risk 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.
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
Who is the Most Accurate Source on SAP?
Want to find out? See... A Study into The Accuracy of SAP