The MoSCoW method sorts tasks into four categories: what must be done, what should be done, what could be done, and what won’t be done now. The real value isn’t the sorting itself, it’s naming the fourth category clearly, which protects your time from everything that merely looks important.
Key Takeaways
- MoSCoW sorts work into must, should, could, and won’t-now, in that order of priority.
- The fourth category, won’t-now, is where the method actually earns its value.
- Naming what won’t happen now is clarity, not failure.
- Clients or stakeholders usually want everything; the real work is helping them see what makes the project succeed versus what’s just an addition.
- When a task list feels too long, the fix is subtraction, not another slot for more items.
Why This Is Harder Than It Looks
In project management work I led for enterprise clients, the first step in any large project was sorting the requirements this exact way, before writing a single line of the work plan. The client usually wanted everything, and the job was helping them separate what would make the project succeed from what was only an addition.
The real benefit of this method isn’t the ranking itself, it’s the fourth category: what won’t be done now. Admitting that something won’t happen now isn’t failure, it’s clarity. Naming what you won’t do now protects your time from leaking toward everything that looks important, which is exactly what Continuity, one of the five elements of The Method, is meant to protect.
The Steps
Step 1: Sort every requirement into one of the four categories before planning anything. Planning around an unsorted list guarantees the loudest request gets the most attention, not the most important one.
Step 2: Push hardest on defining the fourth category, won’t-now, not the first. Everyone agrees quickly on what “must” happen. The disagreement, and the real clarity, lives in what gets set aside.
Step 3: Write down the reason something landed in won’t-now. An unexplained exclusion invites it to quietly creep back into the plan later. A documented reason holds the line.
Step 4: Revisit the four categories at fixed checkpoints, not whenever someone objects. Priorities do shift, but re-sorting on demand turns the method into whoever asks loudest wins again.
A Worked Example
On the projects where this sorting happened honestly and early, the plan that followed stayed stable even when the client’s enthusiasm for extra requests grew mid-project. The fourth category was already written down, and pointing back to it was enough.
Closing
Next time your task list feels too long, don’t ask what to add. Ask what to remove from the list right now and place in a later category.
FAQ
What if a stakeholder disagrees with what lands in “won’t-now”?
Show them the reasoning you documented. A visible reason is easier to negotiate than an unexplained exclusion.
Does this only work for large projects?
No. The same four categories apply to a personal task list; the fourth category is just as valuable there.
How often should the categories be revisited?
At fixed intervals tied to the project’s natural checkpoints, not every time a new request appears.
