What to do when you have too much to do
The short answer
Before choosing a method, settle one question: is there a version of today where all of this fits?
If yes, this is an ordering problem and the fix is a limit and a sequence. If no, it is a capacity problem, and no ordering rule solves it — putting the right things first still leaves the same number of hours. Those two situations feel identical from the inside and need completely different responses, which is why so much advice about being overwhelmed misses.
Most days that feel impossible are ordering problems. Some genuinely are not, and recognising that is not defeatism.
If it is an ordering problem
The mechanism is the same one that makes a queue slow: too many things open at once. Little's Law says average completion time is proportional to work in progress, so the single highest-value move is reducing what is simultaneously live, not working faster. The arithmetic is here.
In practice, in about ten minutes:
- Write everything down first, in one place. Not to plan — to stop the list running in your head, where it takes up room and is never fully visible. You cannot choose between things you have not seen.
- Pick three for today. Not the three most important in the abstract; the three that most need to be true by this evening. Top 3 is the whole of this and the constraint is the point — three forces a decision, ten does not.
- Put a duration on each. This is where a plan meets reality. Three things at ninety minutes each is four and a half hours, and you will know immediately whether that fits what is left of the day.
- Close the list. The rest stays captured and unchosen. Nothing is lost by not being picked today.
The reason to do this on paper or on a screen rather than in your head is not organisation. It is that a mental list has no capacity check, so it never tells you the arithmetic does not work.
If it is a capacity problem
Sometimes step 3 produces eleven hours of work and five hours of day. That is not a planning failure; it is information.
Overload has a name and a shape. In computing it is called thrashing: when the set of things actively needed exceeds what the system can hold, it spends nearly all its effort swapping between them and useful output collapses. The machine is fully occupied and producing almost nothing. That is a capacity fact and not a statement about the machine's character.
What actually works here is unpleasant and short:
- Say what will not happen, in writing, to whoever is affected. Not "I'll try" — the specific thing, and when it will happen instead. This is the only real lever, and delaying it does not make it smaller.
- Look for the blocked item first. Some of what is stacked up is not waiting on you at all. A significant piece of work held up by a two-minute reply from someone else is the cheapest thing on the list to move, and it is invisible until you look for it specifically.
- Cut scope before cutting quality. Half a thing done properly is usually more useful than all of it done badly, and it is easier to explain.
None of that is a productivity technique. It is the honest response to arithmetic that does not work, and no method substitutes for it.
How to tell them apart
Add up the durations. That is genuinely the whole test.
If your estimates total more than the hours available, you have a capacity problem today regardless of how you order things. If they fit but the day still feels impossible, the problem is that nothing has been decided — everything is live at once, so everything is competing, and the cost of that switching is being paid all day without appearing anywhere.
The estimates do not need to be accurate for this test to work. They need to exist. An unestimated list will always feel like it might fit.
What not to do
Do not start with the easiest thing to get momentum. It is tempting and it usually costs the day. Small things are small; clearing six of them can feel productive while the thing that mattered has not moved.
Do not reorganise the list. Reorganising feels like progress and is not. If the list is already visible, further sorting is just more time in the planning surface rather than in the work.
Do not add a new system today. A day that is already over capacity is the worst possible day to learn a method. Use the simplest thing that produces a decision, and evaluate systems on an ordinary day.
Where to go next
- The Top 3 method — the limit, in full
- Little's Law, applied to a working day — why a smaller number finishes sooner
- How to prioritise your tasks — the three conditions and which method fits each
Using this in Decide One
Decide One asks for a duration on every line you choose, which is what turns a plan into a check. Three things and their times either fit the day or visibly do not, and you find that out at the start rather than at six o'clock.
A line you did not finish is unfinished. It is not marked against you, and a day you did not open is not counted.
Open Decide One — free to use, with no account. Nothing you write leaves your device.
Decide One is a priority instrument. Bring the day into view, choose a method, give the first thing real time.