Skip to main content

Customers Typology: The Self -deprecating Customer

image source: Wikipedia
The Self -deprecating Customer is exactly the opposite type of The Customer who Knows Everything. He automatically accepts the Consultant advice, without any questions or hesitations.

 Probably, you will not believe that the first example of a Self -deprecating Customer I think of, is the CIA. It is about a project named Triangle. Triangle was an Information Technology project of Legacy Modernization and systems expansion after September 11 attacks. 

 After  completing the Development phase, the CIA begun the Implementation phase. However, someone who was a Senior Manager, thought that it will be a good idea to rethink if the project fulfills its goals. A committee of 100 leading academic and IT industry experts, investigated the project.

 The main recommendation in  the committee's detailed report was: stop implementation and fix the errors in the systems. Afterwards the systems could be implemented again.

 It should be noted, that stopping implementation at such advanced stage of the Development Cycle, is very expansive. However, after reading the report in the Web, I understand why the experts recommended to stop and rethink.

 The CIA made almost every mistake I could think of. As far as this post is concerned, the self -deprecating mistake was decisions taken by consultancy vendors instead of CIA Managers.

Is not he the ideal customer a Consultant could think of?
It looks like ideal circumstances for consultancy: The consultant's long term employment is ensured, his vision and recommendations are accepted, as well as the deployment methods he recommended.
However, the scenario could be not as good as the consultant could imagine. The following are main drawbacks:

 1. The customer takes no Responsibility
In case of failure, regardless if it is due to the consultant's mistakes or unrelated factors, the consultant will be responsible for it.
The customer would argue that he done exactly what the consultant recommended.   

  2. Following blindly is not limited to following the consultant
 The customer may easily follow someone else's advices without any doubt. It could be a vendor or another consultant. The result could be lack of consistency and no systematic approach. 
For example, another consultant contradicting recommendations in related topics, could be executed along with the consultant's recommendations.

 3. The Customer is not learning
In the long run this could be the most severe problem. For example, one of the goals of SOA consultancy is to create a Reuse Culture.
Most of SOA initiatives without Reuse Culture fail.  The Self-deprecating Customer could easily preserve the old non-Reuse Culture. 

 Usually I prefer to give to my customers fishing rods and not fish.
The Self-deprecating Customer usually prefers fish.   
Labels:

Comments

Post a Comment

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  ...
16 comments
Read more

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 ...
11 comments
Read more

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...
8 comments
Read more