Skip to main content

Customers Typology: The Cusomer who Knows Everything

I worked as an Information Technology Consultant, for many Customers. Customers are different in their Self-Perception, in their view of the Consultant and the Consultancy Process. They also differ in the Enterprise size (Large, Very Large, SMB) and their Vertical Industry (e.g. Telco, Banking, Insurance, Utilities, Public Sector). 

Customers Typology could effect the interaction between them and the Consultant, as well as the probability of successful consultancy.
This post is about a particular customer type: The Customer who Knows Everything.

The Customer Who Knows Everything
This Customer type is sure that he knows more than anyone else. He is also sure that his understanding is better than any body's understanding. 

His point of view is manifested in the Decision-making process: 

1. There is no correlation between the Consultant's recommendations and the decision.

2. There is no correlation between the consultancy quality and the decision taken.

3. The decisions may not be related to information collected and analyzed during the Consultancy process. 

The consultant may be a knowledgeable and experienced expert in a topic. For the Customer it could be the first time he and his enterprise are exposed to this topic.  

The consultant's work could be excellent: assembling data from variety of sources e.g. Analysts' Research Notes, Case Studies, similar enterprises 's strategies, approaches' solutions and conclusions etc.

The conclusions based on this excellent work could be that strategy A or Software/Hardware product A's implementations usually fail, while strategy B or product B's implementations usually succeed.

The Consultant's recommendation could be: select Strategy B implemented by Product B.   

The Customer who Knows Everything, will chose Strategy A implemented by Product A. He could argue: "I know that everybody in the world selecting Strategy A implemented by Product A failed. I know better and understand more than them, so I will be the first to succeed". Needless to say, that he fails like all the others (sometimes even more sever failures than others).

According to Aberdeen Group's SOA survey, Best in Class (BIC) Enterprises (those whose implementations succeed and provide real Value) used more Consultancy Services than others. Laggards (those who fail to provide Business Value), refrain from using Consultancy Services or purchased less Consultancy Services than others. 

I would guess that, the Laggards group includes, at least, few Customers Who Know everything.

How to Consult a Customer who Knows Everything?
The question in this paragraph's heading contains the answer: If someone knows everything it is impossible or at least very difficult to consult.

Effective consulting requires conceptual change. Information, data and brilliant analysis would not change the customer's approach. 
A Psychologist may change the concept, but we are only IT Consultants not Psychologists. 

He will learn only after painful failures. To help him, the consultant should repeat and emphasize his conclusions contradicting the customer's decision, so the customer could blame only himself in case of failure.

However, sometimes even repetitions of the recommendations contradicting the customer's approach, could be in vain: The customer will know who to blame.
The Consultant opposing the wrong conclusions and actions taken by the customer, is to be blamed.  

Comments

Popular posts from this blog

The mainframe: still alive and kicking

Recently, I was interviewed by  Pcon   (unfortunately the link points to an Hebrew only site) as part of debriefing on Legacy Systems.  Pcon is an Israeli company investigating IT topics by quoting professional articles and interviewing experts. They publish the results of the investigations including practical recommendations. This post is mainly about topics raised by me during the interview, but not included in the debriefing, which will be published.    What are Legacy Systems? The term Legacy Systems refers to old application systems and/or veteran technologies still in use.  Usually, the term Legacy Systems is associated with: 1. Mainframe Hardware e.g. IBM System z and its Operating Systems or Proprietary Servers and Operating Systems such as HP Alpha and OpenVMS Operating System, IBM AS/400 and OS/400   Operating System. 2. Development and Production Environments, e.g. COBOL , Natural and DBMS systems such as Adabas  ...

Will Business and IT Aligned?

For decades we are talking about closing the gap between business and IT , but the gap is still as wide as it was. In the beginning of the ERP era, we focused on aligning Business Processes and Core Systems, but in most enterprises we failed. SOA was the next alignment promise: defining the SOA Services in Business boundaries instead of Technical boundaries, should narrow the gap. However, despite of SOA Business Value ( Agility and Reuse )  in most enterprises,  the large Business-IT Gap remained as large as it was.  The IT Community aimed at the next alignment attempt: SOA is technical and BPM is its Business related complement.  Will the current BPM based alignment attempt succeed? I do not know, but Nick Heath's article  titled: Stop doing what the vendors tell you, CIOs told , published in  Tech Republic , suggests that the root of the problem is not Technological .   Stop Doing What the vendors Tell You Nick Heath's article is based ...

Vendors Survival: Will Software AG Survive until 2019?

This post is another post in the Vendors Survival series following posts on Microsoft , Google , HP , Sun and EMC . On July 14 th Software AG and IDS Scheer announced that Software AG is going to take over IDS Scheer . The intended acquisition is an opportunity to add another post in my Vendors Survival posts series. A brief history of Software AG Mainframe products Software AG is larger than any German software company except SAP . It was established in the Mainframe age (in 1969). I worked with many customers, who used and some of them are still using, its two flagship products Adabas and Natural . Although these products support many platforms, their main platform is IBM Mainframe. Adabas is a database and Natural is a development environment. Like other pairs of Database and Development Environment in the mainframe environment (e.g. Ideal and Datacom , Mantis and Supra) build by the same vendor, they are tied together. As a result, although it is possible t...