Skip to main content

Clients Typology: The Stealth

Picture Source: Wikipedia

The aeroplane in the picture above is Lockheed Martin's F-35 Lightening II. Its nickname is The Stealth. Stealth Technology reduces reflection/emission of radar infrared visible light. The reduction of infrared visible light make the Stealth Technology air crafts more difficult for conventional radar to detect.   

Responsibility is an abstract concept. Imagine that responsibility is not abstract but something analog to aircraft detection. The Stealth Customer escapes from it like a Stealth Technology aircraft would escape from detection by radar. 

What is wrong with taking Responsibility?
I studied Psychology about 30 years ago. In an experiment I studied about, monkeys had to perform tasks. The experiment was performed by Joseph V.Brady in 1958.

After few months monkeys who were "managers" i.e. were responsible for tasks other monkeys preformed, suffered from ulcer. "non-managers" monkeys where as healthy as they were prior to performing the tasks.

The results were explained by worries due to responsibility.
The "managers" worried the "simple workers" had to perform exactly what the "managers" asked them to do: No worries and no ulcer. 

The results could be extrapolated to human beings. 
The Stealth Customer does not want to worry. 
Why should he take responsibility and destroy his health?
He takes no responsibility.

When the Stealth is a Worker
If he is not a manager, he can perform his duties without taking responsibility.
Other co-workers may be fascinated by his stories about restaurants, vacations in exotic countries, his friends and hobbies. He is cooperating with his co-workers. No problem could be identifed.

The Peter Principle
The Peter Principle is a concept in Management Theory. The selection of  candidate is based on his current performance in another role rather than on relevant abilities to the new role.  

The result of this selection method is that they will tend to be promoted until they reach their "position of incompetence".

That could happen to the Stealth as well. He will be promoted to a management position. Sometimes he will be promoted even to an upper management position.

As you already know, the Stealth Customer will not take responsibility. A manager who is not taking the responsibility, he was expected to take, could harm the organization.  

In order to avoid of responsibility, he may use behavioral patterns of other customers type, such as The Bad, The Captive, The Paralysed Analyzer and The Covering.

Another way of avoiding Responsibility
The Stealth may use the patterns cited above. However, he could also avoid of responsibility by transferring it to another manager. It could be a very responsible manager higher in the hierarchy or a manager in the same level of the Stealth. It could even be a manager, the Stealth is managing. 
The Stealth could not care less about the other manager identity, as long as he is not taking the Responsibility.

How should a Consultant deal with the Stealth Customer?

1. He could find someone else in the organization who will take responsibility instead of the Stealth.
The natural candidates are cited in the previous section. 

2. Work with another manager in the organization instead of the Stealth. 
This method is not always possible.

3. Train the Stealth to take responsibility.
This is the most unlikely method, because in most cases it is difficult and no resources are preallocated for training.






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