The One-Page Decision: Clarity Without Another Meeting
Decisions move work forward. Discussions, on their own, rarely do.
Most workplaces spend enormous amounts of time talking about choices but little time capturing them. As such, meetings end with "let's circle back", threads multiply and everyone remembers a slightly different version of what was agreed.
In reality, a decision without documentation is just another conversation.
The one-page decision changes that. It distils context, options, and next steps into a single, visible summary — making thinking transparent and ownership clear.
Why One-Page Decision works
The answer is simple - it forces focus and eliminates the comfort of endless context.
It demands that you separate what's essential from what's interesting. If you can't explain your decision briefly, you probably don't understand it clearly.
It also can accelerate collaboration. When everyone can read the same page in five minutes, there's less room for misinterpretation and more room for execution.
I've seen this approach reduce meetings and increase accountability. People no longer wonder "Where did we land last time?" because the answer lives in a single page.
The anatomy of a one-page decision document
The page makes decision logic transparent. Stakeholders see both the thinking and the ownership, which builds alignment without another meeting.
One-Page Decision — Template
Use this framework to capture context, options and ownership on a single page.
Section 1 – Context
Write 2–3 sentences summarizing what’s changed or why action is needed.
Section 2 – Options Considered
- Option A — brief description and reason for rejection.
- Option B — brief description and reason for rejection.
- Option C — brief description and chosen direction.
Section 3 – Decision
Decision: __________________________________________
Section 4 – Rationale
Briefly describe the reasoning, metrics, or insights that shaped the final decision.
Section 5 – Next Steps / Owner
| Action | Owner | By |
|---|---|---|
| — | — | — |
| — | — | — |
One-Page Decision — Example
Customer support ticket routing redesign
Section 1 – Context
Customer satisfaction dropped 8 points last quarter. Root cause analysis shows longer first-response times and mis-routed tickets due to product-line routing.
Section 2 – Options Considered
- Hire more agents — fastest to implement, highest cost.
- Redesign ticket triage — moderate effort, sustainable improvement.
- Expand self-service — slower ramp-up, long-term benefit.
Section 3 – Decision
Redesign ticket triage to route issues by complexity instead of product line.
Section 4 – Rationale
Expected 10% faster first-response rate. Uses existing team capacity and workflow. No additional cost.
Section 5 – Next Steps / Owner
| Action | Owner | By |
|---|---|---|
| Draft and test new triage flow | Ops Lead | 10 Apr |
| Training plan and rollout | Support Mgr | 20 Apr |
Common
Mistakes
Over-explaining
Turning the one-pager into a report defeats the purpose.
Skipping rationale
When you leave out the “why,” confusion fills the gap.
Forgetting ownership
A decision without a name behind it is only an opinion.
Hiding behind consensus
Writing “we agreed” without naming a responsible person keeps accountability vague.
Reflection
How often do your team’s decisions live only in memory or chat history?
What project in the last month would have benefited from a single written page?
What would change if every decision had a clear owner and next step within 24 hours?