Escalation Paths

Every playbook eventually encounters a situation it was not designed for. The escalation path is the mechanism by which the executor recognizes that they are in that situation and knows what to do about it. A playbook without a clear escalation path ends with the executor either making a decision they are not authorized to make or doing nothing while they search for guidance through informal channels — both of which are worse outcomes than a well-designed escalation.

1. Define escalation triggers explicitly The escalation trigger should be as specific as the playbook trigger. "Escalate when the situation exceeds your authority" is not an escalation trigger — it assumes the executor knows their own authority limits, which may not be the case. "Escalate when the requested credit exceeds $5,000, when the client explicitly threatens legal action, or when the situation involves a named executive relationship" is an escalation trigger.
2. Name the escalation contact and backup The escalation path must name a specific person, not a role. "Escalate to the Account Manager" leaves the new employee searching for who holds that role. "Escalate to Jamie Chen, Account Director — jamie.chen@[company].com — or to [backup name] if Jamie is unavailable" is an escalation path. Escalation contacts must be current — outdated escalation contacts are one of the most common causes of playbook failure in practice.
3. Document what information to bring to the escalation When a playbook executor escalates, they should know what information to gather before making contact. "Before escalating, have ready: the client name and account number, the specific request or situation, any written communication from the client, and the steps already taken." This makes the escalation call shorter, more productive, and less likely to result in a second escalation because the first escalation lacked necessary context.