Agency operations workshop / 5 MIN READ
Write the update people can use without another meeting
Report meaningful changes, decisions needed and the next dependency in a consistent place.
AI-assisted research and analysis for the SNS Creative Fieldbook
Sources checked 2026-11-06
A written update earns attention when it helps colleagues understand what changed and what they need to do. A list of activity without consequences leaves readers unable to tell whether the project needs their help.
What you will leave with: A concise campaign update format with evidence, ownership and a response route.
Use this when
- Status meetings repeat information that could be read.
- Project messages are scattered across several conversations.
This is not a replacement for urgent incident communication or a meeting needed to resolve a complex decision.
Choose the audience and the update’s job
Atlassian’s project-update guidance supports asynchronous reporting of status and challenges. Define what this audience needs to know to coordinate its work.
A delivery team needs different detail from an executive sponsor. Keep one authoritative update location and link to supporting tasks rather than copying every task into every message. Agree an appropriate cadence and a separate route for time-sensitive changes. Readers should know when an issue will appear in the ordinary update and when they will be contacted sooner.
Lead with what changed and why it matters
Describe completed outcomes, material changes and unresolved dependencies. “Venue confirmed for the approved format” communicates more than “several venue calls.” Include a direct reference where readers need to inspect the result. Avoid dressing routine activity as progress when the decision remains blocked.
State whether the plan still holds and explain any meaningful change in scope or timing. Use factual language rather than unsupported optimism. If an item is uncertain, say what must be checked and who owns it. A short update can acknowledge uncertainty without becoming a detailed risk report or an excuse for not making a decision.
Make requests specific and answerable
For each item needing input, name the question, responsible recipient and useful response date. Explain what depends on the answer. Do not tag a whole leadership group when one authorized person needs to decide. Keep requests in the relevant channel and within the appropriate confidentiality boundary.
Distinguish a question from an informational notice. A reader should not have to infer whether “waiting on legal” means they must act. If the issue needs discussion, propose a focused meeting with the unresolved choice rather than restoring a broad recurring status call. Do not treat a read receipt or reaction as approval unless the agreed process supports it.
Maintain continuity between updates
Start the next update by closing or revising earlier requests. Link material decisions and show how they changed the plan. This makes the update a continuing account rather than a series of disconnected snapshots. Remove stale blockers once resolved and avoid repeating the entire project history.
Ask readers occasionally whether the update gives them enough context to act. Adjust the format if important information is consistently missed. Keep sensitive discussion out of a broadly visible status record, using an appropriate summary and restricted route instead. The aim is fewer coordination surprises, not a more elaborate reporting ritual.
Make the reasoning concrete.
A fictional campaign lead sends a weekly list of calls, drafts and meetings. A sponsor is surprised to learn that an unresolved venue decision now threatens the public invitation date.
Add more activity detail
Opening: Describe every call so the sponsor can see how busy the team is.
Hypothesis: The update becomes a fuller work diary.
Risk: The decision and its consequence may still be buried.
State the dependency and request
Opening: Explain the venue choice, the decision owner and the latest useful approval point.
Hypothesis: The sponsor can act on the actual issue.
Risk: The decision may require a focused discussion outside the normal update.
The lead changes the update to foreground the unresolved choice and tracks its resolution in the next message. Routine activity remains in the linked task records.
Take the questions into your next brief.
Use these prompts in your own notes. Nothing is submitted from this page.
Audience
What coordination decision does this reader need to make?
Change
What outcome or condition changed since the last update?
Evidence
Where can the reader inspect the relevant result?
Request
Who needs to answer which question by when?
Continuity
What happened to the previous update’s open request?
Watch for the wrong conclusion.
- Reporting busyness instead of consequences.
- Hiding a decision request inside a general status paragraph.
- Repeating stale blockers without updating their owner or next step.
Your next action
Rewrite your latest status update so its first lines state what changed, what remains blocked and the one action the reader needs to take.
Sources & scope
The workflow, worksheets and hypothetical examples are original editorial analysis. Sources support only the identified principles. No measured business results or named human reviewer are claimed.
- Atlassian Team Playbook: Weekly Project Updates →Primary framework-publisher guidance · Supports: Written asynchronous updates can communicate project status and challenges; the campaign update format is original analysis.