Owner decision
What must leave a meeting with one owner, deadline, and decision right?
Every material commitment should leave with one accountable owner, a date, the authority to make the normal decisions, the condition that requires escalation, and a visible completion test. Shared participation does not require shared accountability.
Use this now: Use a meeting decision receipt with commitment, owner, deadline, decision limit, escalation condition, and completion evidence.
Owner worksheet
Meeting decision-continuity receipt
| Check | Write down |
|---|---|
| Precise outcome | Record the result the meeting decided to create, the option selected, and the unresolved item that remains outside this decision. |
| Continuity owner | Name the one person responsible for keeping the decision alive across handoffs, not merely the person performing the first task. |
| Decision right | State the normal tradeoffs, resources, and exceptions the owner may decide, plus the reserved condition that requires escalation. |
| Next state change | Write the first irreversible or externally visible action, its owner, and the artifact or system state that will prove it happened. |
| Deadline and closure | Set the consequential due time, acceptance evidence, reviewer, and escalation time when the receipt remains unsigned or overdue. |
Close the decision: Close the meeting only when outcome, continuity owner, decision right, state-changing action, deadline, and acceptance evidence are all written.
Worked example
Illustrative completed meeting decision receipt
Illustrative only: Illustrative operating example only; replace inputs with verified business evidence and do not present the example as a universal benchmark or achieved result.
| Step | Illustrative input | Replace with your evidence | Completed test or status |
|---|---|---|---|
| Decision | Delay the illustrative beta launch from June 10 to June 17 because the payment-reversal test is incomplete. | Approved meeting record and exact unresolved test. | The outcome is a decision, not a discussion summary. |
| Decider and action owner | COO is decider; product manager owns the revised launch plan; QA lead owns the reversal test. | Decision-right map and named action assignments. | Decider and executors are distinct. |
| Deadline and dependency | QA evidence due June 13 at 3:00 p.m.; product plan due June 14; launch depends on a passed reversal receipt. | Calendar/task readback and linked dependency. | Every action has a date and prerequisite. |
| Authority and escalation | Product manager may move tasks inside the revised week; any further launch-date change returns to the COO within four hours of a failed test. | Written authority envelope and alert path. | The owner knows what can move without a new meeting. |
| Acceptance evidence | Close only when the reversal receipt, revised release checklist, and customer notice owner are attached. | Exact artifacts and final decision readback. | Decision: June 17 remains conditional, not falsely reported as released. |
Decision produced: Carry one conditional launch decision with named decider, executors, deadline, authority, escalation, and evidence; do not treat attendance or minutes as completion.