Skip to main content

Escalate, Escalate, Escalate!

What is escalation at organizations? Is it a way to solve problems? Is it a way to report things? Is it a way to put more pressure? Is it a CYA technique? What is it? How do you use it at your organization? How other colleagues of yours use escalation? Really, think about it and observe.

At IT service companies, leadership measures the performance of IT Help Desk by number of escalated work items over a period of time. The less escalation the better. The reasons are simple:

  1. It is cheaper for companies if an IT Help Desk Specialist resolves an issue than an experienced technical specialist at one or two level higher. This is simple math, one gets $X and the other get $X*2
  2. And when client gets result fast, he/she will be happier. So, less escalation equals happier client in IT Services. Client raise an issue, IT Help Desk Specialist resolve it, BOOM, Next!

At organizations, It is amazing (sadly) to see how much lower level managers escalate problems, that they and their fellows can resolve without escalation  to more senior managers, these days. How much money is wasted?! Studies show that escalating a problem that can be resolved at lower level of organization will increase the cost and the duration of  the resolution time. So, why do you do this? either the organization has a lot of money to waste, or the senior manager has nothing do and has lots of time to waste? or this is again a CYA strategy. And yes, 90% is CYA by escalation.

The relationship issues and conflicts that happen because of escalation is even more expensive than the time senior management spends on investigating and resolving a problem that could be resolved by a lower level manager at the first place.

Here are 6 simple and common sense use of escalation:
  1. Escalate only, if you are not able to solve the problem on your own or at your level.
  2. Do not create artificial problems to exaggerate the main problem to justify your escalation.
  3. Do not blame when escalating, Simply concentrate on resolving the problem at hand and preventing it from happening again.
  4. As a senior manager, advise your directs to escalate less, unless your help is really needed.
  5. As senior manager, reward those who solve problems before informing you about the problem!
  6. Do not cover escalation by "informing" excuse. Sometimes, people escalate indirectly and they call it informing. But, in reality they do not have the courage to handle problems alone, therefore they escalate indirectly!


Popular posts from this blog

DAD Inception Phase Workshop Agenda

Disciplined Agile Delivery (DAD) realised the reality of the projects and introduced back phases to Agile community. Whoever works in a project based company, especially a project based company where projects are usually less than one year in length and each are for different clients, understands the reality of Agile in such environment. When you start working on a new project for a new client, it is essential to go through a phase that you get to know each other better, to understand the business purpose of the project, to understand the scope of the project, to know what are the high level architecture and what technologies are going to be used and who is the initial team, and if funding is available and also when things must be delivered and to whom.
In answering these questions you may need to meet with different people, run couple of workshops and brainstorming sessions. And this is called Inception Phase. As DAD is more like a goal oriented decision framework and not a prescrip…

Stay Fitter

1st edition of Fit for Purpose: How Modern Businesses Find, Satisfy, and Keep Customers from David J Anderson and Alexei Zheglov was published in Nov 2017. They wrote the first edition in 7 weeks during summer 2017. I had a chance to provide feedback to them as they were writing and editing their chapters.

The book basically talks about what a product and service is made up of, how customers measure the product or service and what metrics company managers must apply at different levels to be always fit for customer purpose (the Why's of the customer). If I want to summarise the book in one statement, it would be like: Align your business to how your customers measure your product and service.

When I was reading the chapters, four guys came to my mind: Peter Drucker, Jack Trout, Eliyahu M. Goldratt and Clayton Christenson.

The book reminded me of Peter Drucker; because he once made a profound observation that has been forgotten by many, his observation goes like this: "Because…