A brain dump is one uninterrupted session where you write down every task you are carrying, before you decide what any of it is worth. It is the first step of planning a six-week cycle, it takes about four hours, and it should happen on a wall rather than in an app. Everything else in the method depends on it, because you cannot scope a cycle around work you have not admitted exists yet.
Do it physically, not digitally
Get whiteboards, large pads of paper, or at minimum a to-do list application. But if you have the choice, choose the wall.
I lose the concept of scale when I only look at things in a digital environment. A list of eighty items in an app is a scrollbar. The same eighty items across a conference room wall is a physical fact you cannot argue with. Scale is the whole point of the exercise, so use the medium that shows it to you.
My version: I lock myself inside a whiteboard room for about four hours with a playlist and some dry erase markers. That is it. No laptop, no meetings, no notifications.
By the time you are done, the walls should be covered with everything that was in your head.
The seven steps
- Read all the instructions before you begin. Including this list. The order matters more than it looks.
- Put something on that helps you focus. A playlist, silence, whatever gets you into it. I coordinate playlists to the kind of work, which sounds silly until you try it.
- List the major categories of all active projects. Anywhere from two to twenty, depending on how many things you are trying to move at once.
- List every task under each category. Do not filter. Do not sort. Just get it out.
- Decide which items only you can complete. Anything someone else could do moves to a separate list and gets assigned to that person.
- Write down how long each task will take. Anything longer than 90 minutes gets broken into smaller tasks.
- Celebrate. Genuinely. Especially the first one, because that was a lot of work.
The 90 minute rule does most of the work
Of those seven steps, step six is the one that changes your estimates.
If a task cannot be described in under 90 minutes, you have not defined it. You have named it. "Redesign the onboarding" is a name. "Rewrite the welcome email, 45 minutes" is a task.
Anything above that limit is hiding steps you have not thought about yet, and those hidden steps are exactly where six-week plans go to die. We messed up plenty of cycles by scheduling "plan a project" inside a cycle, then discovering we had wildly underestimated what that meant. It ruined the careful planning around it, upset the team, and made us think cycles were stupid and would never work for us.
The tool for breaking those down is the kind of thinking you have to do yourself, and specifically it is the "and then?" game, which deserves its own explanation.
What to expect, so you do not quit halfway
- It is going to feel overwhelming. That feeling is information, not failure. It is the first honest look at a load you have been carrying without ever weighing it.
- The order does not matter. You are not prioritizing yet. You are emptying.
- Plan a full day. Not an afternoon you squeeze in.
- Allow a few days of additions. Even after four solid hours you will not have gotten everything. Random tasks keep surfacing for days afterward, and your job is to capture each one as it appears.
That last point is the one people skip. The dump is not a single event, it is a session followed by a few days of catching stragglers.
The part that changed how I managed people
Step five looks administrative. It is not.
One of the many things I got wrong running my agency was expecting each person to simply do their job. It seemed like a straightforward formula: hire someone who can do web development, and they will do web development. It does not work like that.
I saw my team as independent operators. What I eventually understood is that as their leader I needed to see them as extensions of the work I was responsible for. Not "what can they do" versus "what can I do," but "I need this done, and I get it done by having this person work on it."
I did not need to know how they did it. That is the entire reason you hire specialists. But I did need to know exactly what outcome I expected, and that is my job to define, not theirs to guess.
Which means when you get to step five and start moving tasks onto other people's lists, you are not offloading. You are taking responsibility for defining the outcome clearly enough that someone else can own the method.
What happens next
The wall full of tasks is raw material, not a plan. From here they go onto the cycle sheet: each week across the top, each day given a single focus, and tasks arranged underneath until no day holds more than six hours of work.
That constraint is where most of the hard decisions actually happen. The dump tells you what exists. The sheet tells you what is possible.
The full sequence is in the guide to running your work in six-week cycles.