Lean Onboarding Series – Bottlenecks

Forming a Bridge on Level Three

On one project, an elevated concrete deck sat on level three with nothing underneath it, no level one or level two to support conventional formwork. The crew had to build high-bay formwork towers, laced and braced together to support a deck suspended well above open space, essentially forming something closer to a bridge than a typical floor. Work had been moving smoothly from deck to deck until it hit this one zone, where everything genuinely slowed down, not because anyone was doing anything wrong, but because the nature of that specific scope was simply harder than everything around it.

The Real Pain: Assuming a Slow Trade or Zone Means Someone’s Doing Something Wrong

The real pain is the natural, mistaken assumption that a slow-moving trade or a difficult zone automatically reflects poor performance. In reality, some scopes of work are inherently slower by nature, regardless of how skilled the crew handling them actually is. Complex mechanical systems, with piping, ductwork, hangers, devices, and controls all needing to tie together, tend to move more slowly simply because of how much genuinely has to happen. Taping drywall requires real drying and sanding time no crew can rush past. Specialty flooring often takes considerably longer than something like basic carpet tile. None of this reflects a problem with the people doing the work.

The Failure Pattern: Fixing a Bottleneck Once and Assuming You’re Done

The failure pattern is treating bottleneck-hunting as a single, one-time fix rather than an ongoing, continuous process. Once one bottleneck gets genuinely optimized or resolved, a new one reliably emerges somewhere else. This is not a sign that the original fix failed. It reflects a real, consistent pattern worth understanding directly: every project will have bottlenecks, whether in a trade, a specific zone, or even in the flow of information or materials to the site.

A few common places bottlenecks tend to show up on a construction project are worth naming directly:

• Inherently complex trade scopes, like mechanical systems or specialty finishes, that require more time by their very nature.
• Specific zones with unusually difficult conditions, like complex formwork or challenging site logistics.
• The flow of information or materials reaching the project site, which can bottleneck just as easily as physical work itself.

This Isn’t About Blaming the Slow Trade, It’s About Recognizing Where Real Improvement Lives

None of this is about calling out a trade as bad or incompetent. Even the most skilled, capable crew in the world can still be the bottleneck, simply because of the nature of their specific scope of work. The real purpose of identifying a bottleneck is not assigning blame, it is knowing exactly where to focus genuine improvement effort next.

Not All Bottlenecks Are Bad: The Hot Sauce Bottle

Here is a useful reframe worth understanding directly. Picture a hot sauce bottle and a beer bottle, each with a differently sized neck, deliberately designed that way on purpose. Put a hot sauce bottle’s narrow neck on a beer bottle, and drinking it becomes frustratingly slow. Put a beer bottle’s wider neck on hot sauce, and you get far more than you actually wanted, possibly a mouth full of unexpected heat. Bottlenecks are not inherently bad. They exist to regulate flow appropriately, and the goal is sizing them correctly for what actually needs to move through them, not eliminating every constraint indiscriminately.

Why It Matters: Pushing Harder Doesn’t Widen the Hose

This matters directly because of a simple, physical truth worth carrying into every constrained situation on a project. Picture a garden hose with its spray nozzle only partially open. No amount of additional water pressure behind that nozzle increases how much water actually comes out the other end. The only way to genuinely increase that flow is to open the nozzle itself, widening the actual constraint.

The same logic applies directly to a bottleneck trade or zone. Pushing harder, adding pressure, or throwing more resources at the system around a bottleneck does not speed anything up. Only genuinely optimizing, adding capacity to, or otherwise widening the actual bottleneck itself produces real improvement.

Teach the Framework: The Law of Bottlenecks

A genuine, recognized principle applies here, worth stating plainly: every project will have bottlenecks. Once an identified bottleneck gets optimized, improved, or removed, a new one will reliably emerge to take its place. This means bottleneck-hunting is a continuous, ongoing process, never a single milestone to check off and move past permanently.

The practical response follows directly from this law. Once a bottleneck trade or zone is identified, whether that means speeding up a slow process, adding another crew, or otherwise adjusting its productivity rate, real effort should go toward genuinely widening that specific constraint. Once that bottleneck improves, the next one should be actively sought out immediately, rather than assuming the work of improvement is finished.

A few practical steps help identify and address a genuine bottleneck once it is found, and they are worth naming directly:

• Confirm the constraint is genuinely inherent to the scope or zone itself, rather than a symptom of poor preparation or a lack of resources elsewhere.
• Focus real effort specifically on widening that bottleneck, additional capacity, faster methods, more crews, rather than simply adding pressure to the surrounding system.
• Once that bottleneck improves, immediately begin looking for the next slowest trade, zone, or process, since another one will reliably emerge.

Turning This Into Daily Practice

Build a consistent habit of asking directly, what is our slowest trade, zone, or process right now, rather than assuming last month’s fix solved the problem permanently. When a genuine bottleneck is identified, direct real effort toward widening it specifically, rather than pushing more general pressure, more people, more urgency, onto the system as a whole.

Connecting It Back to Building People, Not Just Projects

None of this happens without leaders willing to treat bottleneck-hunting as a genuine, ongoing discipline rather than a problem to solve once and move past. Building that continuous improvement habit directly into how a project runs is exactly what keeps real progress happening long after the first obvious constraint gets resolved.

If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams build the kind of ongoing bottleneck identification that drives genuine, sustained improvement.

The Challenge

So here is the challenge worth carrying onto your next project: identify your current slowest trade, zone, or process, focus real effort on widening that specific constraint, and then immediately start looking for the next one. As Jason put it plainly, “The only thing you can do to increase the flow is to open up that nozzle and open up that bottleneck.” On we go.

FAQ

Does being a “bottleneck trade” mean that trade is performing poorly?

No. Some scopes of work, like complex mechanical systems or specialty finishes requiring real drying time, are inherently slower by nature regardless of how skilled the crew handling them is. Identifying a bottleneck is about knowing where to focus improvement effort, not assigning blame to the people doing the work.

Why does fixing one bottleneck just reveal another one?

This reflects a genuine, consistent pattern in how projects function: once one constraint gets optimized or resolved, a new one reliably emerges somewhere else in the process. Bottleneck-hunting is therefore a continuous, ongoing discipline, not a single fix to complete and move past.

Why doesn’t adding more pressure or resources to a bottleneck actually speed it up?

Much like a garden hose with a partially closed nozzle, additional pressure behind a genuine constraint does not increase the flow coming out the other side. Real improvement only comes from directly widening the actual bottleneck itself, whether through added capacity, faster methods, or additional crews.

Are all bottlenecks something that should be eliminated?

Not necessarily. Some constraints exist deliberately to regulate flow appropriately, much like a hot sauce bottle and a beer bottle have differently sized necks on purpose. The goal is sizing a bottleneck correctly for what actually needs to move through it, not eliminating every constraint indiscriminately.

Where besides trades and zones can bottlenecks show up on a construction project?

Bottlenecks can appear in the flow of information or materials reaching the project site, not just in physical trade work or specific zones. Any point where flow slows down relative to the rest of the project deserves the same kind of attention and improvement effort.