What to Do With an Unmanageable To-Do List

Close the list. Not item by item, and not after an evening of careful sorting, but all at once: move everything into an archive you can retrieve later, then write down three things you would do tomorrow if the old list had never existed. That is the entire repair, and the reason it works is the same reason it feels reckless.

The instinct runs the other way. Faced with two hundred accumulated items, most people plan an afternoon of sorting, and the plan is defensible until it meets the arithmetic. Judging two hundred items one at a time is several hours of demanding work, performed with exactly the attention the list has already worn down. It also tends not to work when it is finished, because each item gets weighed against nothing in particular, and on its own almost everything looks worth keeping. You end up holding the same list in a tidier order.

Declaring bankruptcy on a list borrows a word from elsewhere, and the borrowing holds in one respect only: the obligations are acknowledged rather than settled, and the ledger begins again. Nothing is destroyed. What ends is the pretense that a document you no longer open is managing your work.

Why a list stops being usable

A list does two jobs, and only one of them stays cheap as it grows. Capture costs seconds. Writing an item down takes almost no thought and quiets the worry that something will be forgotten. Deciding is the expensive half: working out what an item requires, what it is worth, whether it should happen at all. When capture runs faster than deciding, and it usually does, the gap between the two becomes the list.

The cost of that gap is paid on every reading. Twelve items can be taken in at a glance. Two hundred require a scan, and the scan happens several times a day, each time asking you to pass over the same stale entries to reach the few that matter. A small tax, collected often, and it falls heaviest late in the day, when judgment is lowest and the list demands most of it.

The contents themselves also spoil. Items whose context has evaporated sit beside items that were never tasks at all, but decisions wearing a task’s clothing: work out whether to keep the arrangement, think about the second project. A decision cannot be done in twenty minutes the way a task can, so it is skipped on every pass, and it teaches you to skip.

And then the part that finishes the list off. Once a document mostly records what you failed to get to, it becomes unpleasant to open, and people quietly stop opening unpleasant documents. The work keeps arriving, so it arrives another way, through interruption and whoever asks most recently. The list still holds the promises. It no longer has any part in keeping them.

A list long past the point of being read has stopped being an instrument for working. It has become a full accounting of everything you agreed to and a schedule for none of it.

Closing the old list without losing anything

The move is deliberately crude, and the crudeness is what makes it survivable. Copy the whole list into one place, label it plainly as closed, and set it aside. One action, a few minutes, no judgment applied to any individual line.

Do not read while you move it. Reading is sorting in disguise, and sorting is what has already failed. The moment you begin evaluating entries you are back in the afternoon that never ends.

Two exceptions are worth handling first, and only two. Anything with a genuine deadline and another person waiting on it goes onto your calendar rather than into the archive, because a date is not a task and a list was always the wrong home for it. And anything you explicitly promised somebody that will now not happen deserves a short message saying so, which is uncomfortable to send and considerably less uncomfortable than the silence that would otherwise stand in for it. That category is usually smaller than the dread suggests.

Deleting is the wrong instinct, even though it looks bolder. The fear of losing something important is precisely what makes people sort item by item instead of closing the list, so removing that fear is the mechanism here. Keep everything, keep it retrievable, and the closing becomes an easy act rather than a brave one.

Rebuilding from three items

Now write three items, and write them from memory with the archive shut.

The recall is doing real work. What surfaces without prompting is what carries actual consequences, and the several dozen entries that fail to surface have told you something honest about their weight. The filter is imperfect and does not have to be better, because the archive is sitting right there for anything urgent that slipped your mind.

Three is a modest number and not an arbitrary one. Once meetings, correspondence, and the ordinary administrative residue come out of a working day, what remains is rarely enough for more than two or three real pieces of work, which is the same arithmetic behind planning a week you can actually keep. A list of three is a claim about the day, not about your ambition.

Size each one so it names a concrete step you could finish in a single sitting. Website is not an item. Draft the two paragraphs for the site’s opening page is an item, because you can picture beginning it and you would know when it was done. Vague entries survive indefinitely for this reason: nothing about them ever changes, so nothing forces a decision.

Then adopt the rule that makes the arrangement hold. A fourth item may be added only when one of the three leaves. The ceiling is the mechanism, and a ceiling is what the old list never had. Without one, adding is free while your attention pays the bill, which is how two hundred items accumulated without any single addition looking unreasonable.

If three sounds absurd against the forty open threads your job contains, notice what the three are for. They are a working surface, not an inventory of your responsibilities. The other thirty-seven still exist, held in the archive, on the calendar, or in the heads of the people who care about them. They do not have to be visible to remain real.

What the archive is actually for

Give the archive one short reread a week, at a fixed time, and treat it as a supply rather than a backlog. Bring back one item, occasionally two, when a slot opens.

What becomes clear after a few rereads is worth sitting with. Most items die quietly and nothing happens as a result. No one asks. Nothing breaks. Which suggests that much of what the old list carried had never been work you were going to do, but work you felt you should have wanted to do.

The entries also sort naturally into a few kinds. Some are decisions, and the right response is to make the decision or put ten minutes on the calendar for making it. Some need a conversation before they can become work, in which case the conversation is the item. Some were never yours and can be handed back, more calmly than would have been possible at the time. And some are good ideas whose moment has not arrived, which belong on a separate page you look at rarely and without guilt.

If several rereads supply nothing at all, that is a result rather than a failure. Let the archive go dormant. Its job was to make closing the list safe, and it has done that.

The door the new list comes in through

Bankruptcy is a repair rather than a practice. If you find yourself needing it repeatedly, the problem has moved upstream to intake, and no rebuilding will fix a door that does not close.

The useful question at that door is what would happen if this were never done. A surprising share of arriving items answer, honestly, nothing much, and the correct response is not to write them down at all. Writing something down commits a piece of future attention, and a list that accepts everything is not a list so much as a transcript.

For what does earn a place, write the next concrete step rather than the topic, and send anything with a date to the calendar where dates live. Keep the working three separate from everything else, because the moment the archive and the active list share a page, they will merge again within a fortnight.

The larger source of swelling sits outside any list, in the ordinary difficulty of declining things. Most overloaded lists were assembled one reasonable agreement at a time, which is why declining well and early does more for a list’s size than any reorganizing. A list can only record the promises you have made. It has no power to make fewer of them.

This will not squeeze more work out of the same day, and it would be dishonest to suggest otherwise. What it gives you is a surface small enough to act from. Three visible items get done because they can be seen and because finishing one visibly opens a space. Two hundred get read, and reread, and eventually avoided. The difference is not effort. It is whether the document in front of you describes your obligations or tells you what to do next.

One small step: Copy your entire current list into a new file, name it something like “closed list,” and shut it. Then, without opening it again, write down the three things you would do tomorrow if that list had never existed.