ADHD Diary #010: Conference Brain Doesn't Scale

I just got back from three days of a regional NOG meeting. By the end of day one I had fourteen good ideas. By the end of day three I had thirty-seven good ideas. As of writing this — three weeks later — I have implemented two of them.

The other thirty-five are still sitting in a note called "ASK YOURSELF LATER". They will sit there for an indeterminate time. Some will surface in conversation later this year. Some will quietly age out of relevance. Most will probably never get done.

This is conference brain. It is a specific ADHD failure mode and the standard productivity advice for handling it doesn't work. Here's what I've learned about why.

What conference brain feels like

The three days at the meeting are operating at peak intellectual stimulation. Every talk has a new idea. Every hallway conversation has a new perspective. Every coffee break is one or two more "I should try X" moments. The brain is on fire in the good way. Notebooks fill up. The future feels expansive.

Then the conference ends. You go home. The first morning back, you sit at your desk with a notebook full of ideas and you don't know which one to start. The cognitive context that made the ideas feel implementable was the conference itself. Out of the context, they're just words on a page.

Some of those ideas survive the trip home. Most don't. The ones that survive are the ones that connected to something you were already working on — they got integrated into existing work and got executed.

The ones that didn't survive are the ones that required new infrastructure, new relationships, or new commitments. Those need an activation energy that conference-fueled excitement doesn't supply. Once the excitement fades, the activation energy isn't there, and the idea sits.

Why standard advice fails

The standard productivity advice for handling conference notes is:

"Block out time the week after to review your notes." This assumes that re-reading the notes will recreate the conference brain state. It doesn't. The brain that's reading the notes a week later isn't the brain that wrote them. The reading is academic, not generative.

"Identify the top three actions and commit to them." This assumes that the ideas can be ranked by importance. At the moment they were captured, they all felt equally important. The ranking exercise is fake — there isn't real information about which is "most" valuable.

"Send a follow-up email to anyone you met." This works for the relationship-building part, kind of. It doesn't address the idea-implementation problem.

"Build them into your next quarterly OKRs." This requires that the ideas pre-existed your quarterly planning cycle. They didn't. Retrofitting them into existing OKRs reshapes the OKRs in ways that the rest of your stakeholders haven't agreed to.

The advice was written for a brain that has uniform attention and stable enthusiasm over time. That brain isn't mine.

The pattern that catches something

I've been experimenting for years. The thing that catches some non-zero percentage of conference-fueled ideas is the 48-hour implementation rule.

The rule: any idea I want to keep gets a first concrete implementation step within 48 hours of returning from the conference. Not a plan. Not a research task. A concrete action. Send an email. Open a terminal. Spec a script. Write a draft. Something that exists in the world after 48 hours that didn't exist before.

The 48-hour window is short enough that the conference brain is still partially active. The activation energy is still there. The momentum from the meeting hasn't fully decayed.

Ideas that survive the 48-hour rule have a meaningful chance of getting implemented. Ideas that don't generally never do.

The honest accounting: of the 37 ideas from the last conference, 2 had concrete steps taken within 48 hours. 35 didn't. The 35 are the ones still in the "ASK YOURSELF LATER" note. The 2 are the ones I've actually been working on.

The 14 / 2 / 21 split

The math from the meeting is informative. Day one had 14 ideas captured. Day three had 37 cumulative. The growth was almost linear — about 12 ideas per day.

Of those 37: roughly half were technical observations I already knew, just framed differently in someone else's voice. Useful for confirming my thinking but not generative. Call these "pattern reinforcement" — comforting, not actionable.

About a third were ideas that connected to existing work I was already doing. These integrated into the work and got implemented over the following months. Call these "amplification" — they made existing work better, didn't require new initiatives.

The remaining ones — maybe a quarter — were genuinely new directions. New tools to build, new relationships to develop, new problems to investigate. Almost none of these get done. They sit in the note.

The 48-hour rule converts a small fraction of the "new directions" category into actual work. The rest never get out of the note.

What I'd tell other ADHD operators

Three practical things.

Lower your expectations for conference-driven action. Going to the conference is valuable for the pattern reinforcement and the relationships even if no new initiatives come out of it. Don't beat yourself up about the 35 unimplemented ideas. Most of them were never going to get implemented by anyone. The value was in the thinking, not the doing.

Bias your effort to the 48-hour window. Don't try to implement everything. Pick one or two things you genuinely want, and execute the first concrete step before the dopamine fades. The narrowing-down is the work.

Accept the "ASK YOURSELF LATER" graveyard. The unimplemented ideas don't have to disappear. They can sit in a note. Some of them resurface naturally when the work in front of you reminds you of them. Some don't. The accumulation isn't waste — it's a record of thinking. Just don't pretend it's a backlog.

Where I still struggle

The honest version, three weeks after this particular conference.

The two implemented ideas are real and concrete. Both are about half-done. One has stalled because it requires coordination with two other people who haven't yet responded to my emails. The other is progressing but slower than I expected.

The 35 unimplemented ideas include four that I genuinely think would matter and that I won't get to in the next quarter. Possibly not the next year. The opportunity cost of not implementing them is real. I don't have a solution to it. The 48-hour rule produces output, but only as much output as my actual capacity allows. The capacity isn't 35.

The peace with this — knowing that I'll see most of the unimplemented ideas re-surface in other conversations over the next two years, and they'll get implemented by someone else, and that's fine — is something I've worked toward and not always achieved.

Conference brain doesn't scale. The 48-hour rule scales a little. Everything else is still hard. Diary entry filed. See you at the next meeting.