The Hidden Cost of Waiting

When I was the quality assurance manager for a large can manufacturer, people had a saying: a mistake costs twice. Once when you make it, once when you remake it. I never agreed. Every time I heard it, I asked a different question: what about the can we never got to make because we were busy remaking the first?

The two ruined cans got counted, tracked, and paid for. The third can — the good one we never made because the remake consumed the shift — never showed up anywhere. Nobody wrote it down. Nobody could, because nobody could see it.

Waiting doesn’t cost you time. It costs you whatever didn’t get made while you were waiting.

The same principle applies everywhere, not just in manufacturing. An employee waiting on an approval isn’t losing minutes — they’re not shipping the order sitting behind that approval. A truck waiting at a dock isn’t losing time — it’s not delivering the next load. Information sitting unread isn’t just unread — it’s a decision nobody is making. Different asset, same question: what would have been made, delivered, decided, or accomplished if this hadn’t been sitting still?

Organizations are good at measuring the wait itself — how long the truck sat, how long the remake took. They almost never measure what the truck should have delivered during that time, or what the production line should have produced instead of a rework. That’s not a gap in the reporting. It’s the entire cost, sitting just outside of it.

Because that cost is invisible, the blame often lands where it shouldn’t: on the person doing the waiting. Waiting rarely means someone is careless or slow. It usually means a system stopped creating value somewhere upstream — an approval nobody owns, information that never got passed along, a process nobody intentionally designed. Find what’s actually broken, and you’ll find exactly where value stopped being created.

Not all waiting is waste. Waiting for a quality retest protects value because it keeps a defective product from reaching a customer. Waiting for a safety inspection protects people. Waiting for better information before making a million-dollar decision protects the organization from making an expensive mistake. But a purchase order sitting on someone’s desk for three days because nobody knows who’s authorized to approve it protects nothing. The materials don’t arrive. The project doesn’t start. No value is being protected — value is simply not being created. That’s the line worth drawing: does the wait protect value, or does it prevent value from being created?

That second kind of waiting compounds. A batch gets flagged for rework. Before anyone can deal with it, the next batch comes off the line needing attention, so the first batch waits. By the time someone gets back to it, a third batch has stacked up behind it. Nobody on that line is working slowly — they can only work on one batch at a time. The system handed them overlapping work with no way to sequence it, so something inevitably loses its place. Whatever that batch was supposed to become — that’s the hidden cost.

Many organizations respond by hiring more people. That rarely solves the problem. If your employees are waiting on approvals, information, or decisions, another employee simply joins the same line, and now you have two people’s worth of capacity trapped by the same broken process. Fix the process first. Then decide whether you actually need another person.

Organizations that manage waiting well don’t eliminate it — they design around it. An approval routes through DocuSign instead of sitting on someone’s desk. A leader delegates authority before leaving town instead of letting decisions pile up. Information is gathered before the work begins instead of forcing people to stop halfway through a task to hunt for it. In every case, the design decision is really about one thing: keeping value moving.

That’s why I stopped asking, “Where are people waiting?” and started asking, “What asset is waiting — and why?” Four different waits in four different departments often trace back to one missing process. Fix that one process, and four streams of stalled work begin moving again.

I still think about that third can. Nobody ever put a number on it. It never appeared in a report. It never came up during a review. It never got mentioned when someone praised the team for catching the defect and remaking the part correctly. But it was always there — the one thing we never created because we were busy fixing what we’d already created once.

That’s the only question worth asking about any delay: what didn’t get made because we waited?