Lesson 2: The 60-Second Brain Dump

Quick answer: A brain dump is not organized speech. It is getting everything out before your inner editor catches up, in whatever order it comes. Sixty seconds is short enough that you cannot polish and long enough to surface something real. This lesson has you run it on your own problem, with an optional warm-up round on our free One-Minute Challenge tool first.

Lesson 1 had you explain a problem out loud for three minutes and notice what surfaced. That was a demonstration. This lesson is the actual habit: the brain dump, run fast enough that your inner editor cannot keep up.

A brain dump is not organized speech

The instinct, when you sit down to think through something out loud, is to try to say it well. Full sentences, right order, nothing embarrassing. That instinct is the enemy of a brain dump.

A brain dump is the opposite move: get everything out, messy, unordered, contradictions and half-thoughts included, before you have a chance to filter it. The value is not in what you say. It is in what comes out that you would have edited away if you had given yourself time to think about how it sounded.

Sixty seconds does this on its own. It is short enough that you cannot plan ahead, and it is long enough that something real usually falls out before the clock runs. If you gave yourself five minutes, you would spend the first ninety seconds deciding how to start.

Warm up on a topic that is not yours yet

Before you run this on a real problem, it helps to feel the mechanics once on something with no stakes. We built a free tool for exactly that: the One-Minute Challenge. It draws a random topic you cannot explain yet, gives you fifteen minutes to look it up, then runs a sixty-second clock for you to explain it out loud, unscripted, one take. No sign-up, and it never touches your microphone, it just runs the two clocks.

Run it once on a random topic if you want to feel the sixty-second pressure without worrying about getting your own problem "right." Then come back here and run the real version below.

The exercise: dump a real problem in sixty seconds

1. 1. Pick a real, current problem. Reuse the one from lesson 1 if you like, or pick a fresh one: something you are stuck on, avoiding, or have not said out loud yet.
2. 2. Set a sixty-second timer.
3. 3. Talk. Out loud, at whatever pace it comes. Do not organize it first. Do not worry about starting in the "right" place. If you contradict yourself thirty seconds in, keep going, do not go back and fix it.
4. 4. When the timer stops, stop mid-sentence if you have to. The clock is the clock.
5. 5. Read back what you actually said, either from memory or, better, from a recording or transcript if you made one. Circle anything that surprised you: a detail you did not know you had opinions about, an option you had not consciously considered, a sentence that landed more honestly than you expected.

If you have a way to capture the audio as text, even a phone's built-in dictation, use it. Typing what you remember afterward is a weaker version of the exercise, because you will unconsciously clean it up on the way from your memory to the page, which throws away the very mess you were trying to capture.

Why speed matters here

Most people speak considerably faster than they type, so a spoken dump gets more of a messy idea out before it evaporates than a typed one does in the same window. We went deep on that speed evidence, and on where voice helps and where it does not, in Is Talking to AI Faster Than Typing. For this course, the practical version is simpler: speed is what makes the dump raw instead of curated. A raw dump is more useful going into lesson 3 than a tidy one, because a tidy dump has already had its rough edges filed off by whoever was talking.

Continue the course

You now have a fast way to get a real problem out of your head. It is still just raw material, not a plan. Lesson 3 shows you the light structure that turns a spoken monologue like this one into an actual decision.

Next: Lesson 3: Turning a Monologue Into a Plan

Keep reading

• Is Talking to AI Faster Than Typing? What the Research Actually Shows