What it is
A categorization technique that sorts requirements into Must have, Should have, Could have, and Won’t have (this time), giving a shared, blunt view of scope and priority.
When to use it
During Synthesize and Implement, for scoping releases and negotiating with stakeholders.
Why (value)
Creates fast, shared agreement on what is truly essential versus optional, and makes the “Won’t” decisions explicit.
How to run it
- List the requirements.
- Agree on definitions for each category.
- Assign each requirement a category together.
- Challenge an overgrown “Must” list.
- Record the agreed scope, including “Won’t.”
Inputs and outputs
- Inputs: A requirements list and the decision-makers.
- Outputs: Categorized requirements and an agreed scope.
Time and effort
Low. A single prioritization session.
Evidence and limitations
The categories reflect stakeholder inference about importance, not user evidence; without discipline, everything becomes a “Must.” See Evidence and limitations.
Tips and pitfalls
- Cap the “Must” list; if everything is critical, nothing is.
- Make “Won’t this time” explicit, not forgotten.
- Tie categories to goals, not volume.
Variations
Classic MoSCoW and time-boxed release scoping.
Related methods
Need help choosing and applying a method?
Gumshoe helps teams connect research, collaborative workshops and service design to the decisions they need to make.
Sources and further reading
- UX Tigers, “100 UX methods.”
Explore related methods
- Impact-effort prioritization — Plot options by impact and effort to spot the quick wins and avoid the money pits.
- RICE scoring — Rank initiatives with a formula of reach, impact, confidence, and effort.
- Roadmapping — Sequence outcomes and work over time to align the team on where things are heading and why.
