I spent three months waffling on a structural decision. Not because I didn’t know the answer — I did. Because every time I sat with it, I’d think of another angle, another edge case, another reason to wait one more week and see if new information arrived.
No new information arrived. I just kept thinking.
Then one Tuesday I got frustrated and decided the same thing I’d decided twelve weeks earlier, and shipped it that day. The friction I’d been holding all that time? It evaporated the moment I stopped treating the decision like it was still open.
The slowness trap
There’s a version of carefulness that’s actually avoidance dressed up as prudence.
I learned this by accident. A few months ago, I started shipping one-off decisions same-day instead of sleeping on them. Not rushing into them — I’d still think them through — but refusing to let them sit for a week. The pattern was: think, decide, move.
I expected this to blow up. Turns out, it didn’t.
What happened instead was stranger: the decisions were better. Not because I was thinking faster (if anything, I was thinking more clearly because I wasn’t carrying the dead weight of a half-made call). But because I’d removed the space where doubt lives.
Doubt is useful when you’re missing information. When you already have the information, doubt is just overhead. And the longer you sit with it, the more it feels like information.
Why slowness feels smart
I know where this comes from. Slowness feels responsible. In a world that values ship-fast culture, announcing that you’re taking time on a decision reads as thoughtful. It signals that you’re not being reckless.
Except sometimes the responsible thing is to move.
There’s a threshold where the cost of thinking another week outweighs the probability that new information will arrive. Past that threshold, waiting is reckless. It’s reckless because it delays the learning that only comes from the decision being live.
A decision you made three weeks ago and haven’t acted on yet? You’ve learned nothing from it. You’re just carrying it.
Act on it, and suddenly you know if you were right. You hit friction you didn’t see coming. You discover that one edge case you were worried about actually doesn’t matter in context. You find out the real problem was something else entirely.
Slowness buys you false certainty. Speed buys you real information.
The anxiety that masquerades as analysis
Here’s the uncomfortable part: most of my slow decisions weren’t slow because the decision was hard. They were slow because I was uncomfortable with the decision, and I’d learned that if I sat with discomfort long enough, sometimes it became curiosity, and curiosity feels more legitimate than doubt.
Doubt = I’m not sure. That sounds bad. Curiosity = There’s another angle to explore. That sounds thoughtful.
But they’re the same feeling. I’m just dressing one up as intellectual rigor.
The test is simple: when I finally make the decision, do I feel relief or do I feel afraid? Relief means I was sitting with uncertainty. Afraid means I’m about to move on something I don’t actually trust.
Most of the time, it’s relief.
What changed when I started shipping fast
When I moved faster, three things happened in sequence:
First: I discovered that most decisions don’t need a week. They need a decision. The difference is huge.
Second: I stopped building a narrative around indecision. When I sat for a week, I’d generate reasons why waiting was smart. “Let’s see if the market shifts.” “Let’s give the team time to raise new concerns.” Plausible-sounding reasons that were usually just delay dressed as strategy.
Third: The friction that felt like it was coming from the decision itself? It was coming from holding it. Once I shipped, it was just work. Work is fine. Held decisions are torture.
When slowness is actually right
I’m not arguing for recklessness. There are decisions that actually do need time. Decisions that affect how a team is structured. Decisions about who to work with or what to build. These are slow decisions and they should be.
But the slowness is in the thinking, not the announcement. You think for two weeks. Then you decide and you move. You don’t announce the decision and then think for two more weeks about whether you really meant it.
The distinction matters. One is due diligence. The other is performance.
The thing I’m still learning
Velocity isn’t recklessness until you start believing slowness is caution.
Then it becomes a trap. You move fast enough that you’re learning, but slow enough that you feel like you’re thinking. You’re in the middle zone where you get the worst of both worlds: no speed, no clarity, just spinning.
I’m getting better at asking: do I need another week, or do I need to move and learn?
Most of the time, the answer is move.
The week I was holding didn’t buy me certainty. It bought me anxiety. And I don’t need to ship that with every decision.
Some things you can’t know until you move. The longer I wait for that knowledge, the less I have.