A practical guide to MoSCoW, value vs effort, WSJF and Eisenhower, with a decision table and how to apply it in Syncro.
Prioritizing is not ordering a list: it is deciding what you are not going to do. When everything is urgent, nothing is, and the backlog becomes a queue of guilt. These four techniques solve the same problem from different angles; what matters is choosing one, applying it with judgement and revisiting it every cycle.
| Technique | When it fits | What you need | What it produces |
|---|---|---|---|
| MoSCoW | A release with a bounded scope and a near date | A list of tasks and a conversation with the business | Must / Should / Could / Won't |
| Value vs effort | Many loose ideas and little time to analyse them | A quick value score (1-5) and effort score (1-5) | An order by expected return |
| WSJF | Several teams or dependencies and repeated decisions | Delay impact, job duration and risk | A comparable score |
| Eisenhower | Personal urgencies, support and day-to-day tasks | Two questions: urgent? important? | Four action buckets |
None is better in the abstract. MoSCoW closes a scope; value vs effort unblocks a long list; WSJF compares initiatives; Eisenhower separates urgent from important.
MoSCoW splits tasks into four categories:
| Category | Meaning | In Syncro |
|---|---|---|
| Must have | Without it the release makes no sense | Urgent priority |
| Should have | Very important, but there is a temporary workaround | High priority |
| Could have | Desirable if there is time left | Medium priority |
| Won't have | Explicitly out of this cycle | Backlog, no date |
The rule that keeps MoSCoW from degrading is a limit: if more than 60% of tasks are Must, you are not prioritizing, you are justifying. A common split is 60% Must, 20% Should and 20% Could. Won't is not a dumping ground: it is the list that protects the team from a scope that does not fit.
Example. A two-week release for a booking site:
If the team finishes early, a Could goes in. If it is tight, cut a Should before touching a Must. That is the real value of MoSCoW: having decided in advance what gets sacrificed.
Common mistake: treating Won't as "not now" with no date or owner. If an idea comes back every week, it needs an explicit decision: it becomes a backlog task with a review date or it is dropped. What cannot happen is it reappearing in every meeting without context.
When there are twenty ideas and none has been analysed, you do not need precision: you need a first sieve. Score each task from 1 to 5 on two axes:
| Low effort | High effort | |
|---|---|---|
| High value | Do it first | Split and plan |
| Low value | Fill gaps | Drop or park |
The high value, low effort zone delivers visible results with less work. High value, high effort is not dropped: it is broken into smaller deliveries. Low value, high effort is the classic trap; it is usually work that "has to be done" but moves nothing.
How to score without getting stuck. Do it in one session, with the team present, without chasing perfect data. If a task sparks debate, split it until the debate disappears. A five-minute estimate is usually enough to order; you do not need a business case for every idea.
Limit of the technique: value is not always comparable across tasks. "Fix the login" and "add filters to the report" may score the same and not have the same urgency. That is why value vs effort works best as a first pass, not as a final decision.
WSJF (Weighted Shortest Job First) prioritizes by delay impact divided by duration. The idea is simple: if two initiatives deliver the same value, do the one that finishes first. If one delivers much more, it may be worth waiting.
The full formula is:
WSJF = (business value + time impact + risk reduction) / job duration
To keep it practical, score each block from 1 to 5 or use a Fibonacci scale (1, 2, 3, 5, 8, 13). The result is not a mathematical truth: it is a way to make intuitions explicit and compare alternatives with the same criteria.
Example. Two initiatives compete for the same team:
| Initiative | Value | Time impact | Risk | Duration | WSJF |
|---|---|---|---|---|---|
| Export reports | 5 | 3 | 1 | 3 | 3.0 |
| Metrics dashboard | 3 | 2 | 2 | 8 | 0.9 |
The first wins not because it is more ambitious, but because it delivers part of the value sooner. The metrics dashboard can stay in the backlog without guilt.
When not to use WSJF: in small teams with a single line of work, the formula adds ceremony without improving the decision. If the same team does everything and dependencies are few, value vs effort is usually enough.
The Eisenhower matrix separates two dimensions that are confused all the time:
| Important | Not important | |
|---|---|---|
| Urgent | Do it now | Delegate or automate |
| Not urgent | Schedule it | Eliminate it |
Urgent has a date and pressure; important moves the goal. The mistake is letting the urgent fill the day so the important never gets a slot. In a project, priority review, documentation and flow improvement are usually important and not urgent: if they are not scheduled, they do not happen.
Example. A production alert is urgent and important: handle it. A customer request with no date may be important but not urgent: schedule it. A meeting that decides nothing may be urgent for the person calling it and not important for the project: delegate or cancel it.
Eisenhower does not replace MoSCoW or WSJF; it is for the day to day. If you apply it to the whole roadmap, you will end up reacting instead of deciding.
| Situation | Recommended technique |
|---|---|
| Close the scope of a release | MoSCoW |
| Sieve a long list of ideas without data | Value vs effort |
| Compare initiatives with dependencies | WSJF |
| Order today's or this week's work | Eisenhower |
A sequence that works: Eisenhower for the day to day, value vs effort for the backlog, MoSCoW for the release and WSJF when competing for a shared team. You do not need all four at once.
Syncro does not decide for you, but it does keep decisions in the same place where work happens:
Weekly planning and time tracking close the loop: you decide, execute and check whether the decision matched reality.
Prioritization degrades when it happens once a quarter. Book 20 fixed minutes:
The goal is not a perfect backlog. It is that the team knows what to do on Monday without re-discussing the list.
Does MoSCoW work for a two-person team? Yes, even more so: it forces you to write down what is out. With small teams, Won't is the most valuable part of the exercise.
How many tasks should the backlog hold? There is no magic number. If the backlog takes more than five minutes to read, it is too full. Prune before adding.
What if the business wants everything for yesterday? Translate the request into capacity: how many hours there are and what falls out if everything goes in. The conversation stops being about priorities and becomes about scope, which is where a real decision can happen.
Does Syncro's priority field replace the technique? No. The priority field is how you communicate the decision; the technique is how you reach it. First you decide, then you label.
Takeaway: a priority without an explicit trade-off is just an intention. If you cannot say what is out, you have not prioritized yet.
Start today
Try the practice on a real project, with nothing to set up.
No credit card · ready in minutes