How many tasks should a day hold?

Updated 2026-09-12

The short answer

Fewer than you are currently writing down, and a fixed number rather than whatever fits on the page. Three is a good working figure for things that genuinely require your attention.

But the number is a practical choice, not a discovery. What is established is the direction: fewer things in flight means each one finishes sooner. Nobody has established the number, and this page is not going to pretend otherwise.

What is actually established

Little's Law, published by John Little in 1961, describes any stable queueing system:

L = λW — the average number of items in the system equals the arrival rate multiplied by the average time each spends there.

Rearranged, average completion time is proportional to work in progress. Halve the number of things in flight and you halve how long each takes to come out. This is the reasoning behind work-in-progress limits on Kanban boards, and a work-in-progress limit is simply this idea applied to a team.

It is arithmetic. It does not depend on motivation, personality or how good you are at focusing.

What is not established, stated plainly

Little's Law is a theorem about queueing systems. It is not a finding about human cognition, and it names no number.

This matters because the internet is full of pages that cite it — or cite nothing at all — and then announce that three is the number the brain can handle. That claim is not in Little's Law, it is not in the queueing literature, and this site will not make it.

What the result licenses is precise and still useful: limiting concurrent work reduces time to completion. Everything past that is a practical judgement, and should be described as one.

So where does three come from?

Judgement and long practice, which is a perfectly respectable answer when it is given honestly.

Three is small enough that choosing it forces a real decision — you cannot fit the day's whole list into three, so something has to be left out on purpose. And it is large enough that a day still has shape rather than being a single block that either succeeds or fails.

The 1918 Ivy Lee routine used six, for a full working day worked strictly in order. Kanban boards in practice cap somewhere between one and about three per person. None of these are derived numbers.

How to find your own

Do not pick it in advance. Measure it.

1. For two weeks, write what you planned and what you actually finished. Nothing else. No scoring.
2. Take the median number finished, not the average — one unusual day should not set the figure.
3. Use that as your limit. If you finish three most days, three is your number, whatever a productivity site says.
4. Recheck it after a month of different work. A quarter of long project work and a quarter of short reactive work have different numbers, and neither is better.

This is more useful than any recommendation, including this page's, because it is a measurement of you rather than a claim about people in general.

Count the right things

Most lists mix two different objects and then despair at the total. Only one of them belongs in the limit.

Things that require your attention — the piece of work that needs an uninterrupted stretch and real thought. These are what the limit is for.

Things that merely require your hands — a form to submit, a reply to send, a booking to make. These do not compete for the same resource, and counting them against the limit produces a number that is meaninglessly large.

Keep the second kind on the full list and clear them in a batch. They are not what a limit is protecting.

If even three does not fit

Then the honest reading is that the work does not fit the time, and no ordering makes it fit. Prioritising does not create hours. It decides what gets the hours there are.

That is a capacity fact rather than a personal one. The corresponding failure in a computing system has a name — thrashing, where the working set exceeds available memory and the system spends all its time swapping rather than working — and no scheduler fixes it. The fix is always less work in the system, never a cleverer ordering of the same amount.

Where to go next

• The Top 3 method — the limit as a working method, and how to choose the three
• How to prioritise your tasks — if the number is not really your problem

Using this in Decide One

Decide One holds the limit rather than suggesting it: three lines will not become four. It also records what you planned against what happened, which is what makes the two-week measurement above something you can actually read afterwards.

It never scores the result, and an unfinished line is unfinished rather than failed.

Open Decide One — free to use, with no account. Nothing you write leaves your device.