Product
MoSCoW & Weighted Prioritization
The idea, in plain English
When everything feels 'important', you need a way to separate the truly essential from the nice-to-have. MoSCoW sorts work into four buckets: Must have, Should have, Could have, and Won't have (this time). Weighted scoring goes a step further with numbers: you rate each feature on a few criteria — like value, ease, and urgency — then multiply each rating by how much that criterion matters (its weight) and add them up. It's like judging a cooking contest where taste counts more than presentation, so you weight taste heavier before totaling the scores.
How it works
- 1Choose your criteria (value, ease, urgency) and give each a weight that sums to 1, reflecting how much it matters.
- 2Rate each feature on every criterion, say from 1 to 10.
- 3Multiply each rating by its criterion's weight, then add those up for the feature's weighted score.
- 4Rank by score. The top of the list is your 'Must have'; the bottom slides toward 'Won't have this time'.
When you'd use it
Use MoSCoW for a quick, shared language about what's essential versus optional. Step up to weighted scoring when stakeholders disagree and you need a transparent number that shows exactly why one feature outranks another.
Common beginner mistakes
- Letting everything become a 'Must have'. If it's all essential, you haven't prioritized — MoSCoW only helps when 'Won't' is used honestly.
- Picking weights after seeing the scores to get the answer you wanted. Decide the weights first, then let the math tell you the order.
Try it — edit and run
Click the code to edit · press ⌘/Ctrl+↵ to run
Editable code. Tab and Shift+Tab indent. Press Escape, then Tab, to move focus out of the editor.
Checkout redesign: 7.3
Profile avatars: 4.6
Top priority (Must have): Checkout redesignNot sure this is the right topic? See the learning paths → or where this leads →