Method
A compact workshop that selects and calibrates a prioritization model (impact-effort, RICE, risk-adjusted) before scoring initiatives.
Choose this if
This method works when teams are using conflicting scoring frameworks and the disagreement is slowing prioritisation decisions.
Pack = one session you can run now. Workspace = a saved thread for method choice, planning, and shareable outputs.
What Workspace helps you carry forward
Artifact preview
Selected prioritization framework
Decide · Low
Decide fit before you spend session time.
The core facilitation flow, with enough structure to run the method confidently in the room.
Standard setup for Mixed in remote delivery.
Total planned time: 60 min
What happens
Define the decision horizon, available evidence, and who must defend the outcome.
Facilitator does
Document four non-negotiables before evaluating any framework: who has to defend the decision publicly, what evidence is available for scoring, how fast a decision is needed, and what will actually change based on the prioritisation result. Write these on the board. Frameworks that can't be defended in the room where decisions are made are academic exercises — the right framework is the simplest one that produces a result the decision-makers will trust.
Participants do
Name the constraints honestly — including political ones. If a particular framework will be rejected by the executive sponsor regardless of its merit, that is a real constraint. Surface it now rather than after the scoring session.
Output / signal of success
Four context constraints written on the board and agreed: decision owner, available evidence type, decision timeline, and what changes as a result of the scoring — giving the room a shared basis for evaluating which framework fits.
Watch for
Context constraints are assumed rather than explicitly named — the room jumps to framework comparison before agreeing what the framework needs to do.
Recovery tip
Stop comparison. Ask: "Who has to present this prioritisation outcome, and to whom? What would make them confident in the result?" Write that answer on the board as the primary constraint before framework evaluation begins.
What happens
Evaluate each candidate framework against the context constraints from Step 1.
Facilitator does
Present the framework options against the four context constraints — not against their analytical sophistication. A RICE score is more rigorous than Impact vs Effort, but if the team has no reliable reach or confidence data, RICE produces false precision. Eliminate options that fail on the most critical constraint first.
Participants do
Evaluate frameworks based on what your team can actually populate — not based on what looks most rigorous on paper. A framework you can fill confidently is more valuable than one that requires data you don't have.
Output / signal of success
Framework options evaluated against the four context constraints, one or two frameworks remaining as candidates, with the room able to articulate why eliminated options were ruled out.
Watch for
Framework comparison prioritises analytical sophistication over stakeholder credibility — the room selects the most complex framework because it sounds rigorous, not because the team has the data to populate it.
Recovery tip
Ask: "Can we populate every field of this framework with data we actually have, or would we be estimating?" If more than two fields require estimation, the framework is too complex for the available evidence. Choose a simpler one.
What happens
Write agreed definitions for each scoring level and run a calibration example.
Facilitator does
For the selected framework, write agreed definitions for each scoring level before any item is scored. Run one calibration example together out loud: pick a known initiative, have each person score it independently, then compare. If scores diverge, discuss until the room reaches the same score. This calibration takes ten minutes and prevents the scoring session from devolving into semantic debate.
Participants do
Score the calibration item independently before comparing with others — the divergence in independent scores reveals where the definitions need more precision.
Output / signal of success
Scoring definitions written on the board for every level of every axis, calibration item scored independently by all participants with consensus reached — participants could score a new item without asking for clarification.
Watch for
Scoring definitions are left to individual interpretation, producing incomparable scores in the live scoring session.
Recovery tip
Stop the calibration if scores diverge significantly. Ask each person: "What definition of high impact are you using?" Write the different definitions on the board. Agree one and rewrite the scoring guide before continuing.
What happens
Commit the selected framework, document the definitions, and schedule the scoring session.
Facilitator does
Document the selected framework and its calibrated definitions in a format that can be shared before the scoring session. Confirm who owns preparing the initiative list and who facilitates the next session. Get a date on the calendar before the room closes — a framework agreed today with no follow-through date produces a scoring session that never happens.
Participants do
Commit to a specific role in the scoring session — either as a scorer, a facilitator, or the owner of the initiative list. Leave with a named action and date, not just agreement on the method.
Output / signal of success
Selected framework and calibrated definitions documented and shareable, with a scoring session scheduled — date confirmed, facilitator named, and initiative list owner committed.
Watch for
The framework is agreed but no scoring session is scheduled before the current session closes.
Recovery tip
Before closing, say: "We don't leave until there is a date on the calendar for the scoring session and a name next to 'initiative list owner.'" If neither can be confirmed, escalate before closing — the output of this session has no value without a committed follow-through.
Prepare the room, the evidence, and the working surface so the session can stay focused on synthesis.
A rough draft of the initiatives that will be scored in the follow-through session and clarity on who has to defend the prioritisation outcome. Without knowing what will be scored and who will use the result, the framework selection cannot be evaluated against real constraints.
Initiative list
Optional
Scoring framework options
Optional
Decision criteria
Optional
Calibration examples
Optional
Operational context note
Optional
Bring examples, pain points, or service evidence the room can point to quickly.
Remote facilitation choreography
Required
Pre-plan handoffs, breakout usage, and how people rejoin the main board.
Shared digital board with timer and voting
Required
Keep instructions and voting visible at all times.
Framework selection matrix
Keep the output usable, then use the recovery guidance when the room starts drifting.
What this does not produce
Prioritization Framework Selection produces a committed method and calibrated definitions. It does not produce a prioritised list of initiatives — that requires a separate scoring session. Teams that treat the framework selection as the prioritisation work have done the meta-work without the work itself.
Failure mode
Why it happens
Teams select RICE or weighted scoring because they sound more rigorous and defensible. But RICE requires reliable reach, impact, confidence, and effort data. In the absence of that data, every field becomes an estimate, and the precision of the formula produces false confidence in results that are equally uncertain as a simpler model.
Recover now
If this happens, ask: "Which fields in this framework can we populate from actual data rather than estimation?" If fewer than half have real data, step down to a simpler model. A well-calibrated Impact vs Effort matrix beats a poorly-populated RICE score every time.
Prevent next time
Next time, include a "data availability" column in the framework comparison — for each framework, mark which fields the team can populate with actual data and which require estimation. Use that as a primary selection criterion.
Failure mode
Why it happens
Framework selection feels like the hard work and the room relaxes once a method is agreed. The scoring session feels like an obvious next step that someone will sort out. Without a committed date and owner, it gets deprioritised as the next sprint planning cycle absorbs attention.
Recover now
If this happens, hold the room before closing. Say: "This session has no value without a follow-through date. Who owns the initiative list and when can we schedule the scoring session?" Don't close until both questions have a named answer.
Prevent next time
Next time, make the scoring session date a listed output of this session — write it on the board alongside the framework and definitions as an explicit deliverable.
Failure mode
Why it happens
Teams with strong opinions about prioritisation add axes, modifiers, and weighting factors until the selected framework has been rebuilt from scratch. The result is a bespoke model nobody else in the organisation can interpret and that is harder to defend to stakeholders familiar with the standard framework it started from.
Recover now
If this happens, count the number of modifications made to the base framework. If more than two, ask: "Are we still using the base framework, or have we built something new?" If new, evaluate it against the original context constraints — it needs to earn its complexity.
Prevent next time
Next time, set a modification limit before Step 3 begins: the selected framework can have one optional weighting factor added. Any further customisation requires explicit justification against the Step 1 context constraints.
Change the shape of the session only after the fit and runbook are clear.
Standard variant for Mixed in remote delivery. Waypoint is adapting timing, facilitation emphasis, prep, and recovery guidance here, but the room still needs final tailoring to the exact stakes and participants.
Use this after you have checked the fit and know you want to carry the method forward.
The pack is the fastest way to run this now. Use the links below when you need prep, sharing, or a saved reference point.
Sources and references used in this method page.
Atlassian Team Playbook prioritization methods.
Workshop decision frameworks and facilitation structures.
Reviewed 2026-04-17 by Discovery Waypoint Editorial Team