There’s a specific kind of stuck that doesn’t look like stuck.
You have the data. You’ve done the thinking. You could write the conclusion on a napkin in thirty seconds. And yet — nothing happens. The decision sits in your head, fully formed, waiting.
That’s not an information problem.
I’ve spent years building systems that reduce ambiguity. Better specs. Clearer delegation. Deadlines with proof artifacts. And those things work. They genuinely do.
But they don’t solve this.
This is the gap between knowing and moving. And it’s subtler than it looks.
The thing I kept calling “almost ready”
Earlier this year I had a decision on the table about how I structured a significant part of my working week. I knew what I needed to change. I’d known for about three months.
I kept describing it as “still thinking it through.”
That was a lie. Not a malicious one — I didn’t even know I was lying. But I had already thought it through. I was just not comfortable with what the answer required.
What it required was admitting that the way I’d been doing things had stopped working. That I’d optimized for the wrong thing. That a quiet but real cost had been accumulating.
Knowing that felt fine in the abstract. Acting on it meant changing something real.
Clarity without motion is just expensive thinking
The cost of not moving once you know isn’t neutral.
Every day you sit with a clear decision is a day you spend a little energy maintaining the holding pattern. Re-examining it. Justifying why you haven’t acted yet. Rehearsing what you’ll say when you do.
That’s overhead. It doesn’t show up on a calendar. It doesn’t get logged as a task. But it’s real, and it compounds.
I’ve started calling this decision latency. And it’s not about being slow or indecisive in some general sense. It’s about the specific window after clarity arrives and before action begins.
That window is where a lot of energy disappears.
Why we sit there
Not moving after you know isn’t laziness. In my experience, it’s usually one of three things.
The decision changes something you identified with. If a system you built is now the problem, fixing it means admitting it was the problem. That’s harder than it sounds.
The cost of acting is visible; the cost of not acting is invisible. Change has friction you can feel. The slow drain of inaction doesn’t register the same way, even when it’s larger.
You’re waiting for a version of yourself that’s never coming. The one who’s more certain, more ready, more at ease with the disruption. That version isn’t showing up. You’re already as ready as you’ll be.
What I actually did
I stopped asking “am I sure?” and started asking “what’s keeping me here?”
Different question. Better signal.
“Am I sure?” sends you back into the thinking loop — which is exactly where you don’t need to be.
“What’s keeping me here?” is honest. It points at the real friction. And the real friction is almost never more information. It’s usually discomfort, or identity, or the invisible cost of invisible inaction.
Once I named the actual reason I wasn’t moving, I moved.
It took about two hours to implement the change. It took three months to get out of my own way.
The pattern I keep seeing
This shows up in teams the same way it shows up in my own head.
The project no one closes out. The restructure everyone knows needs to happen. The conversation that gets drafted and unsent for a week.
Not because of missing information. Because of clarity that arrived and sat there, unclaimed.
Decisions don’t expire cleanly. They leak.
What I’m trying now
When I notice I’m holding a decision that feels “almost ready,” I give it a timer.
Not a vague “I should decide soon.” A specific time: by Tuesday noon, I’ve either made the call or written down explicitly why I haven’t.
Writing down why you haven’t is useful. It forces the actual reason to surface. And once the actual reason is named, it’s a lot harder to keep protecting it.
Clarity is only worth what you do with it.
I’ve left a lot of it on the table.
That’s the part I’m working on.