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!


Post a Comment

Popular posts from this blog

Moving from Basic DAD Scrum Based LifeCycle to Continues Delivery (Kanban Based) Lifecycle

I was thinking what the title of this blog post could be, I had couple of options to select from and decided to use a title that uses Disciplined Agile (DA 2.0) Lifecycle. Other options for titles were: Moving From Scrum to KanbanFrom High Performing Scrum Teams to Hyper Performing Kanban  The bottom line is that at some point you may want to move away from Time boxes to a flow of work and service oriented teams and improve performance and throughput without massive and sudden organisational change.  As always, I only share my experience and this may not apply to all situations, context is important. 
Another reason that I selected “Moving from Basic DAD Scrum Based LifeCycle to Continues Delivery (Kanban Based) Lifecycle” as the title, was that for many it is a question mark how to navigate through DAD life cycles. and I think this blog post could be one of the ways to navigate. 
Context: A Delivery Team started with Type A Scrum with 2 weeks Sprints. After a while, they deploy their …

New Organisational Model For Project Based Companies

Elliot Goldratt suggested a Strategy Tree for project based companies. While that may work for some companies, it will not work for knowledge based workers or Software Development Companies, or Digital Agencies. On the other hand traditional resource planning and resource allocation is also not effective despite all the effort one put into it to make it less of a command and control model - Here I assume we know who are knowledge workers and how their productivity works, Peter Drucker has a fantastic article about Knowledge Workers that I highly recommend you to read, if you have not read it yet: http://www.forschungsnetzwerk.at/downloadpub/knowledge_workers_the_biggest_challenge.pdf
Also, it has been proven that stable teams work better together on long term projects in software development. However, almost majority of software development companies or digital agencies break teams and reassemble them based on new projects or clients. This creates unnecessary complication and waste w…