What to do with the list once it is out of your head
The instruction is always the same. Set a timer, write down everything in your head, do not filter, do not organise, just get it out. That part works. It is genuinely easier than it sounds, it takes a few minutes, and the relief at the end of it is real.
Then every version of the advice says the same four words: group and prioritise. That is where it stops, and that is the half the whole thing turns on. You are now holding a page with thirty things on it, all of them true, none of them started, and the page is doing to you exactly what your head was doing twenty minutes ago.
So this is about the second half. Why sorting by priority is the wrong first move, what to sort by instead, the one rule that stops the page becoming a new source of stuck, and what to do with everything you do not pick. The dump itself gets one section, because you already know how to do it.
The dump, briefly, because this part is not the problem
Write for a fixed short stretch, somewhere you will not be tempted to tidy. Paper or a plain note, not an app with fields. Everything goes down: tasks, half tasks, worries, the thing you keep meaning to ask someone, the appointment you have not booked. No categories, no order, no judgement about whether an item deserves to be there.
The mechanism is not mysterious and it is not about clearing your mind. Anything unfinished that you are holding is being held somewhere with very little room, and it has to be rehearsed to stay there. Writing it down ends the rehearsal. The working memory page here goes through what is usually being carried and which part to record first, and the answer surprises people: it is rarely the task list, it is the state, meaning what you already did.
The relief at the end of a dump comes from that and nothing else. It is not progress on any of the items. This matters because the relief is easy to mistake for having dealt with the list, which is one of the two ways a brain dump quietly fails.
Priority is the wrong first sort
Grouping and prioritising is the standard next step and it fails for a specific reason. Priority is a comparison, and a comparison across thirty items is the single most expensive operation you can ask of a tired brain. You have just emptied your head onto a page and the first thing the advice asks you to do is hold all of it at once and rank it.
What happens in practice is that you get a few items in, lose the thread, start again from the top, and after a while the honest outcome is a page with some stars on it and no work done. The ranking also changes the next time you look, which tells you the exercise was not measuring anything stable.
There is a second problem and it is worse. The highest priority item on a dump is almost always the largest one, because importance and size travel together. So a priority sort hands you, as its very first recommendation, the one item you are least able to begin. The page on task paralysis here describes what then happens, and the Eisenhower matrix page makes the same argument about the grid version: sorting is not starting, and a good sort can leave you further from a first move than no sort at all.
Sort by first physical action instead
Go down the list once and ask one question of each item. What is the first thing somebody could watch me do. Not what the item is about, not how long it will take, not whether it matters. The first observable physical action.
Some items answer immediately. Book the dentist has an obvious first move: find the number. Some items cannot answer at all, and that is the useful result, because an item with no first action is not a task yet. It is a project, a decision, or a worry wearing a task costume, and discovering which of the three it is takes seconds once you have asked the question.
This sort has two properties that a priority sort does not. It is item by item, so it never asks you to hold the whole list, which means you can stop halfway and what you did is still good. And it produces something you can act on directly, because the output is a verb and a physical object rather than a rank.
- Has a first action, and it is small: this is ready. Mark it and move on.
- Has a first action, but the action is itself vague, such as sort out the insurance: it needs breaking down, not ranking.
- Has no first action because the next step is a decision: the item is a decision, so write the decision as the item.
- Has no first action because it is not yours to do: it is a message to someone, and the first action is sending it.
- Has no first action because it is a worry rather than a task: it belongs on the page, and it does not belong on the list you work from.
The one item rule
Here is the rule that does most of the work, and almost no brain dump guide includes it. When the sort is done, you take exactly one item off the page and that is the list you are working from. One. Not the top three, not a shortlist, not one plus a backup.
The reason is the one the dump was supposed to solve. A list of six visible things is a comparison you have to make every time you look up, and every glance at it costs a small decision. Six of those in an afternoon is a real tax, and the decision fatigue page here goes through where that budget actually goes. Keeping one item visible means there is nothing to compare, so there is nothing to decide, so the only thing available is the work.
The page does not go anywhere. It stays as the place everything lives, which is the job it is good at. You go back to it when the one item is finished or genuinely blocked, and you take the next one. What you do not do is look at the whole page while working, because that reintroduces exactly the state you ran the dump to get out of.
What happens to the rest of the page
Most of a dump is not work, and treating all of it as work is the other way this fails. The page is usually four different things written in one handwriting, and they want four different destinations.
- Tasks with a first action: these go to wherever you already keep tasks. If you do not have a reliable place for them, the to do list app page here is about picking one by the job it fails at rather than by its feature list.
- Appointments and anything with a time attached: these go in a calendar immediately, not back on the list. A dated thing on an undated list is how dated things get missed.
- Decisions: write the decision as its own item, because a decision pretending to be a task is one of the commonest reasons an item sits for months.
- Worries with nothing to do about them: leave them on the dump page. They were taking up room and now they are written down, which was the point. They do not need converting into anything.
- Things you will not do: cross them out rather than leaving them unmarked. An item nobody has decided about has to be reconsidered every time it is read.
Two ways this stops working
The first is making it a ritual. A daily dump at a fixed time, logged, with a template, is a system you now have to maintain, and the maintenance is the kind of task this was meant to help with. The dump is a tool for a specific state, which is the state of having too much held at once. Do it when that is true. There is no streak to keep.
The second is tidying during the dump. The moment you start putting things in the right place you are editing, and editing means judging whether each item is worth writing, which is the filter the whole exercise exists to bypass. A dump that looks neat was not a dump. The tools page here makes a related point about the gap between a system that looks good and a system that is still in use in three weeks.
Worth being honest about a third thing. A dump can tell you that the list is not the problem. If the page comes out and almost nothing on it has a first action, or the same item has survived five dumps untouched, the obstacle is not capture and it is not sorting. That is useful information and it is the kind that a better method will not change.
What this page is not claiming
The brain dump is a practice taught by coaches rather than a treatment, and it is worth saying so plainly. ADDA, the Attention Deficit Disorder Association, hosts a coach led session on the method in its own library, which tells you the format is taken seriously in the ADHD community. It does not make it a clinical intervention, and material of that kind sometimes carries claims about what mental clutter does to the brain that are not supported. Nothing on this page rests on one.
What the practice is, stated without decoration: writing down what you are holding so that you stop holding it, and then choosing one thing. Both halves are ordinary. The first is well understood and the second is the part that gets left out, which is why so many people report that brain dumps feel good and change nothing.
None of this is a substitute for anything you are doing with a clinician, and a page is not an assessment. If the pattern this describes is costing you work or relationships rather than afternoons, that belongs with a professional rather than with a method.
Where Task Assistant fits
The step this page calls breaking down is the one the app does. You hand it an item that came off a dump with no usable first action, the vague kind, sort out the insurance, and it returns small steps with time estimates, where the first is small enough to actually begin. That is the conversion from a page entry into something you can do, and it is the step a dump leaves to you.
The task breaker on this site runs the same decomposition in a browser with nothing to install, which is the quickest way to test whether your list was fine and the items were simply too big. Paste in the item that has survived the most dumps and see what comes back.
A session then runs for the length of a step rather than a standard block, which pairs with the one item rule: one thing visible, for as long as that thing takes. Pro covers the full set including body doubling. There are no streaks and no points, deliberately, because a counter you can lose becomes a penalty on your worst day, and the worst days are the ones that produce the longest dumps.
Try it now
Questions
What is an ADHD brain dump?
Writing down everything you are currently holding in your head, in one short unfiltered stretch, with no grouping or ordering while you do it. The point is to stop the rehearsal that keeps unfinished things available, which is what makes them feel loud. The relief at the end is from having stopped holding them, not from any progress on them.
How do I do a brain dump without it becoming overwhelming?
The overwhelm almost never comes from the writing, it comes from looking at the finished page. Sort it item by item instead of as a whole, asking only what the first physical action is, then take exactly one item off the page to work from. One visible item removes the comparison, and the comparison is what the page was doing to you.
Should I prioritise my brain dump afterwards?
Not as the first move. Ranking thirty items means holding all thirty at once, which is the most expensive thing you can ask of a tired brain, and the ranking changes next time you look. It also hands you the biggest item first, because size and importance travel together, and that is the item you are least able to start.
What do I do with items that are not really tasks?
Send them somewhere other than your task list. Anything with a time goes in the calendar straight away, a decision gets written down as a decision, and a worry with nothing to do about it stays on the dump page, where being written is already the whole benefit. Things you have decided against get crossed out rather than left sitting.
How often should I do a brain dump?
When you are holding too much at once, which is a state rather than a schedule. Making it a daily logged ritual turns it into a system you have to maintain, and maintaining systems is the kind of work it was supposed to relieve. There is no streak and nothing is lost by not doing one for a fortnight.
My brain dump never leads to anything. What am I missing?
Usually the sort and the one item rule, which most guides leave out, so the page ends as a list of true statements nobody acted on. If you are doing both and items still never move, look at whether they have first actions at all: a page of items with no observable first step means they need breaking down, not better capture.