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.

19 August 20104 min read

Quick take

If everything feels urgent, nothing gets done. MoSCoW helps you focus on what must, should, could, and won’t be delivered.

What it is

MoSCoW is a UX and product method used to categorise , 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 for across teams.

The focus is on , , and managing .

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 .

It is most useful when:

defining product roadmaps or backlogs
managing scope in projects with limited resources
aligning stakeholders on what is critical versus optional
planning releases or iterations
balancing user needs, business goals, and effort

It is less useful when:

all items are equally critical
prioritisation requires detailed quantitative scoring
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 is collaborative and visual.

List candidate items. Categorise each as Must, Should, Could, or Won’t Have. Discuss disagreements and resolve . Document decisions and rationale. Review periodically as changes.

Focus on and consensus rather than perfect scoring.

Capture and make sense of it.

The value comes from shared and .

After : communicate priorities, plan phases from categories, revisit as assumptions shift, and ensure teams understand .

Key takeaway

Use this to manage scope and deliver value efficiently.

What to look for

Focus on:

Must Have
Critical items that cannot be omitted
Should Have
Important items that add value but can be deferred
Could Have
Nice-to-have items that do not impact critical outcomes
Won’t Have
Items agreed out of scope for this phase
Consensus
Alignment among stakeholders on categories

Where it goes wrong

Most issues come from:

If priorities aren’t agreed, scope and suffer.

unclear criteria for categories
lack of stakeholder alignment
overloading Must-Have category
ignoring changes in scope or context
failing to communicate prioritisation decisions

What you get from it

Done properly, this method gives you:

clear prioritisation of features or tasks
alignment across teams and stakeholders
efficient planning and scope management
focus on delivering maximum value

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 to align your team, manage scope, and deliver what truly matters to users and the business.

No guesswork. No assumptions. Just structured 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 or requirements as Must, Should, Could, or Won’t Have.

When should you use MoSCoW prioritisation?

During planning, , or release planning.

What can you prioritise?

, tasks, requirements, or improvements.

Why is it important?

It provides , , and scope management for teams and .

Does MoSCoW prioritisation improve UX?

Indirectly. By focusing on delivering critical first, it ensures essential user needs are met.

LET'S WORK TOGETHER

Ready to improve your product?

UX, research and product leadership for teams tackling complex digital services. The work usually starts where things have become harder than they need to be: unclear journeys, inconsistent products, competing priorities, or teams trying to move forward without a clear direction. I help simplify the problem, shape the right next step, and turn complexity into something people can actually use.

Previous feedback

Will Parkhouse

Senior Content Designer

01/20