The Takt Production System – Part 4

Read 28 min

The Traffic Jam That Revealed What’s Really Broken in Construction

Olivia was the youngest director at Evergreen Construction, but not because she was favored or especially lucky. Her performance was almost always spot-on, and she had a rare ability to disarm even the most volatile of situations, connect with people on a deeper level, and create a sense of calm. She loved her work, and her unique high energy permeated her projects.

Being a fifth-generation builder, she firmly believed that building was in her blood. By all accounts, Olivia was born to be a builder. She knew what she was doing, and she expected her team to as well. There were never any casualties and few deviations or missteps. She was masterful when organizing the chaos and madness of the project and turning it into a success.

But right now she found herself concurrently overseeing eight projects and her presence was stretched too thin to be effective. While her supervisors had complete confidence in her, she was becoming uncharacteristically stressed and uncertain. How could she maintain success on so many projects at once if she wasn’t physically present? How could she train and mentor others to lead these projects in a way that would replicate her stability and create a reassuring atmosphere for the teams and owners? This is where most construction leaders find themselves: heroically managing chaos on multiple projects, knowing there’s a better way but unable to see what it is.

When the Best People Still Can’t Make It Work

One project in particular was becoming increasingly concerning to Olivia. The $150 million hospital was with one of the most important clients Evergreen Construction had ever landed: One Care Health. Olivia knew the project team was made up of some of the best at Evergreen. Experienced PEs, energetic field engineers, and a hungry, motivated team of leaders that had proven unstoppable on previous projects.

Brad, the superintendent, was driven and competent. He demanded respect and received it without resorting to outdated and controlling tactics. At 45, Brad knew it all, the office, the field, integration, design, and a wide range of skills. He was a genuinely superior leader. The project manager, Paul, was in his 30s with a little less experience but shared Brad’s passion for excellence. They were a good team, and they knew what they were doing. But this would prove to be no ordinary project.

The project had gone well from the start and things mobilized quickly. The team worked cohesively and Olivia was once again credited for driving the success in overcoming project obstacles and roadblocks. In fact, she had been sold as the senior project manager on the project and was the main reason the company had won the proposal.

However, as authority began to transition from Olivia to the on-site superintendent and project manager, things began to unravel. Undetectable at first, the drift toward instability became obvious as certain deadlines slipped. The team morale started to decline and they began to have safety incidents. As new projects demanded her attention, Olivia was only able to stay with the team for about three months. Olivia and the Evergreen CEO were in agreement that Brad and Paul would have to step up.

The Warning Shot: When Safety Reports Reveal Deeper Problems

Olivia was preparing for an interview with another hospital when she received a call from Jeff, the senior vice president with One Care’s construction team. After exchanging pleasantries, Jeff broke the news that the insurance carrier safety inspection hadn’t gone well. He wanted to let Olivia know that he would be discussing the reports with a wider group of construction project managers who governed all of One Care’s projects. The warning was loud and clear: no more safety reports or there would be no future opportunity for Evergreen Construction to partner with One Care.

Despite the fact that Olivia should be focusing on the upcoming bid proposal and interview, Jeff’s call overshadowed everything else that day. It was difficult not to be angry about the situation. The team had all the skills they needed. They had the training. They had past successes. They had implemented Last Planner and Scrum concepts. Contracts were in place and the best trades were selected. So what was the problem? Olivia had all the pieces to the puzzle laid out in front of her, but she couldn’t fit them together.

This is the crisis most construction leaders face: you have competent people, proven systems, good contracts, selected trades, and projects still spiral into chaos, delays, and safety incidents. The conventional wisdom says it’s an execution problem. The truth is deeper.

The Interview Where Everything Fell Apart

When the day of the proposal arrived, Olivia continued to be uneasy about the struggling One Care project. However, she had to move forward with Evergreen’s proposal. The interview with Encompass Medical was for a $185 million hospital only 20 miles away from the One Care project she was building with Brad and Paul.

It would be a strategic win for the company and especially for the teams coming off other projects in eight months. Everyone felt the pressure and the burden of winning this mega project. The additional load to win their first landmark hospital with this client seemed almost unfair to the interview team. Olivia had concerns that the issues plaguing the One Care hospital would have the potential to show up with this hospital as well. It was difficult to muster her usual enthusiasm, and it had begun to disrupt her sleep.

Having solidified their strategy the night before, the team was set to arrive at Encompass Medical by 9:30 for a 10:00 interview. Olivia was preparing with her visuals and talking points, and she soon felt a familiar and welcome sense of control. She let the energy of the day push aside her stress and worry. This had the potential to be a remarkable day.

As she visualized her section of their presentation, Brad, Paul, and Abby, Evergreen’s lean guru, arrived and began to quietly prepare as they waited for the rest of the team. Olivia was pulled from her thoughts when her phone vibrated with an incoming text from Juan, the regional scheduling manager: “So sorry, traffic is the worst. Accident cleanup. Be there in less than 10.”

Olivia glanced again at her phone and saw that it was already 20 minutes till 10:00. Setup was supposed to happen in five minutes, and the opportunity to huddle as a team to focus and center was ticking away. She obsessively checked her phone several times over the course of the next 10 minutes. There were seven minutes to spare when Juan rushed into the room carrying his presentation supplies and visuals. “What a nightmare. Traffic was stop and go the entire way. Are we okay for time?” Juan asked, red-faced and slightly out of breath.

“We have to be,” Olivia said, hoping the words didn’t come out sounding as curt to his ears as they did to hers. She was wise enough to focus on the situation and not on Juan. As the team hurried to set up, everything they had planned was completely thrown into disarray. The Encompass Medical selection committee usually enjoyed greeting groups before the proposal interviews but had to wait in the hall while Evergreen rushed to finalize their preparation. Olivia, by now visibly agitated, scrambled to organize the members with no time to rally and refocus the group. They had no alternative but to move forward and pitch their proposal.

The Moment When Competence Isn’t Enough

When the selection panel entered, the tension in the room was palpable. Abby, with her infectious laugh that often helped set the tone for the rest of the team, was oddly quiet. She seemed down this morning, but Olivia hadn’t taken the time to chat, and now she wished she would have. Juan still seemed flustered about his late arrival. The energy that Olivia had come to expect from this team was missing. No inroads were made with the stiff members of the selection panel. By the time introductions were made and everyone took their seats, Olivia was certain that Evergreen would not be asked to partner with Encompass Medical.

The group wasn’t functioning as a team. They seemed more like uncomfortable strangers who had been thrown into a room together. Though Olivia and the team members began to find their footing, she had a shrinking feeling that it was too late. They could not overcome their dismal first impression. She was pleased that evergreen finished strong and left with their heads held high, but the parting thank-yous from the selection panel seemed perfunctory rather than congratulatory. They sounded more like goodbyes and condolences. The team just knew.

“Team, we did the best we could, and I appreciate everyone’s efforts. We’ll wait to hear back,” Olivia said in the most positive tone she could muster. Juan remained by her side to talk. “Olivia, I’m so sorry I was late. That damn traffic. Everybody tailgating and speeding up every chance they got. I wish I had a way to regulate the speed of every car so traffic wouldn’t get all congested and no one would get hurt. And I wish I would have just left earlier.” She placed a reassuring hand on his arm. “It’s not your fault, Juan. I’m glad you were safe and I appreciate you coming through. We’ll just have to wait and see what happens now.”

The Pattern Hidden in Plain Sight

As the group made their way to the parking lot, Olivia began to analyze the situation. She knew not to blame people, but instinct and experience told her they were going to lose that bid. She just wished she knew why. As her mind sought an answer, she kept thinking about what Juan said about regulating drivers. There was a familiar theme with it somehow. Traffic, traffic jams, being late, speeding, distance, space between. It all seemed to trigger something, but she couldn’t quite grasp it.

Her intuition told her Juan might be a good sounding board to help her figure it out. He not only knew everything about CPM scheduling, he’d also had a front row seat at the interview, which she was already thinking of as a complete train wreck. She hurried to catch up to him in the hallway. “Hey, Juan, do you have time to get lunch? I’m trying to figure something out and could really use your insight.” He smiled for the first time all morning. “Absolutely. Right now.”

Here’s what Olivia is beginning to sense but can’t yet articulate: the same forces that create traffic jams create project chaos. When everyone speeds up and slows down randomly, when there’s no rhythm to the flow, when space between vehicles collapses and expands unpredictably, the whole system breaks down. One accident, one delay, cascades through the entire chain. And that’s exactly what’s happening on her projects. Brad and Paul are competent. The trades are skilled. The contracts are solid. But without flow, without a regulated rhythm that creates stability, competence can’t overcome chaos.

What Makes This Different From Every Other Construction Story

Most construction narratives focus on execution: work harder, plan better, hold people more accountable, implement another system. Olivia’s story is different because she already has all of that. Her people are the best. Her systems are proven. Her execution is normally flawless. What’s breaking isn’t the people or the effort. What’s breaking is the fundamental approach to scheduling and flow. CPM creates traffic jams. It slams everything to the left, calculates float that encourages random movement, hides crew ties in complexity, and gives false confidence through excessive detail.

The system itself, not the people using it, is creating the instability that leads to safety incidents, blown deadlines, lost bids, and burned-out leaders like Olivia who are stretched across eight projects trying to heroically manage chaos. Southwest Airlines, the company that let Olivia’s kids announce the flight and sit in the cockpit, understands this. They built a lean culture centered on taking care of people and customers. A culture of happiness, joy, and love. They don’t rely on heroes. They rely on systems that create flow.

Construction can have that too. But it requires seeing what Olivia is beginning to see: that regulating the speed and rhythm of work, creating flow instead of pushing, is what actually creates stability. If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow.

FAQ

Q: Why did Olivia’s project with Brad and Paul fall apart when they had all the right pieces?

Because competence, training, and good intentions can’t overcome a broken scheduling system. They had skilled people, Last Planner and Scrum concepts, good contracts, and selected trades—but without flow, all of that collapses under variability. When authority transitioned from Olivia to Brad and Paul, the instability that was always present but masked by Olivia’s heroic management became visible. Deadlines slipped, morale declined, safety incidents increased. The system was creating chaos that no amount of individual competence could overcome.

Q: What does Juan’s comment about traffic have to do with construction scheduling?

Everything. Juan wished he “had a way to regulate the speed of every car so traffic wouldn’t get all congested and no one would get hurt.” That’s exactly what’s missing in construction: regulated rhythm and flow. When drivers speed up and slow down randomly, when space between vehicles is unpredictable, when everyone tailgates and rushes, and one accident cascades through the entire system. CPM scheduling creates the same dynamic, random movement based on float calculations, activities that speed up and slow down, no regulated rhythm. The result is congestion, delays, and incidents. Flow regulation solves both problems.

Q: Why couldn’t Olivia maintain success across eight projects?

Because her success was built on heroic individual management, not on systems that create flow. She had a rare ability to disarm situations, connect with people, and create calm, but that doesn’t scale. When she was physically present for three months, projects worked. When she had to spread herself across eight projects, the instability underneath became obvious. You can’t scale heroics. You can only scale systems. Until Evergreen builds systems that create flow without requiring Olivia’s presence, they’ll keep losing projects and burning out their best leaders.

Q: What was actually broken if they had implemented Last Planner and Scrum?

Last Planner and Scrum are short-interval production control methods—the short sword. But without a master schedule that creates flow first, the long sword, they can’t overcome the chaos created by CPM. You need both: Takt planning to create the rhythmic flow and stable environment, then Last Planner or Scrum to manage execution within that flow. Implementing collaborative planning tools on top of a CPM schedule that pushes and creates instability is like trying to have productive huddles during a traffic jam. The underlying system is still broken.

Q: How does the Southwest Airlines story connect to construction?

Southwest built a lean culture that doesn’t rely on heroes, it relies on systems that create flow and take care of people. When pilots let kids announce flights, that’s not random kindness, it’s cultural DNA built on respect for people and creating joy in the system. Construction tries to rely on heroic superintendents and project managers to overcome broken scheduling systems. That’s why Olivia is stretched across eight projects and stressed. Southwest shows that when you build the right systems with the right culture, remarkable experiences happen naturally without requiring individual heroics every time.

On we go.

If you want to learn more we have:

-Takt Virtual Training: (Click here)
-Check out our Youtube channel for more info: (Click here) 
-Listen to the Elevate Construction podcast: (Click here) 
-Check out our training programs and certifications: (Click here)
-The Takt Book: (Click here)

Discover Jason’s Expertise:

Meet Jason Schroeder, the driving force behind Elevate Construction IST. As the company’s owner and principal consultant, he’s dedicated to taking construction to new heights. With a wealth of industry experience, he’s crafted the Field Engineer Boot Camp and Superintendent Boot Camp – intensive training programs engineered to cultivate top-tier leaders capable of steering their teams towards success. Jason’s vision? To expand his training initiatives across the nation, empowering construction firms to soar to unprecedented levels of excellence.

On we go

The Takt Production System – Part 3

Read 29 min

The Urinal Test: Why CPM Is a Broken System You’ve Learned to Work Around

Here’s a graphic but accurate analogy: most construction scheduling is like a poorly designed airport urinal. It’s disgusting, there’s always a mess on the floor, and people keep stepping in puddles. The manufacturers keep selling inferior products without caring for the end customer. And when you point out the problem, they say “if people would just aim right, there would be no problem.” Granted. And yet we still have a mess everywhere.

Conversely, there are urinals that work very well, upward-facing bowl shapes that hardly allow any mess. It’s hard to use them incorrectly. You rarely see a mess with this type. Why do they work? Because there’s absolutely no friction in the process of getting it right. It just happens naturally, regardless of how they’re used.

Could someone mess it up if they wanted to? Yes, but they’d have to be trying to get it wrong. Could someone use the first urinals right? Yes, I guess so. So what’s the difference? On a large scale, one is practical and works for the masses with little friction, and the other results in a mess.

If we want to keep stepping in puddles, let’s not change and let’s keep blaming the people. But if we want an easy, clean, and neutral experience, let’s get the proper units and process and help the people to win as a group. That’s the urinal depiction of CPM. And it perfectly summarizes why the system is fundamentally broken.

The Current State: Three-Week Look-Aheads and Crash Landings

Right now, the industry standard is to plan the project with CPM, print look-ahead schedules, and build from a three-week schedule. This will continue to cause the aforementioned problems, and our mission is to share with you information about those issues and their remedy throughout this work.

Our industry is currently benefiting from some parts of the Last Planner System. Typically in the new approach, CPM schedules are created that identify milestones, with the use of the Last Planner System pull planning is done to the milestones, make-ready plans detail out target dates for worker counts and materials and information, and the weekly work plan becomes the production control tool of choice from which the percent plan complete can be tracked as the project team huddles to execute daily work.

This is a step in the right direction, but it won’t be fully supported until CPM stops leading as the unruly master with its unrealistic end dates and poor preparation. Is Last Planner perfect? No. Are there some concepts that have to be clarified and modified? Yes, and we will show that in this book. As for Scrum, we couldn’t be more excited about the possibilities of using this system, and it excites us to have a system that will prepare for Scrum sprints by controlling the supply chains ahead of it. Ultimately, Takt planning is a system that prepares for short-interval production control, whether you use standard Takt control or Last Planner or Scrum.

Flow Must Reign Supreme

So why the need for this book? In Lord of the Rings, it was not originally known that the one ring held power over them all. Similarly, in construction, we have not come to the conclusion yet as a whole that flow rules all other efforts and that it must reign supreme.

Our story is one of teamwork, transparency, and success that begins with respect, creating stability, and continuously improving. Because construction relies so heavily on supply chains of materials, worker counts, and information, the rhythm of a project and the overall throughput will always need to be the first key considerations—even if we employ agile techniques on a short-interval basis.

In the Book of Five Rings by Miyamoto Musashi, the author describes short sword and long sword martial arts. The long swords are used in open warrior-to-warrior combat. The short sword is used in close proximity situations when dueling. A martial artist needs both. Musashi explains that a great martial artist will hold both swords in combat and focus his or her eyes on a fixed position toward the enemy so as to see the peripheral and not get distracted.

In construction, we cannot get distracted by one type of scheduling, one critical path, or one method. We need to keep our eyes forward and fixed on the enemy—waste and variation. If we do this, we will use systems together like Takt, Last Planner, and Scrum. We must fight with a short sword (short-interval planning methods) and long swords (master schedules like Takt planning) and keep our eyes fixed on flow and the overall throughput of the system and not get distracted by a single critical path.

Takt planning has not yet taken hold in the United States like it should, and it needs to be empowered as the main scheduling tool to either replace the critical path method or at a minimum to hold it accountable and govern it. One of the main reasons the construction industry still typically produces projects behind schedule with a crash landing at the end and with poor quality is because we incentivize this with the variation, lack of transparency, and chaos that comes from true CPM scheduling. It is time for this to stop. And Takt is the solution.

The Critical Path Myth: Buffers Are Required, Not Optional

Let’s talk about the details. We all know the concept of a critical path, right? Or do we? Here’s one definition: in project management, the critical path is the longest sequence of tasks that must be completed to successfully conclude a project from start to finish. The tasks on the critical path are known as critical activities because if they’re delayed, the whole project will be delayed.

This is the most common definition. And again, let us be clear: you should never have just a critical path without buffers. There are some in construction that have not allowed buffers in contract language and schedules, which is wrong.

Anyone who has managed risk in construction would attest that traditional CPM has always been missing the statistical probability of completing on time. This is why risk by duration certainty and risk event charting is analyzed to show us the likelihood of success. This gives the rationale for buffer and buffer management to be in any schedule management system. So the critical construction activities by themselves are not a responsible execution method.

This is why you might have heard of CCPM, critical chain project management—which takes buffer management into account. And if we should not have a critical path, why would we want a forward and backward pass to find it? The answer is we wouldn’t.

True CPM vs. Builder CPM: You’re Not Defending What You Think You’re Defending

Most construction builders use flow principles that awkwardly fit into CPM. For instance, a critical path for most builders means the longest string of activities in construction that also includes an activity buffer for the overall schedule. So we do not plan on 100% efficiency within the projection of the activities. But that is not the true definition of a critical path. So let’s differentiate between true CPM and builder CPM, because we want to convince you that true CPM as a standalone system is not serving you well and convince the world that builder CPM is better done in Takt.

As a very wise lean practitioner once said, you can learn to walk with a broken leg, but it would be better to just fix the leg. When people tell us they can do what we do in Takt with CPM, we always ask why. Why spend 12 times the amount of time developing it, overburden the team to manage it, and hide the information within it just to save the 12 hours it would take to learn Takt? The answer is that you wouldn’t and you shouldn’t.

One more thought here: when people push back about the use of CPM, they always say it’s not the process, but people are using it wrong. We blame processes, not people in lean thinking. If CPM is not implementable across the industry in its basic form without people using it wrong, then it is fundamentally broken. Even in the Bible, Paul in the book of Romans spoke about things not being unclean or evil in and of themselves. But when they show forth a bad example and others are hurt by it, then it is unclean and evil. You may be able to make CPM work the way you want, but your example in using it is hurting the 74% of construction projects that fail.

What Builder CPM Actually Looks Like

Here’s what true builders actually do with CPM—and why it proves the system is broken:

Critical Path: True builders add contingencies at the end of their schedules and call that the critical path. Why? Because they know it doesn’t work to plan on 100% efficiency, so they plan in a buffer at the end. That’s good, but now it’s technically not a critical path.

Float: True builders focus more on crew ties for trade flow than they do float and early and late starts and finishes. Many true builders will tell us they create flow in the schedule with logic ties. But then again, you do not have a critical path. Instead, you have a flow analysis—and one that is not easily seen as a point of fact.

Forward and Backward Pass: True builders will level out the work instead of allowing the algorithm to slam everything to the left toward the data date with a float calculation. Most of the time, builders do not even show project float in the schedule. So why does it matter? The answer is it doesn’t.

So you see, when people get offended at us and defend CPM, they’re not defending true CPM. They’re defending builder principles they have fit into builder CPM, incorporating their wisdom into a broken system. Now you can keep using that broken leg, or you can get it fixed and enjoy your life. Ultimately, we feel you would be happier and have more family time if your priority was on living a remarkable life instead of holding on to the significance of being a CPM expert and user.

Float Calculations Are Useless and Dangerous

You should never schedule a project with a critical path that has no buffers. And what about the float calculation? That’s useless too. Showing the allowable float breeds a mindset that activities can and should be moved at random. That increases work in process, extends throughput times, and creates restarts. All of that decreases flow efficiency and resource efficiency.

Once we randomly start an activity with free float or total project float outside of a flow, we’ve created variation in the entire system and the teams executing the work. Therefore, we do not need a critical path, a forward and backward pass, early and late start and finish times, and a complex network diagram that does not visually show what we’re doing. So why do so many competent people still use it? It’s because they use what we call builder CPM, not true CPM.

How to Transition: Takt First, CPM Only When Required

Here’s a question: how can we transition an industry from CPM to Takt? Well, education to start. Eventually, owners and government agencies will need to remove it from contracts. But at a minimum, Takt should govern and control CPM if it’s still used.

If you have to do this, and you’d be surprised at the number of times you actually don’t, it’s our recommendation to plan your project in Takt, create a CPM schedule to appease the owner just in time and only at contract minimums, or even better, use the Takt plan to govern the project and use CPM for the as-built to show the owner status.

We believe you could implement the last option on almost any project. And why keep both systems, you ask? Again, we don’t know. You should switch to Takt or at least negotiate the schedule reporting terms of the project away from CPM language. There are plenty of standard contracts that already do this and still give reports to the owner while also mitigating risk.

We hope this work convinces you that there’s a better way, that you deserve better, that people matter enough to create flow, and that learning a new system is easier than you think. If the friction is that your owner wants an application with metrics, most all desired metrics can be calculated in Excel as one of the best options for starting to use Takt. You can also consider using Tacting or Timotei with some facilitation.

If you’re ready for something new, though most importantly something that works, keep reading. We’ve written this book in a manner to match the fables used in Patrick Lencioni’s books. From here you’ll be introduced to the concept of flow and Takt planning in our story, after which we will detail how to implement Takt successfully so you can begin the use of flow and Takt planning on your projects. If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow.

FAQ

Q: What’s the difference between true CPM and builder CPM?

True CPM uses a forward and backward pass to find the critical path with no buffers, plans on 100% efficiency, calculates float, and slams everything to the left toward the data date. Builder CPM is what competent builders actually do: they add contingencies at the end (so it’s no longer a true critical path), focus on crew ties for trade flow instead of float, level out work instead of letting the algorithm slam it left, and often don’t even show project float. When people defend CPM, they’re defending builder principles they’ve awkwardly fit into a broken system. You can keep using that broken leg, or you can fix it and use Takt.

Q: Why is showing float in a schedule actually harmful?

Showing allowable float breeds a mindset that activities can and should be moved at random. That increases work in process, extends throughput times, and creates restarts. All of that decreases flow efficiency and resource efficiency. Once you randomly start an activity with free float or total project float outside of a flow, you’ve created variation in the entire system and the teams executing the work. Float calculations give false permission to disrupt flow, which is the opposite of what construction needs.

Q: How can I transition to Takt if my owner requires CPM in the contract?

Plan your project in Takt first. Then create a CPM schedule to appease the owner just in time and only at contract minimums. Or even better, use the Takt plan to govern the project and use CPM for the as-built to show the owner status. You’d be surprised how many times you can negotiate the schedule reporting terms away from CPM language, there are plenty of standard contracts that already do this while still giving reports to the owner and mitigating risk. At a minimum, Takt should govern and control CPM if it’s still used.

Q: Why do you say CPM is fundamentally broken if people keep using it wrong?

We blame processes, not people in lean thinking. If CPM is not implementable across the industry in its basic form without people using it wrong, then it is fundamentally broken. It’s like the poorly designed airport urinal—you can blame people for not aiming right, but the real problem is the design creates friction in using it correctly. When 74% of construction projects fail, and competent builders have to modify CPM with buffers, crew ties, and leveling just to make it work that proves the system itself is the problem.

Q: What’s the urinal analogy really saying about construction scheduling?

On a large scale, one urinal design is practical and works for the masses with little friction, and the other results in a mess. CPM is the poorly designed urinal, it creates friction in getting it right, hides the mess in complexity, and requires experts to make it work. Takt is the well-designed urinal, it’s hard to use incorrectly, creates flow naturally, and works for everyone from laborers to executives. If you want to keep stepping in puddles, keep using CPM and blaming people. If you want an easy, clean, neutral experience, use Takt and help people win as a group.

On we go.

If you want to learn more we have:

-Takt Virtual Training: (Click here)
-Check out our Youtube channel for more info: (Click here) 
-Listen to the Elevate Construction podcast: (Click here) 
-Check out our training programs and certifications: (Click here)
-The Takt Book: (Click here)

Discover Jason’s Expertise:

Meet Jason Schroeder, the driving force behind Elevate Construction IST. As the company’s owner and principal consultant, he’s dedicated to taking construction to new heights. With a wealth of industry experience, he’s crafted the Field Engineer Boot Camp and Superintendent Boot Camp – intensive training programs engineered to cultivate top-tier leaders capable of steering their teams towards success. Jason’s vision? To expand his training initiatives across the nation, empowering construction firms to soar to unprecedented levels of excellence.

On we go

The Takt Production System – Part 2

Read 34 min

One Ring to Rule Them All: Why Takt Must Govern Your Schedule

Scheduling is about the visualization of time and space. If your construction schedules don’t do this, they don’t serve you well. Marine Corps General Robert Hilliard Barrow said “Amateurs study tactics, armchair generals study strategy, but professionals study logistics.” Takt planning does all three.

In Takt, you can see the location-based rhythm of the project and its critical supply chains—the logistics of the site. You can also see what needs to happen in those locations and when they should take place. That’s the intersection of what, when, and where. And interestingly, the basic unit in scheduling that represents the intersection of what, when, and where is called a Takt. It’s the cell or box in Excel or Tacting that houses a Takt wagon.

Only Takt accomplishes what all other programs cannot. A normal activity in a Gantt chart or CPM schedule has the element of time and space, but it’s vague and barely visible. The difference is between a database of time and space and the visualization of time and space. Only a Takt unit can provide the visualization of time and space in scheduling.

Takt with stable and lean field environments will do more to stabilize our scheduling processes, reduce material inventory, eliminate waste and variation, decrease durations, and increase profits than anything else in construction. We must be able to visualize and then stabilize time and space.

What Actually Qualifies as a Takt Plan

You must have a schedule that visualizes time and space, clearly shows workflow and trade flow and logistical flow, schedules on a rhythm with the right buffer management, and stabilizes the pace of work with what’s called one-piece flow that limits work in process in order to have a Takt plan. The last requirement for Takt planning is that the schedule has a reasonable overall project duration. If it doesn’t have that, people will begin pushing and the rhythm of the system will be lost.

Here’s what Takt planning actually requires:

  • A visual schedule showing time and space
  • Shows work, trade, and logistical flow (when, what, and where)
  • Schedules on a rhythm
  • Includes buffers
  • Stabilizes the pace of work with one-piece flow and limiting work in process
  • Allows for a reasonable overall project duration

If you don’t have this, you don’t have a Takt plan. We should not want anyone labeling Gantt charts, CPM schedules, or other visuals as Takt plans if they don’t show these things. If this is allowed to happen, Takt will get a bad name and the life-changing magic of the system will be slowed.

One of the main things that will hurt people and families is the pushing of trades without flow. If you schedule work through areas without flow, you’re creating schedules that will fail for the people you care about.

Flow Where You Can, Pull Where You Can’t, and Stop Pushing

Taiichi Ohno, one of the fathers of lean, said “Flow where you can, pull where you must.” To translate it from manufacturing and apply it to construction, we added “and stop pushing.” Flow is king. It rules all and it should be our first priority, value, and focus.

In construction, when we cannot flow, we will need to pull. And we all know there are situations that regardless of our best efforts, we think we have to push hard to get finished. But there’s a better way. In a similar fashion and in this order, we must use Takt, tools like Scrum and Last Planner, and then CPM only if we must, if at all. At times when the last three are used, Takt will govern them all.

Think of it like the ring of power from Lord of the Rings. Last Planner, Scrum, CPM, graphical schedules, and many others ultimately work and fulfill their purpose when they’re governed by one, and that one is flow. It’s Takt planning and the use of Takt time in scheduling. All our rings of power are ruled by one: the ring of flow.

The three basic habits of a builder are studying the drawings, working in the schedule, and taking reflection walks daily. There are seven key positions on a project team. There are nine key meetings that the team must use in a remarkable way to create stability. The focus is on respect for people and resources as the base philosophy of the project team. And in these meetings, there’s a standing tactical order of maintaining flow where we can to guide the team’s efforts to create stability and to govern all other systems.

One ring to rule them all. That ring is Takt.

The Five Major Problems With CPM

The construction industry is incentivizing push. True CPM, the critical path method, when used as a standalone system inherently pushes with its famous forward and backward pass. Although some CPM experts would argue that through proper logic sequencing you can still model flow in the system, the CPM visual representation fools and confuses project teams into thinking there’s a solid plan in the schedule hidden under the excessive detail.

CPM has been used since the 1940s, was fully adopted as industry practice in construction by the AGC in 1965, and is still considered the standard. Even with its widespread adoption and general use, most projects finish behind schedule with crash landings or an accelerated push to the end that expends significant human and physical resources.

Why does this happen? Here are the five major problems with CPM:

Problem 1: CPM Is Too Optimistic

CPM is not a tool that easily shows flow or geographical connections from one work breakdown structure to another. It’s hard to read, unintentionally hides inefficiencies, and essentially miscalculates how long the project will take. When the first draft of a schedule is made, it’s made with the smallest amount of detail. The system is planned for ideal conditions and it’s not usually tied to the proper project risks and constraints.

Whereas Takt is somewhat immune to this because it visualizes flow and projects what should happen, not what will happen. So what does happen with CPM? The owner or team bids the optimistic schedule, falls in love with the end date, and as confirmation bias settles into the psyche of the first planner group, they needlessly give away general conditions and schedule time to save face and please a customer doomed to disappointment when they enter the eventual crash landing with no more contingencies available.

CPM essentially slams everything to the left as close to the data date as possible and gives the team a false sense of security by calming any possible objections with the promise of calculating float, although that float is rarely shown or printed on the schedules used. True CPM deceives us about how long projects take.

Problem 2: CPM Makes Us Think the Plan Is Better Than It Really Is

For most users, CPM masquerades as a solid plan simply because it looks complex. CPM attempts to identify what will happen, which is impossible. Takt identifies what should happen. Often people wrongly associate busyness and motion with productivity, and similarly they mistake excessive detail as an indication that there’s a solid plan. This is the second way CPM fools us—it makes us think the plan is better and more complete than it really is.

Ultimately, CPM scheduling is a wild guess. Many would argue with this, but we have yet to see accurate production rates without advanced Takt work packaging that is applied properly within local market conditions that would make a CPM master schedule anything other than a shot in the dark. And the dark part is the main point. Takt is a shot with data and visibility in a flow simulation that even the most inexperienced laborer can read and understand.

Sure, there’s historical data with certain sequences in CPM, but those same sequences can be used in Takt and do not in and of themselves justify CPM as a method. CPM masquerades as a good plan when all it actually shows is a ton of detailed guessing.

Problem 3: CPM Hides the Plan in the Complexity of Its Format

Very few builders—even those who create their own schedules, can see the overall plan from a CPM printout that well. CPM experts may argue that the use of filters, hammock activities, graphical schedule printouts, and other tools would accomplish this goal, but these solutions don’t answer for nor hold other non-summarized data accountable to flow within the context of the whole plan.

The bottom line is that very few read CPM schedules and no one can fully understand them without a lot of detailed and focused work and effort. CPM isn’t practical or efficient. Even a superintendent building his or her own schedule from the start will lose track of crew ties, the logic tie strategy, and the overall flow of the schedule. Humans are just not sharp enough to stay with the complexity of that system.

At best, the use of CPM schedules relies on the skill, thoughtfulness, discipline, and good fortune of the person who entered the information in the first place. Our quality, safety, and financials rely on this plan, and knowing the plan in its entirety is crucial. No one can take a CPM schedule, read it within a reasonable time frame, and see the overall plan like you can with Takt. CPM is too complex to effectively read and manage.

Problem 4: CPM Has Too Much Unchecked Power

Our legal considerations, analysis, and standards are mostly based on CPM. It’s made its way into most contracts, and it’s difficult to find an owner who doesn’t think it’s vital to success. CPM is seen as the only way to mitigate risk and safeguard us legally. But even those who do this well admit that CPM is quite a poor communication tool.

So it becomes a chore to make it reflect reality, either by employing a scheduling team or having an inefficient series of meetings just to map out the detailed nature of construction. We manipulate and use it for so many pointless purposes that we’ve become addicted to it through sheer familiarity. Better the devil you know than the angel you don’t, right?

It’s like a tyrannical mother-in-law who shows up to help after a baby is born. It sounds like a blessing in the beginning, but over time she’s bossing everyone around, badmouthing you for every move you make, and disrupting your family’s peace and stability. She remains in the house only because the damage to family relationships and drama it would cause if you spoke up makes sending her home seem harder than just enduring her presence.

Conversely, you might welcome her with open arms if she fit in the way you needed her to, if she had self-control and checked power, and if she would stop abusing your family. In a similar manner, Takt can hold CPM accountable if CPM stays within its rightful place—which is under the control and accountability of Takt.

So what stops us from doing this? Ask yourself: do most owners want to see the truth? In a world where developers, owners, and general contractors are all taught to sell the risk of a project, it’s sometimes more profitable to hide the truth in a CPM schedule so any possible data trail can be muddy enough to protect parties upstream and force a negotiated settlement.

The bottom line is that an owner wanting to transfer the cost of a failed project to the GC does not want a Takt plan showing where the owner and designer interrupted flow and created the cost or time delay. This also happens with general contractors. If the GC is not proficient, what would they prefer—a CPM hiding the details or a Takt plan showing the truth? The answer is obvious.

Unaccountable people, teams, and companies want roadblocks hidden so they can more easily transfer blame and costs. Accountable people, teams, and companies will love Takt planning and knowing the truth and bringing the roadblocks to the surface so we can manage around them as a team and win.

Problem 5: CPM Institutionalizes Hiding Problems

Professionals in construction can wrongly adjust a few logic ties and make some well-hidden changes to make the negative float go away. In fact, when using Takt, new practitioners might say “Takt doesn’t work. I’m constantly seeing problems in the system and we’re not tracking to finish on time.” This is precisely because Takt is a productively paranoid system that reflects reality and brings problems to the surface.

The true lean scheduling system—Takt—shows what’s actually happening to your project. CPM hides things and builders feel falsely content and happy in the moment until the evidence that the team will not finish on time is irrefutable and oftentimes too late.

CPM also contributes to superintendents developing dragon sickness. Dragon sickness, borrowed from The Hobbit this time, is our label for the many non-transparent, possessive, and siloed supers that hoard over their schedule like a dragon hoards over his gold. They covet the power and security that comes from being the only one who knows the plan simply because they’re not confident or competent enough to work with the team and let the team collectively own and know the plan.

CPM encourages this bad behavior and destroys collaboration with a promise that the super can reign supreme in the secrecy of being the only one who knows the plan, at least in part. It’s ironic that with dragon sickness, the afflicted person never uses his gold. And in like manner, the afflicted CPM scheduler never uses his schedule because no one can understand it.

Why Takt Brings Transparency and Truth

The problem is that CPM lacks transparency. Even though the hidden logic, calendars, and other functions can all be shown in one way or another, it’s difficult to report and analyze these on an ongoing basis. There’s so much concealed within a CPM schedule that other systems are needed for quality control to make sure there are no missing logic ties, open ends, open finishes, loose ends, redundant logic, loops, bad ties, crew ties, hidden lag durations, an exorbitant amount of predecessors, out-of-sequence activities, status greater than the data date constraints, negative float, and many others.

This entire system has to be monitored in such a way that wastes time due to its complexity and the inability to see when issues appear. It’s a temperamental system prone to quality mistakes and errors. It can take up to seven different applications to properly run a CPM schedule. Some say they can do everything we do in Takt if they build the schedule with Excel first to show flow, then P6 to create the schedule, then Acumen Fuse to QC the schedule, then Acumen Risk to prepare the schedule for construction, then Acumen 360 for recovery analyses, then graphical schedule (a program that summarizes a visual depiction of the schedule into an easily understandable Takt plan format), and Adept for design phase.

Why take all those steps? We can do all that in Excel, Tacting, or Timotei in one-twelfth the time.

Additionally, there’s little value to knowing all these metrics if they only show that the schedule is in trouble without showing why and how to recover it. Takt is the only system that will show the team why and where to focus to recover. You will never recover a schedule without regaining flow. And therefore, you will never properly recover a schedule without Takt.

As we said in the introduction, there should be one that governs them all: Takt. Even if the industry persists in the use of CPM, Takt is the best accountability partner. To use another human analogy, CPM is like the spouse that overprograms a Saturday and Takt is the other one who brings the duo back into reality by realistically planning what should be done within the time allotted. In that scenario, the only way to have a great Saturday is to use the common-sense partner or pair them together. But never should the unrealistic partner plan the Saturday alone.

If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow.

FAQ

Q: If CPM has all these problems, why is it still the industry standard?

Because it’s been structurally incorporated into so many systems, cultures, and processes since 1965 that going against the grain offends positions, relevance, and education. We’ve become addicted to it through sheer familiarity, better the devil you know than the angel you don’t. CPM also has unchecked power in contracts and legal standards, and it’s profitable for parties who want to hide the truth and transfer blame. Unaccountable people want roadblocks hidden. Accountable people want Takt’s transparency. The industry persists with CPM not because it works well, but because changing requires courage.

Q: Can CPM and Takt work together, or do I have to choose one?

Takt should govern CPM, not replace it entirely. Think of CPM as the spouse that overprograms Saturday and Takt as the realistic partner who brings things back to reality. You can pair them together, but never let CPM plan alone. Takt creates the flow schedule first, then CPM can handle logistics and milestone tracking within that flow framework. Takt is the accountability partner that keeps CPM honest and prevents it from hiding problems or creating unrealistic expectations.

Q: What is “dragon sickness” and how do I know if I have it?

Dragon sickness is when superintendents hoard over their schedule like a dragon hoards gold, coveting the power and security that comes from being the only one who knows the plan. It happens because they’re not confident or competent enough to work with the team and let the team collectively own and know the plan. CPM encourages this by making schedules so complex that only the creator understands them. Signs you have it: you protect your schedule, resist collaboration, use complexity as job security, and your team can’t read or understand your plan. The ironic part? Like a dragon who never uses his gold, you never actually use your schedule because no one can understand it.

Q: How does Takt bring problems to the surface instead of hiding them?

Takt is a productively paranoid system that reflects reality. When you visualize flow on a Takt plan, problems become immediately visible, you can see where trades will collide, where material buffers are missing, where durations don’t match capacity, where the rhythm breaks down. CPM hides these problems in complexity, logic ties, and optimistic durations. New Takt practitioners sometimes complain “I’m constantly seeing problems and we’re not tracking to finish on time”, that’s the point. Takt shows what’s actually happening so you can fix it before it’s too late. CPM keeps you falsely content until the crash landing is inevitable.

Q: What’s the difference between what CPM shows and what Takt shows?

CPM attempts to identify what will happen, which is impossible, it’s a wild guess hidden in excessive detail. Takt identifies what should happen based on flow, capacity, and rhythm. CPM is a database of time and space; Takt is the visualization of time and space. CPM shows activities and dependencies; Takt shows the intersection of what, when, and where. A normal CPM activity has time and space elements but they’re vague and barely visible. A Takt unit provides clear visualization that even the most inexperienced laborer can read and understand. You’ll never recover a schedule without regaining flow, and you’ll never properly recover without Takt.

On we go.

If you want to learn more we have:

-Takt Virtual Training: (Click here)
-Check out our Youtube channel for more info: (Click here) 
-Listen to the Elevate Construction podcast: (Click here) 
-Check out our training programs and certifications: (Click here)
-The Takt Book: (Click here)

Discover Jason’s Expertise:

Meet Jason Schroeder, the driving force behind Elevate Construction IST. As the company’s owner and principal consultant, he’s dedicated to taking construction to new heights. With a wealth of industry experience, he’s crafted the Field Engineer Boot Camp and Superintendent Boot Camp – intensive training programs engineered to cultivate top-tier leaders capable of steering their teams towards success. Jason’s vision? To expand his training initiatives across the nation, empowering construction firms to soar to unprecedented levels of excellence.

On we go

What Are Soft Costs In A Construction Project?

Read 23 min

Soft Costs Are Not Waste: Why Cutting Them Tanks Your Hard Costs

Every construction budget has two sides. One is easy to see and easy to respect. The other is easy to see and easy to cut. The first side is hard costs labor, materials, equipment, the site work that turns into a building. The second side is soft costs design, preconstruction, permits, consultants, project management, the systems and supports that wrap around the physical work. Guess which side usually gets cut first when a project needs to hit its number.

Here’s the deal. Cutting soft costs the wrong way doesn’t save money. It transfers money. It moves cost from a line item on a budget into a crisis in the field, where it gets paid back with interest through rework, delays, safety incidents, and burned-out teams. Soft costs are not waste. They are the investment that protects every hard cost downstream.

What Actually Goes Wrong When Soft Costs Get Slashed

Walk any project that’s fighting itself, and you’ll find the same pattern upstream. Preconstruction got compressed. Field engineering got understaffed. Consultants got cut. Design reviews got skipped or rushed. Training for the field team never happened. The right systems and technology were “not in the budget this time.” Each one of those decisions saved a line item. Together, they guaranteed the hard costs would blow past the plan anyway.

Then the project starts. The design has gaps because the design phase was rushed. The permits come in late because the strategy was compressed. The field team is learning on the job because nobody paid for training. Consultants who could have caught exterior skin issues before they became leaks were cut, and now the rework estimate is six figures. The hard costs that looked fine on paper are now running over, and the savings from the soft cost cuts have been erased three times over.

The Failure Pattern: Treating Investments Like Costs

Here’s the pattern, and it’s everywhere. A project manager opens the budget. They look at hard costs and think, “It is what it is.” Labor rates are what they are. Material costs are what they are. Equipment is what it is. Then they move to soft costs and the pen comes out. Cut preconstruction. Cut field engineering. Cut consulting. Cut training. Cut technology. Cut, cut, cut.

That behavior is not a character flaw. It’s a learned habit produced by a system that lists soft costs on the wrong codes, in the wrong categories, with the wrong framing. They get labeled as overhead instead of as investments. Overhead gets cut. Investments get protected. The labeling decides the behavior before the PM ever opens the spreadsheet. Somebody upstream decided that soft costs sit in the “optional” column of the mental budget, and now every PM downstream inherits that framing and acts on it.

The system failed them; they didn’t fail the system. The PMs doing this are not bad people. They are operating inside a framing that taught them soft costs are discretionary. The fix is to change the framing, not to yell at the individuals. Respect for people is not soft it’s a production strategy. That includes respecting the PMs enough to give them the tools and the framing to make investment decisions instead of cutting decisions.

Hard Costs Are Where the Value Gets Added

Let’s be clear about what hard costs are, because this matters. Hard costs are where the workers and foremen add real value. When a carpenter screws up that piece of drywall. When a crew frames a wall. When the concrete team finishes a slab. When steel gets set, rebar gets tied, mechanical systems get rough-in. Hard costs are the labor, the materials, the equipment, and the site work that turn a pile of raw resources into a building somebody will live in, work in, heal in, or learn in for the next fifty years.

In the United States, most hard cost responsibility sits with the trade partners. They bring the labor, the materials, the know-how, the expertise, and the experience of putting the work in place. They prepare the site. They install the work. They carry huge portions of the information flow and the execution. Hard costs are where the building actually becomes a building.

That means hard costs deserve protection. And the way you protect hard costs is not by staring at them and hoping they hold. The way you protect hard costs is by funding the soft costs that enable them.

Soft Costs Are the Enablement Layer

Soft costs are everything around the physical work that lets the physical work succeed. Architects and engineers who design buildable drawings. Permits and fees that keep the project legal. Legal review and insurance that manage risk. Consultants who bring specialized expertise the team doesn’t have in-house. Financing costs. Project management that actually manages the project. Preconstruction time to plan the build before the build starts. Field engineering to establish control lines, verify layout, and protect quality. Training so the team knows how to execute the systems they’re being asked to run. Technology that lets the team see, coordinate, and act together.

The job of the general contractor is to provide the team, the support, the plan, the supply chain, the right environment, and the right rhythm so trade partners can work in sync. That entire sentence lives in the soft cost column. The GC’s responsibility to integrate the team, resource the project with the right information and materials, and build a cultural environment where trades can succeed all of that is funded by soft costs. Cut the soft costs and you cut the GC’s ability to do its own job. Then everybody downstream pays for it.

A Pattern I See on Struggling Projects

Here’s how this story usually plays out. The field team raises a hand early. “We need a little time in preconstruction to pull plan this properly.” The PM says no. “We need Lean Takt help to set up the production system.” The PM says no. “We need a consultant to review the exterior skin so we don’t end up with leaks.” The PM says no. “We need training on the new scheduling system.” The PM says no.

Every one of those “no” answers looked responsible on the budget the day they were made. Every one of those “no” answers showed up later as a problem that cost more than the original ask. The pull plan that didn’t happen became a month of schedule slippage. The Lean Takt setup that didn’t happen became a project that never found its rhythm. The exterior skin review that didn’t happen became a warranty claim. The training that didn’t happen became a team that made the same mistakes over and over because nobody showed them the better way.

This is also one of the main reasons knowledge doesn’t scale across the industry. Learning, development, training, and consulting are the exact line items that get slashed first, because they sit on the wrong codes. That means every project starts from scratch, every team relearns the same lessons, and the industry never compounds what it already knows.

The Cost of Bad Soft Cost Decisions

Before you approve the next round of cuts, look honestly at whether these bad decisions are showing up in your budget:

  • Very little preconstruction time, with the team expected to plan while they build.
  • Less effort in the design phase, with the assumption that field changes will handle the gaps.
  • Rushed permit strategy and no real feasibility study on the front end.
  • Understaffed field teams, especially field engineering.
  • No Lean practices, no Takt, no First Planner or Last Planner discipline funded.
  • No training for the team on the systems they are expected to run.
  • No investment in the right technology to give the team visibility and coordination.

Any one of those is a warning. Multiple of them together is a project that is already quietly failing on paper, before anyone has hit the dirt. The hard costs will absorb the damage, and the savings from the cuts will evaporate before the first milestone.

Why This Matters to Every Crew and Every Family

When soft costs get slashed, the field pays. Foremen spend their weekends rebuilding plans that should have been built in preconstruction. Field engineers work overtime to catch layout issues that better design review would have caught. Trade partners absorb rework they shouldn’t have had to do. Supers fight fires that a proper staging plan, a real pull plan, and a funded consultant review would have prevented months earlier.

If the plan requires burnout to succeed, the plan is broken, not the people. The place that plan usually gets broken is in the soft cost column, months before anyone steps on site. Every family connected to every worker, foreman, field engineer, and trade partner on that project pays a small piece of the cost of those decisions. Protecting soft costs is one of the most concrete ways a leader protects the people who will eventually build the work.

The Right Question to Ask About Soft Costs

Here’s the shift. Don’t ask how to reduce soft costs. Ask which soft costs create flow, stability, and respect for people, and will allow the hard costs to win. That is a completely different question, and it produces a completely different set of decisions.

It moves the conversation from “what can we cut” to “what do we need to fund.” It treats preconstruction as an investment in the build, not a cost of overhead. It treats consultants as specialized expertise that de-risks hard costs, not as a line item to trim. It treats training as the multiplier that lets every future project run better, not as a discretionary expense. It treats the right technology as infrastructure for coordination, not as a budget indulgence. It treats field engineering as the foundation of quality, not as a position to understaff.

Good soft costs mean a stable system. Stable systems produce predictable hard costs. Predictable hard costs produce successful projects. Successful projects produce healthy teams and strong owner relationships. That’s the chain. Break the first link and the whole chain weakens.

Where to Protect Investment, Even Under Pressure

When the budget pressure is real and the PM has to make calls, these are the soft cost investments that should be protected first:

  • Preconstruction time for real pull planning, staging strategy, and constructability review.
  • Feasibility studies and front-end design effort so the project starts with a buildable plan.
  • Field engineering staffing adequate for the scope and complexity of the work.
  • Lean consulting and Takt setup support for teams that don’t have the in-house expertise yet.
  • Training for the field team on the systems, technology, and production standards they will be expected to run.

Those five protect the hard costs better than any amount of line-by-line cutting. If your project teams need help reframing the soft cost conversation, building the preconstruction discipline, and funding the investments that protect every downstream trade, that is the work we do every day. If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow.

We are building people who build things. That includes building the budget discipline that lets the people in the field actually succeed. The way we treat soft costs is one of the clearest signals of whether we understand that mission.

A Challenge for Builders

Open your current project’s budget this week and look at the soft cost column. Not to cut it. To question it. Are the right investments protected? Is preconstruction funded properly? Is field engineering staffed adequately? Is training happening? Are the consultants who would de-risk the hard costs actually engaged? If the answer is weak, the fix is not to cut further. The fix is to reframe the conversation, protect the investments that produce flow, and give the hard costs the enablement they need to win.

As Jason says, “Plan it first, build it right, finish as you go.”

On we go.

Frequently Asked Questions

What’s the difference between hard costs and soft costs?

Hard costs are the physical building labor, materials, equipment, and site work that turn raw resources into a finished structure. Soft costs are everything around the physical work that enables it design, preconstruction, permits, consultants, project management, training, and technology. Hard costs add value. Soft costs protect the conditions that let hard costs succeed.

Why do soft costs usually get cut first in a budget review?

Because they’re often labeled on the wrong codes and framed as overhead instead of investment. That labeling produces a habit where PMs accept hard costs as fixed and attack soft costs as optional. It feels responsible on the spreadsheet and creates real damage downstream when the project loses the support, planning, and expertise those soft costs would have funded.

What’s the better question to ask about soft costs?

Not “how do we reduce them,” but “which soft costs create flow, stability, and respect for people, and will allow our hard costs to win.” That reframes the decision from cutting to investing, and it protects the exact line items preconstruction, field engineering, consulting, training, technology that keep the hard costs on budget.

If you want to learn more we have:

-Takt Virtual Training: (Click here)
-Check out our Youtube channel for more info: (Click here) 
-Listen to the Elevate Construction podcast: (Click here) 
-Check out our training programs and certifications: (Click here)
-The Takt Book: (Click here)

Discover Jason’s Expertise:

Meet Jason Schroeder, the driving force behind Elevate Construction IST. As the company’s owner and principal consultant, he’s dedicated to taking construction to new heights. With a wealth of industry experience, he’s crafted the Field Engineer Boot Camp and Superintendent Boot Camp – intensive training programs engineered to cultivate top-tier leaders capable of steering their teams towards success. Jason’s vision? To expand his training initiatives across the nation, empowering construction firms to soar to unprecedented levels of excellence.

On we go

The Takt Production System – Part 1

Read 23 min

Why Takt Planning Is the System That Will Save Construction

Jason Schroeder didn’t write a book about Takt planning because he thought it was interesting. He wrote it because most construction projects don’t finish on time. Because there’s a better way of running projects. Because the success of cost, quality, and safety is ultimately determined by the execution of the schedule. And because the implications of an improperly scheduled project are disrespect for workers and the families of everyone involved in the project, both of which are unacceptable.

This isn’t about efficiency for efficiency’s sake. This is about bringing respect back to workers and keeping family time sacred. This is about bringing flow back to construction through correct planning and scheduling practices. This is about reversing the productivity decline that’s been plaguing construction for decades while every other industry figured out how to build better, faster, and safer.

The second edition of “The Art of the Builder: The Takt Production System” is being recorded as a podcast series because Takt certification courses are scaling like wildfire, 36 people per class, and the information needs to get out faster. This isn’t just another construction management theory. This is the system that actually works.

The Mission: Workers, Leaders, and Families

Here’s what you need to understand first: the only reason Elevate Construction exists as a company is to bring respect to workers, train leaders, and preserve families. Until you comprehend that the mission is about people, you will not understand the mission. Everything else—the schedules, the plans, the systems, the metrics, exists to serve that purpose.

Jason and Spencer have seen firsthand projects where workers and foremen love coming to work. Projects where bathrooms and lunch areas are inviting and where there’s a flow and a general sanity to the way work is done. These environments improve humanity. That’s the goal.

So how is Takt planning and Takt control tied to remarkable environments? In their experience, only Takt enables the visibility, control, and capacity the team needs to create remarkable environments. In the absence of this, you see burdened teams, overworked leaders, unreliable supply chains, unstable amounts of material inventory, broken families, unsafe and poorly run projects, dirty environments, and jobs without the most basic of human dignity, such as a place to use the restroom and eat lunch.

At its worst, projects are unsafe and harm or kill people. That’s why this book exists. That’s why the time, financial commitment, and mission is dedicated to the wonderful work you do, the project leaders who have good intentions and just need help, and the families that will benefit from better-run projects.

What Makes Takt Different From Everything Else

Takt planning is a strategic, logistical, and tactical initiative in creating a stable environment. That’s the key word: stable. How can anyone continuously improve in a chaotic environment? How can stable environments be built with the exclusion of deep and abiding respect for people and resources?

To bring respect, training, and preservation back to construction, we have to get the formula right for lean. We have to bring back stability which allows for respect and continuous improvement. We have to bring flow. And Takt does this.

Here’s the definition of lean that Elevate Construction espouses: respect for people and resources, stable environments that create flow, total participation through visual systems, and continuous improvement and fanatical quality. Takt planning delivers all of that. It’s not one piece of the puzzle, it’s the foundation that makes the other pieces work.

Jason has always finished projects on time, and he realizes now it’s not because he was good at CPM. It’s because he has always, and he means always, paired Takt with and ahead of CPM by making sure Takt created flow first. Takt has brought sanity to his schedules and has preserved his family and respected workers in his care.

He started out slowly using it mainly for interiors. After learning how German and French experts and companies use Takt on projects, he began experimenting with exterior flow schedules and eventually scaled the system to hundreds of projects. He relied upon principles learned from the Pentagon renovation to build his own unique system. He created his own version, experimented and implemented it, and designed his own way of aligning terminology and additional insights in his journey.

This system is the way. It has made Jason, and he knows if applied correctly, it will make you.

The Problem With CPM (And Why We’re Not Afraid to Say It)

Here’s where this gets controversial. The book attempts to contextualize true CPM and better support Last Planner and Scrum as it elevates Takt planning and Takt control. The assumption was that this would upset some people and incite some pushback, which is fine if it drives change—but the goal is to take this journey with everyone.

Saying that a fork won’t work for tomato soup is not an insult to the fork or the soup for that matter. In a like manner, saying that true CPM is not a standalone project management tool or scheduling system that will serve you well alone is not an insult. The problem with speaking up may stem from the fact that true CPM has been structurally incorporated into so many systems, cultures, and processes that going against the grain might offend someone’s position, relevance, or education.

But here’s the thing: the criticism of current methods is not because Jason and Spencer don’t know the system. Jason is a career superintendent proficient with P6 and CPM. Spencer is a professional expert, both qualified and certified scheduler, and has made a living creating and managing CPM for years. They know the system. They know the drill.

Therefore, they know the best way to be supportive of something is to use it in its right place and in the right way. CPM has a role. It’s just not the role most people think it is. And when you try to force it into a role it can’t fulfill, creating stable flow for workers, you get chaos, delays, and disrespect.

What Takt Actually Delivers

Takt planning changes what’s possible on a construction project. Here’s what it delivers when implemented correctly:

  • Stable environments where workers can actually work instead of constantly fighting chaos, waiting for materials, or being pulled in six directions at once
  • Predictable daily schedules so workers know where they’re supposed to be hour by hour instead of wandering around asking what’s next
  • Visual systems that create total participation so everyone can see the plan, understand the flow, and coordinate with other trades
  • Reduced variability and waste because work moves in a rhythm instead of the stop-start chaos that burns crews out and destroys productivity
  • Flow that respects workers’ time and families because stable schedules mean people can plan their lives instead of living at the mercy of reactive firefighting
  • Quality built into the process because workers have time to do things right instead of rushing to catch up to an impossible schedule

This isn’t theory. This is what happens when you implement Takt. Jason has done it on hundreds of projects. Companies in Germany and France have been doing it for over a decade. BMW uses Takt in their construction management arm for building facilities around the world. This works.

The Coalition Building This Movement

The second edition of the Takt book represents a massive collaboration of lean experts, Takt practitioners, and construction professionals who are done accepting the status quo. The acknowledgments section reads like a who’s who of people actually changing construction:

Adam Hoots expanded concepts on capacity and time buffers and created tracking metrics. Felipe Engineer-Manriquez trained Jason on Scrum and elevated his understanding of lean theory. Hal Macomber provided corrections on key lean concepts and industry resources. Marco Binninger, the co-creator of Takt, shared his experience and simulations and quadrupled Jason’s understanding. Janosch Dlouhy is finishing his doctorate degree in Takt production and construction, working at BMW where they use Takt in manufacturing and construction. Fabian Font has been a Takt planning practitioner since 2009 through hundreds of projects and created project management software to support Takt.

These aren’t academics theorizing about construction. These are practitioners who have proven the system works at scale. They’re sharing their knowledge because they believe in the mission: respect for workers, training for leaders, and preservation of families.

Why This Matters Right Now

The productivity decline in construction has been going on for decades. While every other industry figured out how to do more with less, construction has been stuck using outdated scheduling systems that create chaos instead of flow. We’ve been trying to force CPM to do something it was never designed to do: create stable, predictable work for crews in the field.

The result is burnout. The result is unsafe conditions. The result is workers who hate their jobs and leaders who are drowning. The result is families that never see their spouse or parent because construction demands everything and gives back chaos.

Takt is the answer. Not because it’s trendy or new, but because it’s based on production science that actually works. It’s based on respecting the flow unit, the worker, and designing systems that support them instead of burdening them. It’s based on the recognition that if the plan requires burnout to succeed, the plan is broken, not the people.

LeanTakt LLC exists with a clear vision: reverse the productivity decline in construction. Their values are flow, scale information fast, fail forward, increase education, and be results-driven. Their mission is to scale Takt planning throughout the United States and beyond and enable project teams to run projects in a stable way with respect for workers, enjoyment among the project team, and in a balanced way to support families.

That’s not marketing language. That’s the actual mission. And the podcast series recording the entire second edition of the Takt book is part of scaling that information fast. If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow.

FAQ

Q: What exactly is Takt planning and how is it different from CPM?

Takt planning is a production system that creates stable, rhythmic flow by dividing your project into zones and sequencing work through those zones at a consistent pace. Unlike CPM, which focuses on activity durations and dependencies, Takt focuses on trade flow and creating predictable work for crews. CPM tells you when activities should happen; Takt tells you where each trade should be working each day to maintain flow. CPM is useful for logistics and milestone tracking, but Takt is what creates the stable environment workers need to actually do their jobs well.

Q: Why does Jason say Takt is the only system that creates remarkable environments?

Because Takt is the only system that provides the visibility, control, and capacity needed to stabilize work. Without Takt, you get burdened teams, overworked leaders, unreliable supply chains, unstable material inventory, broken families, unsafe projects, and environments without basic human dignity. Takt creates hour-by-hour schedules, visual systems everyone can understand, predictable trade flow, and the stability that allows leaders to actually support their people instead of constantly firefighting. That stability is what makes remarkable environments possible.

Q: Can Takt work on my type of project or is it only for certain building types?

Jason started using Takt mainly for interiors, then expanded to exterior flow schedules, and eventually scaled it to hundreds of projects of different types. German and French companies have been using Takt on all kinds of construction for over a decade. BMW uses it globally for their facilities. The principles apply anywhere you have repetitive work, multiple trades, and the need for flow. The question isn’t whether Takt can work on your project, it’s whether you’re willing to learn the system and implement it correctly.

Q: What’s the learning curve for implementing Takt and where do I start?

The book “The Art of the Builder: The Takt Production System” is designed to give you everything you need to begin your Takt journey. There are also Takt certification courses (currently scaling at 36 people per class), resources at leantakt.com, YouTube videos on the LeanTakt channel, and training and consulting available through Elevate Construction. Start by understanding the principles, study projects that have implemented it successfully, and begin experimenting on a small scale. The second edition includes formulas, theory, tracking metrics, and practical guidance from world experts.

Q: How does Takt planning respect workers and preserve families?

Takt creates predictable schedules so workers know where they’ll be working each day and can plan their lives accordingly instead of living at the mercy of reactive chaos. It reduces the variability and waste that forces overtime and weekend work. It creates stable environments where people can do quality work without being constantly interrupted or pulled in different directions. When projects run on Takt, workers have flow, leaders aren’t drowning in firefighting, and people can actually go home to their families at reasonable hours. That’s respect made visible through better systems.

On we go.

If you want to learn more we have:

-Takt Virtual Training: (Click here)
-Check out our Youtube channel for more info: (Click here) 
-Listen to the Elevate Construction podcast: (Click here) 
-Check out our training programs and certifications: (Click here)
-The Takt Book: (Click here)

Discover Jason’s Expertise:

Meet Jason Schroeder, the driving force behind Elevate Construction IST. As the company’s owner and principal consultant, he’s dedicated to taking construction to new heights. With a wealth of industry experience, he’s crafted the Field Engineer Boot Camp and Superintendent Boot Camp – intensive training programs engineered to cultivate top-tier leaders capable of steering their teams towards success. Jason’s vision? To expand his training initiatives across the nation, empowering construction firms to soar to unprecedented levels of excellence.

On we go

It’s about People, Feat. Nelson Atagi

Read 22 min

Cleanliness Is Your First Win: Why Superintendents Who Care Start Here

The first thing Nelson Atugi noticed when he walked onto his new site wasn’t the schedule. It wasn’t the budget. It wasn’t even the safety program. It was the mess. Trash scattered everywhere. Materials piled in walkways. Equipment blocking trade flow. The kind of chaos that tells you nobody’s leading.

So he gave the foremen a couple days to clean it up. They didn’t. So Nelson brought in a crew and cleaned house. Within a day, the site looked completely different. It felt better. And since that day, the trades have done a great job keeping it clean, organized, everything in its place. People can maneuver. Workflows improved. The whole site changed.

Here’s what most superintendents miss: cleanliness isn’t just about safety compliance or looking good for the owner. Cleanliness is about respect. It’s about giving your people a stable environment where they can actually do their work. It’s about creating wins when everything else in construction feels chaotic.

The Kitchen Test: Why Clean Matters Before You Start

Nelson explained it like this: “I like to cook. But when I go to cook, if the kitchen has stuff all over the counters, if there’s dishes in the sink, I can’t start. I just can’t do it. The whole kitchen has to be cleaned out—tables wiped off, kitchen floor swept up, and then I can start. I feel clean that I can start.”

That’s the mental game of cleanliness. It’s not about being obsessive or wasting time. It’s about clearing the mental space to actually think, plan, and execute. When your environment is chaotic, your mind is chaotic. When your site looks like nobody cares, your people feel like nobody cares about them.

Think about what happens when you walk onto a clean site versus a disaster zone. On the clean site, you can see what’s happening. You can identify problems. You can walk without tripping. Your trades can find their materials. Your workers aren’t wading through trash to get to their work area. You get a mental win before you even start the day.

On the chaotic site, you’re already behind. You’re frustrated before you solve a single problem. Your people are navigating obstacles that shouldn’t exist. Every trade partner is annoyed because their workspace is contaminated with everyone else’s mess. You’ve lost before you started.

Cleanliness is outer order creating inner calm. And in construction, where chaos is the default, that calm is the competitive advantage.

Small Wins Drive Everything Else

Nelson said something crucial: “The small things we can do to gain wins are the things that ultimately win that war. And the mental state of winning drives a lot of what we do. When we feel like we win, man, we can do amazing things.”

This is the secret most superintendents don’t understand. They think cleanliness is a “nice to have” that you get to after you solve the real problems. But cleanliness is the foundation for solving the real problems. It’s the first win that makes all the other wins possible.

When you clean a site, you’re not just removing trash. You’re sending a message: we run a professional operation here. We respect our people. We expect excellence. We don’t tolerate sloppiness. And when your trades see that message, they respond. They start picking up after themselves. They organize their materials. They take pride in their work area. The culture shifts.

Eric Thomas says “winners win, losers lose.” Winners need to know how to win. And if your site is a disaster, how does anyone know they’re winning? How does the electrician know they’re doing good work when they’re installing conduit in a trash pile? How does the drywall crew take pride in their finish when the entire floor is covered in debris?

You can’t. The mess drowns out the excellence. But when the site is clean, quality stands out. Good work is visible. People can see what they accomplished. That visibility creates motivation. That motivation creates more wins. The cycle builds.

What Cleanliness Actually Looks Like on Site

Cleanliness isn’t about perfection or making your site look like a showroom. It’s about finish-as-you-go discipline and creating functional workspaces. Here’s what that means in practice:

  • Trash gets picked up continuously, not just on Friday cleanup day, workers clean as they go, just like Nelson cleans while he cooks
  • Materials are staged in designated areas, not scattered wherever someone dropped them last
  • Walkways and egress routes stay clear so people can move without navigating obstacle courses
  • Each trade has a defined work zone and is responsible for keeping it organized
  • Delivery areas are planned and controlled so material drops don’t block other trades
  • Scrap and cutoffs get removed daily, not piled in corners to “deal with later”
  • Tool staging areas are organized so crews can find what they need without wasting time searching

This isn’t extra work. This is the work. When you plan material deliveries according to inventory buffers, you’re preventing the mess before it starts. When you define work zones in your Takt plan, you’re organizing the site by design instead of fighting chaos by reaction. When you hold trades accountable for their areas, you’re creating ownership instead of excuses.

Nelson’s approach was simple: he gave the foremen time to handle it themselves. When they didn’t, he brought in a crew and set the standard. Now the trades maintain it because the expectation is clear and the system supports them.

The Real Motivation: Treating Workers Like Your Own Kids

Here’s where this gets personal. Nelson said his motivation used to be ego, proving himself as a superintendent. But as he got further into the role and got to know the workers and foremen and trade partners, his mindset shifted: “It’s these guys, the ones that are putting the work in place, that really make the difference. And if we can’t support them and create a stable work environment for them, one, they don’t want to be here. So they don’t put things in properly and they don’t do it correctly and safe. So what’s the point?”

His motivation now is keeping people happy, making them feel fulfilled and valued. We spend more time with each other at work than we do with our families. Why not care for each other? Why not take care of each other and have a good time at work? When you show up, the work is hard, but at least it’s enjoyable to work with your team.

I told Nelson a story about missionaries in my local church. Every 12 weeks we get new young men serving in the area, and I realized I was taking them for granted. Then I thought: my son Reno will be out serving in six months. Would I want the local members to take him for granted? Would I want him to not have meals, to feel frustrated, to have a flat tire and nobody to help him? Would I want him to feel ignored and underappreciated?

That would break my heart. So now I’m taking care of these young men as much as I can, inviting them over, treating them to meals, giving them rides. And when Nelson was talking about the workers on his site, I got the same feeling: what if we treated the craft workers and foremen on site like we would want somebody to treat our own children?

Think about that. If your son or daughter showed up on a construction site as a laborer or apprentice electrician, how would you want the superintendent to treat them? Would you want them working in trash? Would you want them navigating unsafe conditions because nobody bothered to organize the site? Would you want them feeling disrespected and undervalued?

Hell no. You’d want them working in a clean, safe, organized environment where someone cared enough to create stability. You’d want them led by someone who saw them as a person, not just a production unit. You’d want them treated with dignity.

So why aren’t you giving that to the workers on your site right now?

Cleanliness Is Respect Made Visible

When superintendents tell me they’ve run jobs “like this” for 40 years and made money, I have one question: did all the trade partners make money? And did those workers feel respected and loved?

Because I don’t care if the GC made a little bit of profit. I want to know that the people doing the work, the ones putting their bodies on the line, the ones away from their families, the ones making your project happen, felt valued. I want to know they went home at the end of the day feeling like they mattered.

A clean site is proof you care. It’s proof you see them as people, not just labor units. It’s proof you’re willing to invest time and energy into creating an environment worthy of their effort. Cleanliness is respect made visible.

And when your people feel respected, they give you everything. They show up early. They problem-solve instead of complaining. They watch out for each other. They take pride in the work. They want to be there. That’s the culture you’re building when you prioritize cleanliness.

Nelson said it perfectly: “When we can get to know somebody, you can’t want to see them hurt. You can’t want to see them unproductive. You can’t see them not want to be successful in life or at any small task they’re doing.”

Get to know your people. Care about them like you’d care about your own kids. Create an environment that shows them they matter. Start with cleanliness. It’s the first win that makes all the other wins possible. If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow.

FAQ

Q: How do I get trades to maintain cleanliness without me policing them constantly?

Set the standard, make expectations clear, and hold people accountable. When Nelson cleaned his site, he didn’t just pick up trash, he showed everyone what the new normal looked like. Then he made it clear that maintaining that standard was part of the job. If a trade isn’t keeping their area clean, it shows up in their performance grade. Winners want to know how to win, so put the hoop up and measure it. Most trades will rise to the expectation once they see you’re serious about it.

Q: What if I don’t have time to focus on cleanliness with everything else I’m managing?

You don’t have time NOT to focus on it. A messy site costs you more time than a clean one. Workers waste time searching for materials in piles of trash. Trades trip over debris and get injured. Inspectors flag safety violations. Rework happens because quality issues are hidden in the mess. Cleanliness isn’t extra work—it’s the foundation that makes all other work faster and safer. Build it into your daily rhythm and it becomes automatic.

Q: How do I shift the culture on a site that’s been chaotic for months?

Do what Nelson did: bring in a crew and clean house in one day. Create a dramatic before-and-after so everyone sees the difference. Then communicate clearly: this is the new standard, and we’re maintaining it. Hold daily or weekly accountability checks. Recognize trades that keep their areas clean. Address violations immediately. Culture shifts when people see you’re committed and when the new way feels better than the old way.

Q: What’s the connection between cleanliness and safety?

Clean sites are safer sites because hazards are visible, walkways are clear, and people aren’t navigating obstacle courses to do their work. But the deeper connection is respect. When you keep a site clean, you’re telling your workers “I value your safety enough to create an environment where you can work without unnecessary risk.” That respect creates buy-in. Workers who feel valued watch out for each other and follow safety protocols because they know you care about them going home to their families.

Q: How do I balance cleanliness with production pressure when we’re behind schedule?

Clean sites are MORE productive, not less. When materials are organized, workers aren’t wasting time searching. When walkways are clear, trades aren’t tripping or waiting for paths to open up. When the site is stable, rework decreases and quality improves. The idea that you have to choose between cleanliness and production is a false choice created by poor planning. If you’re behind schedule, stabilize the site first, including cleanliness, and then execute from that stable foundation. Chaos compounds delays. Stability creates flow.

On we go.

If you want to learn more we have:

-Takt Virtual Training: (Click here)
-Check out our Youtube channel for more info: (Click here) 
-Listen to the Elevate Construction podcast: (Click here) 
-Check out our training programs and certifications: (Click here)
-The Takt Book: (Click here)

Discover Jason’s Expertise:

Meet Jason Schroeder, the driving force behind Elevate Construction IST. As the company’s owner and principal consultant, he’s dedicated to taking construction to new heights. With a wealth of industry experience, he’s crafted the Field Engineer Boot Camp and Superintendent Boot Camp – intensive training programs engineered to cultivate top-tier leaders capable of steering their teams towards success. Jason’s vision? To expand his training initiatives across the nation, empowering construction firms to soar to unprecedented levels of excellence.

On we go

We Need Superintendents, not Security Guards!

Read 31 min

Stop Being a Security Guard: What Real Superintendents Actually Do

Here’s the deal: if your superintendent spends half the day in a forklift, running to Home Depot, or pumping water out of a trench, you don’t have a superintendent. You have an expensive security guard pointing people in different directions. And that’s costing you production, safety, and the respect of every trade partner on your site.

I’ve seen it everywhere. The super who jumps in equipment “just this one time.” The foreman who answers every question instead of teaching people to find their own answers. The field leader who stays buried in doing instead of leading. They’re working hard, running constantly, and wondering why the project never gets ahead of schedule.

The problem isn’t effort. The problem is they’re in the wrong role doing the wrong work.

The Real Problem: Addiction to Chaos and Certainty

Let’s name what’s actually happening. Superintendents and foremen can get addicted to the adrenaline of chaos. Someone once posted that online and got pushback, “That’s childish. That’s not real.” But it’s absolutely true. We get addicted to those chemicals that rush, that feeling of being needed in the moment.

Think about the foreman who came up through the trades. They know how to unload that delivery. They know how to operate the equipment. They know how to pump out water. They’re getting certainty from doing things they already know how to do. They’re getting significance from being the hero who saves the day. But they don’t know how to plan a schedule. They don’t know how to lead a huddle. They don’t know how to create stability. They don’t know how to manage trade flow.

So where do they go? Back to what gives them certainty and significance. Back to doing instead of leading. And every time they do, they’re abandoning their actual role.

This ties directly to the six basic human needs: certainty, significance, variety, love and connection, growth, and contribution. When someone focuses too much on certainty and significance, they’ll spend all day on equipment and at Home Depot instead of properly delegating, planning, and executing the work. The system failed them by promoting them without training. But now they’re failing everyone else by refusing to step into the role they were given.

The Construction Industry Created This Problem

Here’s what happened: construction has spent decades saying “Hey worker, go be a foreman. Hey foreman, go be a superintendent” without any training. It’s ridiculous. We take great workers and throw them into leadership positions with zero preparation, then blame them when they don’t know what to do.

I’ve worked with companies that trained like crazy when they were $1.5 billion in annual revenue. As they grew larger, training decreased. That makes no sense. You need more capability and more capacity to expand, not less. You cannot scale without developing your people.

And let me be clear about something: we don’t have a worker problem or a foreman problem in this industry. We have a construction culture problem. We have a process problem. Companies are not providing the right training, the right support, the right environments. They’re not taking care of workers. Then they blame people instead of fixing the broken system.

If your company doesn’t train, if you don’t create stability, if you don’t respect trade partners and workers, you’re part of the problem. The United States has entered an economy of scarcity. There are contractors out there using and abusing trade partners, asking for more manpower and materials because they’re not obeying production laws, slowing everything down because they won’t do any training. These are the folks hurting the industry right now.

What Real Superintendents Actually Do

A superintendent is a military commander. A superintendent is a general. Not a security guard. Not someone pointing people in directions. Not someone doing the work of others.

Your job as a superintendent is this: study your drawings every day, be in your schedule planning and executing work every day, lead huddles and communicate every day, and take reflection walks every day. If you’re not doing those things every day, you’re not a builder you’re a broker. And anybody can be a broker. You could take an Amazon delivery driver and put them in a superintendent role as a broker and they’d be just as successful as you are.

Think about that. If all you’re doing is pointing and saying go here, go there, go here, go there—if you’re always running around like a chicken with your head cut off you’re not adding value. You’re not being a superintendent. You’re being an expensive traffic director.

The three builder habits define how you should spend your time: studying your drawings even if you don’t like to, being in your schedule even if you don’t like to, and doing reflection walks and leading people even if you don’t like to. Everything else interspersed throughout your day should be meetings, fanatical communication, directing and coaching and mentoring other people, having hard conversations, solving problems, and building your team.

That’s it. That’s your job. You are paid to watch. You are paid to see. You are paid to think. You are paid to plan. You are paid to execute. You are not paid to work. You want to work? Go be a worker. They’re great people. I respect workers. They make us money. But your job is in a support role.

Flip that organizational triangle in your mind. Workers are at the top putting in the work. Foremen are a layer below supporting them. Superintendents are a layer below supporting foremen. Every other position is a layer below, a layer below, a layer below. If you get out of your support role, you’re letting everyone fall.

Signs You’re Operating as a Security Guard, Not a Superintendent

Watch for these warning signals that tell you you’ve slipped out of your leadership role and into escapism mode:

  • You’re the first person people call when equipment needs to be moved or deliveries need to be unloaded
  • You spend more time in a truck going to Home Depot than you do in your schedule
  • You get interrupted eight or more times per hour with questions that workers should be able to answer themselves
  • You feel a rush of significance when someone says “can you just help me with this one thing”
  • Your phone rings constantly because people have learned you’ll drop everything to solve their problems
  • You haven’t studied the drawings in three days because you’ve been “too busy putting out fires”
  • Trade partners come to you before researching drawings or asking their own office
  • You’re physically exhausted at the end of every day but can’t point to any planning or leadership work you completed

These are symptoms of the same disease: you’re getting your certainty and significance from doing instead of leading. You’re running away from the hard work of building teams, holding hard conversations, and creating systems. Every time you jump in that forklift, you’re telling yourself “at least I know how to do this” instead of learning how to do what you were actually hired to do.

When “Helping” Is Actually Escapism

Getting in a forklift is escapism. Getting in a piece of equipment is escapism. Pumping out water is escapism. Going to Home Depot is escapism. It’s a way for you to run away from doing your job.

When I see a superintendent get up and walk out eight times in an hour to answer questions, I automatically know they don’t have any idea what they’re doing. There’s no reason that kind of instability should be on your project site. They’re selfishly playing savior to get the significance and certainty from being needed.

The antidote is to actually learn how to be a foreman or superintendent. Once you learn that, you tell your trade partner: “Have you researched the drawings? Have you asked your office? Okay, I have time at 3:00 to help you, but right now I’m focused on leader standard work.” You hold them accountable.

And here’s the truth: if you don’t have trade partners grade you on your performance, and if you don’t grade the performance of trade partners, you’re not doing your job. Winners like to win and they need to know how to win. When you refuse to measure performance, what you’re saying is “I’ve got a bunch of losers on my site that I’m trying to play savior with, and I don’t dare put the hoop up because I know they’re not going to make the shots.”

I believe in people. People are smart. People are incredible. People can rise to the occasion. Winners like to win. Winners like to know how to win. So grade your contractors on site. Make expectations clear. Your winners will start to learn how to win, and the people choosing to lose will realize they’re not going to survive in your culture.

Boundaries and Leader Standard Work

Successful superintendents set boundaries. My boundaries are: I’m not going to let you waste my time. I’m not going to do your work for you. You are going to perform and here are the expectations. You’re going to be safe. You’re going to be clean. You’re going to be organized. You will have scheduled deliveries according to material inventory buffers.

A superintendent has to protect their leader standard work. When somebody from the bottom of the ship tells the captain to come down and sweep the deck, the captain has to have the guts to say “Nope, actually I’m going to steer the ship away from icebergs.”

The superintendent who doesn’t expect foremen to do their own job doesn’t respect people. If you think that foreman is too stupid or unable to go do their own job, you don’t respect people. Every worker on site can wear their safety glasses. Every foreman can do their reports and plan their work. Everybody can research their own answers before wasting your time. They’re smart human beings. Everyone can follow the rules. Everyone can fit into the system. Everyone can earn an A.

When you see a superintendent playing savior with people, they’re pushing other people down to lower levels of existence and disrespecting them, elevating themselves into a false sense of importance. They don’t believe in their people.

What Superintendent Boundaries Actually Look Like

Here’s what it means to protect your role and stay in your lane as a field leader:

  • When a foreman asks a question they should know, you respond: “Have you checked the drawings? Have you called your office? Come back at 3:00 if you still need help.”
  • When a delivery shows up and the foreman asks you to unload it, you say: “That’s your crew’s responsibility. Get your operator or call for one.”
  • When someone interrupts your planning time with a non-emergency, you redirect: “I’m in leader standard work right now. Let’s talk at the huddle or schedule time this afternoon.”
  • When a trade partner hasn’t done their homework, you hold them accountable: “This is the third time this week. We’re tracking this in your performance grade.”
  • When your project manager asks you to run to the supply house, you delegate: “I’ll have the assistant superintendent handle that. I’m working on next week’s schedule.”
  • When equipment needs moving and you’re the only one who can operate it, you stop and ask: “Why haven’t we cross-trained anyone else? This is a training failure.”

These boundaries aren’t about being difficult or unhelpful. They’re about respecting your role, respecting the capabilities of your team, and protecting the planning and leadership work that only you can do. Every time you say yes to do someone else’s job, you’re saying no to do your own.

The Dichotomy of Leadership

Here’s the balance: you have to speak up, you have to lead, you have to build a team, you have to hold people accountable, you have to coach and mentor, you have to lead meetings, and you have to communicate—but you have to do it in a non-asshole way.

You cannot go around yelling at people and blaming people and thinking you’re being a superintendent. That’s not how it works. We have a no-asshole rule. You are not allowed to be an asshole and be a leader.

You have to create stability. You have to create order. You have to create connection. You need to take care of the bathrooms. You need to have a nice lunchroom. You need to have huddles. You need to listen to your trade partners. You need to make sure you have collaborative planning cycles in your weekly work plan. You need to create trade flow. You need to listen. You need to apologize. You need to forgive. You need to be that person who supports and respects people.

When you do that, when you say “I am here for our team, I am here for them, I am a support system, I love them, I care for them, I take care of them, I am their number one support, I am bought into them, I want them to succeed, I respect them, I honor them”, then you will get out of the Home Depot truck, you will get out of the loader, you will get out of the forklift, and you will start connecting and leading people in a dynamic and professional way.

What This Means for Companies and Individuals

For companies: stop blaming people. Fix the process. Fix the culture. Provide training. We have to get professional development to our people and not allow security guard behavior. When you start doing this, some of your security guards will quit. Your future superintendents will elevate and rise to the occasion. That’s the goal.

For individuals: stop being a victim. If you don’t have training, you owe yourself an explanation. If you’re not getting that promotion, you need to put yourself on punishment. The higher you get into leadership positions, the more you get to do the gut-wrenchingly hard things. That’s what leadership means.

A superintendent is a professional project management role. You cannot not learn what you need to learn to succeed. You need to switch your focus to growth and contribution. Stop taking and start giving. Learn your role. Study the drawings. Master scheduling and production laws. Learn building information modeling. Learn survey. Learn lift drawings. Learn fundamental superintendent duties. Keep a to-do list. Fill out daily reports properly.

Your friends are the people who tell you hard things. You have got to stop security guard behavior. You need to become a superintendent. And for those of you who want to be real field leaders, who want to create stability, protect trade flow, and build teams that succeed, that is why I do this podcast. That is why I’m in business. You are my why. I am here for you, and I am going to do everything in my power to elevate you. If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow.

FAQ

Q: How do I know if I’m doing “security guard work” versus real superintendent work?

Ask yourself: am I doing things anyone could do, or am I doing things only a trained leader can do? If you’re unloading deliveries, running equipment, or pumping water, that’s security guard work, pointing people in directions without planning or strategy. Real superintendent work is studying drawings, managing the schedule, leading huddles, coaching your team, creating stability, and protecting trade flow. If you’re physically doing the work instead of planning and leading the work, you’re in the wrong mode.

Q: What if I’m the only one on site who knows how to operate the equipment?

Then you’ve failed to train your team. Part of your job as a leader is building capability in others. If you’re the only one who can do something critical, you’ve created a single point of failure. Your job is to develop redundancy, cross-train your people, and ensure the work can happen whether you’re there or not. Jumping in “just this one time” reinforces the pattern and prevents your team from learning. Set boundaries, delegate, and invest in training.

Q: How do I transition from doing to leading if I’ve been promoted from the trades?

Start with the three builder habits: study your drawings every day, work in your schedule planning and executing work every day, and lead huddles and take reflection walks every day. Read leadership books. Listen to podcasts. Attend training like fundamental builder boot camps. Switch your focus from certainty and significance (doing what you already know) to growth and contribution (learning new skills and giving to your team). It requires a mindset shift from fixed to growth, and it won’t happen overnight, but it’s the only way to succeed in the role you’ve been given.

Q: What should I do when a foreman or trade partner asks me a question they should be able to answer themselves?

Set boundaries and hold them accountable. Ask: “Have you researched the drawings? Have you asked your office?” If not, schedule time later to help them, don’t drop everything immediately. Teach them how to find answers instead of being their answer machine. If this is a recurring problem, grade their performance and make self-sufficiency a clear expectation. You’re not helping them by doing their job for them, you’re disrespecting them by assuming they can’t do it themselves.

Q: How can companies fix this culture of superintendents doing the wrong work?

Provide training. Create clear role definitions. Implement leader standard work. Grade superintendent performance on the right metrics—not how many fires they put out, but how well they plan, communicate, create stability, and develop their teams. Stop rewarding heroics and start rewarding systems. Hold people accountable to staying in their role. And if someone refuses to stop doing security guard work after coaching and support, invite them to leave the role and find one that fits their skillset better.

On we go.

If you want to learn more we have:

-Takt Virtual Training: (Click here)
-Check out our Youtube channel for more info: (Click here) 
-Listen to the Elevate Construction podcast: (Click here) 
-Check out our training programs and certifications: (Click here)
-The Takt Book: (Click here)

Discover Jason’s Expertise:

Meet Jason Schroeder, the driving force behind Elevate Construction IST. As the company’s owner and principal consultant, he’s dedicated to taking construction to new heights. With a wealth of industry experience, he’s crafted the Field Engineer Boot Camp and Superintendent Boot Camp – intensive training programs engineered to cultivate top-tier leaders capable of steering their teams towards success. Jason’s vision? To expand his training initiatives across the nation, empowering construction firms to soar to unprecedented levels of excellence.

On we go

Dependence, Feat. Hal Macomber & Felipe Engineer

Read 40 min

The Production Laws Problem: Why Your Project Keeps Failing Laws You Never Learned

You’re running a project. Making decisions every day. The deck crew needs another day, so you extend just that piece of the schedule. The project falls behind, so you add more people. The electrician is waiting for information, so they start anyway and guess. Every decision seems reasonable. Practical. Based on years of experience. And every decision is violating production laws that govern how work actually flows. Laws you’ve never been taught. Laws that determine whether your project succeeds or fails regardless of how hard you work.

Here’s what Hal Macomber taught Jason Schroeder and Felipe Engineer Manriquez in St. Louis after they just walked past five scrum boards to get to a conference room on a multi-million-dollar Takt-planned project. These production laws have been around since the 1920s. A British engineer wrote about mass production and flow production. That material got into Toyota’s hands around 1945 to 1950. The rest of the world didn’t learn about it for decades. And most superintendents still don’t know these laws exist. Which means they’re violating them constantly, wondering why their projects struggle despite their best efforts.

The projects that succeed consistently aren’t led by superintendents who work harder. They’re led by people who understand the production laws that govern how work flows. Who know that Little’s Law says smaller batch sizes always produce faster throughput. Who recognize that bottlenecks are about capacity, not critical paths. Who’ve learned that variation stacks and compounds with dependence in ways that destroy projects. Who understand Kingman’s formula: cycle time multiplied by capacity utilization multiplied by variation effects equals overall duration. Who’ve discovered that fixing overburden first, then variation, then waste is the sequence that actually works.

The Problem Every Superintendent Creates

Walk onto any struggling project and you’ll find the same pattern. Decisions that seem reasonable are violating production laws. The superintendent extends just the deck schedule because that’s where the delay occurred, never recognizing that isolating one piece increases variation throughout the system. Leadership adds more people to recover schedule, never understanding that this violates Little’s Law and Brooks’s Law simultaneously. The electrician starts work without complete information because waiting seems wasteful, never seeing that this creates decision fatigue and compounds variation. Every decision makes sense in isolation. And every decision violates laws that determine project outcomes.

Most superintendents don’t recognize they’re violating production laws. They think they’re making practical decisions. Experience-based choices. Reasonable responses to field conditions. They frame intuitive management as good leadership instead of recognizing it as violation of fundamental principles. They don’t see that their “common sense” is breaking laws as real as gravity, laws that can’t be violated without consequences.

The pattern shows up everywhere in construction. The project team adjusts isolated pieces of the schedule instead of moving everything together to maintain rhythm, violating the law of variation without realizing it. Leadership focuses on eliminating waste before addressing overburden and variation, following Toyota’s misdirection instead of their actual practice. Superintendents push for one hundred percent utilization thinking efficiency equals productivity, never understanding that high utilization plus high variation creates massive delays. Everyone’s violating laws they’ve never been taught.

Think about the parade of trades in a seven-step operation. The first step finishes early but got off to a slow start. If they got off to a slow start, the second step doesn’t have as much work in process to do. They can’t do better than the slow start the previous person had. Variation compounds with dependence. If you’re reliable at a rate of 0.9, ninety percent of what you said you’d get done, 0.9 to the seventh power is a really small number. When percent promises complete drops below fifty percent, you can have people early in the process that are high, but there’s no way the painter at the end can be high because you’ve got all that compounded variation.

The painter at the end of the process bids the job to spray and back-roll the first two coats, roll the third. How often does that happen? It doesn’t. Do they lose money? No, because they bid based on experience. If they actually get to spray and back-roll the first two, they’re in the money. But it doesn’t happen because they’re at the long end of a chain that could be twenty or twenty-five or twenty-eight operations with compound dependence. That’s one of the fallacies, superintendents early in the process thinking that down the chain time can be made up. It can’t. Variation compounds.

The Failure Pattern Nobody Recognizes

This isn’t about lazy superintendents or incompetent teams. This is about violating production laws nobody taught you existed. That intuitive management breaks fundamental principles. That experience-based decisions violate laws as real as physics. That the system never equipped you with the knowledge required to succeed.

Construction culture treats intuition as sufficient for management. The superintendent who makes decisions based on feel. The project manager who relies on experience. The leadership team that trusts gut instinct. These patterns look like wisdom, like practical knowledge, like real-world expertise. And they’re dangerous because they replace systematic understanding with guesswork, production laws with hope, and knowledge with intuition that’s almost always wrong.

So superintendents make reasonable decisions that violate Little’s Law. They focus on waste elimination while ignoring overburden and variation. They push for high utilization without understanding its relationship to delay. They adjust isolated pieces of schedules without recognizing how variation stacks. They never learn that variation doesn’t offset, it stacks. That early slow starts can’t be made up later because variation compounds with dependence. That the production laws governing their work have been known for a century but never taught to them.

Nobody teaches superintendents that pursuing flow is the preferred way of doing any production work. That architects and engineers getting out of flow have the same problems, rework, losing track of what they were doing, their humanness showing up. That the law of variation is so powerful that Toyota normalizes arrival rates on highway onramps with stoplights every six seconds just to reduce variation in the rightmost lane. That Kingman’s formula explains why the middle two highway lanes during rush hour are generally better than the rightmost lane (high variation) or leftmost lane (high utilization).

A Story From the Field About Discovering Production Laws

Jason Schroeder sat down with Hal Macomber and Felipe Engineer Manriquez in St. Louis. They’d just walked past five scrum boards, five different teams using systematic approaches to manage work. Jason had been implementing production laws for three weeks without fully understanding them. His life had already changed. But he needed to understand why these things worked.

Hal started with history. These laws aren’t new. A British engineer in the 1920s wrote about mass production and flow production. Toyota got that material around 1945 to 1950. The rest of the world didn’t learn about it for decades. In 1999, Lean Construction Institute white paper number three said we must use a continuous flow approach, that’s the ground floor, with Last Planner on top to make flow work. That same year, Hal did his first Takt plan project at the Neinan Company in Fort Collins, Colorado. They completed an entire middle school in seventeen weeks using Takt planning and onsite prefabrication.

Jason interrupted, he does that, with an observation that feels revolutionary but isn’t. “I feel like we’re getting back to what was always supposed to be. When somebody says, ‘Oh, we pre-fabricated onsite,’ they act like it’s some new thing. It’s not new. The Hensel Phelps Pentagon renovation used Takt. The Empire State Building used certain things that were line-of-balance, location-based, Takt-ish. These are decades, hundreds of years ago. I think it’s what it was always supposed to be.”

Hal taught the law of variation. Every human being is born with amnesia, they don’t know what was done before them. The systems we encounter are complex. We have variation and chaos in how we procure and build. To bring order back, you need someone to increase awareness of what production laws are. If your project needs superintendent coaching, project support, or leadership development to understand and apply production laws instead of violating them through intuition, Elevate Construction can help your field teams stabilize, schedule, and flow.

He explained that Toyota teaches waste, variation, and overburden in that order. But Hal told Jim Womack in 1999: “You got it backwards. You need to do it in the other order: overburden, variation, and then waste.” Why? Because in construction, there’s already so much systemic pressure on people trying to do their best. Deming said the worker is just trying to do their best with best efforts, but it’s not enough because of how the system operates on them, sometimes operates against them. When you remove overburden from people, you create capacity to look at variation and understand how it’s wreaking havoc. Then you can get better about removing waste to enable flow because now you have breathing room.

Hal used the highway analogy to teach Kingman’s formula. During rush hour, two lanes on a four-lane highway have the highest delay: the rightmost lane (high variation from people getting on and off) and the leftmost lane (high utilization from everyone trying to go fast). The middle two lanes are better because they have lower utilization and are positioned to absorb variation. Major metropolitan areas deal with the rightmost lane variation problem by putting stoplights at onramp bottoms, green every six seconds, normalizing the arrival rate so variation doesn’t ripple through traffic.

How does that apply to construction? You’ve got to look at any given crew and the operations they perform in a period of time. How much of that time do they need to be working? On the Pentagon remodel, those wedges were five-day wedges. For the most part, everybody needed four and a half days to do the work, except Selfland Industries when they first worked there. They had five and a half days of work. There’s no way to get building access late in the day or on Saturday to pick up that half day. Selfland had to reduce their cycle time through improvements and prefabrication. They learned how to purposefully always get it done in four and a half days. That buffer protected them from variation.

Why This Matters More Than Working Harder

When you violate production laws you don’t know exist, working harder makes things worse. More effort applied to broken systems amplifies dysfunction. Longer hours violating Little’s Law extend duration instead of shortening it. Better intentions while violating the law of variation compound problems instead of solving them. The production laws govern outcomes regardless of effort, intention, or experience.

Think about Little’s Law. Smaller batch sizes always produce faster throughput. If you’ve got a batch of ten, at any point in time you’re only working on one, nine are idle. Drop that to batches of five and only four are idle. Get it down to one and you never have anything idle. With the same number of people, it goes through faster. Yet superintendents routinely create massive batches thinking efficiency requires scale, violating Little’s Law constantly without knowing it exists.

Think about bottlenecks. They’re about capacity, not critical paths. On a Toyota Camry production line with ninety-second Takt time, there might be one hundred operations. No more than fifteen percent operate close to seventy-five seconds. Many are in the low sixties. One or two might be below sixty. Making improvements to operations below sixty doesn’t help flow. Making improvements to the dozen operating at seventy-two seconds improves the speed of the line. With Takt planning, you find your bottleneck, establish pace based on what the bottleneck activity can do, and everybody falls in line with higher capacity on their wagon than the limiting operation.

Think about variation stacking. People think variation offsets each other. It doesn’t, it stacks. Variation compounds with dependence. When you’ve got twenty or twenty-five or twenty-eight dependent operations, that 0.9 reliability rate becomes minuscule by the end. The painter at the end can never recover time lost early in the sequence because variation has compounded through every dependent handoff. Yet superintendents in the honeymoon phase lose time thinking it can be made up later. It can’t.

Think about Kingman’s formula. Cycle time multiplied by capacity utilization multiplied by variation effects equals overall duration. If electricians can do overhead in a three-thousand-square-foot area in five days at one hundred percent capacity with no variation, that’s your baseline. Add eighty percent utilization from overtime fatigue and you’re at six-point-two-five days. Add variation from coordination failures and you’re at eight or nine days. The five-day task became nine days because you violated production laws trying to go faster.

The Framework: Learning and Applying Production Laws

The goal isn’t memorizing formulas. It’s understanding fundamental principles that govern how work flows so you can make decisions that work with these laws instead of against them. Building systems that respect production laws instead of violating them through intuition.

Little’s Law says smaller batch sizes produce faster throughput. Limit work in process. Finish as you go. Prepare work ahead of time. Make work ready for people and people ready for work. The paradox that Nicholas Modig and Par Ahlstrom write about in This Is Lean gets resolved, there isn’t a tradeoff when work is ready for people and people are ready for work. You have both flow and high productivity. The problem is construction doesn’t take seriously the make-ready planning process used in Last Planner System.

The law of bottlenecks says identify and optimize capacity constraints systematically. Think about Takt wagons. You establish pace, say two days, for all work on given flow units. Inevitably, most people on those wagons can perform better than two days, but some are the limiting ones bottlenecking you. You’ve set the pace for the whole line based on the bottleneck activity. Everyone else has higher capacity on their wagon. You could add blocking to framer wagons that doesn’t interfere with other work. Or you provide standby capacity, when every fifth wagon has a three-bedroom-plus-den apartment needing another framer, you pull somebody off workable backlog for two days, then return them.

The law of variation says variation stacks and compounds with dependence. Variation in something as simple as window systems over long walls requires engineering to take up tolerances. If you’re plus-or-minus a half-inch and twenty elements are each plus-an-eighth, you now have a problem. Variation doesn’t offset, it stacks. With Takt, you take out variation of pace and frequency of performing. You now have drumbeat. That train has no variation, every two days that car is in a different spot. You’ve taken out variation so there’s no compounding even though dependence still exists.

Address overburden first, then variation, then waste. Overburden shows up as eighty-pound cement bags when OSHA limits are fifty pounds. As cranes loaded beyond capacity. As eleven decisions required every time someone installs parts five hundred times per shift, creating decision fatigue that produces errors. Toyota reduced decisions from eleven to five by kitting interior parts together, everything in the tote is sandal-colored, not mixed with gray. That’s twenty-five hundred fewer decisions per person per shift. Take care of overburden first so people have capacity to see and address variation.

Kingman’s formula: cycle time × capacity utilization × variation effects = overall duration. On the Pentagon, Selfland learned to always finish in four and a half days instead of five and a half because variation would push them over otherwise. They needed buffer within their cycle time to absorb variation. If you’re highly utilized, using almost all available time, and you have variation that causes you to go over, you ruin yourself. Know your utilization. Know your variation. Build buffer to absorb variation instead of planning to one hundred percent utilization with no margin.

The Practical Path Forward

Here’s how this works in practice. You’re making a decision on your project. Before executing it, ask: does this violate production laws?

Am I creating large batches when Little’s Law says smaller is faster? Am I pushing isolated schedule pieces instead of moving everything together to maintain rhythm? Am I ignoring bottlenecks by improving non-limiting operations? Am I increasing variation instead of reducing it? Am I pushing utilization to one hundred percent without buffer for variation? If any answer is yes, find a different approach.

Study the laws systematically. These aren’t basic concepts, they’re fundamental principles that reveal themselves deeper the more you investigate. Jason walked into that conversation having implemented production laws for three weeks. His life had already changed. But sitting with Hal and Felipe, he kept discovering new applications. The law of variation alone opened his eyes to where it shows up in cycle times, project management, instructions, and schedules, everywhere. Investigate thoroughly like Musashi taught.

Apply them in sequence: overburden, variation, waste. Don’t start with waste elimination like most Lean teaching suggests. That was Taiichi Ohno’s misdirection to maintain competitive advantage. Start with overburden, remove systemic pressure so people can breathe. Then address variation, create rhythm and stability. Then eliminate waste, now that you have capacity and stability to see where waste actually exists and how to remove it without breaking flow.

Build systems that respect these laws. Takt planning takes out variation of pace. Make-ready planning addresses Little’s Law by preparing work before starting it. Bottleneck analysis identifies where to focus improvement. Buffer built into cycle times absorbs variation. These aren’t separate systems, they’re integrated approaches respecting production laws instead of violating them.

Why This Protects Projects and People

We’re not just building projects. We’re protecting jobs, families, and futures from the dysfunction that violating production laws creates. And whether we learn and apply these laws or keep violating them through intuition determines whether we build sustainable success or chronic failure.

When you violate production laws, you’re not just hurting efficiency. You’re overburdening people, compounding variation that destroys their work, forcing them into unsustainable patterns. The electrician who had to guess and do rework because the architect didn’t share information wasn’t lazy or incompetent—the system reinforced behaviors where starting and billing was prioritized over having complete information. That’s a production law violation that harms people.

When you understand and apply production laws, you’re protecting everyone. Overburden gets removed so people can do their best work. Variation gets controlled so handoffs are predictable. Batch sizes get optimized so work flows instead of stalling. Capacity gets right-sized with buffer for variation instead of pushed to one hundred percent. People can succeed because systems respect fundamental laws instead of violating them.

Respect for people means building systems based on production laws instead of intuition. It means learning the principles that govern work so decisions work with reality instead of against it. It means stopping the amnesia where every generation rediscovers through pain what was documented a century ago.

The Challenge in Front of You

You can keep making intuitive decisions that violate production laws. You can keep trusting experience built on broken systems. You can keep working harder within approaches that fundamentally don’t work. You can wonder why reasonable decisions produce unreasonable results.

Or you can learn production laws. You can study Little’s Law, the law of bottlenecks, the law of variation, Kingman’s formula. You can understand why overburden first, then variation, then waste is the sequence that works. You can build systems respecting these laws instead of violating them. You can make decisions based on principles instead of guesses.

The projects that succeed consistently aren’t led by superintendents who work harder. They’re led by people who understand production laws. Who know these aren’t basic concepts but fundamental principles revealing themselves deeper the more you investigate. Who’ve learned that what seems reasonable often violates laws as real as gravity. Who’ve discovered that systematic understanding beats intuitive management every time.

These laws have been known since the 1920s. Toyota has built competitive advantage on them since the 1940s. Construction is just starting to rediscover them. You can be part of that rediscovery or keep violating laws you don’t know exist.

Investigate this thoroughly.

On we go.

 

Frequently Asked Questions

What are the five core production laws and why do they matter?

Little’s Law: smaller batch sizes produce faster throughput, limit work in process, finish as you go. Law of Bottlenecks: identify and optimize capacity constraints, not non-limiting operations. Law of Variation: variation stacks and compounds with dependence, it doesn’t offset. Kingman’s Formula: cycle time × capacity utilization × variation effects = overall duration. The overburden-variation-waste sequence: address overburden first so people have capacity to see variation, then eliminate waste to enable flow. These aren’t suggestions, they’re laws governing how work flows that you violate at your peril.

Why should I address overburden before variation and waste?

In construction there’s already massive systemic pressure on people trying to do their best. Deming said best efforts aren’t enough when the system operates against you. When you remove overburden from people, you create capacity to look at variation and understand how it’s wreaking havoc on your system. Then you can get better about removing waste to enable flow because now you have breathing room. Toyota taught waste-first to maintain competitive advantage, it was misdirection. The actual sequence that works is overburden, then variation, then waste.

How does variation compound with dependence in ways that destroy projects?

In a seven-step operation, if you’re reliable at 0.9 (ninety percent), 0.9 to the seventh power is a really small number. Early slow starts can’t be made up later because variation compounds through every dependent handoff. The painter at the end of a twenty-operation sequence can never recover time lost early. That’s why they bid assuming they won’t get to spray and back-roll, they price in the compounded variation they know is coming. Superintendents in the honeymoon phase lose time thinking it can be made up. It can’t. Variation stacks—it doesn’t offset.

What does Kingman’s formula mean practically for my project?

If a task takes five days at one hundred percent capacity with no variation, that’s baseline. Add eighty percent utilization from fatigue and it becomes six-point-two-five days. Add variation from coordination failures and you’re at eight or nine days. The five-day task became nine days because you violated production laws. Selfland on the Pentagon learned this—they needed four-and-a-half-day actual work in five-day Takt wagons because variation would push them over otherwise. If you’re highly utilized with high variation, you ruin yourself. You need buffer within cycle time to absorb variation.

How do I start learning and applying these laws on my projects?

Study them systematically—these reveal themselves deeper the more you investigate. Read This Is Lean by Modig and Ahlstrom. Study Toyota’s actual practices, not just their public teaching. Implement Takt planning to remove variation of pace. Use Last Planner System for make-ready planning that respects Little’s Law. Analyze bottlenecks to focus improvements where they matter. Build buffer into cycle times for variation absorption. Before any decision, ask: does this violate production laws? If yes, find a different approach that works with these laws instead of against them.

If you want to learn more we have:

-Takt Virtual Training: (Click here)
-Check out our Youtube channel for more info: (Click here) 
-Listen to the Elevate Construction podcast: (Click here) 
-Check out our training programs and certifications: (Click here)
-The Takt Book: (Click here)

Discover Jason’s Expertise:

Meet Jason Schroeder, the driving force behind Elevate Construction IST. As the company’s owner and principal consultant, he’s dedicated to taking construction to new heights. With a wealth of industry experience, he’s crafted the Field Engineer Boot Camp and Superintendent Boot Camp – intensive training programs engineered to cultivate top-tier leaders capable of steering their teams towards success. Jason’s vision? To expand his training initiatives across the nation, empowering construction firms to soar to unprecedented levels of excellence.

On we go

Brooks’s Law, Feat. Felipe Engineer

Read 36 min

The Brooks’s Law Problem: Why Adding More People and Overtime to Late Projects Makes Them Later

Your project is slipping. The critical path is extending. The owner is asking questions. So you do what every superintendent does when they’re behind. You add more people. You authorize overtime. You push harder. You tell yourself that more hands and more hours equal more speed. And then you watch the project duration extend instead of shrink. You’ve just violated Brooks’s Law. And now you’re paying the price.

Brooks’s Law comes from software development. Fred Brooks at IBM studied thousands of projects and found something that contradicted everything project managers believed. When projects were deemed behind schedule, adding more people or spending overtime didn’t make them finish earlier. The data was clear. More people late in the project increases duration. More overtime beyond two weeks kills productivity. The go-to project management reaction, throw resources at the problem, was exactly wrong. And construction follows the same pattern.

The projects that recover successfully aren’t led by superintendents who add more people. They’re led by people who understand that communication channels multiply exponentially as crew size increases. Who recognize that context switching destroys productivity every time someone gets interrupted. Who know that overtime beyond nine weeks drops capacity from one hundred percent to sixty percent or lower. Who’ve learned that the answer to being behind is stabilizing the project so you can optimize it, not throwing manpower and materials at problems hoping speed increases.

The Problem Every Superintendent Creates

Walk onto any project that’s behind schedule and you’ll find the same pattern. Leadership panicked. They added crews. They authorized overtime. They pushed harder. And the project got worse instead of better. More coordination problems. More communication breakdowns. More rework. More delays. The solution they implemented was the exact thing extending their duration. They violated Brooks’s Law thinking they were solving their problem.

Most superintendents don’t recognize they’re making it worse. They think adding people is practical. Authoritative. Decisive leadership responding to crisis. They frame throwing resources at problems as taking action instead of recognizing it as violation of production laws. They don’t see that more people means exponentially more communication channels, that more overtime means dramatically lower productivity, that the thing they’re doing to speed up is exactly what’s slowing down.

The pattern shows up everywhere in construction. The project falls behind, so leadership brings in another concrete crew, never analyzing how many communication channels that creates. The schedule slips, so they authorize sixty-hour weeks, never recognizing that sustained overtime drops productivity to sixty percent. The punch list grows, so they throw more people at it, never acknowledging that fixing defects after the fact takes four to twenty-five times longer than fixing them when noticed. The superintendent pushes harder instead of stabilizing smarter.

Think about what this creates. You’ve got ten people on your crew. That’s forty-five communication channels. Every time someone needs information, there are forty-five potential paths it could travel. Every time there’s a change, forty-five channels need updating. Every coordination meeting requires managing forty-five relationships. Now double the crew to twenty people. You don’t have ninety channels. You have one hundred ninety. The complexity doesn’t scale linearly. It explodes exponentially. And you wonder why coordination is breaking down.

Meanwhile, you’re authorizing overtime thinking more hours equals more production. Week one, maybe you see gains. Week two, productivity starts dropping. Week three, people are exhausted. By week nine, you’re operating at sixty percent capacity. That five-day task now takes eight-point-three days. Add in the variation created by tired crews making mistakes, communication breaking down, and coordination failing, and that five-day task is now taking ten days or more. You threw overtime at the problem and extended duration instead of shortening it.

The Failure Pattern Nobody Recognizes

This isn’t about never adding people or avoiding all overtime. This is about recognizing that Brooks’s Law governs how projects actually flow. That adding manpower late in a project increases duration. That sustained overtime kills productivity. That the complexity of communication grows exponentially, not linearly. That most “solutions” to being behind make the problem worse.

Construction culture sometimes treats adding resources as the only response to problems. The superintendent who sees red on the schedule and immediately authorizes more crews. The project manager who demands overtime when tasks slip. The leadership team that thinks throwing people and hours at problems demonstrates decisive action. These patterns look like strength, like taking control, like solving problems. And they’re dangerous because they violate production laws that can’t be broken without consequences.

So superintendents add crews thinking it increases capacity. They authorize overtime thinking it buys time. They push harder thinking effort equals results. They never recognize that communication channels are multiplying exponentially, that context switching is destroying productivity that overtime is killing capacity, that the thing they’re doing to recover is extending their duration. They don’t see that Brooks’s Law applies to construction just like it applies to software.

The story always goes the same way. Project falls behind. Leadership adds more people. Communication breaks down because now there are exponentially more channels. Coordination fails because nobody can track all the handoffs. Onboarding consumes existing crew productivity teaching new people the project. Context switching destroys focus as interruptions multiply. Overtime extends from two weeks to two months. Productivity drops from one hundred percent to sixty percent. The five-day task becomes ten days. The project duration extends. Leadership adds more people and more overtime thinking that’ll fix it. The problem compounds. And nobody connects the extended duration to their violation of Brooks’s Law.

Nobody teaches superintendents that communication channels follow the formula n times n-minus-one divided by two. That three people create three channels but ten people create forty-five channels and two hundred people create nineteen thousand nine hundred channels. That context switching costs twenty percent productivity every time someone gets interrupted. That multitasking temporarily decreases IQ. That sustained overtime beyond nine weeks kills capacity. That the answer to being behind isn’t throwing more resources at problems.

A Story From the Field About Communication Channels

Felipe Engineer was discussing Brooks’s Law with Jason. Someone had made a mean comment on LinkedIn, and Felipe, demonstrating the character he’s known for, called the person and spent two and a half hours on a Friday night mending bridges. That’s Felipe. Always building relationships instead of burning them. And that dedication to communication makes him the perfect person to explain why adding people destroys projects.

Here’s the math. Jason and Felipe talking creates one communication channel. Add one more person and you’ve got three people with three channels. Not a big jump. But add more people and watch what happens. Four people creates six channels. Five people creates ten channels. Eight people creates twenty-eight channels. Ten people creates forty-five channels. The formula is n times n-minus-one divided by two. And it grows exponentially, not linearly.

Think about a regular project site. Even a twenty-million-dollar job can easily have two hundred construction workers and management staff. That’s nineteen thousand nine hundred communication channels for just two hundred people on a single project. Every time information needs to move, there are nineteen thousand nine hundred potential paths. Every coordination meeting requires managing exponential complexity. Every change requires updating thousands of relationships. And superintendents wonder why communication breaks down when they add more crews.

The communication problem creates the context switching problem. You’re focused on a task. Operating at one hundred percent productivity. Then someone interrupts you. A text message. A question. A coordination issue. You stop. You address the interruption. Then you try to go back to your task. You lose twenty percent of your time just switching back. The longer the interruption, the worse it gets. Interrupt someone writing an email and watch how long it takes them to start typing again after you finish talking. The delay is real. The productivity loss is measurable.

The more you multitask, the slower you get. And multitasking temporarily decreases your IQ. Yet construction runs on interruptions. The foreman coordinating five trades. The superintendent managing ten foremen. The project manager juggling twenty issues simultaneously. Everyone’s multitasking. Everyone’s context switching. Everyone’s operating at reduced capacity. And then leadership wonders why adding more people makes things worse instead of better.

Here’s another pattern Brooks’s Law predicts. The end of projects is when duration extends most dramatically. Construction typically adds manpower at the end trying to finish. All that does is extend overall project duration. Look at the gap between substantial completion and the last worker leaving the site. It’s huge. Because crews are doing shoddy work just to get signed off, then having to come back and fix it properly. Rework takes four to twenty-five times longer than fixing defects when noticed. That punch list item that would have taken fifteen minutes to fix during construction now requires remobilization, coordination, and hours of work.

The answer isn’t adding more people to do more rework faster. The answer is Takt planning with smaller batch sizes, limiting work in process, finishing as you go, and quality at the source. If your project needs superintendent coaching, project support, or leadership development to stabilize systems instead of throwing resources at problems, Elevate Construction can help your field teams stabilize, schedule, and flow.

Why This Matters More Than Looking Busy

When you add people and overtime to late projects, you’re not recovering. You’re extending duration. Brooks’s Law isn’t a suggestion. It’s a production law that governs how projects actually flow. You can’t violate it and expect success any more than you can violate gravity and expect to fly.

Kingman’s formula proves Brooks’s Law mathematically. The cycle time of any process multiplied by capacity utilization multiplied by the effects of variation equals overall duration. Take electricians doing overhead in a three-thousand-square-foot area in five days. That’s only if they’re at one hundred percent capacity with no variation. Add overtime and capacity drops to sixty percent. Now that five-day task takes eight-point-three days. Add in variation from communication breakdowns, context switching, coordination failures, and exhausted crews making mistakes, and you’ve probably gone from eight-point-three to ten days or more. You threw overtime at a five-day task and turned it into a ten-day task.

Communication channels multiply the problem. You started with a crew that had established rhythms and clear handoffs. You added people thinking more hands equal more speed. But now coordination requires managing exponentially more communication channels. Information that flowed smoothly through established relationships now gets lost in the complexity. Handoffs that were clear become confused. The productivity you had drops as everyone spends time coordinating instead of producing.

Context switching destroys what’s left. Your existing crew was focused. Operating efficiently. Then you brought in new people who need onboarding. Teaching them the project pulls your productive crew away from work to transfer knowledge. Every interruption costs twenty percent productivity. Every context switch compounds the loss. The capacity you thought you were adding actually consumed the capacity you had.

Watch for These Signals Brooks’s Law Is Destroying Your Project

Your project is vulnerable when you see these patterns:

  • Leadership response to being behind is immediately adding crews without analyzing communication channel multiplication
  • Overtime extending beyond two weeks with no end date, showing that temporary measures have become permanent dysfunction
  • Punch lists growing exponentially as crews do shoddy work just to get signed off then have to remobilize to fix it properly
  • Coordination meetings consuming more time than production as exponentially multiplying communication channels overwhelm the team

The Framework: Stabilize Then Optimize Instead of Throwing Resources

The goal isn’t avoiding all overtime or never adding people. It’s understanding Brooks’s Law so you know when adding resources helps versus when it hurts. Recognizing that adding manpower late in projects extends duration. Building systems that don’t require heroic effort and violation of production laws to succeed.

Short-term overtime can create gains if kept under two weeks. Beyond that, productivity drops dramatically. By nine weeks, you’re operating at sixty percent capacity or lower. The task that should take five days now takes eight-point-three days or more when you factor in variation. The overtime you’re paying for is extending duration instead of shortening it. If you need overtime beyond two weeks, your problem isn’t hours—it’s systems.

Communication channels grow exponentially with crew size. Three people create three channels. Ten people create forty-five channels. Two hundred people create nineteen thousand nine hundred channels. Every time you add people, you’re not just adding hands, you’re adding exponential coordination complexity. Sometimes that’s necessary. But recognize the cost. Build systems to manage it. Don’t assume that doubling crew size doubles productivity. It doesn’t. It multiplies communication complexity and often reduces productivity.

Context switching costs twenty percent productivity every interruption. Multitasking decreases IQ temporarily. Focus enables flow. Interruptions destroy it. When you add people to late projects, you’re adding interruptions. Onboarding requires pulling productive people away from work. Coordination requires constant communication. The capacity you thought you were adding gets consumed by context switching before it produces anything.

Quality at the source prevents rework multiplication. Fixing defects when noticed takes minutes. Fixing them on punch lists takes four to twenty-five times longer because now you need remobilization, coordination, and reinstallation. Finish as you go. Do it right the first time. Build quality in instead of inspecting it in later. The time saved on rework exceeds any gains from rushing through shoddy work.

Stabilize before you optimize. When your project is behind, the answer isn’t throwing more people and more hours at it. The answer is stabilizing the systems so you can optimize flow. Smaller batch sizes. Limited work in process. Finishing as you go. Takt planning to create rhythm. Once systems are stable, then you can optimize. But optimization on unstable systems just creates more chaos.

The Practical Path Forward

Here’s how this works in practice. Your project is behind. You’re tempted to add crews and authorize overtime. You need to decide whether that helps or hurts.

First question: how long will the overtime last? If less than two weeks and you have a specific recovery plan, maybe it helps. If indefinite or longer than two weeks, you’re killing productivity instead of increasing it. By nine weeks you’ll be operating at sixty percent capacity. Find a different solution.

Second question: how many communication channels are you creating? Use the formula. Current crew size times current crew size minus one divided by two. That’s your current channels. Now calculate what happens when you add people. If you’re going from ten people (forty-five channels) to twenty people (one hundred ninety channels), you’re not doubling capacity, you’re quadrupling complexity. Build coordination systems before adding people or accept that productivity will drop.

Third question: what’s driving the problem? If you’re behind because systems are broken, adding people makes it worse. Stabilize first. Fix the workflow. Establish rhythm. Then optimize. Throwing resources at systemic problems just multiplies the dysfunction across more people.

Execute based on production laws instead of panic. Brooks’s Law says adding people to late projects makes them later. Kingman’s formula says capacity utilization and variation determine duration. Context switching costs twenty percent productivity per interruption. These aren’t suggestions. They’re laws. Build your recovery strategy around them or watch your recovery fail.

Why This Protects Projects and People

We’re not just building projects. We’re protecting jobs, families, and futures from the burnout that Brooks’s Law violations create. And whether we stabilize systems or throw resources at problems determines whether we build sustainable success or temporary chaos.

When you add overtime beyond two weeks, you’re not protecting jobs. You’re burning people out. Productivity drops to sixty percent. Quality suffers. Mistakes multiply. People go home exhausted instead of fulfilled. Their families suffer because they’re working sixty-hour weeks producing less than they would in forty hours with stable systems. The overtime you’re requiring is destroying the people you’re claiming to protect.

When you add people to late projects without managing communication complexity, you’re not increasing capacity. You’re creating chaos. Coordination breaks down. Information gets lost. Handoffs fail. Everyone spends more time in meetings trying to coordinate than actually producing. The people you added to help are consuming the productivity of the people you had.

Respect for people means building systems that don’t require heroic effort to succeed. It means recognizing that Brooks’s Law applies to construction just like it applies to software. It means stabilizing before optimizing instead of throwing resources at problems. It means protecting people from the burnout that sustained overtime creates and the chaos that exponential communication channels produce.

The Challenge in Front of You

You can keep violating Brooks’s Law. You can keep adding people to late projects thinking more hands equal more speed. You can keep authorizing overtime beyond two weeks thinking more hours equal more productivity. You can keep pushing harder instead of stabilizing smarter. You can watch your duration extend and wonder why the solution isn’t working.

Or you can follow production laws. You can recognize that communication channels grow exponentially. You can understand that context switching costs twenty percent productivity. You can acknowledge that sustained overtime kills capacity. You can stabilize systems before throwing resources at them. You can build recovery strategies that work with Brooks’s Law instead of against it.

The projects that recover successfully aren’t led by superintendents who add more people. They’re led by people who understand production laws. Who recognize that the answer to being behind is stabilizing systems, not throwing resources. Who know that Brooks’s Law applies to construction just like every other domain. Who’ve learned that fret not if you’re getting behind, there are absolutely things you can do, and the answer is not just throw more people at it.

Your project is behind. You’re tempted to add crews and authorize overtime. Before you do, calculate the communication channels. Check how long the overtime will last. Analyze what’s driving the problem. Follow Brooks’s Law instead of violating it.

Stabilize. Then optimize.

On we go.

 

Frequently Asked Questions

What exactly is Brooks’s Law and why does it matter for construction?

Brooks’s Law states that adding people to late projects makes them later. It comes from Fred Brooks studying thousands of IBM software projects and finding that the go-to response, throw more people and overtime at problems—actually extended duration instead of shortening it. Construction follows the same pattern. Communication channels grow exponentially as crew size increases. Context switching destroys productivity. Sustained overtime kills capacity. The formula for communication channels is n times n-minus-one divided by two, meaning ten people create forty-five channels but twenty people create one hundred ninety channels. You’re not doubling capacity when you double crew size, you’re quadrupling coordination complexity.

How long can I run overtime before productivity drops significantly?

Short-term overtime under two weeks can create gains. Beyond that, productivity drops dramatically. The absolute maximum before exponential decline is nine weeks, and by that point you’re operating at sixty percent capacity or lower. A five-day task now takes eight-point-three days when you factor in reduced capacity, and closer to ten days when you add variation from exhausted crews making mistakes. The overtime you’re paying for is extending duration instead of shortening it. If you need overtime beyond two weeks, your problem isn’t hours, it’s systems that need stabilizing.

Why does context switching cost so much productivity?

When you’re focused on a task at one hundred percent productivity and get interrupted, you lose twenty percent of your time just switching back to the task. Your brain has to rebuild the context it had before the interruption. The longer the interruption and the more complex the mental work, the worse the loss. Interrupt someone writing an email and watch the delay before they start typing again, that’s context switching cost made visible. Multitasking makes it worse and temporarily decreases IQ. Construction runs on interruptions, which means everyone’s operating at reduced capacity all the time. Adding more people multiplies interruptions and compounds the productivity loss.

What should I do instead of adding people when my project falls behind?

Stabilize before you optimize. Identify what’s driving the problem, is it broken workflows, poor coordination, quality issues, or systemic dysfunction? Fix the systems first. Implement Takt planning to create rhythm. Use smaller batch sizes and limit work in process. Finish as you go with quality at the source. Once systems are stable, then you can optimize flow. Throwing people at unstable systems just multiplies the dysfunction across more crew members. The answer to being behind is building systems that don’t require heroic effort to succeed, not authorizing overtime and adding crews hoping harder work produces better results.

How do I manage communication channels when I do need to add people?

Calculate what you’re creating first using n times n-minus-one divided by two. If you’re going from ten people (forty-five channels) to twenty people (one hundred ninety channels), build coordination systems before adding people or accept that productivity will drop. Use scrum team structures to break large groups into smaller coordinated units. Establish clear communication protocols. Create standard work for handoffs. Limit who needs to coordinate with whom. Recognize that you’re not just adding hands, you’re adding exponential complexity. Plan for it instead of hoping it won’t matter.

If you want to learn more we have:

-Takt Virtual Training: (Click here)
-Check out our Youtube channel for more info: (Click here) 
-Listen to the Elevate Construction podcast: (Click here) 
-Check out our training programs and certifications: (Click here)
-The Takt Book: (Click here)

Discover Jason’s Expertise:

Meet Jason Schroeder, the driving force behind Elevate Construction IST. As the company’s owner and principal consultant, he’s dedicated to taking construction to new heights. With a wealth of industry experience, he’s crafted the Field Engineer Boot Camp and Superintendent Boot Camp – intensive training programs engineered to cultivate top-tier leaders capable of steering their teams towards success. Jason’s vision? To expand his training initiatives across the nation, empowering construction firms to soar to unprecedented levels of excellence.

On we go

And then a Miracle Happens!

Read 42 min

The Miracle Problem: Why “And Then a Miracle Happens” Is Not a Recovery Strategy

Your project hit variation. The deck pour ran into problems. The vertical concrete is behind. Materials didn’t show. Weather shut you down for three days. Now you’re staring at a schedule that doesn’t work anymore and everyone’s asking what the plan is. So you do what most superintendents do. You dissolve some logic in Primavera. You shift a few activities. You tell yourself it’ll work out. You’re banking on a miracle.

Here’s the cartoon that Keith Cunningham loved so much he bought it. Two people standing at a chalkboard. Math on the left side. An equal sign. More math on the right side showing the desired result. And in the middle, written on the board: “And then a miracle happens.” The professor reviewing the work says, “I think we need some more detail around step two.” That’s most construction schedule recovery. We do some things. Then we hope for the best. Then we expect success. We’re missing step two—the actual plan that follows production laws.

The projects that recover from variation aren’t led by superintendents who hope harder. They’re led by people who recognize the impact immediately, analyze it honestly, make a plan that follows production laws, and execute that plan without wishful thinking. Who understand that throwing manpower and materials at problems increases project duration instead of decreasing it. Who know that dissolving logic to make the schedule look better is the same as writing “and then a miracle happens” on your recovery plan. Who’ve learned that anything increasing variation will increase your project duration—and most “solutions” increase variation.

The Problem Every Superintendent Creates

Walk onto any troubled project and you’ll find the same pattern. Something went wrong. The schedule broke. And instead of following production laws to recover, leadership is hoping for miracles. They’re throwing more manpower at the problem thinking speed will increase. They’re shifting isolated pieces of the schedule thinking localized adjustments won’t ripple. They’re dissolving logic in the scheduling software thinking fake plans will somehow produce real results. They’re doing the construction equivalent of writing math on the left, “and then a miracle happens” in the middle, and the completion date they want on the right.

Most superintendents don’t recognize they’re hoping for miracles. They think they’re making practical decisions. Realistic adjustments to handle variation. Strategic responses to field conditions. They frame wishful thinking as planning instead of recognizing it as the avoidance of actual analysis. They don’t see that their “recovery strategy” violates every production law that governs how work actually flows.

The pattern shows up everywhere in construction. The concrete schedule hits variation on decks, so leadership shifts just the deck schedule out while leaving walls and columns where they were, never analyzing whether that creates more problems than it solves. The project falls behind, so they throw more crews at it, never recognizing that Brooks’s Law says adding manpower late in a project increases duration instead of decreasing it. The superintendent sees the critical path extended, so they dissolve some logic to make it look better, never acknowledging they just replaced a realistic plan with a fantasy. The team hopes harder instead of planning better.

Think about what this creates. Your concrete crew is running a rhythm. Columns on day one. Walls on day two. Decks on days three, four, and five. Hook time from the tower crane is scheduled. Procurement is sequenced. Handoffs are consistent. Then the deck schedule hits variation. Someone suggests shifting just the decks out a few days. Sounds reasonable. Isolated problem, isolated solution. Except now you’ve broken the rhythm. Different crane schedules. Different procurement times. Different manpower cycles. Different handoffs. You’ve increased variation trying to fix variation. And increased variation increases project duration.

Meanwhile, you’re congratulating yourself for “fixing” the schedule. You adjusted for the problem. You accommodated the reality. You updated the plan. Except you didn’t. You dissolved logic. You created inconsistent handoffs. You violated production laws. You wrote “and then a miracle happens” in the middle of your recovery strategy and called it planning.

The Failure Pattern Nobody Recognizes

This isn’t about never adjusting schedules or ignoring field realities. This is about recognizing that most “solutions” to variation actually increase variation instead of decreasing it. That throwing manpower and materials at problems extends duration instead of shortening it. That hope is not a strategy and dissolving logic is not planning.

Construction culture sometimes treats urgency as a substitute for analysis. The superintendent who makes fast decisions without checking production laws. The scheduler who dissolves logic to hit the date leadership wants to see. The project team that throws more resources at problems without analyzing whether that helps or hurts. These patterns can look like action, like pragmatism, like getting things done. And they’re dangerous because they replace systematic thinking with wishful thinking, production laws with hope, and actual plans with miracles.

So superintendents shift isolated pieces of schedules thinking it won’t create ripples. They add crews thinking more people equals more speed. They work overtime thinking hours equal productivity. They never recognize that these “solutions” violate production laws that govern how work actually flows. They don’t see that their recovery strategies are built on miracles, not math.

The story always goes the same way. Project hits variation. Leadership makes quick decision without analyzing production laws. Schedule gets “fixed” by dissolving logic or shifting isolated activities. Everyone feels better because the schedule looks better. Except the schedule isn’t realistic anymore. It’s fantasy. The fake plan fails. More variation occurs. More miracle-based solutions get applied. The dysfunction compounds. The project fails. And leadership never connects the failure to their refusal to follow production laws.

Nobody teaches superintendents that Kingman’s formula, Little’s Law, the law of bottlenecks, the law of variation, and Brooks’s Law actually govern how projects flow. That you can’t violate these laws and expect success any more than you can violate gravity and expect to fly. That when variation occurs, the right response is systematic analysis followed by a plan that respects production laws, not quick fixes that hope for miracles.

A Story From the Field About Following Production Laws

Felipe Engineer and Jason were at the St. Louis community of practice doing a four-and-a-half-hour introduction to the Last Planner System. Somebody asked: “When you’re talking about Takt planning and Last Planner, what happens when variation occurs?” Felipe nailed it. When variation occurs, when something happens, you immediately show the reality of what happens. Then you plan. You make a plan that makes sense that follows production laws that will ensure you either can hit the end date or you know what the situation is so you can be realistic and go get help.

You always want to widen your circle. You always want to get help. But you always want to tell the truth. Do not lie. Do not withhold the truth. Do not avoid showing an impact in a schedule. Do not avoid putting the impact in there. You have to show it. You’re not legally allowed to not show the impact. Once the impact is shown, then you make a plan. You can’t just dissolve logic in Primavera or Asta or Microsoft Project. You can’t fake a plan. That’s the same as saying one plus two plus and then a miracle happens equals the result you want. Wishful thinking never gets anybody anywhere.

Here’s a concrete example. Weston Woolsie at Okland taught Jason about smaller batch sizes and smaller crew sizes for concrete. Everything in a concrete plan should be Takt’d out. Everything. One hundred percent. Columns, walls, decks—all on consistent rhythms with consistent handoffs. Now somebody asks: what do you do when variation happens? What if variation just happens with the deck or just with the walls?

The instinct is to shift just that piece. Deck schedule hits problems, shift the deck schedule. Leave everything else alone. Sounds reasonable. But let’s test it against production laws. Does shifting just the deck schedule help with Kingman’s formula? Kingman’s formula says cycle time multiplied by capacity utilization multiplied by effective variation tells you overall process time. To improve that, you need consistent cycle times in a rhythm, reduced variation, and operation at one hundred percent capacity. Shifting just the deck schedule breaks the rhythm, increases variation, and disrupts capacity. So no, it doesn’t help with Kingman’s formula.

Does it help with the law of bottlenecks? If your decks had variation and you’re considering moving just the deck schedule out while leaving walls and columns isolated, does that help you see and optimize bottlenecks? No. You’ve increased variation, which violates another law and brings in so much inconsistent data that you cannot isolate and optimize bottlenecks.

Does it help with the law of variation? If you changed the sequence and interrelatedness between walls, columns, and decks and didn’t move them together, does that increase or decrease variation? It increases variation. Now you have different handoffs. Different crane schedules. Different procurement times. Different manpower cycles. Different everything. If you ever see concrete crews where they’re moving people from decks to walls to columns, shuffling everyone everywhere, you’re losing massive time because of context switching. You’re never going to make production.

Does it help with Little’s Law? Little’s Law says rightsize batch sizes, finish as you go, limit work in process. From that standpoint, you probably need to finish everything together as you go. Shifting just one piece doesn’t align with Little’s Law.

Does it help with Brooks’s Law? Brooks’s Law says when you put more manpower on a task, especially in later parts of that task or project duration, it increases throughput time and project duration. If you have a problem with decks and don’t move columns and walls with it, you’re likely going to shift manpower from one area to another and increase crew counts, which actually slows down your production rhythm. The adjustment doesn’t fit with Brooks’s Law either.

The lesson from the Germans Yanosh and Marco: sometimes in Takt’d systems, if you have variation in the system, it might be better to move everything together in that variation and keep it consistently together. Keep the workflow rhythm, the trade flow rhythm, and the logistical rhythm together instead of creating little ripples of variation which also create inconsistency in handoffs. When you have a problem on your schedule, when variation shows up, don’t freak out and make random decisions. Don’t wish for a miracle. Sit back and analyze the schedule and the impact, be realistic with it, and shift everything in a commonsensical manner according to production laws.

Why This Matters More Than Looking Busy

When you respond to variation by hoping for miracles instead of following production laws, you’re not recovering your project. You’re extending its duration. Every decision that increases variation increases project duration. Every violation of production laws costs time. Every fake plan built on dissolved logic creates more problems than it solves.

Think about the five production laws that govern how projects actually flow. Little’s Law says limit work in process, rightsize batch sizes, adjust procurement to meet dates on a rhythm, do quality work as you go, and finish as you go. The law of bottlenecks says identify and optimize constraints systematically. The law of variation says reduce variation to improve flow. Kingman’s formula says improve cycle times on a rhythm with consistent capacity and reduced variation. Brooks’s Law says adding manpower and materials late in a project increases duration instead of decreasing it.

These aren’t suggestions. They’re not guidelines. They’re laws. You can’t violate them and expect success. When your project hits variation and you respond by throwing more crews at it, you’re violating Brooks’s Law. When you shift isolated pieces of the schedule instead of moving everything together to maintain rhythm, you’re violating the law of variation and Kingman’s formula. When you dissolve logic to make dates look achievable, you’re abandoning Little’s Law and the law of bottlenecks. You’re replacing production laws with hope. Math with miracles.

The cartoon Keith Cunningham bought captures this perfectly. Math on the left. “And then a miracle happens” in the middle. Results on the right. The professor says, “I think we need some more detail around step two.” When you dissolve logic in your schedule, you’ve eliminated step two. When you throw manpower at problems without analyzing Brooks’s Law, you’ve replaced step two with hope. When you shift isolated activities without checking whether that increases variation, you’re banking on miracles instead of following production laws.

If your project needs superintendent coaching, project support, or leadership development to build teams that follow production laws instead of hoping for miracles, Elevate Construction can help your field teams stabilize, schedule, and flow.

Watch for These Signals You’re Hoping for Miracles

Your project is vulnerable to miracle-based planning when you see these patterns:

  • Schedule “fixes” that dissolve logic or shift isolated activities without analyzing production laws, revealing that planning has been replaced with wishful thinking
  • Responses to variation that throw more manpower and materials at problems without checking Brooks’s Law, showing that hope is being substituted for systematic analysis
  • Recovery strategies that break rhythms and increase variation while claiming to fix problems, indicating that solutions are creating more dysfunction than they’re solving

The Framework: Following Production Laws When Variation Occurs

The goal isn’t avoiding all variation or pretending problems don’t exist. It’s responding to variation systematically instead of hopefully. Following production laws instead of banking on miracles. Making actual plans instead of fake ones.

Show the reality immediately when variation occurs. Do not lie. Do not withhold truth. Do not avoid showing impact in the schedule. You’re not legally allowed to hide it. You have to show what actually happened. Once the impact is shown, then you make a plan. Not a fake plan. Not dissolved logic. Not wishful thinking. An actual plan that follows production laws and respects how work actually flows.

Test every response against production laws before implementing it. Does this help or hurt Kingman’s formula? Does it increase or decrease variation? Does it improve or disrupt bottleneck optimization? Does it align with Little’s Law? Does it violate Brooks’s Law? If your “solution” violates production laws, it’s not a solution. It’s a miracle dressed up as planning. Find a different approach that actually works with how production flows.

Move schedules together to maintain rhythm instead of shifting isolated pieces. When concrete decks hit variation, don’t just shift the deck schedule. Shift columns, walls, and decks together. Keep the rhythm consistent. Maintain the handoffs. Preserve the crane schedule. Protect the procurement sequence. Keep crew cycles stable. It’s better to call that day a buffer day or lost day altogether and keep all relationships between phases consistent in rhythm than to create ripples of variation throughout the system by adjusting pieces in isolation.

Widen your circle and get help when needed. When variation occurs, you want to show the reality, make a plan that follows production laws, and determine whether you can hit the end date or whether you need help. If you need help, reach out. Bring in people who understand production laws. Get support from leadership. Expand your resources. But do it systematically, following Brooks’s Law, not randomly hoping more people equals more speed.

Don’t freak out when problems occur. Calm down. There are ways to get help. There are people who can help. And there are production laws that govern how to recover successfully. Follow them. When impact happens, you have to at least have one thing: a plan. Not hope. Not miracles. A plan. Patton said a good plan violently executed today is better than a perfect plan tomorrow. But Patton didn’t say no plan today violently executed. He said a good plan instead of a perfect plan. Everything you do has to have a plan that follows production laws.

The Practical Path Forward

Here’s how this works in practice. Your project hits variation. The deck schedule breaks. Someone suggests shifting just the decks out a few days. You need to decide whether that’s a plan or a miracle.

First question: does this follow production laws? Test it against Kingman’s formula, the law of bottlenecks, and the law of variation, Little’s Law, and Brooks’s Law. If it violates any of them, it’s not a plan. It’s wishful thinking. Find an approach that works with production laws instead of against them.

Second question: does this maintain rhythm or break it? If your concrete crew is running columns-walls-decks in consistent sequence with consistent handoffs and your “fix” disrupts that rhythm, you’re increasing variation. And anything that increases variation increases project duration. Shift everything together to maintain rhythm instead of breaking it with isolated adjustments.

Third question: are you showing reality or hiding it? If your recovery strategy involves dissolving logic to make dates look achievable, you’re lying. You’re not legally allowed to hide impact. Show what actually happened. Then make a plan based on reality instead of fantasy. The truth might be uncomfortable, but it’s the only foundation for actual recovery.

Make decisions based on production laws instead of hope. When someone suggests throwing more crews at the problem, check Brooks’s Law. When someone wants to shift isolated pieces of the schedule, check the law of variation. When someone proposes a solution, test it systematically before implementing it. If it doesn’t follow production laws, it won’t work. Find something that does.

Execute the plan without wishful thinking. Once you’ve made a plan that follows production laws, execute it. Don’t hedge. Don’t hope for miracles to fix the parts that are hard. Don’t assume things will work out. Follow the plan systematically. Adjust based on production laws when new variation occurs. Keep analyzing. Keep planning. Keep executing based on math instead of miracles.

Why This Protects Projects and People

We’re not just building projects. We’re protecting jobs, families, and futures from the dysfunction that miracle-based planning creates. And whether we follow production laws or hope for miracles when variation occurs determines whether we recover successfully or compound failure.

When you respond to variation with miracle-based planning, you’re not protecting the project. You’re threatening it. Fake plans fail. Dissolved logic doesn’t produce real results. Hope without production laws extends duration instead of shortening it. The project that looked “fixed” on the schedule is actually worse because now you’re operating from fantasy instead of reality.

When you follow production laws, you’re protecting everyone. The schedule reflects reality. The plan actually works. Recovery is possible because it’s based on how work actually flows instead of how you wish it would flow. Jobs become more secure because projects succeed when planning follows production laws instead of banking on miracles.

This protects families by creating realistic schedules that people can execute. When your recovery strategy is “work harder and hope for miracles,” people burn out trying to accomplish impossible things. When you follow production laws and make realistic plans, work becomes sustainable. People can execute successfully. They can go home at reasonable hours because they’re following plans that actually work instead of chasing miracles that never arrive.

Respect for people means making plans they can actually execute instead of asking them to produce miracles. It means following production laws so rhythm stays consistent and handoffs stay predictable. It means showing reality so people know what they’re actually dealing with instead of hiding behind fake schedules. It means building cultures where planning is systematic instead of hopeful, where recovery follows laws instead of wishes.

The Challenge in Front of You

You can keep hoping for miracles. You can keep dissolving logic when schedules break. You can keep throwing manpower and materials at problems without analyzing Brooks’s Law. You can keep shifting isolated pieces without checking whether that increases variation. You can keep writing “and then a miracle happens” in the middle of your recovery strategies.

Or you can follow production laws. You can show reality immediately when variation occurs. You can test every response against Kingman’s formula, the law of bottlenecks, and the law of variation, Little’s Law, and Brooks’s Law. You can move schedules together to maintain rhythm instead of breaking it. You can make actual plans instead of fake ones. You can replace hope with systematic analysis.

The projects that recover from variation aren’t led by superintendents who hope harder. They’re led by people who follow production laws. Who recognize that anything increasing variation increases project duration. Who understand that throwing manpower and materials at problems extends duration instead of shortening it. Who know that dissolved logic is the same as writing “and then a miracle happens” on the schedule. Who’ve learned that production laws govern how work actually flows and can’t be violated with wishful thinking.

Your schedule just broke. Variation occurred. Someone’s suggesting a quick fix that sounds reasonable. Before you implement it, test it against production laws. Does it follow Kingman’s formula? Does it reduce variation or increase it? Does it maintain rhythm or break it? Does it violate Brooks’s Law? Does it align with Little’s Law?

If it doesn’t follow production laws, it’s not a plan. It’s a miracle. And as Miyamoto Musashi said: investigate this thoroughly. Make sure you’re making decisions according to production law and actual math and actual science. Stop throwing manpower, materials, and information at problems and hoping they go away.

Anything that increases variation will increase your project duration.

On we go.

 

Frequently Asked Questions

How do I know if my recovery strategy is a plan or a miracle?

Test it against production laws. Does it follow Kingman’s formula by maintaining consistent cycle times in rhythm with reduced variation? Does it help identify and optimize bottlenecks? Does it reduce variation instead of increasing it? Does it align with Little’s Law by rightsizing batch sizes and limiting work in process? Does it avoid violating Brooks’s Law by not throwing manpower at problems late in the project? If your strategy violates any of these laws, it’s not a plan, it’s wishful thinking. Real plans work with production laws, not against them.

When deck schedules hit variation, why is it better to shift everything together instead of just the decks?

Because shifting just the decks breaks rhythm and increases variation. Your concrete crew is running a sequence: columns on day one, walls on day two, decks on days three through five. Hook time is scheduled. Procurement is sequenced. Handoffs are consistent. When you shift just decks, you create different crane schedules, different procurement times, different manpower cycles, different handoffs. You’ve increased variation trying to fix variation. Shifting everything together maintains the rhythm, keeps handoffs consistent, preserves the sequence, and follows the law of variation instead of violating it.

What should I do immediately when variation occurs on my project?

Show the reality. Do not lie. Do not withhold truth. Do not avoid showing the impact in your schedule. You’re not legally allowed to hide it. Once you’ve shown what actually happened, make a plan that follows production laws. Test your response against Kingman’s formula, the law of bottlenecks, the law of variation, Little’s Law, and Brooks’s Law. If it violates any of them, find a different approach. Widen your circle and get help if needed. But always start by showing reality and making actual plans instead of fake ones.

Why doesn’t throwing more manpower at problems speed up recovery?

Brooks’s Law. When you add manpower to a task, especially in later parts of that task or project, it increases throughput time instead of decreasing it. More people means more coordination. More communication. More context switching. More training. The productivity loss from adding people typically exceeds the capacity gain. That’s why projects that respond to variation by throwing more crews at problems usually see duration extend instead of shorten. Recovery requires following production laws, not violating them.

How do I convince leadership that we need realistic schedules instead of hopeful ones?

Show them the cartoon: math on the left, “and then a miracle happens” in the middle, results on the right. Ask which recovery strategies follow production laws versus which ones hope for miracles. Demonstrate that dissolved logic fails when executed. Explain that anything increasing variation increases project duration. Help them understand that realistic plans based on production laws actually recover projects while hopeful plans based on miracles compound failure. The truth might be uncomfortable initially, but it’s the only foundation for actual success.

If you want to learn more we have:

-Takt Virtual Training: (Click here)
-Check out our Youtube channel for more info: (Click here) 
-Listen to the Elevate Construction podcast: (Click here) 
-Check out our training programs and certifications: (Click here)
-The Takt Book: (Click here)

Discover Jason’s Expertise:

Meet Jason Schroeder, the driving force behind Elevate Construction IST. As the company’s owner and principal consultant, he’s dedicated to taking construction to new heights. With a wealth of industry experience, he’s crafted the Field Engineer Boot Camp and Superintendent Boot Camp – intensive training programs engineered to cultivate top-tier leaders capable of steering their teams towards success. Jason’s vision? To expand his training initiatives across the nation, empowering construction firms to soar to unprecedented levels of excellence.

On we go

    Related Books

    The First Planner System: The Project Planning System for Executives, Project Managers, and Superintendents in Pre-construction - Book 2
    Pull Planning For Builders: How to Pull Plan Right, Respect People, and Gain Time (The Art of the Builder)
    The Ten Improvements to Production Planning: What Lean Builders Can Do To Improve Short Interval Planning (The Art of the Builder)

    Related Books

    The First Planner System: The Project Planning System for Executives, Project Managers, and Superintendents in Pre-construction - Book 2
    Built to Fail: Why Construction Projects Take So Long, Cost Too Much, And How to Fix It

    Related Books

    The First Planner System: The Project Planning System for Executives, Project Managers, and Superintendents in Pre-construction - Book 2
    The 10 Myths of CPM: How The Critical Path Method Systematizes Disrespect for People
    Calumet "K"

    faq

    General Training Overview

    What construction leadership training programs does LeanTakt offer?
    LeanTakt offers Superintendent/PM Boot Camps, Virtual Takt Production System® Training, Onsite Takt Simulations, and Foreman & Field Engineer Training. Each program is tailored to different leadership levels in construction.
    Who should attend LeanTakt’s training programs?
    Superintendents, Project Managers, Foremen, Field Engineers, and trade partners who want to improve planning, communication, and execution on projects.
    How do these training programs improve project performance?
    They provide proven Lean and Takt systems that reduce chaos, improve reliability, strengthen collaboration, and accelerate project delivery.
    What makes LeanTakt’s training different from other construction courses?
    Our programs are hands-on, field-tested, and focused on practical application—not just classroom theory.
    Do I need prior Lean or takt planning experience to attend?
    No. Our programs cover foundational principles before moving into advanced applications.
    How quickly can I apply what I learn on real projects?
    Most participants begin applying new skills immediately, often the same week they complete the program.
    Are these trainings designed for both office and field leaders?
    Yes. We equip both project managers and superintendents with tools that connect field and office operations.
    What industries benefit most from LeanTakt training?
    Commercial, multifamily, residential, industrial, and infrastructure projects all benefit from flow-based planning.
    Do participants receive certificates after completing training?
    Yes. Every participant receives a LeanTakt Certificate of Completion.
    Is LeanTakt training recognized in the construction industry?
    Yes. Our programs are widely respected among leading GCs, subcontractors, and construction professionals.

    Superintendent / PM Boot Camp

    What is the Superintendent & Project Manager Boot Camp?
    It’s a 5-day immersive training for superintendents and PMs to master Lean leadership, takt planning, and project flow.
    How long does the Superintendent/PM Boot Camp last?
    Five full days of hands-on training.
    What topics are covered in the Boot Camp curriculum?
    Lean leadership, Takt Planning, logistics, daily planning, field-office communication, and team health.
    How does the Boot Camp improve leadership and scheduling skills?
    Yes. You’ll learn how to run day huddles, team meetings, worker huddles, and Lean coordination processes.
    Who is the Boot Camp best suited for?
    Construction leaders responsible for delivering projects, including Superintendents, PMs, and Field Leaders.
    What real-world challenges are simulated during the Boot Camp?
    Schedule breakdowns, trade conflicts, logistics issues, and communication gaps.
    Will I learn Takt Planning at the Boot Camp?
    Yes. Takt Planning is a core focus of the Boot Camp.
    How does this Boot Camp compare to traditional PM certification?
    It’s practical and execution-based rather than exam-based. You learn by doing, not just studying theory.
    Can my entire project team attend the Boot Camp together?
    Yes. Teams attending together often see the greatest results.
    What kind of real-world challenges do we simulate?
    Improved project flow, fewer delays, better team communication, and stronger leadership confidence.

    Takt Production System® Virtual Training

    What is the Virtual Takt Production System® Training?
    It’s an expert-led online program that teaches Lean construction teams how to implement takt planning.
    How does virtual takt training work?
    Delivered online via live sessions, interactive discussions, and digital tools.
    What are the benefits of online takt planning training?
    Convenience, global accessibility, real-time learning, and immediate application.
    Can I access the virtual training from anywhere?
    Yes. It’s fully web-based and accessible worldwide.
    Can I access the virtual training from anywhere?
    Yes. It’s fully web-based and accessible worldwide.
    What skills will I gain from the Virtual TPS® Training?
    Macro and micro Takt planning, weekly updates, flow management, and CPM integration.
    How long does the virtual training program take?
    The program is typically completed in multiple live sessions across several days.
    Can I watch recordings if I miss a session?
    Yes. Recordings are available to all participants.
    Do you offer group access or company licenses for the virtual training?
    Yes. Teams and companies can enroll together at discounted rates.
    How does the Virtual TPS® Training integrate with CPM tools?
    We show how to align Takt with CPM schedules like Primavera P6 or MS Project.

    Onsite Takt Simulation

    What is a Takt Simulation in construction training?
    It’s a live, interactive workshop that demonstrates takt planning on-site.
    How does the Takt Simulation workshop work?
    Teams participate in hands-on exercises to learn the flow and rhythm of a Takt-based project.
    Can I choose between a 1-day or 2-day Takt Simulation?
    Yes. We offer flexible formats to fit your team’s schedule and needs.
    Who should participate in the Takt Simulation workshop?
    Superintendents, PMs, site supervisors, contractors, and engineers.
    How does a Takt Simulation improve project planning?
    It shows teams how to structure zones, manage flow, and coordinate trades in real time.
    What will my team learn from the onsite simulation?
    How to build and maintain takt plans, manage buffers, and align trade partners.
    Is the simulation tailored to my specific project type?
    Yes. Scenarios can be customized to match your project.
    How do Takt Simulations improve trade partner coordination?
    They strengthen collaboration by making handoffs visible and predictable.
    What results can I expect from an onsite Takt Simulation?
    Improved schedule reliability, better trade collaboration, and reduced rework.
    How many people can join a Takt Simulation session?
    Group sizes are flexible, but typically 15–30 participants per session.

    Foreman & Field Engineer Training

    What is Foreman & Field Engineer Training?
    It’s an on-demand, practical program that equips foremen and engineers with leadership and planning skills.
    How does this training prepare emerging leaders?
    By teaching communication, crew management, and execution strategies.
    Is the training on-demand or scheduled?
    On-demand, tailored to your team’s timing and needs.
    What skills do foremen and engineers gain from this training?
    Planning, safety leadership, coordination, and communication.
    How does the training improve communication between field and office?
    It builds shared systems that align superintendents, engineers, and managers.
    Can the training be customized for my team’s needs?
    Yes. Programs are tailored for your project or company.
    What makes this program different from generic leadership courses?
    It’s construction-specific, field-tested, and focused on real project application.
    How do foremen and field engineers apply this training immediately?
    They can use new systems for planning, coordination, and daily crew management right away.
    Is the training suitable for small construction companies?
    Yes. Small and large teams alike benefit from building flow-based leadership skills.

    Testimonials

    Testimonials

    "The bootcamp I was apart of was amazing. Its was great while it was happening but also had a very profound long-term motivation that is still pushing me to do more, be more. It sounds a little strange to say that a construction bootcamp changed my life, but it has. It has opened my eyes to many possibilities on how a project can be successfully run. It’s also provided some very positive ideas on how people can and should be treated in construction.

    I am a hungry person by nature, so it doesn’t take a lot to get to participate. I loved the way it was not just about participating, it was also about doing it with conviction, passion, humility and if it wasn’t portrayed that way you had to do it again."

    "It's great to be a part of a company that has similar values to my own, especially regarding how we treat our trade partners. The idea of "you gotta make them feel worse to make them do better" has been preached at me for years. I struggled with this as you will not find a single psychology textbook stating these beliefs. In fact it is quite the opposite, and causing conflict is a recipe for disaster. I'm still honestly in shock I have found a company that has based its values on scientific facts based on human nature. That along with the Takt scheduling system makes everything even better. I am happy to be a part of a change that has been long overdue in our industry!"

    "Wicked team building, so valuable for the forehumans of the sub trades to know the how and why. Great tools and resources. Even though I am involved and use the tools every day, I feel like everything is fresh and at the forefront to use"

    "Jason and his team did an incredible job passing on the overall theory of what they do. After 3 days of running through the course I cannot see any holes in their concept. It works. it's proven to work and I am on board!"

    "Loved the pull planning, Takt planning, and logistic model planning. Well thought out and professional"

    "The Super/PM Boot Camp was an excellent experience that furthered my understanding of Lean Practices. The collaboration, group involvement, passion about real project site experiences, and POSITIVE ENERGY. There are no dull moments when you head into this training. Jason and Mr. Montero were always on point and available to help in the break outs sessions. Easily approachable to talk too during breaks and YES, it was fun. I recommend this training for any PM or Superintendent that wants to further their career."

    agenda

    Day 1

    Foundations & Macro Planning

    day2

    Norm Planning & Flow Optimization

    day3

    Advanced Tools & Comparisons

    day4

    Buffers, Controls & Finalization

    day5

    Control Systems & Presentations

    faq

    UNDERSTANDING THE TRAINING

    What is the Virtual Takt Production System® Training by LeanTakt?
    It’s an expert-led online program designed to teach construction professionals how to implement Takt Planning to create flow, eliminate chaos, and align teams across the project lifecycle.
    Who should take the LeanTakt virtual training?
    This training is ideal for Superintendents, Project Managers, Engineers, Schedulers, Trade Partners, and Lean Champions looking to improve planning and execution.
    What topics are covered in the online Takt Production System® course?
    The course covers macro and micro Takt planning, zone creation, buffers, weekly updates, flow management, trade coordination, and integration with CPM tools.
    What makes LeanTakt’s virtual training different from other Lean construction courses?
    Unlike theory-based courses, this training is hands-on, practical, field-tested, and includes live coaching tailored to your actual projects.
    Do I get a certificate after completing the online training?
    Yes. Upon successful completion, participants receive a LeanTakt Certificate of Completion, which validates your knowledge and readiness to implement Takt.

    VALUE AND RESULTS

    What are the benefits of Takt Production System® training for my team?
    It helps teams eliminate bottlenecks, improve planning reliability, align trades, and reduce the chaos typically seen in traditional construction schedules.
    How much time and money can I save with Takt Planning?
    Many projects using Takt see 15–30% reductions in time and cost due to better coordination, fewer delays, and increased team accountability.
    What’s the ROI of virtual Takt training for construction teams?
    The ROI comes from faster project delivery, reduced rework, improved communication, and better resource utilization — often 10x the investment.
    Will this training reduce project delays or rework?
    Yes. By visualizing flow and aligning trades, Takt Planning reduces miscommunication and late handoffs — major causes of delay and rework.
    How soon can I expect to see results on my projects?
    Most teams report seeing improvement in coordination and productivity within the first 2–4 weeks of implementation.

    PLANNING AND SCHEDULING TOPICS

    What is Takt Planning and how is it used in construction?
    Takt Planning is a Lean scheduling method that creates flow by aligning work with time and space, using rhythm-based planning to coordinate teams and reduce waste.
    What’s the difference between macro and micro Takt plans?
    Macro Takt plans focus on the overall project flow and phase durations, while micro Takt plans break down detailed weekly tasks by zone and crew.
    Will I learn how to build a complete Takt plan from scratch?
    Yes. The training teaches you how to build both macro and micro Takt plans tailored to your project, including workflows, buffers, and sequencing.
    How do I update and maintain a Takt schedule each week?
    You’ll learn how to conduct weekly updates using lookaheads, trade feedback, zone progress, and digital tools to maintain schedule reliability.
    Can I integrate Takt Planning with CPM or Primavera P6?
    Yes. The training includes guidance on aligning Takt plans with CPM logic, showing how both systems can work together effectively.
    Will I have access to the instructors during the training?
    Yes. You’ll have opportunities to ask questions, share challenges, and get real-time feedback from LeanTakt coaches.
    Can I ask questions specific to my current project?
    Absolutely. In fact, we encourage it — the training is designed to help you apply Takt to your active jobs.
    Is support available after the training ends?
    Yes. You can access follow-up support, coaching, and community forums to help reinforce implementation.
    Can your tools be customized to my project or team?
    Yes. We offer customizable templates and implementation options to fit different project types, teams, and tech stacks.
    When is the best time in a project lifecycle to take this training?
    Ideally before or during preconstruction, but teams have seen success implementing it mid-project as well.

    APPLICATION & TEAM ADOPTION

    What changes does my team need to adopt Takt Planning?
    Teams must shift from reactive scheduling to proactive, flow-based planning with clear commitments, reliable handoffs, and a visual management mindset.
    Do I need any prior Lean or scheduling experience?
    No prior Lean experience is required. The course is structured to take you from foundational principles to advanced application.
    How long does it take for teams to adapt to Takt Planning?
    Most teams adapt within 2–6 weeks, depending on project size and how fully the system is adopted across roles.
    Can this training work for smaller companies or projects?
    Absolutely. Takt is scalable and especially powerful for small teams seeking better structure and predictability.
    What role do trade partners play in using Takt successfully?
    Trade partners are key collaborators. They help shape realistic flow, manage buffers, and provide feedback during weekly updates.

    VIRTUAL FORMAT & ACCESSIBILITY

    Can I access the virtual training from anywhere?
    Yes. The training is fully accessible online, making it ideal for distributed teams across regions or countries.
    Is this training available internationally?
    Yes. LeanTakt trains teams around the world and supports global implementations.
    Can I watch recordings if I miss a session?
    Yes. All sessions are recorded and made available for later viewing through your training portal.
    Do you offer group access or company licenses?
    Yes. Teams can enroll together at discounted rates, and we offer licenses for enterprise rollouts.
    What technology or setup do I need to join the virtual training?
    A reliable internet connection, webcam, Miro, Spreadsheets, and access to Zoom.

    faq

    GENERAL FAQS

    What is the Superintendent / PM Boot Camp?
    It’s a hands-on leadership training for Superintendents and Project Managers in the construction industry focused on Lean systems, planning, and communication.
    Who is this Boot Camp for?
    Construction professionals including Superintendents, Project Managers, Field Engineers, and Foremen looking to improve planning, leadership, and project flow.
    What makes this construction boot camp different?
    Real-world project simulations, expert coaching, Lean principles, team-based learning, and post-camp support — all built for field leaders.
    Is this just a seminar or classroom training?
    No. It’s a hands-on, immersive experience. You’ll plan, simulate, collaborate, and get feedback — not sit through lectures.
    What is the focus of the training?
    Leadership, project planning, communication, Lean systems, and integrating office-field coordination.

    CURRICULUM & OUTCOMES

    What topics are covered in the Boot Camp?
    Takt planning, day planning, logistics, pre-construction, team health, communication systems, and more.
    What is Takt Planning and why is it taught?
    Takt is a Lean planning method that creates flow and removes chaos. It helps teams deliver projects on time with less stress.
    Will I learn how to lead field teams more effectively?
    Yes. This boot camp focuses on real leadership challenges and gives you systems and strategies to lead high-performing teams.
    Do you cover daily huddles and meeting systems?
    Yes. You’ll learn how to run day huddles, team meetings, worker huddles, and Lean coordination processes.
    What kind of real-world challenges do we simulate?
    You’ll work through real project schedules, logistical constraints, leadership decisions, and field-office communication breakdowns.

    LOGISTICS & FORMAT

    Is the training in-person or virtual?
    It’s 100% in-person to maximize learning, feedback, and team-based interaction.
    How long is the Boot Camp?
    It runs for 5 full days.
    Where is the Boot Camp held?
    Locations vary — typically hosted in a professional training center or project setting. Contact us for the next available city/date.
    Do you offer follow-up coaching after the Boot Camp?
    Yes. Post-camp support is included so you can apply what you’ve learned on your projects.
    Can I ask questions about my actual project?
    Absolutely. That’s encouraged — bring your current challenges.

    PRICING & VALUE

    How much does the Boot Camp cost?
    $5,000 per person.
    Are there any group discounts?
    Yes — get 10% off when 4 or more people from the same company attend.
    What’s the ROI for sending my team?
    Better planning = fewer delays, smoother coordination, and higher team morale — all of which boost productivity and reduce costs.
    Will I see results immediately?
    Most participants apply what they’ve learned as soon as they return to the jobsite — especially with follow-up support.
    Can this replace other leadership training?
    In many cases, yes. This Boot Camp is tailored to construction professionals, unlike generic leadership seminars.

    SEO-BASED / HIGH-INTENT SEARCH QUESTIONS

    What is the best leadership training for construction Superintendents?
    Our Boot Camp offers real-world, field-focused leadership training tailored for construction leaders.
    What’s included in a Superintendent Boot Camp?
    Takt planning, day planning, logistics, pre-construction systems, huddles, simulations, and more.
    Where can I find Lean construction training near me?
    Check our upcoming in-person sessions or request a private boot camp in your city.
    How can I improve field and office communication on a project?
    This Boot Camp teaches you tools and systems to connect field and office workflows seamlessly.
    Is there a training to help reduce chaos on construction sites?
    Yes — this program is built specifically to turn project chaos into flow through structured leadership.

    agenda

    Day 1

    Agenda

    Outcomes

    Day 2

    Agenda

    Outcomes

    Day 3

    Agenda

    Outcomes

    Day 4

    Agenda

    Outcomes

    Day 5

    Agenda

    Outcomes