The Hidden Cost of Waiting

One of the most common reasons projects stall isn't a lack of effort. It's waiting. Waiting for approval, for feedback, for requirements, for information, for the perfect plan, for a little more certainty (my personal kryptonite). At first glance waiting seems harmless. In practice it might be one of the most expensive kinds of delay in modern work.

Work rarely stops, it just slows down

Something I've learned running a lot of projects at once, sometimes more than I can honestly keep track of on a given Tuesday, is that progress is rarely blocked by nothing happening. It gets trapped in partial progress instead. The design is almost ready. The copy is nearly there. The strategy is mostly approved. The project looks active, and yet meaningful forward motion gets harder and harder to find. Everyone is busy, and the outcome just sits there. Those are the sneaky ones, because from the outside they don't look like a project stalling. They look like movement. They're just movement without much velocity.

Waiting creates invisible costs

The real problem isn't only the time spent waiting. It's everything that piles up around it. Context gets lost. Momentum fades. Priorities shift underneath you. Energy drains away. New work lands on top. People move on to other things and have to come back and rebuild their footing later. When you're the person juggling dozens of projects and campaigns at a time (hi, it's me), you feel this constantly, because a project you set down for a week is never as easy to pick back up as it was to put down. What looked like a one-day delay quietly becomes something much bigger, because restarting almost always costs more than continuing would have. That invisible cost rarely gets measured, but it is very real.

Progress creates information

A lot of the time, people wait because they're trying not to make a mistake. That's fair. Nobody wants to head off in the wrong direction. The catch is that uncertainty usually can't be talked away. A lot of questions only get answered by doing the thing. A draft shows you what needs work. A prototype shows you what isn't holding up. A test shows you whether your assumptions were right (they often aren't, and that's kind of the point). Progress generates information, and waiting usually doesn't. That's why the best teams I've worked with spend less energy chasing the perfect plan and more energy making the next useful version.

The myth of perfect timing

I've built enough things to know that perfect timing is mostly a story we tell ourselves. There's always going to be one more revision, one more stakeholder, one more risk, one more open question. Waiting for total certainty often just means waiting forever. That doesn't mean rushing, and it doesn't mean ignoring feedback or cutting corners on quality. It means accepting that a lot of decisions only get clearer once you're moving, not while you're standing still thinking about them.

Momentum is a strategic asset

Something I've come to appreciate more and more is the plain power of momentum. Momentum creates optimism. It creates learning. It creates visibility. It keeps people engaged. When progress is visible, teams get more confident, and when progress disappears, uncertainty rushes in to fill the space. Publishing twice a week has taught me this in my bones, because the schedule keeps things moving whether I feel ready or not (spoiler: I usually don't). Momentum isn't just a nice byproduct of good execution. It's one of the inputs.

What building continues to teach me

The longer I spend building things, the more I notice that progress and perfection are often pulling against each other. The goal was never to eliminate all uncertainty before acting. It's to learn quickly enough that the uncertainty shrinks as you move. That's why I've grown wary of waiting just for the sake of waiting. Sometimes patience really is the right call and timing really does matter. But a lot of the breakthroughs I've had only showed up after something moved from conversation into action. At some point, building actually requires building, and the cost of standing still is usually a lot higher than it looks.

Lessons from Building is an ongoing series on work, craft, curiosity, and the messy middle where ideas turn into things.