In this guide
  1. Define the audience and the action
  2. Build around situation, change and next step
  3. Separate evidence from interpretation
  4. Choose detail that earns its place
  5. Adapt the same evidence to common work formats
  6. Use stories ethically
  7. Create a story bank and practise deliberately
01

Define the audience and the action

Before choosing a story, name the reader or listener and the action you need from them. A leadership update may require a decision. A team briefing may need alignment. An interview answer may need evidence of your judgement. If the action is vague, the story will usually become a collection of details.

Write one audience sentence: ‘After this, they should understand ___ and be ready to ___.’ Use it to decide what belongs. Different audiences may need different context, but the underlying facts should remain consistent.

02

Build around situation, change and next step

Use a three-part spine. Situation explains the relevant starting point and stakes. Change shows the action, decision or evidence that altered the position. Next step tells the audience what happens now or what you need from them.

This structure works for progress updates, recommendations, change communication and career examples. It creates movement without forcing drama. Keep the situation short enough that the change arrives early. End where the audience’s responsibility begins.

03

Separate evidence from interpretation

List the facts you can verify: dates, outputs, observations, measures, decisions and direct feedback. Then list your interpretation separately. This prevents a story from presenting an assumption as a result or a team outcome as an individual achievement.

Use measured language when the evidence is limited. Say ‘followed the change’ instead of ‘was caused by’ unless you can support causation. Mark estimates and unresolved questions. A credible story can contain uncertainty; it simply shows the audience where that uncertainty sits.

04

Choose detail that earns its place

Include details that explain the stakes, reveal a decision or make the next step easier to understand. Remove chronology that does not change meaning. Names, colour and background can make a story memorable, but they must also be appropriate to share.

Use plain language and familiar terms. Define necessary specialist language. Prefer one strong example to five weak ones. Read the story aloud and notice where attention drops. That is often where context has become longer than the decision needs.

05

Adapt the same evidence to common work formats

A status update can lead with the change, then add the minimum situation and next decision. A presentation can give one slide to each part of the spine. An interview answer can add your specific responsibility and reflection. A change announcement should include what remains stable and how questions will be handled.

Do not copy the same length into every channel. Preserve the evidence and intended action while changing sequence, detail and tone. The audience should receive the same truth in the form that best supports their work.

06

Use stories ethically

Obtain permission where a story identifies a person, customer or organisation. Remove sensitive information and use approved systems. Do not combine events in a way that creates a false result. Label fictional, composite or illustrative examples.

Represent contribution accurately. Say what you owned, what the team did and which outcome can be verified. Avoid using vulnerability as performance or another person’s difficulty as content. A professional story should create understanding without spending someone else’s privacy.

07

Create a story bank and practise deliberately

Keep a private bank of situations, decisions, outcomes, feedback and lessons that you are permitted to record. Tag entries by capability, audience and possible use. Capture evidence close to the event while details are still clear.

Once a month, turn one entry into a short update, presentation opening or interview answer. Ask a trusted reader what they understood, what they remembered and what action seemed required. Revise the structure, not the facts. Practice makes it easier to communicate clearly when the moment matters.

Before you move on

  • The audience and required action are explicit.
  • The story has a clear situation, change and next step.
  • Facts, estimates and interpretations are distinguishable.
  • Every detail helps explain the stakes, decision or action.
  • The format fits the channel while the evidence stays consistent.
  • People, organisations and confidential information are protected.
  • My story bank records real work I am permitted to use.

Sources and further reading

These official resources informed the guardrails and practical method in this guide.

  1. Digital.gov Plain Language Guide ↗
  2. ICO: Guidance on AI and Data Protection ↗
Use the free Workweek Starter →

This preview uses fictional examples where indicated. Read our editorial approach.