Back to the Playbook
Product BrainPB-04
Define success metrics
Define how the success of an objective or feature will be measured before work is committed.
Product statusAssisted workflowAnalytics data is added as files or exports; there is no live analytics connector yet.
Context in4 required inputsProduct objective · Target user and problem · Expected behaviour change
TransformationProduct Manager + Product AgentLocal Files · Atlassian
OutcomeSuccess metric definition with targets and measurement rules.Artifact: Success metrics
Owner
Product Manager
Human-led
Participants · Agents
EngineerHead of ProductProduct Agent
Trigger
A new objective, feature brief or PRD.
Required context
Product BrainProduct objectiveProduct BrainTarget user and problemFilesExpected behaviour changeAnalyticsAvailable measurement sources
Optional context
AnalyticsHistorical baselinesFilesBenchmarksAnalyticsAnalytics definitions
Skills
Local FilesAtlassian
Methods used inside this Activity: Outcome metrics and leading indicators · Guardrail metrics
Activity steps
- 1Choose the outcome metric.
- 2Define the baseline.
- 3Set target and time frame.
- 4Define leading indicators and guardrails.
Output
Success metric definition with targets and measurement rules.
Artifacts
Creates: Success metrics
Updates: Product Brain
What good looks like
- Outcome-based, not delivery output.
- Measurable with the sources you have.
- Attributable enough to guide decisions.
- Guardrails protect what must not get worse.
Quality gate
The product owner approves the metric definition.
Destination
Product BrainConfluence
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.
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.