How to Turn a Brain Dump Into an Action Plan

A brain dump becomes an action plan in three steps: sort what came out, because most of it is not a task; give every non-task item a destination; then put numbers on the tasks that remain and keep only what fits tomorrow. Nearly every method stops after the capture and tells you to prioritise, which skips the part where the work actually happens.

Start by accepting what is on the page. If you have just emptied your head onto paper, you are not looking at a task list. You are looking at a mixture of tasks, worries, decisions you have been avoiding, questions for other people, information you filed in the wrong place, and things that are not really yours to do. Sorting that mixture is the job.

What a real dump contains

Take each line and put it in one of six buckets. Do this fast, without fixing anything, because the point of the sort is speed: you are routing, not solving.

Two of those routings are the ones that make the difference.

A decision is not a task

"Whether to renew the lease" cannot be done, so it sits on a list forever looking like work. What it needs is a named moment to be decided, and often what it really needs is to identify the one piece of information that would settle it. Then that becomes a task: "ask the landlord what the new rate would be". The decision is unblocked by a task, and the task is doable in four minutes.

A question is faster to send than to schedule

If an item begins "find out whether" or "check with", send the message now, during the sort. Thirty seconds each, and it moves the item off your plate and onto someone else's, which is where several of them belonged all along.

The worries, honestly

Some of what comes out of a dump is not actionable in any form. "Money is tight." "I am not sure this job is right." "Mum is getting older."

Putting those on a to-do list does two bad things: it makes the list heavier without making anything happen, and it quietly suggests you are failing at a task when you are actually living with a situation.

So separate them, deliberately, onto a different page. Then look at each one and ask whether there is any action, however small, hiding inside it. Sometimes there is: "Money is tight" might contain "cancel the two subscriptions I never use", which is a ten-minute task with a real effect. Sometimes there is not, and the honest answer is that it is a thing to think about or talk to someone about rather than a thing to do.

That distinction is worth making on paper rather than in your head, because an unsorted dump leaves everything at the same weight, and the genuinely heavy items make the light ones feel heavy too.

Why the dump helped at all

It is worth knowing the mechanism, because it tells you which part to be rigorous about.

The relief you feel after writing everything down is real, and it does not come from the writing. It comes from deciding. Peter Gollwitzer and Paschal Sheeran's meta-analysis of implementation intentions, published in Advances in Experimental Social Psychology in 2006, pooled 94 independent tests from 63 reports and found that forming a specific when-and-where plan produced an average effect of d = 0.65 on whether people actually achieved the goal. A large effect, from one sentence.

Which is why the sort above matters more than the dump. A captured item is still an open loop. An item with a destination is not. "Sort out the website" on a page is noise; "Tuesday 10am, list what the five pages need" is a plan, and the difference is not effort, it is specificity.

Then do the arithmetic

Now you have a list of genuine tasks, and this is where most dumps die. The standard advice is to prioritise them, which produces an ordered list that is still far longer than any day.

So put a rough number on each task, in fifteen-minute steps. Add the numbers up. Compare the total against what tomorrow actually holds, which is your working hours minus meetings, minus the email and messages and the gaps between things. For most people with a desk job that is three to four hours of real task time, not eight.

A dump of 60 items typically yields perhaps 20 real tasks, and 20 real tasks will not fit in one day. That is not a failure of the dump. It is the dump doing its job: it has shown you the size of what you were carrying, and the next decision is which part of it happens tomorrow.

A worked example

Say the sort left 14 real tasks and tomorrow holds 210 minutes of task time. Estimated roughly:

That is 495 minutes against 210. Fill tomorrow in order of what cannot wait and stop when the minutes run out rather than when the list runs out: the five-minute landlord question, the two ten-minute items, the domain, the form, the auditor, the review. That comes to 130 minutes, which leaves 80 minutes for the project brief to start rather than finish, and a little slack.

Nine items did not make it. They get a specific later day or go to a backlog you trust, which is the next problem.

Expect the totals to run low. Estimates systematically are, and asking yourself to be pessimistic does not fix it. Plan under your capacity, and leave the slack at the end of the day where you can see it.

Where to put a brain dump once it is sorted

This is the question no brain dump guide answers, and it is the one that decides whether you ever do this again.

If the unscheduled items go back into the same undifferentiated pile, you have rebuilt the problem and you will feel it within a week. An organized task list is not one long list that has been sorted. It is two places: the handful of things happening now, and everything else, kept somewhere you trust but not somewhere you keep reading.

That second place is what people mean when they ask where to put a brain dump. Not hidden, not deleted, but not sharing a screen with the six things you are actually doing today.

The test of whether that place works is whether you are willing to stop thinking about what is in it. If you keep checking, it is not trusted, and you will keep the items in your head as well, which costs you the whole benefit of having written them down.

How to prioritize a brain dump that keeps repeating itself

Here is the most useful signal a dump produces, and I have never seen a brain dump method mention it.

If you dump regularly, some lines appear every single time. The same six items, month after month, never done, never deleted. That repetition is information, and it means one of four things.

The item is a project with no first action, so there is nothing to start. Name the first action and it stops recurring.

Or it depends on somebody else and you have never asked them. Send the message during the sort.

Or you have decided not to do it and have not admitted it. This is the common one. An item that has survived six dumps without being done is usually not a commitment, it is a wish, and the kind thing is to take it off the list.

Or it genuinely matters and keeps losing to urgent work, which is the only case where the answer is scheduling. Give it a real slot on a real day, early, before the day fills.

Running that check takes two minutes and removes more weight than the dump itself.

Doing this with less friction

The sort above is judgement and paper handles it fine. What paper handles badly is the second half: the arithmetic, and keeping the backlog separate from today without losing it.

That is the shape of Todonado. Inbox is one capture place where nothing needs organising to be safe, so a dump can land in seconds. Projects and sections hold the items that are not happening this week without them sharing a view with the ones that are. Tasks carry effort estimates in minutes, and the Today view totals them against the capacity you set, so the comparison happens whether or not you feel like doing it. Week planning spreads the overflow across the next seven days against each day's own capacity.

One thing to be clear about, because it would be easy to imply otherwise: Todonado does not do the sort for you. An organiser that takes a messy dump and proposes the structure, the estimates and the plan for you to approve is a planned feature and is not available today. Nothing in the product currently reads your dump and turns it into projects and tasks. Until it exists, the six-bucket sort above is a manual job, and it is a manual job worth doing.

If the dump was triggered by a list that had already grown past the point of usefulness, organizing a huge to-do list is the better starting point. And once the sort is done, planning a realistic day is the daily version of the arithmetic above.