Method
A rapid prioritization matrix where initiatives are scored by expected impact and implementation effort to identify quick wins and strategic bets.
Why you were brought here
You came here from prioritise initiatives quickly.
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
Prioritization matrix
Prioritise · Low
Decide fit before you spend session time.
Room fit check
Best when the options already exist and the room needs a defensible shortlist rather than another brainstorm. This room has enough of the right conditions for the method to hold without extra ceremony.
Primary risk: The room scores initiatives without a shared definition of impact.
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: 75 min
What happens
Set shared scoring definitions before any item is placed.
Facilitator does
Write the definition of "impact" and "effort" on the board before anyone scores anything. Impact must be defined as a customer or strategic outcome — not a delivery milestone, not urgency, not stakeholder preference. Effort must be defined as resource investment — time, people, cost — not complexity or risk. Run one calibration item together: place a known initiative that everyone understands and reach consensus on its position before individual scoring begins.
Participants do
Challenge the definitions before scoring starts. If your understanding of "impact" differs from the written definition, say so now — not after 30 items are placed.
Output / signal of success
Two clear, written definitions visible on the board — one for impact, one for effort — agreed by the room, with a calibration item placed and confirmed before individual scoring begins.
Watch for
Effort axis is conflated with complexity or risk rather than resource investment.
Recovery tip
Stop placement. Write "effort = resource investment (time, people, cost)" visibly on the board. Ask the room to re-place the calibration item against that specific definition before continuing.
What happens
Each participant places items independently, then the board is revealed for discussion.
Facilitator does
Have each person place their own items silently, then reveal the full board. Divergence is more informative than consensus — items placed very differently by different participants are the ones worth discussing. Surface the three most divergent placements first. Don't allow negotiation during individual placement.
Participants do
Place items based on your own knowledge and judgment against the agreed definitions — not based on what you think others will place, and not lobbying others during the silent phase.
Output / signal of success
All items placed with genuine spread across quadrants and at least 3–5 items showing visible divergence in placement across participants.
Watch for
Participants lobby each other during the silent placement phase, producing false consensus before discussion has happened.
Recovery tip
Stop the board. Enforce silence until all items are placed. Tell the room: "The disagreements are the most valuable part of this step — don't resolve them before we've seen them."
What happens
Revisit items with the highest placement divergence, surfacing the reasoning behind each.
Facilitator does
Start with the widest disagreements, not the full list. Ask: "What do you know that makes you place this differently?" rather than declaring any placement wrong. An item moves only when the room agrees what information changed — not because a louder voice argued for it. If the disagreement reveals genuine uncertainty about effort or impact, flag the item as assumption-dependent rather than forcing a placement.
Participants do
Justify placements with what you specifically know — a past project, a customer conversation, a technical constraint. "It just feels high effort" is not a valid justification. Name the specific factor.
Output / signal of success
The most divergent items discussed and either moved to a consensus position or flagged as assumption-dependent, with reasoning visible for each final placement.
Watch for
The most senior person in the room shifts items without surfacing reasoning, and others defer without pushback.
Recovery tip
When an item moves, ask the person who moved it: "What information are you using to justify this placement?" Write the answer on the board next to the item. If the answer is opinion rather than evidence, flag it: "That sounds like an assumption — should we mark this item as needing validation before we commit to it?"
What happens
Name the quadrant tiers, assign owners to the top-right items, and confirm next steps.
Facilitator does
Draw the quadrant lines together and name the tiers before assigning actions — the room should agree where the lines sit, not accept a default. For every top-right item: ask who owns it and what the next concrete step is. An unowned quick win is not actually quick. If an item has no owner in the room, it doesn't belong on the shortlist.
Participants do
Accept ownership only for items you have the authority and capacity to move. If you can't own it, name who can — don't leave it ownerless on the shortlist.
Output / signal of success
Named priority tiers on the matrix, every top-right item with a named owner and first next step, and bottom-left items explicitly parked with status.
Watch for
Priority tier language is soft ("we should probably look at this") rather than committed ("owner X will do Y by date Z").
Recovery tip
For each shortlisted item, require the owner to complete this sentence out loud: "I will [specific action] by [date]." If they can't complete it, the item isn't ready to commit — move it to a "needs owner" column and address it in the follow-up.
Prepare the room, the evidence, and the working surface so the session can stay focused on synthesis.
A defined list of initiatives to score — at least five, preferably 10–20 — and at least one person in the room with direct delivery or technical knowledge who can ground effort estimates. Without the initiative list, there is nothing to place. Without delivery knowledge, the effort axis is business optimism and the matrix is not trustworthy.
Opportunity list
Optional
Sizing assumptions
Optional
Voting criteria
Optional
Operational context note
Optional
Bring examples, pain points, or service evidence the room can point to quickly.
2x2 matrix board
Optional
Remote facilitation choreography
Required
Pre-plan handoffs, breakout usage, and how people rejoin the main board.
2x2 matrix board
Required
Shared digital board with timer and voting
Required
Keep instructions and voting visible at all times.
Impact-effort matrix
Keep the output usable, then use the recovery guidance when the room starts drifting.
What this does not produce
Impact-effort prioritisation produces a shortlist based on the room's judgment about relative value and cost. It does not validate impact estimates, verify effort sizing, or model dependencies and risks. Items that emerge as quick wins may not be quick — effort estimates from non-technical rooms require validation before they can be treated as commitments.
Failure mode
Why it happens
Teams under deadline pressure conflate "this is due soon" with "this matters most." Deadline proximity feels like impact when you're in the middle of it. Without an explicit written definition of impact on the board, participants score against what's most salient — and what's most salient is usually the thing with the nearest due date.
Recover now
If this happens, stop scoring. Write "impact = customer or strategic outcome, not deadline proximity" visibly on the board. Ask the room to re-rate the top five items against that specific definition. If urgency matters, add a separate axis rather than collapsing it into impact.
Prevent next time
Next time, open Step 1 by asking: "What would constitute a real impact for this team?" Write the agreed answer on the board and keep it visible throughout.
Failure mode
Why it happens
Product and business stakeholders overestimate ease when they want something done and underestimate complexity when they don't. Without at least one person with delivery knowledge in the room, the effort axis reflects business preference, not realistic sizing. The matrix then produces a shortlist of "quick wins" that are not actually quick.
Recover now
If this happens, flag every high-impact/low-effort placement as an assumption pending technical validation. Mark them clearly: "Effort estimate unvalidated." Schedule a calibration with an engineer or delivery lead before committing these items to the plan.
Prevent next time
Next time, require at least one person with delivery knowledge in the room before running the session. If that's not possible, define effort as "our current best guess pending technical input" and document that qualifier on the matrix.
Failure mode
Why it happens
Participants score all items optimistically when they brought the items to the session themselves. Nobody wants to place their own initiative in the low-impact zone. The result is a flat matrix where everything is high-impact/low-effort and no real prioritisation has occurred.
Recover now
If this happens, enforce forced ranking: no more than three items can occupy the top-right quadrant. Ask the room to choose which three they would implement if budget covered only three items. Remove the constraint framing once the discipline is re-established.
Prevent next time
Next time, before placement, tell the room: "Assume we can only fund the top-right quadrant. If everything ends up there, we've made no decision."
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 facilitation playbook resources.
LUMA method library for collaborative prioritization practices.
Reviewed 2026-04-17 by Discovery Waypoint Editorial Team
Related playbooks
These pages translate recognizable external methods into Waypoint-native guidance so the team can borrow the useful part without importing the whole mythology.
A facilitator-grade health check that is useful only if the red signals turn into named repairs immediately.
Open when Teams that can feel friction but cannot yet name where the damage really sits.
Treat Shape Up as an operating system for scoping and delivery, not as a workshop you can casually run in a single afternoon.
Open when Teams that repeatedly start work too vague and let scope sprawl silently.
A scoping session that runs before the observation itself — it maps every candidate user group, scores each on five signal dimensions, and produces one clearly justified target rather than a guess or a committee compromise.
Open when Customer engagements where a Day-in-the-Life is planned but the right user group has not yet been agreed.
