I’ve been sitting on a decision for six weeks. Not because I don’t know what to do. Because I’m waiting for it to become obvious.
The setup is simple: we have two paths forward on a product feature. One is fast and incomplete. One is slower and more complete. I’ve run the math twice. I’ve asked the team. I’ve read the edges. And I still haven’t decided, because some part of me believes that if I wait long enough, the answer will crystallize and I won’t have to choose.
It won’t. And waiting is costing me more than either path forward would.
The decision that decays
Here’s what actually happens when you postpone a decision: it doesn’t get clearer. It gets older.
Six weeks in, we have three incomplete features on the branch because the team has been working under uncertainty. They’re hedging their bets, building context for both paths, not committing to architecture that assumes one direction. They’re moving slower and producing less because the decision is pending.
It’s not that they’re waiting for me. It’s that they’re spending energy deciding for every subtask whether it should assume path A or path B. That’s the real cost of the open decision — every single line of code carries the weight of “but what if we go the other way?”
The clarity I’m waiting for would reduce that friction. Except the clarity isn’t coming from waiting. It’s going to come from deciding, implementing, learning, and adjusting.
I’ve been waiting for the learning without doing the implementation.
The urgency you avoid becomes urgency you inherit
When you hold a decision open too long, you don’t gain time. You spend time. And then you inherit the consequences of that spending.
The six-week delay meant we missed a release window. Now the feature is creeping into a more critical timeline. Now the pressure is higher. Now the stakes feel different, which means I’m more reluctant to decide, because the consequences feel bigger.
But the consequences aren’t actually bigger. They’re the same. What’s bigger is my awareness of them, because I’m now running into hard deadlines I didn’t have six weeks ago.
This is the trap: delayed decisions don’t stay small. They accumulate pressure. The longer you wait, the more work is piling up in front of them, and the more you feel like you can’t afford to be wrong.
You become paralyzed by the cost of the delayed decision, not the quality of the decision itself.
What waiting actually costs
Let me be specific about what six weeks of “waiting for clarity” has cost:
- Team output: Three engineers building on uncertain ground is less output than three engineers building on a clear path, even if that path turns out to be wrong.
- Technical debt: Because the team wasn’t committing to either path, they built generality into places that should have been specific. That generality will have to be ripped out or worked around.
- Decision fatigue: I’ve revisited this decision so many times in my head that I’m now much more doubtful than I was six weeks ago. The uncertainty I created by waiting is now worse than the risk of being wrong.
- Team frustration: They don’t see the deliberation. They see a decision not being made, and it creates a background hum of “why aren’t we moving?”
The clarity I was waiting for? It doesn’t exist in the waiting. It would only exist in the doing.
The decision made badly beats the decision not made
Here’s what I’m learning: a clear wrong decision is usually better than a held good decision.
Not because wrong decisions are good. They’re not. But because a wrong decision you implement, learn from, and adjust is still a path forward. A held decision that you’re trying to get “right” is a path that stops.
In this case, I should just pick a path. Implement it. Get feedback from how it actually works. Then adjust. That cycle — pick, do, learn, adjust — takes four weeks. The cycle of “wait for perfect clarity” has already taken six weeks and produced nothing.
Even if I pick wrong, the cost of being wrong and adjusting is probably less than the cost of waiting another six weeks while three people work on two paths that don’t fully exist yet.
The permission I had to give myself
The thing that finally broke the paralysis was admitting this: I don’t have enough information to make a perfect decision, and I’m not going to get it by waiting.
The only information I’m going to get is from building one thing and seeing how it responds.
So I made a call this morning. We’re going with the faster path. If it doesn’t hold up, we’ll know in two weeks. Then we rearchitect. The cost of being wrong and correcting is lower than the cost of waiting for certainty that doesn’t exist.
This wasn’t some flash of insight. It was just: I’m tired of waiting, the cost of waiting is now visible, and the cost of being wrong is bounded.
The rhythm of real decisions
I’m starting to notice a pattern with myself: I’m good at making decisions when there’s a clear deadline. Bad at making them when there’s flexibility. The flexibility makes me believe I can wait for clarity. The deadline forces me to work with incomplete information.
I hate deadlines. But they’re clearly better for me than open-ended problems.
So now I’m trying to build fake ones. When I catch myself waiting for clarity that isn’t coming, I ask: “What happens if I decide in 24 hours?” The answer usually is: nothing terrible. The decision barely matters enough to wait. And that realization is usually what releases me from the paralysis.
This six-week delay taught me something simple: waiting for clarity is the most expensive way to buy nothing.
The cost of waiting for clarity is higher than the cost of being clear about your uncertainty, making a decision anyway, and then responding to what you learn.
I should have decided six weeks ago. I didn’t. Now I’m deciding. And what I’m not doing is waiting any longer.