Back to the Playbook
OperateOP-03
Communicate product update
Give internal or external stakeholders the right level of change, impact and next steps, with links to the source of truth.
Product statusAvailable now
Context in4 required inputsVerified change or decision · Audience · Impact
TransformationProduct Manager + Product AgentLocal Files · Atlassian
OutcomeAudience-specific update or stakeholder report.Result only
Owner
Product Manager
Human + Agent
Participants · Agents
Head of ProductProduct Agent
Trigger
A release, roadmap decision, milestone or material product change.
Required context
Product BrainVerified change or decisionFilesAudienceJiraImpactJiraRelevant links
Optional context
AnalyticsMetricsConfluenceRelease notesCustomer evidenceCustomer implications
Skills
Local FilesAtlassian
Activity steps
- 1Choose the audience.
- 2State what changed and why.
- 3Explain the impact and the next step.
- 4Link to the source of truth and review.
Output
Audience-specific update or stakeholder report.
Artifacts
Result only
What good looks like
- Right audience and level of detail.
- No unsupported claims.
- Decision and impact are clear.
- Links to the source of truth.
Quality gate
The owner reviews external or high-impact communication.
Destination
Release channelConfluence
Usually next
People and agents work from the same Product Brain. The owner stays accountable. Assigned agents prepare and check. A named person approves at the gate.
Deep dives from the AI PM Lab
Articles that explain the thinking behind this Activity.
Show us exactly how product work happens today.
Thirty minutes with a founder. We compare your process with the Playbook and pick the first Activity to run on your Jira and your repo.