> For the complete documentation index, see [llms.txt](https://www.designreference.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.designreference.xyz/cognitive-tools/universal/prioritisation/moscow.md).

# MoSCoW Method

<figure><img src="/files/ElmNrlA666X7SYXql2NR" alt=""><figcaption><p>Image by <a href="https://metroretro.io/templates/product-boards/moscow-prioritization">Metro Retro</a></p></figcaption></figure>

When determining design priorities, the MoSCoW method (Must Have, Should Have, Could Have, Won't Have) is particularly useful. This method enables design managers to categorise design features based on their importance to the product and business objectives.

For example, a 'Must Have' might be an essential feature that ensures the product meets market standards, while a 'Could Have' might be a feature that enhances the user experience but isn't critical to the product’s core function.

This structured prioritisation helps the design team focus on delivering value in line with strategic goals, especially when managing limited resources.

#### Further Viewing

{% embed url="<https://www.youtube.com/watch?v=pm4GbSRMElc>" %}

#### Further Reading

{% embed url="<https://www.productplan.com/glossary/moscow-prioritization/>" %}

{% embed url="<https://medium.com/the-good-boss/the-moscow-method-how-to-make-tough-choices-without-the-guilt-f901890d3819>" %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://www.designreference.xyz/cognitive-tools/universal/prioritisation/moscow.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.