Back to the Playbook
Strategy & DiscoverySD-13
How to prioritise against your objectives
Prioritise by objective contribution without forcing essential maintenance into an invented strategic link.
Product statusAvailable now
Input4 required inputsBacklog candidates · Agreed objectives and their measures · Expected impact and effort or maintenance rationale
SkillsPrioritise against objectives · Prepare task context · Review an artifact against agreed criteriaProduct Manager + Product Manager Agent
OutcomeObjective alignment: each candidate mapped to objectives with evidence, unmatched obligations, the recommended order and deferrals.Artifact: Objective alignment
Owner
Product Manager
Human + Agent
Participants · Agents
Head of ProductEngineerProduct Manager Agent
Trigger
Backlog candidates meet the agreed objectives of the current period.
Required context
JiraBacklog candidatesProduct BrainAgreed objectives and their measuresFilesExpected impact and effort or maintenance rationaleProduct BrainInitiative focus and approved Product Brain guidance
Optional context
CodeDependencies in the codeCustomer evidenceCustomer evidence per candidate
Skills
Prioritise against objectivesPrepare task contextReview an artifact against agreed criteria
Suggested conversation arc
- 1Confirm decision objectivesAgree specific current objectives and the decision horizon; clarify vague goals before assessing any backlog item.Skills: Prepare task context
- 2Map candidate contributionsLink each item to supported objectives with impact evidence. Keep unmapped work and necessary maintenance explicit rather than fabricating alignment.Skills: Prioritise against objectives
- 3Resolve competing contributionsRank candidates within each objective by impact and use effort to illuminate close choices. Discuss conflicts between objectives and the maintenance allowance.
- 4Confirm chosen and deferred workCheck that selected items support the agreement and deferred items have reasons. Preserve exceptions and their rationale for the next review.Skills: Review an artifact against agreed criteria
Output
Objective alignment: each candidate mapped to objectives with evidence, unmatched obligations, the recommended order and deferrals.
Artifacts
Creates: Objective alignment
What good looks like
- Every candidate is represented, including unmatched obligations.
- Recommendations rely on stated current objectives.
- Necessary maintenance is never dropped for lacking an OKR mapping.
Quality gate
The Product Manager confirms the chosen order, the deferrals and the recorded exceptions.
Destination
RoadmapJira
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.
Choose the path that matches your role.
Set the Product AI direction with us, or test the shared Product Brain on real work with Jira and code.