Where Did Each Of These Concepts Come From And What Problems Were Each Built To Solve?

Where These Systems Actually Came From, and What Problems They Were Built to Solve

Here’s the deal. None of what we teach at Elevate got invented in a vacuum. Every piece of it came from real jobsite experience, real training, and a genuine willingness to steal good ideas from wherever they existed. I want to walk through exactly where each piece came from, because understanding the origin makes the whole system easier to trust.

Where It Actually Started

Early in my career, working at DPR Construction and Hensel Phelps, I learned the Last Planner System, a collaborative planning approach that pulls trade partners into short interval planning so real commitments get made human to human, inside an integrated environment, rather than dictated from a schedule nobody actually agreed to. Hensel Phelps also ran something called short interval production scheduling, and I picked up enough of that early exposure to know, without yet having the right vocabulary for it, that what I was chasing was genuine flow.

I had a strong instinct from that experience that pre-construction planning mattered enormously, and I carried that instinct with me when I finally got the chance to run my own project as a superintendent.

The Project That Proved the System Worked

On the Bioscience Research Laboratory project, I pushed to implement everything I had learned, and I was told directly by my general superintendent at the time that I did not need eight to ten months to plan the job, that I needed to go build a few other projects first and prove myself before earning that kind of planning time. I disagreed, and I held my ground.

That project finished on time, on budget, and it went beautifully. I say this plainly because I want to be honest about what actually made that possible. I do not think I was necessarily better than anyone else at the time. I followed the systems, deliberately and completely. Pair a decent person with a great system, and you will win every single time.

Before implementing that project, I completed CM-BIM and CM-Lean training through the AGC, including a course specifically on Lean logistics. I was studying for my DBIA certification simultaneously, and I completed a planning, scheduling, and production planning program at DPR. I also read Paul Akers’s book 2 Second Lean and committed fully to applying everything I was learning, not selectively, but as one integrated approach. The result was a project people genuinely traveled from around the country to see, on time, under budget, with clients who became real advocates for the work.

Discovering What the System Actually Was

Once that project wrapped and I moved into general superintendent and field director roles, I started asking myself a real question. What was that system I had actually built? I knew the Last Planner System was part of it, but there was clearly more underneath it than I had a name for yet.

Partway through the project, I had been exposed to Takt terminology through a representative from a German Takt planning company, and while I do not agree with every aspect of how that company approaches Takt planning, the exposure to the terminology mattered. I also found the book How Big Things Get Done, which documented real research showing exactly why pre-construction planning mattered as much as it did. Put together, the real system was pre-construction planning, Takt, and the Last Planner System, working as one integrated approach rather than three separate ideas.

Building the Business Around What Actually Worked

I offered to bring this system into the company I was working for at the time, and the offer did not get much traction. Not long after, my wife Kate and I decided to start our own business instead. I cashed in my retirement to make it happen.

We began teaching superintendents, and quickly realized that training alone does not accomplish much without a real underlying system to teach against. That is where the Takt production system came from, named with help from an engineer colleague, built as construction’s equivalent to the Toyota production system. As we consulted on real projects with genuinely strong results, we recognized we also needed something formal for the Last Planner side of things, which eventually became its own trademarked system, alongside bringing project managers into the framework as well, since I had real experience in that role too.

Watch for these signs a company is trying to implement pieces of this without the full structure underneath it:

• Adopting Takt terminology without a real pre-construction planning process behind it
• Running Last Planner sessions disconnected from an actual Takt sequence
• Training superintendents without ever building the underlying system they are being trained to use

Why We Named It the Integrated Production Control System

The core insight underneath all of this is simple to state. A project only goes well if it is planned on a genuine rhythm, together with the trades actually doing the work. Three systems, pre-construction planning, Takt, and the Last Planner System, work together to make that possible, and we named the combination the Integrated Production Control System, because that name describes exactly what it does. We layered in additional frameworks on top of that foundation too, military strategy concepts, the fourteen principles of the Toyota Way, the theory of constraints, and Deming’s fourteen points, specifically to make sure the underlying philosophy was as thoroughly covered as possible.

The Pattern Underneath Every Successful Implementation

There is a broader pattern worth naming here, because a lot of advice in the Lean world tells people to start small, pick one system, and go slowly. I think that advice is largely wrong. A company genuinely needs four things together: a real business system, a real operating system, real training, and real field support.

The business system draws heavily from thinkers like Patrick Lencioni, Jim Collins, and Peter Drucker, whether a company chooses a framework like the table group model or an entrepreneurial operating system. The operating system is where our books live, since a company can genuinely buy the books and have that operating system in hand. Training is where our bootcamps came from, born directly out of the recognition that a system without trained people behind it does not hold. And field walks, meaning ongoing monthly implementation support, is where our project support services originated, because concepts taught once in a classroom rarely survive contact with a real jobsite without continued reinforcement.

Why Lean Logistics Exists

One more piece emerged later, almost as a byproduct of everything else. Implementing this system at scale required real physical supplies, printed field guides, boards, maps, pull planning kits, training materials. That need is what led to Lean Logistics, the company that now supplies exactly what a project needs to actually run this system in the field, not just understand it conceptually.

Today, this has grown into a genuine set of organizations working together, employing dozens of people across consulting, training, and logistics, plus a construction company and contractor’s license held in reserve specifically for companies interested in a joint venture or an industry showcase project.

Why We Built Any of This in the First Place

If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your organization implement this same integrated system, business system, operating system, training, and field support, rather than picking pieces of it in isolation. We offer consulting to help with business and operations, training through bootcamps and certification style programs, project support to help plan and run the actual work, and the supplies through Lean Logistics that make implementation genuinely practical rather than theoretical.

None of this exists purely as a business model. The actual problem we are trying to solve is helping people enjoy their families, protecting the workers who build our projects, and elevating this industry as a whole. Training elevates people, and stability elevates the system, and both of those things only happen when a real, integrated system is actually in place to support them.

So here is the challenge. If your organization has been implementing pieces of Lean thinking in isolation, a Takt board here, a Last Planner meeting there, without the business system, operating system, training, and field support that actually holds them together, that gap is exactly where to focus next. Piecing together fragments rarely produces the results a genuinely integrated system delivers.

Jason Schroeder said it plainly: “Pair a decent person with a great system, you’ll win every day.” Build the whole system, not just the pieces that look good individually.

On we go.

FAQ

What are the three core components of the Integrated Production Control System?
Pre-construction planning, Takt planning, and the Last Planner System, working together as one integrated approach rather than three separate initiatives. Pre-construction planning sets the foundation, Takt planning provides the time by location structure and rhythm, and the Last Planner System brings genuine trade partner collaboration into short interval planning, based on real human commitments.

Why does the article argue against the common advice to start small and pick one Lean system at a time?
Because a company genuinely needs a business system, an operating system, real training, and ongoing field support all working together, rather than isolated fragments. Adopting a single tool, like Takt boards or Last Planner meetings, without the underlying system and training behind it tends to produce a technique that looks good on paper but does not actually hold up once real project pressure hits.

How did the need for physical supplies and materials lead to a separate company?
Once training and project support scaled to real implementation, teams needed actual physical materials, printed field guides, boards, maps, and pull planning kits, to run the system day to day rather than just understand it conceptually. That practical need for supplies at scale is what led to creating a dedicated logistics company to provide exactly what a project needs to implement the system in the field.