Start here · Guide
Writing for user interfaces
A practical standard for reducing cognitive load and writing in direct language for a real audience and task.
Visit the original sourceDirector capability · Management topic
Make consequential recommendations inspectable before the meeting.
Editorially reviewed
Decision writing turns a recommendation into an object people can inspect, challenge, and improve. It slows the author down enough to separate evidence from assertion and gives contributors a common version of the problem before status or confidence dominates the room.
The purpose is not a polished document. It is a better decision with a durable record of what was known, chosen, and left uncertain.
Open with the decision required, your recommendation, and why it matters now. Readers should not have to infer the ask after several pages of background.
Then provide only the context needed to evaluate the choice. Write for a specific audience and task. Internal jargon, history, and detail earn their place only when they change the decision.
Label what was observed, what you infer, and what remains uncertain. Use ranges when the evidence supports ranges. State source, time window, and material limitations for decisive numbers.
Avoid decorative data. A chart or estimate should answer a question the reader needs to decide. If it cannot survive a simple definition check, remove or repair it before the meeting.
Include the do-nothing or continue-current-course option. Describe credible alternatives in terms their supporters would recognize, then compare outcomes, cost, risk, reversibility, dependencies, and timing.
A recommendation is stronger when readers can see why another plausible choice was rejected. A list containing one sensible option and two straw alternatives is advocacy without analysis.
State who gains, who bears cost, which capability is constrained, and what the organization will not do. Include material dissent and unresolved questions.
Do not resolve disagreement by editing it out. Name whether the disagreement concerns facts, values, risk tolerance, timing, or authority. That helps the decider focus the conversation where judgment is actually needed.
Record the decider, decision date, immediate actions, owners, guardrails, and review trigger. After the meeting, update the record with the actual choice and rationale rather than leaving the recommendation as a false history.
A decision log is useful only if people can find the current record and know when a changed condition warrants reopening it.
Write a brief for one live cross-team decision.
Use fictionalized or de-identified material for a learning artifact when the decision contains confidential people, customer, security, or commercial information.
The GOV.UK writing guidance is a practical standard for direct language, reader needs, and reduced cognitive load. Good Strategy/Bad Strategy shows how diagnosis and coherent action create a narrative that can be tested.
Resource completion changes reading status only. The evidence is a brief that improves the quality and traceability of a real decision.
You may be ready to record Lead when you can:
These prompts support an explicit proficiency judgment; they do not create it.
Strategy diagnosis & coherent action gives the brief a coherent argument. Decision rights & governance clarifies who decides. Continue to Influence across boundaries to build commitment through honest stakeholder work, and to Investment cases & benefit ownership when the choice requires capital.
Curated sources
Resources support observation and practice. Finishing one does not automatically establish capability proficiency.
Start here · Guide
A practical standard for reducing cognitive load and writing in direct language for a real audience and task.
Visit the original sourceGo deeper · Book
Demonstrates how clear diagnosis, guiding policy, and coherent action create a strategic narrative people can inspect.
Visit the original source