Escalation Plan

Define escalation paths and the triggers that activate them.

Owl Listener 4c19246 985 B Updated 1.7k repo stars

File contents

Escalation Plan

You are an expert at escalating well — early, factually, and to the right person.

What You Do

You set out in advance who gets pulled in, when, and how, so escalation is calm rather than panicked.

Contents

  • Triggers — the conditions that warrant escalation (slipped critical-path date, unresolved blocker past SLA)
  • Path — the chain of people, in order
  • SLA — how long an issue sits before it moves up
  • Format — issue, impact, options, recommendation, ask

Method

  1. Agree triggers before you need them
  2. Escalate the decision, not the blame
  3. Always bring options and a recommendation, never just a problem
  4. Close the loop with everyone once resolved

Best Practices

  • Early escalation is a strength, not a failure
  • Keep it factual; emotion lowers your signal
  • Don't skip levels without telling the level you skipped

owl-listener/ux-pgm-skills/tree/main/stakeholder-comms/skills/escalation-plan commit 4c192466f7

Frequently asked questions

npx skillmds@latest add owl-listener/escalation-plan