Why most decision docs fail
Most decision docs fall into one of two traps:
1. Slide spaghetti:
Too many slides, too many angles, too much “context” , and the decision disappears.
2. A manifesto: A long narrative that tries to convince everyone, but never clearly states what must be decided and by when.
A
decision-ready brief does the opposite. It removes noise and forces the trade-offs into daylight.
The decision-ready brief
Here is the structure I use. It is deliberately simple.
1) The decision statement (one sentence)
Make it binary or a clear A vs B.
Example: “Do we consolidate endpoint security onto one platform by the end of Q2, or keep the current best-of-breed stack for another 12 months?”
2) The context (what is true, what changed)
Only the facts that matter. No history lesson.
- What is happening now
- What has changed
- Why the decision exists now (the trigger)
3) The constraints (non-negotiables)
These prevent fantasy options.
- Budget ceiling
- Regulatory requirements
- Delivery deadlines
- Internal resourcing limits
- Customer commitments
4) The options (real options, not strawmen)
Usually 2 to 3 options is enough.
For each option: what it is, what it requires, and what it gives you.
5) The trade-offs (this is the decision)
This is the part most teams avoid, then wonder why they cannot decide.
Spell it out clearly.
- Faster risk reduction vs more platform lock-in
- Maximum capability vs operational simplicity
- Central control vs team autonomy
- Short-term cost vs long-term flexibility
6) The risks (and who owns them)
Not vague “risks exist” language.
- Risk
- Likelihood (low, medium, high)
- Impact (low, medium, high)
- Mitigation
- Owner
7) The recommendation (and why)
The recommendation is not “the best option”.
It is “the best option given the trade-offs we are choosing”.
8) The decision owners and decision date
One name. One date.
Also define who is accountable, consulted, and informed.
9) The first two weeks of execution
This is what makes the decision stick.
- First actions
- Who does what
- What gets communicated
- What gets measured
A quick example of how this unlocks speed
A security leadership team I worked with had a decision stuck for weeks: consolidate tools, or keep best-of-breed.The debate was not actually about tools.
It was about this trade-off: “Are we optimising for consistent coverage and simpler operations, or maximum capability even if it increases complexity?”
Once that trade-off was written down in the brief, two things happened fast:
1. The arguments stopped repeating.
2. The decision owner could finally make the call with confidence.
That is what a good brief does. It turns noise into a clear choice.
How this fits The Exec Memo
This is the core deliverable behind both offers:
Decision Sprint
For decisions that are stuck but solvable quickly.
- Short working session
- Decision-ready brief produced within 48 hours
- Follow-up call to land the decision and actions
Alignment Sprint
For decisions that need buy-in.
- Stakeholder input gathered
- Friction and incentives made explicit
- Facilitated decision meeting
- Commitments captured in the brief
Either way, the aim is the same: clarity, trade-offs, ownership, and a decision that sticks.
If you want the template
If you have a decision that is looping,
send me:
- The decision in one sentence
- Who is involved
- What happens if it slips another month
I will reply within 48 hours with:
- The missing trade-off I suspect is driving the loop
- Whether a Sprint would help
- And a simple template you can use internally
Justin
Founder, The Exec
Memo
