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.
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
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 the shared understanding and agreement between teams, stakeholders, and objectives.Open glossary term, and managing glossaryTrade-offsTrade-offs are decisions where improving one aspect requires compromising another.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.
Before you start, be clear on the items to prioritise, who is involved, and what criteria define each category.
Prepare a workshop or board for collaborative sorting.
Run the method.
MoSCoW glossaryPrioritisationPrioritisation is the process of ranking tasks, features, or initiatives based on their importance, impact, and effort.Open glossary term is collaborative and visual.
List candidate items. Categorise each as Must, Should, Could, or Won’t Have. Discuss disagreements and resolve glossaryTrade-offsTrade-offs are decisions where improving one aspect requires compromising another.Open glossary term. Document decisions and rationale. Review periodically as glossaryContextThe surrounding conditions that shape behaviour and decisions.Open glossary term changes.
Focus on glossaryAlignmentAlignment is the shared understanding and agreement between teams, stakeholders, and objectives.Open glossary term and consensus rather than perfect scoring.
Capture and make sense of it.
The value comes from shared glossaryClarityClarity is how easily users can understand what is happening and what they need to do.Open glossary term and glossaryPrioritisationPrioritisation is the process of ranking tasks, features, or initiatives based on their importance, impact, and effort.Open glossary term.
After glossaryCategorisationCategorisation is the process of grouping content or items based on shared characteristics or meaning. It helps users understand relationships and find relevant information more easily.Open glossary term: communicate priorities, plan glossaryDeliveryDelivery is the process of building, testing, and releasing a product or feature.Open glossary term phases from categories, revisit as assumptions shift, and ensure teams understand glossaryTrade-offsTrade-offs are decisions where improving one aspect requires compromising another.Open glossary term.
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 glossaryPrioritisationPrioritisation is the process of ranking tasks, features, or initiatives based on their importance, impact, and effort.Open glossary term to align your team, manage scope, and deliver what truly matters to users and the business.
No guesswork. No assumptions. Just structured glossaryPrioritisationPrioritisation is the process of ranking tasks, features, or initiatives based on their importance, impact, and effort.Open glossary term 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 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 or requirements as Must, Should, Could, or Won’t Have.
When should you use MoSCoW prioritisation?
During glossaryRoadmapA roadmap is a strategic plan that outlines the direction, priorities, and timeline for a product or initiative. It communicates what will be delivered and why, rather than just listing features.Open glossary term planning, glossaryBacklogThe backlog is a prioritised list of work that needs to be delivered, including features, fixes, and improvements.Open glossary term glossaryRefinementRefinement is the process of preparing and clarifying backlog items before development.Open glossary term, or release planning.
What can you prioritise?
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, requirements, or improvements.
Why is it important?
It provides glossaryClarityClarity is how easily users can understand what is happening and what they need to do.Open glossary term, glossaryAlignmentAlignment is the shared understanding and agreement between teams, stakeholders, and objectives.Open glossary term, and scope management for teams and glossaryStakeholderA stakeholder is any individual or group with an interest in a product, project, or outcome, including internal teams and external parties.Open glossary term.
Does MoSCoW prioritisation improve UX?
Indirectly. By focusing on delivering critical 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 first, it ensures essential user needs are met.