This article is for executives and founder-CEOs with ADHD or AuDHD who understand what they need to achieve but find it almost impossible to make sustained progress on complex, multi-month challenges — particularly when those challenges are fuzzy, high-stakes, or politically loaded.
ADHD is not a motivation problem. It is an activation problem. And the structure of how you frame a challenge is either part of the solution or part of the problem.
Why Woolly Goals Don’t Work for ADHD Brains
Most ADHD executives and founders are perfectly clear on what they broadly need to achieve. They need to “get better at leadership.” They need to “sort out the business development.” They need to “improve team performance.”
These are real goals. They are also completely useless to an ADHD brain trying to figure out what to do next. [Why SMART Goals Don’t Work For ADHD Brains]
The problem is specificity — or the lack of it. Woolly goals give the brain nowhere to land. They have no start, no end, no clear set of actions, and no obvious moment of completion. For a neurotypical brain, that ambiguity might be manageable. For an ADHD brain, it creates a kind of activation vacuum: the task exists in theory, but the brain has nothing concrete to engage with.
The result is avoidance. Not because the person doesn’t care, but because the conditions for engagement are simply not met.
“When it’s in our heads, we put it on paper. We say: what is this thing, really? And we give it a name.”
Framework: The Project Frame
The Project Frame is the practice of converting an ambiguous challenge into a named, bounded project with a specific outcome to aim for.
It sounds almost absurdly simple. But the act of naming changes something important in how the brain processes a challenge.
When a client was called into a difficult conversation with senior leadership about performance concerns, the challenge was clear in its content but completely unclear in its structure. There was no handle on it. It felt overwhelming and slightly paralysing. The work we did together wasn’t to fix the underlying challenges immediately — it was first to reframe the situation as a project.
We called it Project LeadWell.
That name did several things at once:
- It turned a continuous, ongoing pressure into something finite and completable
- It gave the challenge an identity outside of the person experiencing it — it became something to work on rather than something to feel bad about
- It created a category to put things into: every action, every conversation, every small win or setback could now be filed under Project LeadWell
- It activated the ADHD brain’s engagement with challenge rather than with threat
Within that framing, progress became possible in a way it hadn’t been before.
The Project Frame works because named projects engage the brain’s interest and challenge circuits. The woolly version of a goal sits in the anxiety system. The project version sits in the motivation system. Same challenge, entirely different neurological experience.
Why ADHD Brains Activate Around Projects
ADHD brains do not run on importance, willpower, or delayed reward. The research and clinical experience are consistent: the brain responds to a specific set of activation signals, and almost nothing else.
The ADHD Motivation Engine runs on four fuel sources:
- Curiosity and challenge — Is there a problem here worth solving? Is there a clear outcome to reach?
- Novelty and change — Is this a new approach, a new context, a new way of tackling something?
- Passion and emotional meaning — Does this connect to something the person genuinely cares about?
- Urgency and external consequences — Is there a deadline? Is there accountability? Is something at stake?
The fourth fuel — urgency — is worth treating carefully. It works, but it comes at a cost.
For many ADHD people, urgency activates via anxiety rather than via energy. They feel the stick rather than the pull. That tends to produce short bursts of reactive effort followed by crashes, and over time it builds a relationship between performance and threat that is neurologically expensive.
The first three fuel sources — challenge, novelty, and meaning — are far more sustainable. And a well-named project activates all three.
When Project LeadWell became a real thing with a name, it became a challenge to complete. The process of designing systems, building buy-in across the team, and figuring out how to get different people engaged introduced novelty at every step. And for someone who cares about leading well and contributing to a growing organisation, meaning was never far away.
The ADHD brain engaged because the conditions were right — not because the person became more disciplined.
Framework: The Horizon Stack
Naming a project solves the immediate activation problem. But projects don’t exist in isolation. They live within a larger picture of where you’re trying to get to, and how close you are.
The Horizon Stack is the practice of holding your goals at three levels simultaneously, and knowing how to move between them deliberately.
The three levels are:
Level 1 — The Three-Year Horizon. The broadest possible view. This is where you are heading: a role you want to hold, a business you want to build, a financial position you want to reach. It is not a detailed plan. It is a direction — specific enough to orient you, broad enough to stay stable as the details change.
Level 2 — The Quarterly Project. The medium view. Given where you are now and where you’re heading, what is the one thing most worth solving in the next 90 days? This is where the Project Frame lives. One named project, one clear outcome, one time-bounded sprint.
Level 3 — The Current Focus. The close-up view. This week, this fortnight — what is actually in the way? What is the blocker that most needs addressing right now? This level is about execution: conversations to have, decisions to make, problems to clear.
The Horizon Stack is designed to be zoomed in and out deliberately, not experienced all at once. An ADHD brain that tries to hold the three-year vision and the specific tasks for this Tuesday simultaneously tends to either freeze under the weight of the gap or get so lost in the detail that it loses sight of the direction.
“You can zoom into this, see it’s six months. And then you can go, this is my next three months. And you can zoom way out and go: this is where I am now, and this is the three-year horizon.”
The skill is knowing which level currently needs your attention, and deliberately shifting to it — rather than being pulled between them unconsciously.
How Sprints Fit In
Within Level 2, the most effective unit for ADHD brains is the sprint: a time-bounded period of focused effort on one project, with a clear start, a clear end, and a defined measure of success.
Three months is a reliable sprint length for most ADHD executives and founders. It is long enough to make meaningful progress on a complex challenge. It is short enough to maintain activation — the brain can feel itself approaching a finishing line.
When a sprint ends, the project either completes or evolves. Project LeadWell becomes Project Execute.
The brain gets a moment of natural transition, which doubles as a natural re-activation point: a new name, a slightly new challenge, a new sprint beginning.
For leaders in larger organisations, quarterly sprints remain useful. For founders in the early stages of a business, monthly sprints may feel more natural.
The principle holds at any scale.
The “What’s in the Way?” Question
The Horizon Stack creates structure. But structure alone doesn’t produce progress. What keeps the system moving is one repeating question:
“What’s in the way of this?”
This is not a complicated question. But it is a discipline. The ADHD brain, left to itself, will tend either to avoid the stuck points — drifting back to what feels comfortable — or to lose sight of the overall direction entirely. The “what’s in the way?” question holds both tensions at once: it assumes the project is real and worth continuing, and it surfaces the specific blocker that most needs attention.
Asked at the right moment, it converts vague frustration into a solvable problem. When the client’s confidence was the blocker to leading well, we worked on confidence specifically — not as a general topic, but as an obstacle between where they were and where they were trying to go.
When the blocker was getting buy-in from a particular team member, that became the next focus. When it was getting the right reporting systems in place, that became a delegation problem to solve.
“Every single roadblock along the path — that’s a roadblock, that’s a roadblock — you can solve all of those things. But you’ve got to keep asking what’s in the way.”
The question should be asked at every level of the Horizon Stack. What’s in the way of the three-year goal? What’s in the way of this quarter’s project? What’s in the way of this week’s focus? Each level of zoom has its own blockers. Identifying them is the work.
Designing for Results, Not Hoping for Them
One of the more important shifts for ADHD executives and founders is the move from hoping things will improve to designing for specific outcomes.
Hope is not a planning tool. “I hope we’ll get results from this” is a statement about optimism, not about causation. It puts the outcome outside the person’s agency — something that happens if things go well, rather than something that is made to happen by design.
Designing for results means asking a different set of questions:
- What outcome do I need by when?
- What’s in the way of that?
- What project will solve that blocker?
- Who needs to be on board, and how will I get them there?
- What does success look like in 90 days?
The distinction matters more for ADHD brains than for others, because ADHD is particularly vulnerable to a pattern of energised planning followed by ambiguous execution. The vision is vivid. The motivation is real. And then the path between vision and outcome remains undefined, which means the brain has nowhere to go when the initial energy subsides.
Design creates that path. It replaces optimism with architecture.
One Project at a Time
For most ADHD brains, the right number of concurrent projects is one.
Two is manageable in some circumstances. Three or more is typically where progress stalls — not because the person is incapable, but because attention splits across projects produce the activation vacuum that kills momentum. The brain is constantly re-orienting rather than building the state that allows deep work to happen.
This applies both to the projects you are actively running and to the blockers you are working through. Solving the buy-in problem and the reporting system problem and the team development problem simultaneously is not a plan. It is a list of things that will remain undone until they’re prioritised.
Choosing one thing and working on it until it is resolved — or until it is genuinely no longer the most important blocker — is how ADHD brains make real, sustained progress.
What Changes When This Is Implemented
When ADHD executives and founders start working within this structure, a few things become visible fairly quickly.
Progress feels different. When a woolly challenge becomes a named project, the brain has something to engage with each day. There is a direction to move in. The sense of being stuck in something shapeless shifts toward building something specific.
The relationship with setbacks changes. Within a project frame, setbacks are obstacles to solve rather than evidence that the whole thing is failing. “What’s in the way?” converts a discouraging moment into a problem-solving prompt.
Strategic thinking becomes accessible. When the three-year horizon is genuinely held — not just gestured at, but kept as a real orienting reference — decisions at the task level become easier to make. “Is this the most important thing to work on right now given where I’m trying to get to?” is a much more manageable question when the answer to “where am I trying to get to?” is already clear.
Confidence often improves as a downstream effect. Not because anything changed psychologically first, but because the brain finally has evidence that it can make real progress on hard challenges. That evidence is hard to argue with.
What We Now Know
ADHD brains do not stall on hard challenges because they lack discipline or motivation.
They stall when the conditions for activation are absent — when a challenge is too woolly to engage with, when there’s no clear project to orient around, when the path between now and the goal is undefined.
The Project Frame converts ambiguous pressure into a named, bounded challenge that the ADHD brain can actually work on. The Horizon Stack provides the structure for moving between the three-year direction, the quarterly project, and the immediate blocker — without getting lost at any one level. The “What’s in the way?” question keeps the system moving by converting stuck points into solvable problems.
And the shift from hoping for results to designing for them replaces optimism with a genuine architecture for progress.
None of this requires the ADHD brain to become a different brain. It requires the work environment to be designed in a way that the ADHD brain can actually use.