AtlasLibrary
Browse articles

131 articles

Put the crowded thoughts somewhere visible

The Braindump

Read the articleMarkdown
A hand writes an uneven unedited stream across a notebook in early morning light.
Put the thoughts somewhere you can look at them before deciding which one matters.

What It Is

"Should work on Idyllic" sounds like a task, but it does not tell you what to do. Writing a little longer can reveal the missing decision: "Need to define the skill integration architecture." Now the obstacle is specific enough to work on.

The braindump is ten minutes of continuous writing, first thing in the morning. You put tasks, worries, ideas and unfinished thoughts onto a page without organizing or filtering them. Then you read what you wrote.

Its purpose is to free working memory and reduce the cost of starting work. Instead of reflecting on selected meaningful experiences, you record everything occupying attention so you can examine it without continuing to hold it all in mind.

The Problem It Solves

You can wake up already thinking about yesterday's unfinished tasks, an approaching deadline, a shower idea, a project you're anxious about and things you need to remember. Together they produce a vague sense of overwhelm.

Each concern occupies 0.5-1 unit of working memory. By the time you sit down to work, 3-4 units may already be occupied. A complex task needs another 4-6 units to hold its context, but only three remain available.

Starting feels impossible because the task requires more capacity than you have free. The brain refuses work whose context it cannot load. Trying harder does not remove the concerns already occupying that capacity.

The Mechanism

graph LR
    A[Wake State<br/>WM: 60% full] --> B[10-min Braindump<br/>Externalize everything]
    B --> C[Cleared State<br/>WM: 10% full]
    C --> D[Work Launch<br/>Now possible]

    A -.->|Without dump| E[Try to work<br/>6 units needed]
    E -.-> F[Only 3 available<br/>Procrastination]

In the example, working memory begins 60% full. Only 2-3 units are free, while the task requires six. Since 6 > 3, the task cannot start and procrastination follows.

Writing externalizes the concerns. Working memory falls to roughly 10% full, leaving 6+ units available. The task still requires six, but now 6 ≤ 6. The person and task have not changed; the available capacity has.

The 10-Minute Protocol

  1. Open a blank page in a notebook or a digital document.
  2. Set a timer for ten minutes.
  3. Write continuously, without stopping to edit or organize.
  4. Include whatever is occupying your attention: tasks, worries, ideas, feelings and random thoughts. Do not judge whether a thought is important enough to include.
  5. Stop when the timer ends.

Nobody else needs to read it. The writing only has to get the thoughts onto the page, so incoherent or poorly phrased sentences still do the job.

What Happens During the Dump

The first three minutes usually bring up obvious obligations:

  • "Need to respond to that email"
  • "Meeting at 2 PM today"
  • "Should work on Project X"

During minutes 4-7, the concerns behind them emerge:

  • "Worried that Project X isn't going well"
  • "Don't actually know what next step is"
  • "Feeling behind on everything"

Minutes 8-10 often reveal the issue that matters most:

  • "Actually avoiding Project X because I'm not sure it's the right direction"
  • "Need to have difficult conversation with person Y"
  • "Core blocker is that I don't have clarity on strategy"

The most important insight usually appears during minutes 8-10, after the obvious thoughts have been recorded. Continuing after the initial list gives the underlying concern time to become explicit.

After the Dump: The Analysis Phase

Read the page after writing it. With the thoughts externalized, you can use working memory to examine them instead of holding them.

Four useful distinctions often become visible:

  • An instruction may still be ambiguous. "Work on Project X" names a project without specifying an action. "Write 300 words of documentation" gives you a first task you can actually perform.
  • Apparent priorities may be noise. Of 15 things you "need" to do, only two may matter this week. The other 13 can be deferred or deleted.
  • The blocked task may depend on an earlier decision. What looked like procrastination on Task A can turn out to be anxiety about an unresolved strategic question. Resolving that question makes Task A tractable.
  • Overwhelm can become a set of specific concerns. Once written, each concern can be addressed separately. The vague overwhelm dissipates when its contents are externalized.

The Activation Energy Drop

Externalization also reduces the work of choosing where to start. With 15 obligations in your head, each can feel equally urgent. Holding them while comparing them makes the combined problem feel impossible, with an activation cost of 6+ units.

On the page, you can see all 15, identify the two urgent ones and select one specific action. The startup cost falls to two units. "I don't know where to start" becomes "I'll start with this specific thing."

Clearing capacity and clarifying the action are related effects. The earlier example kept the task's cost at six and increased available capacity. Here, resolving competing priorities reduces the cost of starting itself.

Why It Must Be Morning

Do the braindump as the first mental activity of the day, before email, meetings and other reactive tasks add more concerns. You can then choose a priority from the relatively small set of thoughts you woke up with.

Waiting until the afternoon allows six hours of incoming tasks and context changes to fragment working memory. The accumulated noise makes the dump less effective. Doing it in the morning establishes a direction before those demands start choosing it for you.

The Bridge Script Function

The braindump provides a bridge script between wake_state and work_state.

Without it, the transition is wake_state → ??? → work_state. The undefined middle has high activation energy, so it often fails. Checking email, news or social media supplies an easier default: wake_statedistraction_state.

The routine replaces the gap with a sequence:

  • wake_statebraindump_state: opening a page and writing is easy to begin.
  • braindump_stateclear_mind_state: writing produces this change automatically after ten minutes.
  • clear_mind_statework_state: the identified priority makes starting work easier.

Each step handles part of the total startup cost, instead of requiring you to pay it all at once.

Common Failure Modes

Trying to Make It Good

Editing grammar, coherence or style interrupts the process. Let the writing be incoherent. Its function is to externalize thoughts, and you are its only reader.

Filtering While Writing

A thought can occupy working memory even if it is objectively unimportant. Skipping it because it seems unworthy leaves it in your head. Record it now and decide whether it matters when you reread the page.

Not Reading It After

Closing the notebook immediately moves the thoughts onto paper without examining them. Spend 2-3 minutes rereading so you can notice patterns and decide what to address.

Skipping When "Not Much to Dump"

Feeling clear does not give you conscious access to every concern using working memory. Writing often reveals something you did not realize you were holding. Do it every day, including mornings that seem quiet. The ten-minute routine gives you eight hours of clear mental space for the day.

Integration with Other Systems

The braindump is a specific form of journaling used to prepare for the day. It creates a record of your state that supports tracking over time.

Making an ambiguous task explicit reduces procrastination. Externalizing concerns frees working memory. The braindump is the primary tool for keeping the active load below its seven-item limit. Both effects lower the cost of starting.

Seeing the actual priorities also improves expected-value comparisons, so limited resources can go to the work that matters.

Examples in Practice

Will's Morning Protocol

Will's sequence begins after waking:

  1. Turn on Luminettes for morning light and circadian synchronization.
  2. Write for ten minutes while the light runs.
  3. Read the page.
  4. Identify 1-2 priorities for the day.
  5. Start work, with the startup cost now low.

The braindump is the preparation that makes the rest of this sequence work.

Debugging Project Stuck

The Idyllic entry moved through four thoughts:

  • "Should work on Idyllic"
  • "Don't know what to work on in Idyllic"
  • "Need to define the skill integration architecture"
  • "Actually avoiding this because I don't have clarity on the design"

The obstacle was an unresolved architectural decision. Will spent 30 minutes sketching the architecture in his journal. Once the design was clear, implementation became tractable.

Without writing through the initial obligation, he would have spent the day vaguely procrastinating and asking "why am I so unmotivated?" The page made the actual decision visible, which made it possible to resolve.

Return to the libraryBack to the beginning