Back to the Playbook
Strategy & DiscoverySD-15
How to prioritise with a 2×2 matrix
Use shared relative placement to surface assumptions; the matrix is not a precision ranking.
Product statusAvailable now
Input4 required inputsCandidate changes · Impact rationale · Whole-team effort estimates
SkillsMap impact against effort · Prepare task context · Review an artifact against agreed criteriaProduct Manager + Product Manager Agent
OutcomeImpact/effort matrix: axes and anchors, placements with evidence and disagreements, quadrants and the candidates that proceed.Artifact: Impact/effort matrix
Owner
Product Manager
Human + Agent
Participants · Agents
EngineerDesignerProduct Manager Agent
Trigger
A bounded group of candidate changes needs a quick relative decision.
Required context
JiraCandidate changesProduct BrainImpact rationaleArchitectureWhole-team effort estimatesProduct BrainInitiative focus and approved Product Brain guidance
Optional context
CodeAffected code and dependencies
Skills
Map impact against effortPrepare task contextReview an artifact against agreed criteria
Suggested conversation arc
- 1Agree axes and anchorsDefine impact on a specific outcome and effort across design, engineering and verification. Establish low/high anchors together.Skills: Prepare task context
- 2Place the candidatesPropose relative placements using the agreed anchors, beginning with obvious extremes. Label uncertain boundary cases and evidence behind estimates.Skills: Map impact against effort
- 3Discuss disputed placementsInvite alternative placements and explain differing assumptions. Compare quick wins, major bets, small fill-ins and costly low-impact work.
- 4Agree what proceedsCheck decisions against the agreed outcome and capacity. Record candidates to pursue or defer without treating visual distance as a precise score.Skills: Review an artifact against agreed criteria
Output
Impact/effort matrix: axes and anchors, placements with evidence and disagreements, quadrants and the candidates that proceed.
Artifacts
Creates: Impact/effort matrix
What good looks like
- Axis definitions are consistent across candidates.
- The output stays a relative grouping rather than unsupported precision.
- Conflicting placements are shown, not hidden behind one voice.
Quality gate
The Product Manager records which candidates proceed and which are deferred.
Destination
JiraTeklens only
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.