IT teams know that strong escalation policies are like the net under an acrobat. They ensure that if an alert is not heard or cannot be handled by the recipient, the alert won’t fall out of view and suffer a quick demise.

However, what are the best ways to incorporate escalation policies while not encouraging teams to shirk responsibility? Our latest whitepaper Mastering Escalation Management looks into this conundrum by highlighting:

• Use of runbooks
• Avoiding the use of email
• Use of messaging applications integrated with persistent alerting capabilities