# MoSCoW

<figure><img src="https://3653531953-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaUGavCwJG3yTK1JeiOyH%2Fuploads%2FcCPk3cQkBY9w30nZU6cu%2Fmoscow-prioritization-1.png?alt=media&#x26;token=27b1d284-3a95-4fe4-b848-a7d80751303f" 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.&#x20;

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.&#x20;

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>" %}
