Back to the Playbook
OperateOP-04
Monitor product outcome
Evaluate whether shipped work produced the intended user and business outcome, and feed the result back into the Product Brain and the roadmap.
Product statusAssisted workflowMeasurement data is added as files or exports; there is no live analytics connector yet.
Context in3 required inputsSuccess metric definition and baseline · Release date and scope · Actual measurement data
TransformationProduct Manager + Product AgentLocal Files · Atlassian
OutcomeOutcome review with recommendation.Artifact: Outcome review
Why it matters
Teklens does not stop at «shipped». The metric defined before the build is compared with what happened after it, and the answer changes the next prioritisation.
Owner
Product Manager
Human-led
Participants · Agents
EngineerHead of ProductProduct Agent
Trigger
A defined review date, or enough post-release data exists.
Required context
Product BrainSuccess metric definition and baselineJiraRelease date and scopeAnalyticsActual measurement data
Optional context
Customer evidenceCustomer feedbackCustomer evidenceSupport volumeJiraIncidentsCustomer evidenceQualitative research
Skills
Local FilesAtlassian
Activity steps
- 1Collect the results and compare them with the target.
- 2Investigate variance and unintended effects.
- 3Separate correlation from causation.
- 4Recommend continue, iterate or stop, and record it.
Output
Outcome review with recommendation.
Artifacts
Creates: Outcome review
Updates: Product Brain, Roadmap
What good looks like
- Uses the pre-defined metrics.
- Negative and unexpected outcomes are included.
- Correlation is separated from causation.
- The recommendation is explicit.
Quality gate
Product decides whether roadmap changes follow.
Destination
Product BrainRoadmap
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.