Escalate on Criteria, Not Frustration Escalation should activate on observable criteria: a required approver blocks, the decider lacks authority, a deadline will be missed, or risk exceeds a named threshold. Frustration is a signal to facilitate first. Use RAPID when roles are tangled across functions. Use DACI when a project needs a Driver, Approver, Contributors, and Informed loop. Use escalation only when a named trigger shows the normal path cannot decide. Before -> After: vague alignment becomes named authority, named input, and a visible escalation route. Common trap: adding more approvers feels safe but usually hides who owns the trade-off.
Read the full lesson
Sign up free: one personalized lesson every day, matched to your role and goals.
Already have an account? Sign in