In this guide
Give the update a purpose
Choose the question your update should answer. Are you explaining progress, raising a risk or asking for a decision? A single update can contain several facts, but it needs a clear organising purpose.
Write that purpose in one sentence before drafting. When a detail does not support it, remove the detail or move it to supporting notes. Your reader should not have to infer the point from a list of activities.
Use situation, change and next step
Start with the relevant situation. Describe the change using evidence. End with the next step or decision. This is a practical structure, not a formula that belongs in every conversation. For an urgent message, lead with the request and put the situation afterwards.
Keep the story proportionate to the task. A routine project update may need three sentences. A major decision may need a fuller account, a comparison of options and a separate evidence section.
Rewrite the activity list
The following example is fictional. Notice how the improved version connects the events while keeping uncertainty visible.
Before
We reviewed the process, spoke to the team and updated the handover document.
After
The team was receiving handovers without a clear owner. We reviewed the process together and added a named owner and due date to the handover document. We will test it next week and check whether fewer tasks need follow-up.
The rewrite explains the problem, the action and the intended check. It does not claim an improvement that has not been measured.
Make your evidence easy to inspect
Use a concrete observation, a verified measure or a relevant example. If a result is preliminary, say so. If several factors could explain a change, resist the temptation to credit your own intervention alone.
Storytelling can make evidence easier to understand, but it must not create a stronger causal claim than the facts support. Link to the supporting document when your audience needs to inspect the detail.
Match the story to the reader
A colleague implementing the next step needs ownership and timing. A manager allocating resources needs the trade-off and the decision. A wider team may need to understand how the change affects their work.
Change the emphasis for the audience without changing the underlying facts. Read the update aloud. Replace language you would never use in a conversation, and shorten sentences that hide the action.
Build a small bank of useful stories
At the end of each week, save one example of a problem, an action and a result or learning. Record the evidence while it is still easy to find. Mark anything that is confidential or not suitable for sharing.
Over time, this record can support performance conversations, presentations and professional profiles. Keep it accurate and specific. A modest example with clear evidence is more useful than an impressive claim you cannot substantiate.
Before you move on
- The purpose of the update is clear.
- The situation gives enough context without a long preamble.
- The change is backed by evidence.
- Results and intended results are distinguished.
- The next step has an owner or an explicit request.
TAKE THE NEXT STEP
Make this lesson your own.
The companion PDF includes examples and a worksheet you can keep.
Explore the companion guide →Email delivery coming soon.
This preview uses fictional examples where indicated. Read our editorial approach.