Publish a structured operating update
Give distributed readers one current record of outcomes, evidence, risks, decisions, and next work.
- Preparation
- One setup session, then a short recurring update from each owner.
- Difficulty
- Easy
- Task
- Publish async operating updates
Before you start
Get what you need before you start
- Choose the update period, audience, owner, and authorised decision forum.
- Define the meaning of each status and the evidence required.
- Set access rules for confidential customer, employee, financial, and security information.
Steps
Work through the method
Use the listed inputs and tools. Check the evidence when you need to verify a step.
Define the update contract
Set one format: period, owner, intended outcome, completed evidence, next work, risk, decision needed, and next update. Define every status label.
Why it matters: A shared format lets readers compare updates without treating an unsupported label as evidence.
- Input
- The operating cadence, active commitments, access rules, and decision forum.
- Output
- An update template with field definitions, owner, audience, and cadence.
Tools in this stepAtlassian GoalsEvidence for this step
Atlassian Goals can assign owners, prompt recurring updates, show status, link work, and retain update history.
Atlassian Support: Sections covering owners, recurring updates, status, linked work, and update history; lines 132–158 and 181–187
Write the current update
For each active outcome, link dated evidence, state what changed, list the next work, and separate a risk from a decision request.
Why it matters: A narrative status can sound current while hiding the source and the decision needed.
- Input
- Current source records, the prior update, and the update template.
- Output
- A draft update with traceable evidence, risks, decisions, and next work.
Tools in this stepAtlassian GoalsEvidence for this step
Wade Foster describes recorded all-hands meetings, archived discussion, weekly written updates, and different founder schedules at Zapier.
Zapier: Lines 328–345, 380–409, and 422–451Atlassian Goals can assign owners, prompt recurring updates, show status, link work, and retain update history.
Atlassian Support: Sections covering owners, recurring updates, status, linked work, and update history; lines 132–158 and 181–187
Review evidence and access
Have each owner check their claims and links. Remove unnecessary sensitive detail and confirm the intended audience can open every permitted source.
Why it matters: An async record can spread stale or confidential information more widely than a meeting.
- Input
- The draft update, source links, named owners, and access policy.
- Output
- An owner-checked update with tested access and recorded gaps.
Tools in this stepAtlassian GoalsPublish and route decisions
Publish in the agreed archive, link the prior update, and move each decision request to its authorised forum with an owner and due point.
Why it matters: An update informs readers but does not grant decision authority.
- Input
- The checked update and list of decision requests.
- Output
- A current archived update plus owned decision items and the next update date.
Tools in this stepAtlassian GoalsEvidence for this step
Wade Foster describes recorded all-hands meetings, archived discussion, weekly written updates, and different founder schedules at Zapier.
Zapier: Lines 328–345, 380–409, and 422–451
Success checks
Check the result before you finish
- The current update is findable and links to the prior update.
- Every status claim has dated evidence or a visible gap.
- Risks and decision requests remain separate.
- Each decision request has an authorised forum, owner, and due point.
Failure modes
Watch for these problems
- The update repeats activity without an outcome. State what changed and link its evidence.
- A colour or label replaces evidence. Add the dated source and state definition.
- Sensitive detail reaches the wrong audience. Remove it and repair access before republishing.
- Discussion stays in comments without a decision owner. Route it to the authorised forum.
Tools
Choose the tools you need
Tool
Atlassian Goals
A shared goal record with owners, recurring updates, linked work, status, and update history.
Check fit, limits and pricingSources
Read the sources behind this practice
Check what each source supports and where the advice has limits.
- Zapier: How to manage a remote teamFirst-hand founder account on a vendor site · Publication date unavailable
- Atlassian Support: Use goal status to track objectives and key resultsOfficial product documentation · Publication date unavailable