Frank
There’s gold in the water. You can see it. You know exactly how to get it out. You’ve done this a hundred times. You have the pan right there. And you are completely, utterly unable to pick it up.
That’s executive dysfunction. Not a metaphor that sanitizes it into something manageable — the most accurate description I can give you of what it actually feels like to sit in front of a task you are fully qualified to complete and not be able to start it.
I’ve got 28 years in IT. Nearly 17 years at the same organization. I can troubleshoot a broken mail flow at midnight while half asleep and walk out the other side with a working Exchange environment. I’ve built real applications from scratch, taught myself half a dozen languages, and keep a homelab running that most companies would pay consultants to architect. And some mornings I sit at my desk and cannot begin the first ticket of the day.
Both of those things are true at the same time. This is what nobody outside of it understands.
The Paradox Nobody Talks About: High Competence, Broken Ignition
Executive dysfunction doesn’t attack your ability to do things. It attacks your ability to start them. That distinction breaks your brain when you first understand what’s happening, because it feels like it should be the same thing. It isn’t.
Think of a classic muscle car sitting in the driveway. ’70 Chevelle, big block, all the right parts, built right. That engine, when it runs, is genuinely impressive. But the starter motor is shot. The ignition won’t catch. You can turn the key all day long and that car is going nowhere. Not because the engine is broken. Everything under the hood is exactly what it should be. The car just won’t start.
That’s the closest I can get to an accurate picture of what this feels like from the inside.
The midnight mail flow crisis gets handled because there’s urgency. There’s a ticket. There’s a notification. There’s someone waiting. The crisis provides its own ignition, bypasses the broken starter, and the engine fires. But the routine task at 9 AM on a quiet Tuesday? The one where you know exactly what to do, nobody’s watching, and there’s no immediate consequence for waiting another hour? That’s when the starter motor fails.
The cruelest part is this: the longer you sit there unable to start, the more that inability feeds a story about who you are. Not what your brain is doing. Who you are.
What Executive Dysfunction Actually Is (And Isn’t)
Let me be straight about this. There’s a lot of noise around ADHD and executive dysfunction that flattens it into “gets distracted easily” and cartoon squirrel jokes. That’s not this.
Executive dysfunction is a neurological failure of specific cognitive systems: task initiation, prioritization, working memory, and the ability to translate intention into action. These are functions managed by the prefrontal cortex, and in a brain wired the way mine is, those systems don’t fire the way they’re supposed to. This isn’t a discipline problem. It’s not laziness. It’s not a character flaw. It’s closer to a corrupt process that won’t launch, no matter how many times you try to execute it.
The distinction that matters most, the one that feels almost impossible to explain to someone who hasn’t lived it is the gap between knowing and beginning.
I can describe the exact steps required to complete a task in precise detail. Every dependency, every consideration, every potential complication. I understand the work completely. And then I cannot begin step one.
From the outside, that looks like avoidance. Procrastination. Someone who just doesn’t want to do the thing. From the inside, it feels like standing at the edge of a pool, knowing how to swim, and being physically unable to step off the edge. The knowledge is there. The skill is there. The gap is somewhere between intention and action, in a system that isn’t under conscious control.
I got my AuDHD diagnosis at 55. That’s a long time to carry this without a name for it. Having the name doesn’t fix the starter motor. But it does stop you from blaming the engine.
The IT Brain Is Especially Vulnerable – And Here’s Why
Technical roles create conditions that make executive dysfunction significantly worse. Nobody in the industry talks about this honestly.
The work is high-complexity by default. Constant context switching. You’re managing a ticket queue, responding to Teams messages, monitoring alerts, handling an escalation, and trying to make forward progress on a project that requires deep focus, all at the same time. Every interruption resets the context buffer. For a brain that already struggles with working memory and task initiation, that environment is exhausting in ways that don’t show up on any metric.
Then there’s the visibility problem. IT work, especially infrastructure and systems work, is largely invisible. No physical output. Nobody walks past your desk and sees the pile of things you’ve built. When you’re frozen, nobody sees that either. You can look busy. The freeze is completely internal, and in an environment where nobody’s checking on you because you’re the expert and you’re trusted to self-manage, you can be frozen for an hour and the world has no idea.
That invisibility cuts both ways. Nobody’s breathing down your neck? That’s good. Nobody’s going to notice you need help? That’s very bad.
My world at Advocate Health is real-stakes infrastructure. Exchange Hybrid. Active Directory. Systems that, when they break, break for 162,000 employees. That pressure doesn’t motivate around executive dysfunction. It makes it worse. The more important the task, the harder the brain locks up, because the stakes amplify everything. An urgent task with real consequences attached should be the thing that gets done first. For a brain with executive dysfunction, “urgent and high-stakes” can translate directly into “frozen completely.”
I’ve had days where I handled a genuine crisis before 8 AM and then couldn’t start a routine documentation task until 3 PM. That’s not a time management problem. That’s neurological.
How executive dysfunction creates a self-reinforcing loop in high-stakes technical environments: the more important the task, the harder the initiation system fails, which increases pressure, which makes the next attempt harder.
dark
The Self-Esteem Spiral: When You Start Questioning Everything
Here’s where it gets genuinely painful. I’m going to be honest about it because most people in tech won’t say it out loud.
The freeze cycles don’t stay contained, they compound…..
A task sits longer than it should. A deadline gets close. An email goes unanswered for a day because answering it requires starting a conversation you haven’t been able to initiate mentally, and now it’s been long enough that the not-answering is its own problem. None of this is dramatic in isolation. But it accumulates. And somewhere in that accumulation, the internal narrative shifts.
It stops being “I’m stuck on this specific thing” and starts being “I am someone who cannot be trusted with this job.”
That’s the shift that does the real damage. Because once that narrative takes hold, you’re not just fighting executive dysfunction anymore. You’re fighting executive dysfunction plus an active belief that you don’t deserve to be where you are. Every freeze confirms the story. Every missed start becomes evidence.
I know this spiral well. I’ve lived in it. There are mornings I sit down and before I’ve even opened a ticket, I’m already calculating whether today is the day somebody finally figures out that I’m not keeping up, that I’m slower than I should be, that something somewhere fell through a crack. That low-grade dread is real. It runs in the background all day like a process you can’t kill.
And here’s the particularly vicious layer: executive dysfunction doesn’t just freeze you on tasks. It freezes you on asking for help. Because asking for help feels like confirming the story. Say “I’m struggling with this” and you’re handing someone a reason to look closer. Looking closer feels like the thing you cannot survive. So you stay quiet, you look busy, and you fight it alone.
That isolation is what turns a manageable neurological difference into a slow erosion of self-worth. It’s not the dysfunction itself that breaks you. It’s the silence around it.
What Has Actually Helped (Real Strategies, Not Motivational Poster Garbage)
I’m not going to tell you to eat the frog. I’m not going to recommend an app that changed my life. Here’s what actually moves the needle for me, specific to how my brain works and what my workflow looks like.
Externalize everything that’s in your head. My working memory is unreliable under load. If a task lives only in my head, it has a real chance of becoming invisible to me even when I’m actively looking for it. Getting tasks out of my head and into something physical: a list in Trilium Notes, a ticket, anything with a persistent external existence removes the cognitive weight of holding it and makes it something I can actually act on. HomeBase, the home lab asset tracker I built, started partly because I needed things to live outside my head where I could see them.
Use small manufactured urgency. The freeze is worst when there’s no immediate pressure. I’ve learned to create tiny artificial deadlines as an ignition mechanism. Set a timer for ten minutes, not to finish the task, but just to open it. Not to solve anything. Just to look at it. That sounds almost insultingly simple, but lowering the target from “complete this task” to “open this file” changes the activation energy required dramatically. Sometimes that’s enough to catch.
Lean on routine as scaffolding. Decision fatigue is real, and a brain that’s already struggling with initiation doesn’t need more decisions at the start of the day. When the first hour of my workday follows a predictable pattern, I’m not spending initiation budget on figuring out what to do first. The sequence is already decided. I just follow it. Disruptions to that routine cost more than they seem like they should.
Use Claude as a thinking partner, not a task executor. This one is specific to where I am right now, and I want to be precise about it because it’s not what you might expect. When I’m frozen on a task, sometimes the block is that I can’t break it into pieces small enough to start. The decomposition step itself requires cognitive resources that aren’t available. What I’ve started doing is describing the problem to Claude and asking it to help me structure the approach. Not to do the work. Just to help me see the steps I already know but can’t currently access. It lowers the activation energy because I’m not starting alone. There’s something to think with. That’s been genuinely useful in a way I didn’t anticipate.
None of this is a cure. The starter motor is still unreliable. But these are the things that have helped it catch.
