1.2MoSCoW method & Pareto law (80/20)
The essentials in 30 seconds
- MoSCoW decides: Must (essential), Should (important), Could (desirable), Won't (not this time) — not everything can be “Must”.
- Pareto 80/20: about 20% of efforts produce 80% of outcomes — identifying these high-impact tasks multiplies productivity.
- Focus, don't scatter: owning the “Won'ts” frees energy for the Musts and the decisive 20%.
Running case — Anis and his impossible list
Anis has 23 “urgent” tasks on his list: follow-ups, quotes, reporting, filing, social networks. Everything seems “to do”. With MoSCoW, he forces the sort: 4 Musts (hot-client quotes, high-potential follow-ups), the rest in Should, Could and owned Won'ts. Then he applies Pareto: 3 decisive visits will make 80% of his revenue — he handles them first.
Following on from case 1.1 — Anis moves from urgency/importance sorting to vital/comfort sorting.
1. MoSCoW: decide
The MoSCoW method ranks tasks in four categories: Must (essential, without which the goal fails), Should (important), Could (desirable), Won't (not this time, explicit giving-up).
Ideal to decide when everything seems “to do”: it forces telling vital apart from comfort. Anis sorts his 23 tasks into it and discovers half are Coulds disguised as Musts.
2. Pareto: 80/20
The Pareto law (80/20) recalls that 20% of our efforts produce 80% of outcomes. Identifying these 20% high-impact tasks — and devoting energy to them first — multiplies productivity.
Together, MoSCoW and Pareto push to focus forces rather than scatter them: prefer impact (one decisive visit) over volume (ten reassuring but sterile ticks).
🔎 Concrete example — 🔎 Concrete example — Owning the “Won'ts”
Saying no frees energy.
On a list where everything seems important: rank Must / Should / Could / Won't.
Owning “Won'ts” (not now) frees energy for essentials.
→ prefer impact (20%) over volume (doing a lot).Outcome: forces focused where they count.
Reflex: beware easy, numerous tasks with no real outcome.
Section vocabulary
- MoSCoW method
- Prioritisation into 4 categories: Must (essential), Should (important), Could (desirable), Won't (not now).
Simple example: Anis ranks his hot quotes as Must and filing as Could.
What it is not: ranking all tasks as Must to “miss nothing”.
Reflex: force hierarchy: a true Must is rare.
- Pareto law (80/20)
- The principle that ~20% of causes produce ~80% of effects: few tasks make most outcomes.
Simple example: 3 of Anis's visits will make most of his month's revenue.
What it is not: believing each task contributes equally to the outcome.
Reflex: seek the 20% before handling the rest.
- High-impact task
- A task among the 20% generating most value: to handle first.
Simple example: Anis's follow-up with a big client about to sign.
What it is not: an easy, numerous task reassuring without producing.
Reflex: if I did only one task, which would count?
- Must / Won't
- Must: without which the goal fails. Won't: what you explicitly give up doing (for now).
Simple example: Anis's Must: send 4 hot quotes; Won't: redoing email templates this week.
What it is not: a shameful hidden Won't cluttering the list.
Reflex: write your Won'ts down in black and white to free your mind.
- Focusing efforts
- Channelling energy on the vital rather than scattering it on accessories.
Simple example: Anis blocks his morning on decisive visits, inbox closed.
What it is not: fluttering between ten easy tasks to “move forward”.
Reflex: impact first, volume after.
In practice — In practice — Prioritising with MoSCoW and spotting your 20%
- Take a task list or project and rank each item Must / Should / Could / Won't.
- Own the “Won'ts”: saying no now to some things frees energy for essentials.
- Apply Pareto: among your tasks, which (the 20%) will produce most outcomes?
- Reorganise your time to address Musts and high-impact 20% first.
Ready-to-say script — negotiating your Musts with your manager (30 s)
“Here are my week's Musts: these 4 quotes and 3 visits making most of the outcome. The rest goes to Should or Won't this week. Do you validate, or must a Should rise to Must?”
To say in the weekly check-in: making the sort visible forces shared arbitration instead of silent piling.
Copy-paste template — MoSCoW + Pareto sort
MUST (essential, without which I fail): _______________
SHOULD (important): _______________
COULD (desirable): _______________
WON'T (not this time, owned): _______________
MY 20% HIGH-IMPACT (to handle first): _______________Field sales rep
Anis notes each client's potential alongside: big potentials close to signing rise to Must, the rest drops.
Solo VSE
With no team to delegate to, the Won't is vital: one deleted Could task equals one hour gained, nobody to convince.
SME Algiers
Weeks chopped by travel: Musts grouped on 2 protected days, Shoulds and Coulds on fragmented slots.
Team project
Sort together: each defends their Musts, the group keeps only 3–5 — the rest becomes explicit Should, Could or Won't.
✓ Best practices
- Force hierarchy: not everything can be “Must”.
- Own “Won'ts” to free energy.
- Prefer impact (20%) over task volume.
✗ Common pitfalls
- Ranking everything “Must” (prioritisation loses meaning).
- Drowning in easy, numerous tasks with no impact.
- Confusing “feeling progress” with “producing outcomes”.
Key takeaways
- MoSCoW: Must, Should, Could, Won't — to decide when everything seems to do.
- Pareto: ~20% of efforts produce ~80% of outcomes.
- Identifying and prioritising the 20% high-impact multiplies productivity.
- Focus forces rather than scattering them.
48h Challenge — apply tomorrow
Rank your current list as Must / Should / Could / Won't, circle your 20% high-impact and handle them first tomorrow morning. Note what the Won'ts freed for you.
- I can cite the 4 MoSCoW categories without hesitating.
- I can state the Pareto law in one sentence.
- I have ranked my list and handled my 20% first.
Frequently asked questions
MoSCoW and Eisenhower matrix, must I choose?
No, they complement each other. The Eisenhower matrix sorts by urgency and importance; MoSCoW ranks necessity degree (essential → desirable), very useful on a project or list where everything seems important. Use one or the other by context, or combine them. What matters is forcing a hierarchy rather than handling everything equally. Two tools beat none; the true risk is prioritising with neither.
How do I concretely identify my 20% high-impact?
Ask: which tasks, if accomplished, would most advance my goals? Often, they're the most important and least urgent (thus neglected). Conversely, beware easy, numerous tasks giving the impression of progress without real outcomes. Pareto invites preferring impact over volume. A single decisive task accomplished is often worth more than ten small reassuring but sterile ticks.
Anis's list overflows: 23 “to do” tasks. What must he do first with MoSCoW and Pareto?