New Constraints Reveal System Bottlenecks.

If You Are Not Finding a New Constraint, You Have Not Optimized the Last One

Here’s the deal. I recently had a realization that genuinely excited me, and it came from the most unexpected place, running out of knee pads at one of our own training bootcamps. That small, almost silly problem turned out to reveal something important about how real continuous improvement actually works.

A Problem We Had Never Had Before

At a recent bootcamp, class sizes had grown, and I had made real improvements to how our physical training models were built, specifically by pre-cutting sections so teams could spend far more of their time on genuine logistics planning rather than basic fabrication. The session ran smoothly. Then my dad, who was helping run the event, pointed out that people were missing knee pads and tools. We simply did not have enough to go around, something that had never happened at any previous bootcamp.

At first, that felt like a straightforward equipment shortage. Looking closer, it was actually proof of something much bigger.

I had spent years slowly refining these bootcamps without ever hitting a genuine supply problem like this one. The fact that it showed up now, right after a real improvement to how teams built their models, was not a coincidence. It was a direct signal that something underneath the surface had genuinely changed.

Why Standardization Is What Makes Improvement Possible

We have standardized nearly everything about how these bootcamps run. Standard presentation files. Standard outlines. Standard work for setup and teardown. Standard processes for nearly every piece of the event. That level of standardization is exactly what has let us make so many improvements, sometimes in real time during a single event, and sometimes as major overhauls between one bootcamp and the next, that it genuinely becomes hard to keep track of them all.

The teams at this particular bootcamp were so well prepared, the content so clear, and the supplies so easy to use, that they moved through the model building process noticeably faster than ever before, spending more of their actual time together as a team rather than struggling with the mechanics of assembly. That speed is exactly what created the sudden tool shortage. Not because we planned poorly, but because we had genuinely gotten faster.

The Law of Bottlenecks

This is where it clicked for me. Every system has a limiting factor, a genuine bottleneck, and once you find and optimize it, another one will show up in its place. That principle, closely tied to Eliyahu Goldratt’s work on the theory of constraints and explored further by researchers like Niklas Modig, means something specific and genuinely useful. If you are not finding a new bottleneck after resolving the last one, that is not actually a sign of success. It usually means the original bottleneck was never fully optimized in the first place.

Running out of tools proved two things simultaneously. First, our original constraint, the model building and pre-planning process itself, really had been genuinely optimized, since teams were now moving through it noticeably faster than before. Second, a brand new constraint had emerged in its place, our actual physical tool supply, and now I had a clear, specific target to solve before the next event.

Watch for these signs a previous bottleneck was never actually optimized, even if it looks resolved on paper.

• The same recurring complaint keeps showing up in a slightly different form, rather than genuinely disappearing.
• No measurable improvement in speed or output after the supposed fix was implemented.
• No new limiting factor ever emerges, months after a change was made, suggesting nothing actually shifted underneath it.

Why a New Constraint Is Actually Good News

I solved the immediate tool shortage quickly, getting extra supplies delivered before the next event and making sure we had more than enough going forward. The more important realization was recognizing that discovering this new constraint was genuine proof of progress, not a setback. I now have a clear next target to optimize, and once that gets solved, I fully expect a third constraint to reveal itself at the following bootcamp. Finding out exactly what that turns out to be is honestly one of the more exciting parts of running this training.

That mindset shift matters more than the specific fix itself. Plenty of leaders would have looked at a tool shortage and simply ordered more tools, closing the loop without ever asking what that shortage actually revealed about the rest of the system. Treating it instead as data about where the next real constraint lives is what keeps this whole cycle moving forward rather than stalling out after the first visible win.

Watch for these signs your own continuous improvement process is actually working the way it should.

• A newly discovered limiting factor that is genuinely different from the one you just solved, rather than a repeat of the same underlying issue.
• Teams or processes measurably faster or more effective than before, even if that speed reveals a new gap elsewhere.
• A growing willingness to treat each new constraint as a signal of real progress rather than a frustrating setback.

Why We Have Barely Scratched the Surface

Even after training thousands of people through these bootcamps, I genuinely believe we have barely scratched the surface of what this training can become. The audio system. The headsets. The floor layout. The music. The level of automation behind the scenes. The specific Lean examples we use to teach each concept. Every one of those is a place a future constraint is likely still waiting to be discovered and optimized.

My goal is for this to become the best training available anywhere in the world, the kind where people look at it and genuinely cannot imagine how it could be topped. And even once we reach that point, I expect it will still only be the beginning, because that level of standardization tends to open up an entirely new world of improvements nobody could have anticipated from where we currently stand.

Applying This Same Discipline to Your Own Project

None of this only applies to running a training bootcamp. The exact same law of bottlenecks applies to a construction schedule, a pre-construction process, or any recurring system your team runs repeatedly. Solve one constraint, and if nothing new ever surfaces afterward, that silence is worth investigating rather than celebrating.

A Takt plan works exactly the same way. Optimize the first bottleneck holding a phase back, and a genuinely faster, better coordinated crew will almost always run straight into whatever the next limiting factor happens to be, whether that is material staging, a specific trade’s capacity, or a piece of equipment shared across too many zones. Expecting that next constraint, rather than being surprised by it, is what separates a team that keeps improving from one that quietly stalls after its first success.

If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your teams build the genuine standardization that makes this kind of continuous, compounding improvement possible, rather than settling for a single fix and assuming the work is finished.

So here is the challenge. Think about the last constraint your team genuinely solved. Has a new one shown up since then. If the honest answer is no, that silence deserves a second look, because it may mean the original fix never actually took hold the way everyone assumed it had.

Jason Schroeder said it plainly: “If you’re not finding a new bottleneck, you haven’t actually optimized the first one.” Keep looking for the next constraint, and treat finding it as the genuine sign of progress it actually is.

On we go.

FAQ

Why does discovering a new constraint count as evidence that the previous one was actually solved?

Because a genuinely optimized system moves faster or performs better than before, and that improved performance naturally exposes whatever limiting factor comes next in line. If no new constraint ever appears after a supposed fix, it often means the underlying process never actually sped up or improved in a way that could reveal the next bottleneck.

Why does standardization enable more improvement rather than locking a process in place?

Because a standardized process gives everyone a shared, documented starting point, which makes it possible to identify exactly what changed when something improves or breaks down. Without that shared baseline, it becomes far harder to isolate which specific change actually caused an improvement, which slows down the entire cycle of finding and solving the next constraint.

What should a team do when a newly discovered constraint feels like a step backward rather than progress?

Recognize that the constraint itself is evidence the previous fix genuinely worked, since a truly unresolved system would keep producing the same old problem rather than revealing a new one. Reframing a new constraint as a sign of real progress, rather than a frustrating setback, is what keeps a team motivated to continue the cycle of improvement rather than treating each new problem as a failure.

Why is it significant that a team can trace a tool shortage directly back to a genuine process improvement?

Because it demonstrates the constraint moved location within the system rather than disappearing entirely, which is exactly what the law of bottlenecks predicts. Tracing that connection clearly, from a specific improvement to a specific new limitation, shows the team is genuinely diagnosing its own system correctly rather than guessing at unrelated fixes.