> 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="https://1194756820-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F7GrawCzldiDSsP1yfNLi%2Fuploads%2Fgit-blob-e6c40ca50e65fdaaf14dc1f431b2c241307c54be%2Fmoscow-prioritization-1.png?alt=media" 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

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

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
