The Execution Gap
Why capable people stall -- and what actually moves them.
You know the person. They can whiteboard the decision in an hour, name every option, weigh every tradeoff; six months later they still haven't moved. The manager who's back on individual-contributor work at 11pm because the org needs a call they keep not making. The founder who rewrites the plan for the fourth time instead of picking up the phone.
This isn't laziness, and it isn't ignorance. The same people execute flawlessly for everyone but themselves; they ship for the team, hit the quarter, unblock everyone else's work. The gap shows up only where the decision is theirs. That's the tell, and it's worth taking seriously, because it rules out the explanations everyone reaches for first.
More information won't close it
The reflex, when you're stuck, is to get more input. Another book. Another framework. A 1am conversation with an AI that reflects your situation back in clean paragraphs. It feels like progress because it produces clarity, and clarity feels adjacent to movement.
It isn't. The input lands in the part of you that already agreed. You didn't need convincing; you've been convinced for months. Information closes a knowledge gap, and this isn't a knowledge gap. The proof is sitting in front of you: you already know what to do, and you already aren't doing it. When more knowing produces no more doing, the problem was never knowing.
What's actually running
Underneath a stall is a loop, and a loop fires faster than thinking. It has four parts: a trigger, an automatic move, a payoff, and a cost you don't price in.
Take the most common one. A hard, ambiguous decision comes into view; that's the trigger. Instead of sitting in it, you drop into work you're genuinely excellent at -- the dashboard, the refactor, the deck. That's the automatic move. The payoff is real and immediate; you feel competent and useful by end of day. The cost is the decision, still unmade, compounding quietly in the background. That's the competence refuge: retreating into work you're great at to avoid a decision you're not sure of.
The loop runs below deliberation. By the time your reasoning mind arrives, the move has already happened and you're three hours into something legitimate. That's why willpower and better arguments don't touch it; they show up late.
A small number of these shapes recur. Naming yours is most of the work.
The more-research loop: you convert every decision into a research project, because gathering feels like progress and deciding feels like risk.
The quit-or-stay oscillation: you swing between leaving and committing without doing either, because the swing itself relieves the pressure of choosing.
The calendar-defense loop: you let a full calendar stand in for a made decision, because being busy is easier to defend than being wrong.
Each one pays you something. That's why it survives.
Permission, not information
So if it isn't more information, what precedes the move?
Usually not certainty; you rarely get that, and waiting for it is its own loop. What precedes the move is permission: a clean, honest sentence about what the loop has been protecting you from, said in a setting that makes the next step feel ordinary instead of enormous.
The distinction matters. Insight is still input; it's one more thing you know. Permission is a state change. You can collect insights about your stall for years and stay exactly where you are -- I've watched sharp people do it. The move happens when the loop stops being invisible and its cost stops being abstract, not when you learn one more thing.
I'll be careful here. This isn't a trick, and it isn't a guarantee; the loop doesn't vanish because you named it once. But naming it correctly is the first thing that changes the odds, because you can't interrupt a pattern you can't see.
A short audit you can run this week
You don't need a program to start. You need three honest answers.
What is the move I've been deferring? Name the specific one, not the category. "Have the conversation with my co-founder," not "fix the partnership."
What fires when I get close to it? Watch what you do instead. The substitute behavior is the loop showing its hand.
What's the smallest version of the move that would prove the loop wrong? Not the whole thing. The first irreversible inch.
Answer those honestly and you'll notice something uncomfortable: you've known the move the whole time. That isn't a failure. That's the execution gap, and it's the most fixable problem you have -- because the thing in your way isn't out in the world. It's a pattern, and patterns can be named.
I send occasional letters on this -- the loops, the moves, what I see working. No cadence, no pitch.
Sources
On the knowing-doing gap -- why understanding doesn't produce action: Use a Coach Approach to Overcome the Knowing-Doing Gap (Forbes, on B.J. Fogg's behavior model, 2022)
On insight alone not producing behavior change: Why insight in psychotherapy does not always lead to behaviour change (Kuncewicz et al., 2014).
