// description
A prioritisation method that sorts requirements or tasks into four categories: Must Have (non-negotiable for the project to be viable), Should Have (important but not essential for launch), Could Have (nice-to-have if time/resources allow), Won't Have (explicitly out of scope this time).
// history
Dai Clegg developed MoSCoW in 1994 while working at Oracle UK, as part of the DSDM (Dynamic Systems Development Method) agile framework. The name is a mnemonic from the first letters of the four categories (with Os added for pronunciation). MoSCoW became widely adopted in software development, project management, and product design as a practical tool for managing scope creep and keeping teams focused on what actually matters for a given release.
// example
Launching a new coloring book series: Must Have (12 complete illustrations, properly formatted PDF, KDP-ready cover). Should Have (a preview flipbook for the sales page, an email announcement). Could Have (a bonus colouring tutorial video, a companion journal). Won't Have (a physical version this launch, a bundle discount — those are for next quarter). The Won't Have list prevents you from delaying launch by trying to do everything.
// katharyne's take
MoSCoW has saved more of my launches than I can count. The "Won't Have" category is the most important one — it's where you officially park the things you're tempted to add but that would delay you. Writing them down (rather than quietly hoping you'll get to them) both scratches the itch and makes the decision explicit. Most launch delays are scope creep in disguise. MoSCoW is the antidote.
// creative uses
- Apply MoSCoW to your KDP interior files: Must Have (complete page count, correct trim size, bleed set up, no typos in front matter). Should Have (a cohesive interior pattern theme, page numbers). Could Have (a bonus activity page). Won't Have (full-colour interior this edition — that's a premium version for later). It gets the book out rather than endlessly refined.
- Use MoSCoW for your Etsy shop build-out: Must Have (10 listings, all with mockups and keyword-researched titles). Should Have (shop banner, About section, shop policies). Could Have (a video listing preview). Won't Have (a full brand photoshoot this quarter). Launch with the Must Haves and iterate.
- Apply it to course content planning: treat your first cohort as a Must Have / Should Have release only. Run it, get feedback, then add Could Haves to version 2. Shipping a 70% course is infinitely better than never shipping a 100% one.
// quick actions
- Take whatever project you're currently procrastinating on and write out every task you think it requires. Then label each one M, S, C, or W. If you have more than 5 Must Haves, you're probably inflating that category — push things down into Should or Could. Launch on your Must Haves only.
- Create a "Won't Have This Quarter" list in Notion or a plain text file. Every time an idea or addition tempts you mid-project, put it there instead of adding it to the current scope. This is where good ideas go to wait, not die.
- Before your next product listing or launch goes live, run a 5-minute MoSCoW check: what absolutely must be done before you hit publish? Do only those things. Publish. Everything else is iteration.
// prompt ideas
Apply MoSCoW prioritization to my upcoming launch. I'm releasing [describe your product — e.g. "a KDP coloring book series" or "an Etsy printable bundle"]. Here's everything I think I need to do before launch: [paste your task list]. Sort these into Must Have, Should Have, Could Have, and Won't Have. Be ruthless with Must Have — if the product can ship without it, it's not a must. Give me a clear launch checklist for the Must Haves only.
I keep delaying [project name] because I keep adding to it. Here's what I originally planned: [describe the original scope]. Here's what I've added since then: [list additions]. Help me apply MoSCoW to separate the launch-critical items from scope creep. Then write me a "Won't Have This Launch" list I can paste somewhere visible as a commitment to ship what I have.
Help me plan a minimum viable version of [your course / digital product / service offering]. My full vision is: [describe everything you want it to include]. Use MoSCoW to cut this down to a first cohort or first version that I could actually ship in [timeframe]. What's genuinely non-negotiable for buyers to get value, and what can be added in version 2 after I've tested the core with real customers?