Why your to-do list keeps growing — and how WIP limits fix it.

Here's the mechanism, stated plainly: capture is free, and finishing is bounded. Adding a task costs three seconds and no thought. Completing one costs real time, attention, and effort. So intake outruns output, permanently, by design. A to-do list with no limit on how much can be in progress at once isn't a productivity tool — it's a growing pile you occasionally take from.

Think of your list as a queue: work arrives, waits, and eventually gets pulled. Anyone who has managed a queue — a support inbox, a factory line, a kanban board — knows the failure mode. If arrivals outpace completions and nothing caps the middle, the queue grows without bound and everything in it gets slower.

That last part is the cruel twist. It isn't just that the list gets longer. Everything already on it gets older, because your finite attention is now spread across forty open loops instead of three. This is what flow practitioners call work item age, and it's the metric that actually predicts whether things get done — the agile-for-one thesis makes the case that age beats almost every other number you could track.

More tasks in progress does not mean more throughput. It means slower throughput and a nagging sense that nothing ever closes.

The instinct is to process harder — a better morning routine, a stricter triage, inbox zero for tasks. It doesn't hold, because it treats a structural problem as a willpower problem. You can't out-discipline an unbounded intake. The moment your discipline slips for a busy week, the queue catches up on you.

There's also a real cognitive cost to carrying everything at once. Sophie Leroy's research on "attention residue" found that when you switch between tasks without finishing the first, part of your attention stays stuck on it — you show up to the next thing already diminished. A list of forty open items isn't neutral storage. It's forty small residues, taxing every hour you work.

You can't stop tasks from arriving — life generates them. What you can do is cap how many you allow yourself to actively work at once. That cap is a work-in-progress limit, and it's the single most counterintuitive, most effective move in personal productivity.

The idea comes from Kanban and lean manufacturing, and was adapted for individuals by Jim Benson and Tonianne DeMaria Barry in Personal Kanban, whose two rules are the whole game: visualize your work, and limit work-in-progress. A WIP limit says: no more than N things may be in flight at any moment. Everything else waits in the backlog — visible, safe, but explicitly not started.

When you cap WIP:

• Things finish faster, because your attention isn't fragmented across a dozen half-done tasks.
• The list stops feeling infinite, because "active" is a short, honest number instead of a wall.
• Starting a new thing forces a decision — to start, you must finish or consciously drop something. The cap does your triage for you.

That last effect is the point. A WIP limit isn't a container; it's a forcing function. It converts "I'll get to it" into "not now" — a real, made choice.

You don't need new software to try this today:

1. Pick a small number. Two or three active items across everything — not per project, total. It will feel too small. That's the signal it's working.
2. Move the rest to a backlog. Not deleted, not scheduled — just clearly not in progress. The backlog can be huge; that's fine, because it isn't lying to you about what you're doing.
3. Enforce the cap at the moment of starting. Want to start a fourth thing? Something has to leave the active set first — finished, or honestly deferred.
4. Let dead tasks die. If something has sat untouched for weeks, it isn't a task, it's a decision you keep postponing. Cut it. A backlog you never prune is just a slower version of the same problem.

The discomfort you feel capping WIP at three is the productivity system finally telling you the truth about your capacity. Most lists lie by implying you'll do all of it. A WIP limit stops the lie.

Underneath the mechanics is a shift in what a to-do list is for. Most apps are built to help you collect — infinite capture, folders, tags, someday-maybe lists. Collecting feels productive and accomplishes nothing. The alternative is to treat the list like a swordsman treats a fight: a few decisive strikes, no wasted motion, no hoarding a backlog of enemies you'll face "someday." You don't manage more tasks. You have fewer, done.

WIP limits are how you make that real. They're one of five disciplines in the method behind Zoro — alongside sizing by effort instead of time and naming just three things today.