Strategy
MoSCoW Prioritisation
A practical prioritisation framework for aligning teams on critical scope and explicit trade-offs.
How to apply MoSCoW prioritisation to categorise work, manage scope, and keep delivery focused on high-value outcomes.
What it is
MoSCoW glossaryPrioritisationPrioritisation is the process of ranking tasks, features, or initiatives based on their importance, impact, and effort.Open glossary term is a UX and product method used to categorise glossaryFeatureA feature is a specific piece of functionality within a product that delivers value to users. It represents something users can do or experience as part of the overall product.Open glossary term, tasks, or requirements based on their importance.
It groups work into Must Have, Should Have, Could Have, and Won’t Have (this time).
The method provides a simple, shared glossaryFrameworkA framework is a structured set of tools and conventions used to build applications more efficiently.Open glossary term for glossaryPrioritisationPrioritisation is the process of ranking tasks, features, or initiatives based on their importance, impact, and effort.Open glossary term across teams.
The focus is on glossaryClarityClarity is how easily users can understand what is happening and what they need to do.Open glossary term, glossaryAlignmentAlignment is a shared understanding of goals and priorities across teams and stakeholders, strong enough that people act consistently without checking first. It is not the same thing as everyone agreeing.Open glossary term, and managing glossaryTrade-offsTrade-offs are decisions where improving one thing requires giving up another, such as speed against quality or scope against cost. Every product decision involves them, whether or not they are made explicit.Open glossary term.
Key takeaway
The goal is to make informed decisions about what to build or deliver first.
When to use it
Use this method when you need to prioritise requirements or glossaryFeatureA feature is a specific piece of functionality within a product that delivers value to users. It represents something users can do or experience as part of the overall product.Open glossary term.
It is most useful when:
It is less useful when:
MoSCoW is often used alongside RICE scoring, JTBD, and feature prioritisation workshops.
How to run it
Set up properly
Be clear on the items, who is involved, and what each category actually means for this project. MoSCoW fails when "must" is defined as "important".
Define Must as genuinely non-negotiable: the glossaryReleaseA release is the point at which a product or feature is made available to users. It marks the transition from development to real-world use and often involves deployment, communication, and monitoring.Open glossary term fails without it. Without that discipline everything becomes a Must and the method has done nothing.
Run the method
MoSCoW sorts work into Must, Should, Could and Won't have. It is fast and communicates well, and its entire value depends on the honesty of the first and last categories.
- List the candidate items at a consistent level of detail.
- Categorise each as Must, Should, Could or Won't, requiring a justification for every Must.
- Challenge the Musts hard. A common rule of thumb is that Musts should be well under half the effort, leaving room to flex.
- Discuss disagreements openly and resolve the glossaryTrade-offsTrade-offs are decisions where improving one thing requires giving up another, such as speed against quality or scope against cost. Every product decision involves them, whether or not they are made explicit.Open glossary term rather than promoting items to end the argument.
- Document the decisions and reasoning, particularly the Won't-haves. That category is what makes the method useful.
Protect the Won't list. It is the only part that creates capacity, and it is the first thing to be quietly reopened.
Capture and make sense of it
The value comes from an honest, communicable priority. After the glossarySessionA session is a single period of user interaction with a product, from entry to exit within a defined timeframe.Open glossary term, document:
- Each item's category with the reasoning
- The proportion of effort sitting in Must, as a sanity check
- Won't-haves, explicitly, with why and when they might return
- Disagreements and how they were settled
Review periodically as glossaryContextContext is the set of surrounding conditions that shape how someone behaves and decides, including their goal, their environment, their time pressure, and what happened immediately before. The same action can mean different things in different contexts.Open glossary term changes. MoSCoW is a snapshot, and treating it as permanent is how Shoulds silently become Musts.
Key takeaway
Use this to manage scope and deliver value efficiently.
What to look for
Focus on:
Where it goes wrong
Most issues come from:
If priorities aren’t agreed, scope and glossaryDeliveryDelivery is the process of building, testing, and releasing a product or feature.Open glossary term suffer.
What you get from it
Done properly, this method gives you:
Key takeaway
It helps ensure critical items are delivered first and optional items are managed realistically.
Get in touch
If this sounds like something you need, we can help you apply MoSCoW prioritisation to align your team, manage scope, and deliver what truly matters to users and the business.
No guesswork. No assumptions. Just structured prioritisation that works.
FAQ
Common questions
A few practical answers to the questions that usually come up around this method.
What is MoSCoW prioritisation in UX?
It is a method for categorising features or requirements as Must, Should, Could, or Won’t Have.
When should you use MoSCoW prioritisation?
During roadmap planning, backlog refinement, or release planning.
What can you prioritise?
Features, tasks, requirements, or improvements.
What does MoSCoW give you that a ranked list does not?
It provides clarity, alignment, and scope management for teams and stakeholders.
Does MoSCoW prioritisation improve UX?
Indirectly. By focusing on delivering critical features first, it ensures essential user needs are met.
Quick take
If everything feels urgent, nothing gets done. MoSCoW helps you focus on what must, should, could, and won’t be delivered.
Related Services
Related Guides
