Your list lies by omission.
Not on purpose. It just has nowhere to put the truth.
Take any item on it: "renovation quote". On the list it is one line, weighing exactly as much as "buy batteries". But you already asked for the quote. The builder said he would send it by Friday. Friday came and went. And the item is still sitting there, looking like something you have not even started.
It is not "to do". It is waiting. And your list has no word for that.
Sounds like a detail. It is not.
It is the whole difference between the two tools, and the reason picking the wrong one leaves you feeling that nothing moves, even after a full day of work.
The difference in one sentence
A list is an inventory. One column, two states: done and not done.
A kanban board is a map. Several columns, and the task travels across them.
When every task you have is a single step, the map shows nothing the inventory did not. When your tasks have stages, waits and dependencies, the inventory hides exactly the part that matters.
What each one actually does
The list has a good experiment in its corner.
In a 2011 paper in the Journal of Personality and Social Psychology, E. J. Masicampo and Roy Baumeister showed that an unfinished goal keeps occupying your mind. It produces intrusive thoughts during an unrelated reading task and drags down performance on an anagram test. When participants wrote a specific plan for the goal, those effects disappeared, without the goal having been met.
Now the detail people skip.
What quieted the mind was the plan, not the medium. Writing "deal with renovation" closes nothing; writing when, where and how does. That holds for a line on a list and a card on a board in exactly the same way. On this point, it is a tie.
Personal kanban, as Jim Benson and Tonianne DeMaria Barry described it in 2011, has two rules: make your work visible and limit how much work is in progress at once. The first rule changes the format. The second changes the behaviour.
Without the second, a board is a list with columns.
The maths your list hides
There is an equation from 1961 that explains the feeling that nothing moves.
John Little proved, in Operations Research, that in a stable system the average number of items inside it equals the rate at which they leave multiplied by the average time each one spends there. L = λW. It works for bank queues, assembly lines and, with a little goodwill, your week.
Run it with your own numbers.
You finish, on average, two things a day. You have twelve started. Each one will take, on average, six days from start to finish. With four started, two days.
You did not get faster. You just started less.
How long each task takes depends less on your effort than on how many others are open alongside it.
A list keeps that maths invisible, because it does not separate "started" from "not started". A board shows it: you look at the middle column and count.
What the evidence supports, and what it does not
It supports this: a specific plan eases the mind. It also supports the queueing maths, which is not psychology and does not need replicating: it is an identity between averages.
It does not support this: that personal kanban works better than a list for anyone. There is no controlled study comparing the two in individuals. Even in software teams, where kanban is studied most, the systematic mapping study by Ahmad and colleagues, published in 2018 in the Journal of Systems and Software, gathered 23 primary studies and described the literature as largely descriptive, with little rigorous research.
Plenty of reported benefits. Almost no experiments.
And Little's law has small print: it holds for averages, in a system that is not growing without end. If more comes into your week than goes out, no column fixes that. The board will only show you, more clearly, that the queue is growing.
Which one to use when
| To-do list | Personal kanban | |
|---|---|---|
| Question it answers | What is left to do? | Where is each thing stuck? |
| States it can see | Done and not done | To do, doing, waiting, done |
| Best for | Single-step tasks | Projects with stages and dependencies |
| Typical failure | Hides what is half-done | Becomes decoration without a WIP limit |
| Upkeep | Low | Medium: moving cards, reviewing the column |
The honest limits
Neither one calls you. The list waits to be opened; the board waits to be looked at. And on a packed day, the day it would matter most, you do neither.
Where I ended up
I used lists for years thinking my problem was forgetting. It was not. I remembered almost everything; half of it was just parked, waiting on someone, and my list would not let me see that.
With ASB I wanted the task to carry its state with it ("waiting on the builder's quote until Friday") and, on Friday, for someone to ask me on WhatsApp whether he sent it.