Decision Rights Need a Receipt
Write a concise decision receipt that names owner, rationale, and execution handoff.
Decision Rights Need a Receipt The decision receipt is the bridge from authority to execution. It names the question, decision, decider, rationale, input considered, perform owner, informed audience, and escalation trigger. 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.
Sign up free — one personalized lesson every day, matched to your role and goals.
Already have an account? Sign in