MoSCoW Prioritization Tool
Sort your features into Must, Should, Could and Won't have. See a count for each bucket, and get a warning when too many things are Musts.
RICE = Reach x Impact x Confidence / Effort. Switching method keeps your ideas and the other method's numbers.
Ranked by RICE score (0)
No ideas yet. Add one on the left, or start from the example.
Kept in this browser. Log in to save it to your account. Download or copy anything you want to keep.
Four steps to a MoSCoW list.
- 1
List the items
Add each feature or requirement for this release.
- 2
Sort them
Drag each card to a bucket, or use its Move to menu.
- 3
Check the Musts
If more than 60% are Musts, some of them aren't.
- 4
Export
Copy a Markdown list or download a CSV.
FAQ
What does MoSCoW stand for?
Must have, Should have, Could have and Won't have this time. The lowercase o's are only there to make the word readable. Must haves are what the release can't ship without. Should haves matter but have a workaround. Could haves are nice extras. Won't haves are agreed out of scope for now, not rejected for ever.
How many Musts is too many?
The usual guideline is that Musts take up no more than about 60% of the effort, so the team has room to absorb surprises. This tool counts items, not effort, and warns when more than 60% of your sorted items are Musts. If it fires, ask of each Must: what happens if we ship without it? If the answer is "nothing terrible", move it down.
How do I decide between Must and Should?
Ask whether the release still works without the item. If it would be illegal, unsafe or useless, it's a Must. If it would be worse but usable, or there's a workaround, it's a Should. Try to decide with the people who'll feel the cut, not alone.
Is MoSCoW enough on its own?
It sorts, but it doesn't rank inside a bucket. Once you have your Shoulds, score them with RICE or ICE in the same tool. To find out what users actually think is a must-have, run a Kano survey on the same list.
Is my list saved?
It's kept in this browser, and it's the same list the RICE, ICE and Kano modes use, so your items carry across. Log in to save it to your account. You can also copy it as Markdown or download a CSV.
Beginner UX (AI) Design starts 12 January 2027.
Tools help you do the work. They don't teach you the judgement behind it. Beginner UX (AI) Design is taught live online by working UX professionals, built for career-changers with no design background.
Working in a team rather than learning on your own? We run in-house UX training built around your own product, and we can talk it through on the same call.