Skip to main content

Customers Typology: The Paralized Analyzer



The Paralyzed Customer is not like the Customer who Knows Everything. He is very different from The Captive. The Paralyzed Customer is engaged in Analysis, so the process is: Analyze-Paralyze.


The Paralyzed Customer reacts to the Consultant's papers and recommendations, with no biases. The main problem is the endless loop of analysis in order to ensure no error included in the Consultant's product. No error is 100% error free product (not even the slightest error).

For example, if the product is a Request For Proposals (RFP), the Paralyzed Customer will initiate an endless evaluation process, even if the Consultant built the RFP together with the best customer's employees.

In a large number of long meetings, he will investigate the RFP. The following questions are only examples:

Do the requirements conform to the Business Strategy? 

Are the requirements in accord with the IT Strategy, Policy etc.? 

What are the expected costs for the implementation in one year? 

What are the expected costs for the implementation in 5 years, ten years, twenty years? 

You can be sure that he will ask any question, you never think of and ask for detailed answers.

After completing this tedious process he will give the corrected RFP  to the enterprise's lawyers and administrator. They should confirm the RFP or ask for additional corrections. 

The RFP is submitted  2 or 3 years after it was written. Sometimes it is too late because of major changes and sometimes the RFP is less adequate than it was when it was released by the Consultant. 

Considerations
The description in the RFP example, depict the problem of the Paralyzed Analyzer: If a Short Term or immediate action is required it will not be taken. In extreme Paralyzed Analyzer cases, no action will be taken at all after a long analysis process.  

I will demonstrate the problem by using a technology illustration located in the beginning of this post.

At the time of defining the selection criteria the Leading Products developed Capability A. This Capability has significant Business Value for the customer. Other products lack this capability. Probably the difference is because vendors developing Leading products invest more than others in R&D.

Vendors learn from their competitors, so after a year, they also developed Capability A. Meanwhile, the Leading Vendors developed another significant capability: Capability B. 

The damage caused by Paralyzed-Analysis is multi fold: 

1. For two years he did not select and implement a product, so he did not utilize Capability A and for one year he did not utilize Capability B (in case of selecting Leading Product) or he did not  utilize Capability A for one year (if he would select non-leading product, which may be cheaper to purchase).

2. After two years he will not be able to distinguish between Leading products and other products, because his criteria will focus on Capability A and Ignore Capability B. After two years Capability A will be included in all candidate products. The result will be selection process assigning higher than planned weight to Cost and lower weight than planned to Quality.  

3. The long analysis is costly.

Conclusions
The Consultant will face a problem if a quick decision and implementation is required.

His challenges are identifying states requiring quick decisions and actions and leading the Paralyzed Customer towards a shorter process than he used to.

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...