Skip to capability
Tree of ManagementE
Your tree
Communication

Communication

Writing & strategic narrative

Turn complexity into a recommendation people can examine and remember.

Essential question

What decision should this writing enable, for whom, and with which evidence?

Build the capability

Practices to build

  1. 01

    Lead with the recommendation

    State the proposed choice before the chronology.

  2. 02

    Decision memos

    Separate context, evidence, options, trade-offs, and ask.

  3. 03

    Uncertainty language

    Name what is known, inferred, assumed, and unknown.

  4. 04

    Narrative coherence

    Connect diagnosis, choice, action, and consequence.

Put it to work

Fieldwork

Write a two-page decision memo with context, recommendation, alternatives, evidence, risks, and a direct ask.

Go deeper

Field guide

Edited by Ethan Hussong · Last 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.

Name the decision at the top

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.

Separate facts, interpretation, and assumptions

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.

Present real alternatives

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.

Make trade-offs and dissent visible

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.

End with ownership and review

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.

Practice with a two-page brief

Write a brief for one live cross-team decision.

  1. Put the decision and recommendation in the first paragraph.
  2. State the relevant context, evidence, and uncertainty.
  3. Compare at least three options, including the current course.
  4. Name trade-offs, affected stakeholders, risks, and guardrails.
  5. Ask one informed critic to mark unsupported claims and missing alternatives.
  6. Revise for direct language and remove detail that does not change the choice.
  7. Record the final decision, owner, actions, and review trigger.

Use fictionalized or de-identified material for a learning artifact when the decision contains confidential people, customer, security, or commercial information.

Use resources selectively

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.

Finishing Core resources contributes to route completion, but does not establish proficiency. The evidence is a brief that improves the quality and traceability of a real decision; Supplemental resources remain optional.

Evidence of Practice

You may be ready to record Lead when you can:

These prompts support an explicit proficiency judgment; they do not create it.

Continue through the tree

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.