Guide · 4 min read

MoSCoW Prioritization for Beginners: Decide What to Build First

Your idea has a hundred features. Your weekend has 48 hours. MoSCoW is the little trick that tells you which two features to actually build — and which 98 to ignore (for now).

What MoSCoW actually means

MoSCoW isn't the city. It's four buckets you drop every feature into:

  • M — Must have. Without this, the product literally does not work. Zero. Nada.
  • S — Should have. Important, but the product still kinda works without it. Ship next week.
  • C — Could have. Nice sparkle. Fun. Not urgent. Ship "someday".
  • W — Won't have (this time). A polite way of saying "not now, maybe never." Say it out loud so nobody keeps asking.

A pizza example 🍕

You're opening a pizza place. Here's your MoSCoW:

  • Must: dough, sauce, cheese, an oven.
  • Should: a menu, a phone to take orders.
  • Could: a fancy logo, playlist, cute napkins.
  • Won't (yet): a mobile app, franchise plan, delivery drones.

Notice: none of the "Could" or "Won't" items stop you from selling one pizza tomorrow. That's the whole trick.

How to use it on your MVP

  1. Write every feature idea on a sticky note (or one line in a doc).
  2. Force yourself into the 4 buckets. No "M/S" hybrids. Pick one.
  3. Rule of thumb: Musts should be no more than ~60% of your effort. If everything is a Must, nothing is.
  4. Build only the Musts this week. Don't peek at the other buckets.
  5. Ship. Show real humans. Then revisit the list — the buckets will shuffle.

The most common mistake

Beginners mark 15 things as "Must." That's not prioritization — that's a wishlist with extra steps. If you can't cut your Must list in half, you don't have priorities yet, you have panic. And panic is what the crisis button on the home page is for. 😅