How to brain dump, then turn the mess into a plan

A brain dump is exactly what it sounds like: you get everything about a project or problem out of your head and onto a page, without organizing it as you go. It works because your head is a bad place to keep a list. Ideas compete for attention, you keep re-remembering the same worries, and the one detail that matters hides behind ten that don't.

Most advice stops at the dump. The dump is the easy part. The value comes from the second pass, where the mess becomes something you can act on or hand to someone else.

Part 1: the dump

Give it a fixed time

Set a timer for 10 to 15 minutes. A limit keeps you writing instead of polishing, and it makes starting easier because you know it ends.

Write everything, in any order

Facts, worries, half-ideas, names, numbers, questions, things you're unsure about, things you've already decided. One line each is fine. Don't fix spelling, don't group things, don't decide what matters yet.

A real dump looks like this:

• got the lot on Elm St, 1 yr lease, free if we "maintain it"
• need raised beds (maybe 12?), water, tool shed
• city says the hydrant needs a backflow thing??
• $800 from the neighbourhood association
• who gets plots? first come? lottery?
• worried about vandalism
• build in April, plant by mid May

Include the uncomfortable parts

The worries and unknowns are the most valuable lines in the dump, because they're what usually gets left out of tidy plans. "Worried about vandalism" and "nobody knows what the backflow thing costs" are exactly what the next pass needs to see.

Stop when the timer ends

If you're still going strong, add five minutes. Otherwise stop. You can always add a line later when you remember something.

Part 2: the sort

Now read the dump once, slowly, and give each line one of a few labels. You can do this with highlighters, tags in a notes app, or by moving lines under headings.

Facts and decisions

Things that are true or already settled. "We have the lot for a year." "Build in April." These are your foundation, and writing them as decisions stops you from relitigating them.

Open questions

Things you don't know yet. "Who gets plots?" "What does the backflow device cost?" Each one is a small research task or a decision someone has to make.

Risks

Things that could go wrong. "Vandalism." "The lease requires us to maintain it, but nobody has defined what that means." Name each risk plainly; you don't have to solve it yet.

Next steps

Concrete things someone could do this week. "Ask the city what 'maintain it' means." "Get a quote for the backflow device." If a line doesn't suggest an action, it probably belongs in one of the other groups.

Part 3: find the shape

Once the lines are labeled, look for themes: clusters that keep coming up together. In the garden example, "water", "backflow device", "hydrant" and "budget" are all tangled up. So are "plots", "who gets them" and "the school wants two beds".

Themes matter because they show where the real dependencies are. You can't settle the budget until you know what the backflow device costs. You can't decide plot allocation until you know how many beds you're building. Seeing those connections tells you what to do first.

A simple way to show this is a map: each theme in a box, with lines between themes that depend on each other. Even a rough sketch makes it obvious which questions are blocking the most.

Part 4: write the one-sentence version

Before you share anything, try to state the whole thing in one sentence. "Turn the city lot on Elm St into a working community garden, built in April and planted by mid-May." If you can't, the dump probably mixes two projects, and it's worth splitting them.

That sentence goes at the top of whatever you share. Everyone who reads further now knows what the rest is for.

Part 5: share it while it's still rough

The point of sorting the dump is usually to get other people involved. Share it as soon as the core idea, open questions and next steps are clear. Don't wait until every question is answered; the open questions are often the reason to share, because someone else may already know the answer.

A useful shared version has:

1. the one-sentence core idea
2. key facts and decisions
3. how the themes connect
4. what's still open, and the risks
5. next steps, with names where you have them

Common mistakes

• Organizing during the dump. It slows you down and filters out the half-formed lines that turn out to matter.
• Dropping the worries. A plan without its risks feels confident and fails quietly.
• Turning every line into a task. Some lines are context, and that's fine.
• Waiting for certainty before sharing. Rough and shared beats polished and late.