Your ADHD brain is not the problem. The workplace is.

What 9 years as an ADHD engineer taught me about work

My name is Stephan. I have worked as a software engineer for nearly a decade, most of it in open offices and agile teams. I was diagnosed with ADHD at 47. Looking back, the diagnosis explains pretty much every conflict I ever had with a work environment.

This page is not career advice. I am writing down what I have understood about ADHD and work after spending nine years convinced I was just bad at my job. The app I built helps me. But the app is just a tool. The more important part is understanding why your brain fights back in an office.

Why open offices wreck ADHD brains

After an interruption, I need about 25 minutes to get back into flow. Mark et al. (2008) measured this — it is not my imagination. In an open office with Slack, colleagues at my desk, and the third notification of the day, I am done by 9:30.

The ADHD brain has a working memory problem. What I hold in my head while I work is fragile. A single "hey, got a second?" wipes the entire stack. I then spend the next twenty minutes trying to reconstruct what I was doing. It usually does not fully come back.

The solution is not "more discipline." The solution is fewer interruptions. Noise-canceling headphones. Slack notifications off. A work culture that understands asynchronous communication is not a preference for some brains — it is a necessity.

Task paralysis: when starting feels like hitting a wall

This is the thing that wrecked me the most before I had the diagnosis. I sit in front of the empty IDE, the blank Google Doc, the task list. I know what to do. I want to do it. And my brain simply will not engage.

This is not a character flaw. Task initiation is a neurological problem in ADHD. Volkow et al. (2009) showed with PET scans that the reward system works differently — fewer dopamine D2/D3 receptors in the nucleus accumbens. Tasks without immediate reward feel disproportionately heavy. "Write the report so you can have your review in two weeks" is about as motivating to my brain as an empty battery. No juice.

What helps: making the task so small my brain cannot see the threshold. Not "implement feature X." But "open the file." It sounds ridiculous. It works anyway. (More in the article Start small.)

The 3 PM crash and why tracking breaks matters as much as tracking tasks

With ADHD, I do not just forget tasks. I forget breaks. I work through because I am in flow or scared of losing the thread. Then it is 3 PM, my brain gives up, and the rest of the day is gone.

This is not an endurance problem. The prefrontal system — the part that controls impulses and makes decisions — fatigues faster in ADHD. After hours without a real break, the tank is empty. No amount of willpower brings it back.

What I learned: breaks are not a luxury. They are work infrastructure. Five minutes turning away from the screen. A quick step outside. No phone. No doomscrolling. I track these now, the same way I track work tasks. Not to control myself, but to see the pattern: on days with real breaks I am still functional at 5 PM. On days without, I am done by 3 PM. The pattern becomes visible after two weeks.

Meetings drain energy — they are not the work

The average meeting costs me more energy than two hours of coding. Not because meetings are exhausting — though they are — but because of the cognitive load before and after.

Before the meeting: my brain loads context. Who is there? What is this about? Do I need to say something? After the meeting: my brain unloads the context and tries to find its way back to where it was an hour ago. It rarely gets there completely.

My strategy: batch meetings. Do not scatter them across the week. Monday and Thursday are meeting days. Tuesday, Wednesday, Friday are for deep work. This requires team buy-in. But even if you cannot get that: a single meeting-free morning per week beats none.

Brain dump at end of day: shut your head off

The ADHD brain does not stop after work. It replays the open loops of the day: the unsent email, the unresolved bug, tomorrow's meeting. Zeeb et al. (2015) describe this as "aversive delay" — the brain avoids the unpleasant task but cannot let it go. The result: you lie in bed thinking about work.

What helps: 30 seconds of brain dump before closing the laptop. Spoken, into the app. Everything still open. The signal to my brain: it is noted. You do not need to hold it. You will see it again tomorrow morning.

This sounds like journaling with extra steps. But it actually works. Masicampo & Baumeister (2011) showed that unfinished tasks bind cognitive resources until they are externalized. Writing them down — or speaking them — unloads the system.

When your manager does not know your diagnosis

I do not tell my employer I have ADHD. That is a personal choice, not a principle. In some teams, with some managers, openness is a strength. In others, it is a risk.

What I do instead: communicate needs without the diagnosis. "I work better with async updates instead of status meetings." "Can we handle this in writing, I retain things better when I read them." These are not ADHD demands. They are work preferences that are legitimate for anyone.

The app helps because all data stays on my device. No server, no cloud, no IT admin seeing anything. This matters to me. Not out of paranoia, but because my mental health is none of my employer's business.

What nine years have made clear

Your brain is not broken. The work environment was built for a standard brain, and yours runs on a different operating system. That is not a defect. It is a compatibility problem.

The app I am building is scaffolding. It tracks routines, mood, energy. It reminds you to take breaks. It unloads your head at the end of the day. But it does not replace therapy, medication, or a good manager.

What it does: it makes the invisible visible. After two weeks, you see patterns you never noticed. On meeting days, your energy drops. On days with real breaks, it lasts longer. This is not magic. It is data your own brain produced, telling you: you are not lazy. You are just working in the wrong environment.