It’s almost lunch time and the phones are lighting up in the IT department. The email system is down, and everyone from the President to the Receptionist is calling to say there’s a problem. Of course, thanks to your monitoring system, IT had already noticed that something was wrong, but the calls are providing immediate feedback regarding how widespread the problem is. Because email is a mission-critical system at your company, if the Tier 1 engineer cannot quickly fix the problem, your Information Technology escalation process will kick in.
An Information Technology escalation process is a formal process for addressing IT issues and problems when they arise. It is built on IT monitoring, which—when properly configured—will provide you with alarms and warnings whenever something is amiss.
All IT departments should have a written escalation process in place, with the entire IT staff trained on its use. Your escalation plan should remove all guess work, making actual emergencies a matter of simply implementing decisions that have been made in advance. Your escalation process should assign priority levels to different types of issues (thus eliminating judgement calls), delegate responsibilities to specific personnel, and define how much time personnel at different support levels will spend attempting to fix a given issue before the problem is “escalated” to the person or people at the next support tier. Just as important, one of the purposes of the escalation process is to have a plan in place for informing and alerting those who are impacted by the problem itself.
Within IT, who needs to be notified about a problem, called in to help fix the problem, or communicated with about the problem? Outside of IT, what functional groups need to be informed that there is a problem in the system that affects them and impacts the business? And who is responsible for making sure that all of this communication takes place?
For example, here is a sample Information Technology escalation process and timeline that an organization might follow for critical issues:
IT escalation drills are tests to see if your written process and plan actually work. When we run IT escalation drills we like to create a mock situation, make it as realistic as possible, and then take the drill all the way through escalation to the highest tier contacts in the plan. Why? Because it is important that the drill not be confined to IT staff. To be most effective it must include everyone in the escalation chain company-wide.
For clients of our Remote Monitoring and Management Service the process is a little different than what’s outlined above, because our escalation process involves people both within the Praecipio chain of command and at the client site. In most cases we will start by escalating issues internally before we escalate to the client.
Your overall goal is to avoid prolonged outages, and your Information Technology escalation process is there to help you reach that goal. However, even if your IT escalation looks great on paper, until you test it you won’t know if it actually works.
Through IT escalation drills you can:
If you want to be sure that your team is prepared to quickly and appropriately address outages and problems, running IT escalation drills is vital. If you need help getting monitoring in place, and/or creating and testing an IT escalation plan, give us a call. This is one of our areas of expertise.