I wake up at 3:45am with ideas crashing into each other faster than I can write them down.
This has been happening for 10 years, but recently it got dramatically more intense. I want to share what I've learned about this state — what triggers it, why AI makes it worse (or better?), and how to actually capture something useful from it.
What Is Thought Waterfall?
It started with free writing. You dump thoughts on paper, and while writing one idea, you read another — and it triggers a third. Each thought reinforces the next. They cascade like a waterfall.
I call it Thought Waterfall — a state of associative reinforcement where ideas arrive faster than you can process them.
It's Not Flow State
Flow state (as described by Mihaly Csikszentmihalyi) is deep single-task focus. You're absorbed in one activity, time disappears, and you produce high-quality work on that one thing.
Thought Waterfall is the opposite architecture:
| Flow State | Thought Waterfall | |
|---|---|---|
| Focus | Single-task, deep | Multi-thread, divergent |
| Speed | Steady, absorbed | Accelerating, overwhelming |
| Output | Polished work | Raw connections |
| Feeling | Calm mastery | Euphoric chaos |
| Risk | Burnout | Forgetting, sleep loss |
Edward De Bono described something similar with "lateral thinking" — but Thought Waterfall is messier, faster, and increasingly triggered by AI.
How AI Made It 10x More Intense
Recently I started working with AI sub-agents. I dispatch a prompt, and while waiting for the result, I start formulating the next prompt. The visualization of how everything connects keeps accelerating.
The pattern looks like this:
- Start with a seed idea
- Dispatch it to an AI agent
- While waiting, a new connection forms
- Dispatch that too
- First result comes back — triggers two more ideas
- Repeat until overwhelmed
The ideas come so fast I'm afraid I'll forget them. But I'm also in this joyful, almost euphoric state where everything connects to everything.
The Risks
- Sleep disruption: The waterfall doesn't respect bedtime
- No quality filter: Volume ≠ value. Most raw ideas need heavy editing
- Fear of forgetting: Creates anxiety that undermines the creative state
- Context switching cost: Each thread is shallow compared to deep flow work
Practical Tips for Capturing the Waterfall
After years of experiencing this, here's what actually works:
- Voice memos over typing: Your mouth is faster than your fingers. Capture the essence, not the details
- Don't organize during the waterfall: Raw capture first, structure later. Organizing kills the associative state
- Set a timer: Give yourself 30 minutes of pure capture, then stop and process
- Use AI as a capture tool: Dictate to an AI assistant that can structure your chaos after the fact
- Accept impermanence: Not every idea deserves to survive. The good ones come back
Do You Experience This?
I'm curious whether this resonates with others. Some questions I'm still exploring:
- Is Thought Waterfall a recognized cognitive pattern, or am I naming something new?
- Does working with AI agents trigger this for other developers?
- What's your capture system when ideas arrive faster than you can process them?
I wrote the full exploration on my blog: razbakov.com/blog/2026-03-23-thought-waterfall
Would love to hear your experiences in the comments.
Top comments (0)