Showing posts with label Escalation Management. Show all posts
Showing posts with label Escalation Management. Show all posts

Thursday, September 3, 2009

Criteria for Triggering an IT Escalation – some examples

"Escalation" is often mentioned when dealing with Incident and Problem Management processes. The ITIL Incident Management process talks about Hierarchical and Functional escalations. Hierarchical escalations are where higher management attention and additional resources are needed. Functional escalations are done when incidents are assigned to next level support personnel with greater expertise to work on them. Criteria for triggering such escalations are very much organisational dependent. The majority of escalations will be initiated from Incident Management and there are a number of triggers, both time and event based.

Incident Management handles many incidents each month and only a very small percentage will require escalation. It is important that Incident Management adhere diligently to the triggers. Failure to do so may result in Customer anxiety and dissatisfaction. On the other hand, "false alarms" or "crying wolf" may lead to increased costs due to the additional attention and resources required to manage the Customer.

Hence the criteria should be well-defined, documented and made known to the Service Desk, and other IT Support functions. These criteria could be embedded within support tools to help the support staff. The tool could also be used to control the process flow within agreed timescales for those escalations that are triggered due to prolonged service outages.

Examples of reasons to initiate an escalation could include the following:

  • A prolonged service outage that exceeds or threaten to exceed the Service Level Requirements or timeframe, leading to high customer anxiety or complaints.
  • Frequently recurring or multiple related High Priority incidents where Priority is related to business impact and urgency. In situations like this, the Customer's confidence in the Service Provider would have been greatly impacted, not to mention the impact to the Customer's business. Hence, an escalation is called for to bring about management attention and also expertise to find the root cause and prevent future incidents.
  • Management of a major Incident (part of Major Incident Procedure). Typically, a Major incident procedure would have included activities related to escalation or crisis management
  • Management of a major Problem especially where impact to business is high and the assigned problem management team is taking too long to isolate the cause of the incidents. This could in turn cause other issues, such as high customer anxiety, recurring incidents and lost of Customer’s confidence in the Service Provider.
  • Data loss or risk of potential data loss. Any loss of data has a significant impact on the Customer. For example, a disk storage system has malfunctioned, leading to a service outage. The customer's last backup was done yesterday and there is potential data loss if the right solution is not found. In situations like this, an escalation may be called for to ensure the right steps is done to repair the disk storage system and recover the data or ensure no data is lost.
  • Risk of actual or potential damage to customer or provider's reputation
  • Safety issue identified or reported by Customer
  • Risk of breach or non-compliance of regulations e.g. industrial health or safety
  • Customer's crisis situation or customer's anxiety is high and customer requests for escalation
  • Common sense
The last one is a good one, as not all situations can be well foreseen! So, service staff needs to exercise judgement and common sense when it comes to triggering an escalation, even with a documented checklist or tool. When in doubt, check with a more experienced colleague or better still, check with the immediate supervisor.

Tuesday, August 4, 2009

Importance of Having an Escalation Management process

"Escalation" is often mentioned when dealing with Incident and Problem Management processes. The ITIL Incident Management process talks about Hierarchical and Functional escalations but did not call out "Escalation Management" as a separate and important ITIL process within Service Operation.

In my previous organisation, escalation management is well-defined and documented process. It is even handled or managed by a separate dedicated team of people. This "escalation center" function, called the Customer Escalation Center (CEC), works closely with the Service Desk function called the Response Center. It also supports the field or onsite support engineers who taking on maintenance and support roles.

When I started out as a rookie service engineer in the Response Center, the knowledge that there is a team of experts which I can call upon to help out in major incidents or problems is often reassuring. The fact that the Response Center or an onsite technical or application support engineer has escalated a major incident or problem to the CEC and there is a team of experts attending to the escalated incident or problem is also reassuring to the Customer.

Escalation Management is to bring order, structure, focused management attention and additional resources to those customer situations which could otherwise result in a high level of customer dissatisfaction and/or damage to the service provider’s reputation. These are situations which could lead to significant loss of business to the Customer or IT Service Provider or where significant costs may be incurred by IT Service Provider to resolve the customer situation.

The criteria to trigger an escalation depends on the organisation or service provider. But it should be well defined.

The process could consist of the following activities:

· Initiate an Escalation, based on meeting specific escalation criteria

· Assign an Escalation manager for the escalation

· Log the Escalation and link the Escalation record to related Incident or Problem records

· Escalation manager assigns or appoints the escalation team. The escalation team should include the Incident owner, Problem owner, and other subject matter experts, as required

· Identify appropriate Service Provider and Customer management contacts

· Conduct a detailed situation appraisal and review, led by the Escalation manager

· An escalation management action plan, including additional resources needed, is developed in conjunction with the Customer. The escalation management plan is to be executed in parallel with the detailed technical action plan (as per Incident/Problem Management)

· The escalation management action plan is reviewed and adjusted as required

· A Hierarchical Escalation (as per Incident Management process) is initiated, if appropriate. Senior management and executives are alerted.

· Escalation team works to resolve the problem. At each stage, records are updated and management contacts and team are informed of the progress and escalation plan reviewed and adjusted as required.

· Once resolved to the Customer’s satisfaction, the situation is monitored for an agreed period

· The escalation team remains on standby and available in case the problem recurs during the monitoring period

· Once the monitoring period is successfully completed, the escalation is closed by the Escalation manager, after seeking agreement with the Customer

· Once the escalation is closed, a post escalation review is conducted and input provided to the Problem Management process. This can be done in conjunction with the Major Problem Review which is part of Problem Management.

As can be seen above, Escalation Management is closely related to and supports the Incident Management, Request Management and Problem Management processes. It is an important process that should be treated with equal or greater focus as compared to these other well-defined ITIL processes.