Extract the call
- Start with “We will…” or “We will not…”.
- If there are two independent calls, write two memos.
Shape · Core skill lab
Turn a fuzzy meeting outcome into a decision that an absent builder can execute and a sceptic can challenge.
Your work saves in this browser.
Field tools
Copy these into your interview, agent, review, or working document. They are specific to this repetition.
Keep this order; it matches how a builder consumes the decision.
# Decision One sentence. ## Why now Evidence and constraint. ## Judgment What we believe the evidence means. ## Tradeoff / non-goals What we choose against. ## Execution Owner — action — date. ## Dissent Strongest objection. ## Reopen when Observable reversal condition and review date.
Do not explain the memo before asking these questions.
1. What decision did we make? 2. What would you do next if you owned this? 3. What did we explicitly choose not to do? 4. Which claim would you challenge? 5. What event would make us revisit the call?
Calibrate judgment
A beta team must choose its first segment.
We will limit the next six weeks to UK agencies with 10–50 employees. This sacrifices breadth, but eight of 11 qualified interviews show the same handoff failure. Reopen on 8 August if fewer than three of five partners repeat the workflow twice.
Why it works: The call, evidence, sacrifice, timebox, and reversal condition are all legible.
We met to discuss the beta and had a productive conversation. There was broad alignment around focusing, although we should keep options open. Next steps are to circle back with the team.
Why it fails: No decision, owner, deadline, tradeoff, or trigger for revisiting the choice is present.
Review → revise → repeat
Check only standards your current artifact actually meets. Then record one consequential revision before exporting it.