The Knowing-Doing Gap
I've documented this for five years. The gap between knowing what to do and actually doing it. Notes, frameworks, mental models, playbooks. One hundred and nine mental models in a vault, last I counted. A library of advice I have given myself and not taken.
For most of those five years I treated this as a knowledge problem. If I just understood the gap precisely enough — its mechanics, its triggers, its evolutionary lineage — I would close it. The understanding was the work.
It wasn't.
Documentation Is Not Action
Documentation is a structure I rationalised myself into. I can read, I can think, I can systematise. I can build a framework for almost anything and write it down with confidence. What I struggle with is the next step — going live, putting myself out, finding out if any of it actually works.
The documentation itself becomes the action. It feels productive. It feels like progress. The vault gets bigger. The shelf gets fuller. The plans get more detailed. And nothing ships.
This is the cleanest disguise an avoidance pattern can wear. Reading is not procrastination. Note-taking is not procrastination. Building a system is not procrastination. Each one is a respectable thing in itself — which is exactly what makes the stack of them so dangerous. You can spend a decade looking like a serious person and never expose a single belief to the world.
What This Has Cost Me
I'm thirty-six. I should be a long way ahead of where I am.
If I had acted on half of what I have written down — half — I would be in a different position financially, professionally, and in every other dimension that compounds. The gap is not theoretical. It is the difference between the person whose career I have on paper and the person who shows up day-to-day. The cost shows up in the bank account. It shows up in the relationships. It shows up in the projects that exist as 90% complete plans and 0% complete businesses.
The harder thing to admit is this: the cost is largely self-inflicted. The framework was already there. I just preferred refining it to using it.
A Knowledge Problem It Is Not
Most of what people call a knowing-doing gap isn't a gap at all. It's a categorisation error.
There are two real categories underneath. One is a capability gap. You don't actually know how to do the thing — you have read about it, but reading isn't doing, and the muscle memory isn't there yet. Distribution is mine. I have built tools. I have written a book. I have published playbooks. Nobody has come. That isn't an execution failure. It is a skill I do not yet possess. Knowing it exists is not the same as knowing how to do it.
The other is an execution gap. You know what to do. You have done it before, or it is so simple it doesn't matter that you haven't. You agree with the advice when you receive it. You promise yourself you'll do it. Then three days pass and you haven't done it. The Instagram scroll instead of the LinkedIn post. The unsent message to the warm contact. The pitch that lives in a draft folder forever. Thirty-second actions that don't happen for weeks.
The capability gap is a project. You close it by doing reps and getting better. The execution gap is something else, and it is the one I have spent five years dressing up as a knowledge problem so I didn't have to look at it directly.
The Real Mechanism
The execution gap, in my case, is not laziness or poor planning. It is exposure.
To act is to be seen acting. To pitch is to risk the rejection. To ship is to find out whether the thing was any good. To send the message is to find out whether they wanted to hear from you. Documentation has none of those properties. Documentation is private. Documentation is reversible. Documentation can always be improved.
When my self-worth is fused with my competence — and it is, more than I would like — going live is not putting out an output. It is putting myself up for judgment. If the thing flops, it does not feel like feedback on the thing. It feels like a verdict on me.
So I refine the framework one more pass. And one more. And the framework becomes a fortress.
The Structural Layer
The structural framing — fix the triggers, fix the feedback loops — is what I wrote about in Habits Over Goals. It is real and it works. The 5:30am ride happens because the trigger is the alarm and the people. The morning priorities did not happen for nine days because there was no trigger.
But structure alone doesn't close the execution gap when the unwritten cost of acting is identity exposure. You can build the most beautiful trigger system in the world for sending the message and still not send it, because the system isn't fighting absence of structure. It's fighting fear of being seen.
The honest answer is that both layers have to move. Build the structural container. And drop the requirement that the work be excellent before it leaves the room. Both. Not one.
The Way Out
I'm not going to pretend I have closed this. I am writing this on a website I built specifically as a forcing function — because publishing is the version of doing I have avoided most. Every essay on this site is a small bet that the catastrophe I keep anticipating is mostly imaginary.
What I do believe, after five years of looking at it:
- The documentation is not the work. It was never the work. The work is the version of the document that other people see.
- The gap is not a knowledge problem. It is a disguise problem. The mind that loves frameworks will offer you an infinite supply of reasons not to ship.
- Capability gaps close with reps. Execution gaps close with smaller, more frequent exposures — until the act of being seen stops carrying the weight it currently carries.
- The cost of one more refinement pass is invisible and feels free. It is not free. It is paid in the years.
I have a vault full of advice I gave myself and didn't take. I am going to spend the next phase of my life taking it.
The shelf doesn't change a life. The shipping does.