Back to the Playbook
Define & DesignDD-04
How to prioritise with ICE scoring
Use ICE for a quick relative comparison with consistent anchors and honest confidence.
Product statusAvailable now
Input4 required inputsComparable candidates · Impact evidence and uncertainty · Rough implementation ease
SkillsCalculate ICE scores · Prepare task context · Review an artifact against agreed criteriaProduct Manager + Product Manager Agent
OutcomeICE score sheet: scales with anchors, per-candidate factors and product, interpretation and the proposed order.Artifact: ICE score sheet
Owner
Product Manager
Human + Agent
Participants · Agents
EngineerProduct Manager Agent
Trigger
Comparable candidate initiatives need a quick relative order.
Required context
JiraComparable candidatesProduct BrainImpact evidence and uncertaintyArchitectureRough implementation easeProduct BrainInitiative focus and approved Product Brain guidance
Optional context
CodeEngineering input on ease
Skills
Calculate ICE scoresPrepare task contextReview an artifact against agreed criteria
Suggested conversation arc
- 1Agree ICE scalesDefine a shared 1–10 scale for impact, confidence and ease for this comparison; clarify that higher ease means less effort.Skills: Prepare task context
- 2Calculate ICE comparisonsRate each factor with rationale and multiply impact, confidence and ease. Keep missing evidence visible instead of inflating confidence.Skills: Calculate ICE scores
- 3Inspect surprising scoresExamine close results and unexpected leaders for inconsistent scales or optimistic confidence; change estimates only with reasons.Skills: Review an artifact against agreed criteria
- 4Agree the working orderUse the comparison to select a working order and record any strategic exception. Set a reconsideration trigger for weak assumptions.
Output
ICE score sheet: scales with anchors, per-candidate factors and product, interpretation and the proposed order.
Artifacts
Creates: ICE score sheet
What good looks like
- Each valid score equals the visible three-factor product.
- Ease direction and evidence-based confidence are preserved.
- Out-of-range or missing factors block that item's calculation.
Quality gate
The Product Manager selects the working order and records strategic exceptions.
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.
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.