By the end of this lesson you can
- Use prioritisation frameworks to decide what to design and build.
- Make and explain trade-offs between scope, quality and time.
- Define a minimum viable version without harming users.
The idea
There is always more to do than time allows. Prioritisation decides what comes first.
Frameworks
- RICE: Reach × Impact × Confidence ÷ Effort.
- MoSCoW: Must have, Should have, Could have, Won't have (this time).
- Value versus effort: a simple two-by-two matrix.
- Kano model: basic expectations, performance features and delighters.
Frameworks structure discussion; they do not replace judgement.
Trade-offs
Most decisions trade between scope, quality and time. If the date is fixed, reduce scope rather than quality. Make trade-offs explicit and record them so they can be revisited.
Minimum viable, not minimum awful
A first release should be the smallest version that delivers real value and lets you learn. Cutting features is fine; cutting accessibility, error handling or clear content usually is not, because it harms users and creates expensive debt.
Why it matters in real projects
Designers constantly face pressure to fit more into less time. Knowing how to prioritise and negotiate trade-offs lets you protect what matters most to users while still shipping. It also makes you a trusted partner for product managers and engineers, rather than someone who only asks for more.
A realistic example
A team has six weeks to launch online booking for a physiotherapy clinic. The full design includes booking, rescheduling, reminders, payments, a practitioner profile page and reviews.
Using MoSCoW with RICE scores, they agree: must have booking, cancellation and email confirmation; should have reminders; could have profiles; won't have reviews or online payment this time. They refuse to cut accessible forms and error states. Launch happens on time, and data from real bookings shapes the next release.
Step by step
List candidates
List all features or design improvements.
Score
Apply RICE or value versus effort with the team.
Sort with MoSCoW
Agree must, should, could and won't.
Protect quality
List non-negotiables such as accessibility and error handling.
Record trade-offs
Write down what was cut and why.
Revisit
Review priorities after launch with real data.
Common mistakes
Mistake Cutting quality instead of scope.
Instead Reduce scope and keep core quality.
Mistake Treating framework scores as final answers.
Instead Use them to structure discussion.
Mistake Unrecorded trade-offs.
Instead Write them down for later.
Check your understanding
Choose an answer, then check it. There is an explanation either way.
Practice exercise
Exercise · about 45 min
Prioritise a release
Prioritise a first release for a product idea.
Steps
- List ten candidate features.
- Score them with RICE.
- Sort them with MoSCoW.
- List non-negotiables and recorded trade-offs.
Deliverable
A prioritised list with trade-off notes.
Self-assessment
Tick each item when it is true of your exercise. Be honest; this is for you.
4 items
Summary
- Frameworks like RICE and MoSCoW structure prioritisation.
- Trade scope before quality.
- Minimum viable means valuable, not broken.
- Record and revisit trade-offs.
Further reading
Third-party sources, chosen for reliability. They open in a new tab.
Your notes
Marking complete updates your course and roadmap progress.