Home › The Garage › Prioritisation
Transformation

Prioritisation techniques

Everything can’t be first. Good prioritisation replaces the loudest voice with a shared rule — so the sequence is defensible, and the team spends its scarce effort where it pays back most.

By LeanBean · Updated November 2026 · 5 min read
What's in this guide
  1. Why a method beats opinion
  2. Impact vs effort
  3. MoSCoW
  4. RICE scoring
  5. Common questions
Impact → Effort → Quick winsdo first Major projectsplan & resource Fill-insif time allows Thanklessavoid
Plot each item by impact and effort. Quick wins go first; thankless work gets dropped.

Why a method beats opinion

When everything is “a priority,” nothing is. A prioritisation method does one useful thing: it makes the trade-off explicit and shared, so the order of work comes from an agreed rule rather than whoever argued hardest. The method matters less than the fact that the whole team can see why item A comes before item B.

Impact vs effort

The simplest technique, and often enough: plot each item on two axes — how much value it delivers, and how much effort it takes. High impact, low effort are quick wins; do them first. High impact, high effort are major projects to plan properly. Low impact, low effort are fill-ins. Low impact, high effort is thankless work to avoid. It is fast, visual, and surfaces disagreement about impact early.

MoSCoW

MoSCoW sorts items into four commitment levels: Must have (non-negotiable for this release), Should have (important but not vital), Could have (nice if there’s room), and Won’t have this time (explicitly out, which is the discipline most teams skip). It’s strong for scoping a release because it forces the “not now” decision to be said out loud.

RICE scoring

RICE: a number you can defend
RICE scores each item on Reach (how many are affected), Impact (how much per person), Confidence (how sure you are), and Effort — then ranks by (Reach × Impact × Confidence) ÷ Effort. The value isn’t precision; it’s that it forces you to name your confidence and divide by cost, which quietly demotes the expensive, low-certainty favourites. Use it when a ranked backlog needs to survive scrutiny.

Describe a process. Get the whole analysis.

LeanBean turns a plain-language description of any process into a professional map — with Lean waste, SIPOC, design-thinking, AI-readiness and capacity analysis built in, and a Transformation Coach that sequences the fixes. Free to start.

Build your first map free →

The Garage — a community of practice

The Garage is where Lean, process and AI-readiness practitioners learn in the open — short lessons, real examples, and a place to compare notes. Join the community: follow along, try it on your own work, and share what you find.

Common questions

What is the simplest prioritisation technique?

An impact-versus-effort matrix. Plot each item by the value it delivers and the effort it needs: high-impact low-effort items are quick wins to do first, and low-impact high-effort work is avoided. It is fast and makes disagreement about impact visible.

What does MoSCoW stand for?

Must have, Should have, Could have, and Won’t have this time. It sorts work by commitment level and is useful for scoping a release, because it forces the team to state explicitly what is out of scope for now.

How does RICE scoring work?

Each item is scored on Reach, Impact, Confidence and Effort, then ranked by (Reach × Impact × Confidence) ÷ Effort. Dividing by effort and multiplying by confidence demotes expensive, uncertain ideas and produces a ranking you can defend.

Why prioritise at all instead of just doing everything?

Because capacity is finite and starting everything finishes nothing. An explicit method concentrates scarce effort where it pays back most and replaces ‘whoever argued hardest’ with an agreed, visible rule.

Related guides: Transformation roadmap · Work decomposition · Capacity modelling