Month: April 2026

Construction Retrospective: What Worked, What Didn’t, What’s Next

Posted on by Danny Jiménez⁩
Read 18 min

Construction Retrospectives: The Continuous Improvement Practice Every Team Needs

Continuous improvement is one of the six pillars of Lean construction. Every serious Lean practitioner will tell you it belongs at the core of how a project team operates. But here is the honest reality on most projects: continuous improvement gets talked about more than it gets practiced. Teams finish a meeting, a phase, a training, or even a whole project and move immediately to the next thing without ever stopping to examine what went well, what did not, and what specifically should change the next time. The retrospective is the practice that closes that gap. And when it is embedded in the standard work of a project team, it compounds into something remarkable.

The Pain of Skipping the Retrospective

Projects that never do retrospectives have a recognizable pattern. The same problems recur on project after project. The same communication gaps reappear. The same pre-construction meeting that went poorly last time goes poorly again because nobody systematically captured what needed to change and updated the process. The team is always applying effort, always working hard, but the effort is not compounding. Each project starts from roughly the same place as the last one because the learning from the last one was never extracted, standardized, and carried forward.

This is not a laziness failure. Most project teams are working at full capacity and then some. The issue is that learning requires a dedicated practice a structured pause with specific questions and without that structure, the lessons dissolve into the general blur of moving from one project to the next.

The System Never Built the Learning Loop

When a project team does not run retrospectives, it is almost never because the individuals do not want to improve. It is because the system never built the mechanism for improvement into the workflow. No standard agenda for the retrospective. No scheduled time for it. No safe environment for honest feedback. No process for updating the standard work when an improvement is identified. The system failed to create the learning loop, and the team kept working without one.

The goal of a retrospective is not to assign blame or score performance. It is to improve the system. And when the system is designed to support that with psychological safety, clear questions, and a direct connection to updated standard work the loop closes and the team accelerates.

Where Retrospectives Come From

The retrospective is a core component of the Scrum framework. In Scrum, the team holds a retrospective at the end of every sprint not to celebrate or debrief, but specifically to examine the process and identify one or two improvements to carry into the next sprint. Over time, those small improvements compound into a significantly better way of working.

I learned it through the Scrum.org Scrum Master certification, and I have implemented it everywhere I possibly can since after Super PM Boot Camps, after training events, after planning sessions, after trade partner meetings. Some people run a plus-delta format. Some use roses, buds, and thorns. Some use stop, start, continue. The format matters less than the practice. The important thing is that after any meaningful event, the team pauses, evaluates honestly, and captures what to do differently next time.

The Five Elements of a Constructive Retrospective

The first element is psychological safety. This is the foundation without which nothing else works. If people do not feel safe sharing honest feedback, the retrospective produces only the polished, comfortable version of what happened not the real one. Building psychological safety means creating an explicit invitation to surface problems, separating the feedback from the person who delivers it, and responding to hard feedback with curiosity rather than defensiveness.

I learned this the uncomfortable way. After one of our boot camp days, the feedback I kept hearing was that I had not been clear enough about what was coming. I added visuals. I added a pre-meeting. I explained things more explicitly. And I still heard it. I was starting to get frustrated. The problem was not the clarity. The problem was that I had not created a safe enough container for the specific, actionable feedback that would have actually told me what to change. Without psychological safety, you get the symptom. You need the root cause.

The second element is identifying what worked. Not just what people liked that is subjective and not always useful. The question is what met the purpose of the event. What produced the outcome you were aiming for? What should absolutely be carried forward unchanged because it is working well? Starting with what worked before moving to what did not is not just good facilitation. It creates an accurate baseline and prevents the session from collapsing into a complaint list.

The third element is identifying what did not work. What did not meet the purpose? What pushed people in the wrong direction? What created confusion, friction, or outcomes that were the opposite of what you intended? This is where the most valuable learning lives, and it requires the psychological safety built in the first step. When the environment is safe and the focus is on the system rather than the person, people surface real observations that can actually change outcomes.

The fourth element is specifying what changes to make. Feedback without a proposed change is less useful than feedback with one. The format that works well is: I noticed this, if we did this, we would get this. That structure takes an observation and turns it into an actionable improvement. It requires more thinking than just pointing at a problem, but it produces something the team can actually implement. And critically always blame the system, not the person. Every improvement should be framed as a change to a process, a standard, an agenda, a structure. Not as a judgment about someone’s character or effort.

The fifth element is standardizing the improvement. This is the step that makes the retrospective compound over time. When an improvement is identified, it needs to go into the standard work the presentation, the agenda, the checklist, the prep guide, whatever document governs that activity. If the improvement stays in someone’s memory, it will not survive the next time someone else runs the same process. If it gets updated into the standard, it becomes the new baseline and the team starts from a higher floor the next time.

Here are the signals that a team is running retrospectives effectively:

  • The standard work for recurring activities gets updated after each iteration
  • Problems that appeared last time do not appear again in the same form
  • People leave retrospective sessions with specific, actionable items rather than general impressions
  • The team’s meetings, trainings, and processes are noticeably better than they were six months ago

The PDCA Cycle in Real Life

The retrospective is the check and act phase of the PDCA cycle plan, do, check, act. The planning is the design of the event or process. The doing is the execution. The checking is the retrospective. The acting is updating the standard work with the improvements identified. Without the retrospective, PDCA becomes plan-do, plan-do, plan-do the same loop, never improving. With it, the cycle genuinely compounds.

At our Super PM Boot Camp in Dallas and Atlanta, we had 78 people. They left as raving fans. But the retrospectives we ran after each day with attendees, with the guide team, with everyone who watched the process produced a list of improvements that is already being implemented for the next boot camp. The 4D visualization is being added. AI elements are being integrated. Some segments are being shortened. Others lengthened. Video capture is being improved. None of that would happen without a structured retrospective that gives the team permission and a framework to be honest.

Connecting to the Mission

The mission is to build remarkable people who build remarkable things. Remarkable people do not arrive at remarkable. They build toward it iteratively, improving every time, never accepting the current standard as the final one. The retrospective is the mechanism that makes that iterative improvement real. If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow.

Apply retrospectives to every significant activity: your weekly work planning meeting, your trade partner pre-construction meeting, your pull plan session, your phase completion, your project closeout. Every time you do it, you improve the standard. And every improvement makes the next iteration better than the last.

On we go.

Frequently Asked Questions

What is a retrospective and how is it different from a debrief?

A retrospective is a structured improvement practice that examines what worked, what did not, and what changes to make with those changes going into updated standard work. A debrief often stops at reflection. A retrospective commits to specific improvements and carries them forward.

How often should construction teams run retrospectives?

After every significant repeated activity weekly work planning meetings, pull plan sessions, pre-construction meetings, training events, and project phase completions at minimum. The more frequently teams retrospect on recurring processes, the faster those processes improve.

Why is psychological safety the first requirement for a useful retrospective?

Because without it, people share the comfortable version of what happened rather than the honest version. The most valuable learning comes from the hard observations, and those only surface when people trust that their honesty will be met with curiosity, not defensiveness.

How does a retrospective connect to standard work?

Every improvement identified in a retrospective should update the relevant standard work the agenda, the checklist, the presentation, the preparation guide. If the improvement does not make it into the standard, it will not survive the next time someone else runs the same process.

What is the best format for running a retrospective?

Plus-delta, roses-buds-thorns, stop-start-continue, or any structured format works. The format matters less than the three core elements: what worked, what did not, and what specific changes will be made. The Scrum retrospective framework from Scrum.org provides an excellent foundational model.

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

Respect For People In Lean Construction (What It Actually Looks Like)

Posted on by Danny Jiménez⁩
Read 19 min

Respect for People in Lean Construction: What It Actually Looks Like

Respect for people is the foundational principle of Lean construction. Every serious Lean thinker, every Lean practitioner, every organization that has tried to implement these systems will tell you that respect for people is where it starts. But here is the problem: the phrase gets said a lot more than it gets defined. And without a clear, operational definition of what respect for people actually looks like on a construction site, it stays a value on a poster instead of becoming a standard on a project. This blog is about making it concrete.

The Litmus Test That Reveals the Truth

Here is the bottom-line standard that I apply. Nobody in construction is respecting people if they push, if they rush, if they panic, if the jobsite is dirty, and if the jobsite is unsafe. Those five conditions are not compatible with genuine respect for the people working on that project. You cannot hold both at the same time. You can say the words, you can mean well, you can genuinely believe you care and still be running a project that is disrespecting the people on it through the conditions you have created or allowed.

This is hard to hear for leaders who care about their teams and still run projects under constant pressure. The intent is not the issue. The system that produces the pushing and the dirty sites and the unsafe conditions is the issue. And until the system changes, the words “we respect our people” remain disconnected from the daily experience of the people those words are supposed to describe.

The Paradox That Most Leaders Miss

There is a paradox at the heart of this that I want to name directly because it resolves a false choice that most leaders feel stuck between. Leaders often think they have to choose: be warm and permissive, or be strict and demanding. Neither of those alone is right. The actual standard is warm-hearted, strict, but fair and the key is that strictness applies to different things depending on whether you are dealing with people or environments.

When dealing with people their development, their ideas, their mistakes, their growth we are shoulder-to-shoulder coaches. We listen. We mentor. We guide rather than punish. We bring emotional intelligence to every interaction. But when dealing with the environment whether the site is clean, whether safety procedures are followed, whether the area is organized there is no negotiation. That is where command and control is not just acceptable, it is required. Zero tolerance for an unsafe site. Zero tolerance for a dirty, disorganized project. How a crew works through a zone, how they organize their method, how much time they need those are conversations. Whether the site will be clean and safe that is not a conversation. It simply will be.

This is not contradiction. It is clarity. The warm heart protects the person. The unyielding standard protects their life, their environment, and everyone who works alongside them.

The Seven Things That Define Respect on a Construction Site

The first is stable phasing and zoning. When trade partners know exactly how they will move through the project which zones, in which sequence, at what pace, with what roadblocks cleared ahead of them they can plan, prepare, and execute with confidence. When phasing is chaotic, when zones shift without notice, when the train of trades has no stable rhythm, trade partners cannot do their best work. Stability is not a preference. It is the structural expression of respect.

The second is the elimination of trade stacking and trade burdening. Trade stacking is too many trades in one area at the same time. Trade burdening is one trade stretched across too many areas at the same time. Both destroy flow, both create stress and rework, and both are preventable with good production planning. A leader who allows trade stacking or trade burdening has not respected the trades enough to design the system that protects them.

The third is clear handoffs. When one trade finishes in a zone and the zone behind them is ready for the next trade to enter, that is respect in action. The handoff is the moment where one trade’s work becomes another trade’s foundation. When handoffs are clean, clear, and confirmed, the whole train moves with dignity. When handoffs are murky, rushed, or conditional, every trade downstream absorbs the chaos that the upstream trade left behind.

The fourth is through-process inspections and finishing as you go. Waiting until the end of a project to address quality issues is not just a schedule risk it is a disrespect to the trade partners who built the work, because it signals that nobody cared enough to check while there was still time to correct things cleanly. Finishing as you go, doing in-process inspections at the first in-place and follow-up stages, and holding quality as a continuous standard is what respect for the craft looks like.

The fifth is truly listening at every level. Listening to workers. Listening to foremen. Listening before reacting. This is not passive it is one of the most demanding disciplines in leadership. When a foreman raises a problem in a huddle, the response in that moment tells the whole team whether it is safe to keep bringing problems to the surface. When workers surface ideas in their crew preparation huddle, whether those ideas are received or dismissed tells them whether their expertise is valued or just tolerated. True listening is active, followed by action, and without it the culture of psychological safety that Lean requires cannot take root.

The sixth is a mentorship culture. Mentorship is one of the most specific and concrete expressions of respect on a construction project. It looks like helping a trade partner’s crew 5S their truck before they come on site. It looks like helping kit and stage materials so the crew starts their zone with full kit. It looks like training during orientation and the worker huddle, aligning crews in the pre-construction meeting, and standing shoulder to shoulder with a foreman during the first in-place inspection. These acts of investment say, without words, that the leader believes the person in front of them is worth developing.

The seventh is making decisions in the right order: what is best for our people, then what is best for our client, then what is best for the business. When this order is followed not as a slogan but as an actual decision-making framework the people on the project feel the difference. Their needs are not the last consideration after everything else has been accounted for. They are the first one.

Here are the signals that respect for people is structural on a project, not just stated:

  • The site is clean, safe, and organized without being asked every day
  • Trade partners surface problems early because they trust the response will be helpful
  • Foremen walk into their zones with full kit and clear expectations
  • Workers at the morning huddle can describe the plan for the day in their own words
  • The quality standard is being caught in process, not on a punch list at the end

What Disrespect Actually Looks Like

The opposite of that list is disrespect. Pushing trades into areas that are not ready. Cramming more scope into a zone than the crew can reasonably execute. Issuing cure notices as the first response to a problem rather than a conversation. Dirty portables with graffiti that leadership has decided are someone else’s problem. Workers who do not know the plan because nobody bothered to communicate it to them. Foremen who are afraid to raise roadblocks because the last person who did got blamed for the delay. A schedule that can only be hit if people work through the weekend with no notice.

All of that is disrespect. Not because anyone intended it. Because the system was not designed to prevent it.

Connecting to the Mission

We will never reach Lean on our projects until we bless the lives of the people on our sites. That is the test. Not the percent plan complete. Not the schedule. Not the margin. Those are outcomes. The input is whether the people building this project are being respected by the conditions, the systems, and the culture they are working inside. If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow. Respect for people is a production strategy. It is also just the right way to build.

On we go.

Frequently Asked Questions

What is the simplest test for whether a project respects its people?

Walk the site and check five things: is the project being pushed, rushed, or panicked? Is the site dirty? Is it unsafe? If any of those are true, the system is producing disrespect regardless of what the values poster says.

Is zero tolerance for site conditions compatible with a warm leadership culture?

Yes, because zero tolerance applies to things and environments cleanliness, safety, organization. The warm, mentorship-oriented leadership style applies to people. The two are not in conflict. They are complementary.

What is trade stacking and why is it disrespectful?

Trade stacking is too many trades in one area simultaneously. It creates congestion, unsafe conditions, quality problems, and pressure that no crew can reasonably work through. Allowing it signals that the production system was more important than the people executing it.

Why is finishing as you go a form of respect?

Because it signals that quality matters while there is still time to address it with dignity not as a crisis at the end. It respects the trade’s craft, the owner’s investment, and the future occupants of the building.

What does shoulder-to-shoulder mentorship look like on a construction project?

It looks like a superintendent helping a foreman understand their work package before the first day in a zone, a field engineer doing layout alongside a crew lead rather than directing from a distance, and a GC helping a trade partner stage their materials properly because that preparation is how the handoff succeeds.

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

Daily Correction Systems

Posted on by Danny Jiménez⁩
Read 33 min

The Daily Correction System Nobody’s Running (And Why Your Project Is Drowning in Small Problems That Become Big Ones)

You walk the project every day. You see trash piled in corners. You notice a handrail that needs repair before someone gets hurt. You spot steps missing treads. You see material staged in the wrong location. You notice weeds growing near the fence. You walk past all of it making mental notes. And nothing gets fixed. Because by the time you get back to the trailer, you’ve forgotten half of what you saw. Because the problems are rattling around in your mind instead of getting dispatched to the people who can fix them. Because you don’t have a system to capture issues in the moment and communicate them immediately to the right person.

Here’s what’s happening. Every project has natural decay. Entropy. The second law of thermodynamics applied to construction. The inevitable increase of chaos in the universe. Your project will enter into entropy if you don’t outpace it and correct it daily. And you’re not outpacing it. You’re letting small problems accumulate until they become big problems. You’re walking past issues instead of fixing them. You’re relying on memory instead of systems. You’re hoping people notice problems on their own instead of teaching them to see what you see. You need a daily correction system. And until you build one, your project will keep drowning in small problems that pile up into chaos.

The Problem Every Superintendent Faces

Walk any project with the superintendent and watch what happens. He sees a problem. Makes a mental note. Sees another problem. Mental note. Sees five more problems. Mental notes. Gets back to the trailer. Immediately gets pulled into a meeting or a phone call or an email crisis. Forgets half of what he saw. Maybe remembers to mention one or two items later. Most problems never get communicated. Nothing gets fixed.

By the next day, new problems appear on top of the old problems. By the end of the week, the project looks cluttered and disorganized. By the end of the month, it’s chaos. The superintendent wonders why his project looks terrible despite walking it every day. He blames the trades for not caring. He blames workers for being sloppy. He doesn’t realize the system failed them.

Most superintendents don’t have a way to capture problems in the moment and dispatch them immediately to the right person for correction. They rely on memory. They rely on people noticing problems on their own. They rely on hoping issues get addressed without specific communication. They walk the project, see dozens of items that need attention, and maybe follow up on two or three.

What’s missing is a system that captures every problem the moment it’s identified, communicates it visually to the person who needs to fix it, creates accountability for correction within twenty-four hours, and builds a feedback loop when items get completed. Without that system, problems accumulate faster than they get solved. Entropy outpaces correction. The project descends into chaos.

The Failure Pattern That Creates Accumulated Problems

This isn’t about lazy superintendents or careless trades. This is about an industry that never taught people how to build systematic daily correction processes using modern communication technology. Construction culture treats problem identification like it happens naturally. We assume people see what needs fixing and fix it. We assume trades care about cleanliness and organization. We assume workers notice safety issues and correct them. We assume problems get addressed without explicit communication and tracking.

But here’s reality. People don’t see problems unless they’re trained to see them. They don’t know your standards unless you show them constantly. They don’t fix issues unless they’re communicated clearly with pictures showing exactly what needs correction. They don’t know something bothers you unless you tell them it bothers you. So problems pile up. The superintendent sees them. The trades don’t. Or the trades see different problems than the superintendent sees. Or everyone sees problems but nobody knows who’s responsible for fixing what. Or someone knows they should fix it but doesn’t know it bothers the superintendent enough to actually do it now instead of later.

And the project slowly degrades. Not because people don’t care. Because there’s no system to capture problems, communicate them visually, assign responsibility clearly, create urgency for correction, and build feedback loops that reinforce the culture of daily fixing. The system failed them. It didn’t fail the workers.

A Story That Reveals the Power of Shared Vision

I worked with a plumbing foreman on a large project about six or seven years ago. At first, I don’t think he liked me. He didn’t get what I was doing. He thought I was emotional, mean, over the top. We had friction. But after a while, we formed a really strong relationship. One day in a trade meeting, he said something I’ll never forget: “Jason, I finally figured you out. You’re not emotional. You’re not mean. You’re not over the top. You want us to see things like you see them. You want us to see cleanliness like you see it. You want us to see organization like you see it. You want us to see safety like you see it.”

I told him I really appreciated that insight. That’s exactly right. I want you to see it like I see it. I want your set point to be as high as where my set point is. He communicated a principle that’s true: to elevate and scale up excellence to the rest of the project, we need everyone to see it like we see it. We need everyone to see as a group, known as a group, and act as a group. What better way to do that than scale pictures and videos together? When everyone’s on the same group text chat seeing the same videos and the same pictures, they start learning what bothers you. What your standards are. What winning looks like? What needs immediate attention versus what can wait?

On most jobs where we implement this system and it works well, the trade foreman start texting each other and sending pictures and communicating primarily even without the superintendent having to chime in. It’s actually quite remarkable. It usually happens after about two months of this system. The foreman are getting these texts throughout the day. They’re learning to see. They’re developing the same standards. They’re holding each other accountable. That’s when you know the culture has shifted. That’s when the daily correction system becomes self-sustaining.

Why This Matters More Than Walking and Hoping

When you don’t have a daily correction system, you’re relying on memory and hope instead of process and accountability. You see problems but don’t capture them. You want things fixed but don’t communicate clearly. You expect standards but don’t teach people what those standards look like visually.

Think about what happens practically. You walk the project and see fifteen things that need attention. You get back to the trailer and remember three. You mention those three in passing to someone. Maybe one gets fixed. The other fourteen never get addressed. By tomorrow, there are thirty problems. By next week, sixty. The accumulation outpaces any random fixing that happens.

Now imagine a different system. You walk the project with your phone. Every time you see something that needs attention, you take a picture or video right then. You text it immediately to either your foreman group chat or your GC carpenters group chat. You clearly state where it’s located, what company needs to fix it, and what done looks like. Within seconds, the problem is captured, communicated, and assigned.

Throughout the day, you’re dispatching ten to fifteen items. Every single one with a picture. Every single one to the right person. Every single one with clear expectations. Your trades are learning to see like you see because they’re getting constant visual feedback on what bothers you. Your GC carpenters are staying ahead of logistics and cleanup because they’re getting immediate direction on what needs attention.

After two months, something remarkable happens. Foreman start sending back pictures of corrected items. You like or comment on those pictures creating a feedback loop. The culture shifts from you catching problems to everyone catching problems and fixing them before you even see them. The daily correction system becomes the way everyone operates. The difference between chaos and control on a project often comes down to whether you have a systematic way to see problems, communicate them visually, assign them clearly, and create feedback loops that reinforce daily correction.

The Framework: Building a System That Outpaces Entropy

Every project has natural decay. Entropy. The inevitable state of increasing chaos in the universe. Our projects will enter into entropy if we don’t outpace it and correct it daily. The question is how do you outpace it?

You stay ahead by noticing the problems that all projects have, communicating them to the right person that can fix it and should fix it and will fix it, and doing that daily at least ten to fifteen times. That means your project will have at least ten to fifteen things in a day that need correction. From a project that’s five million to eighty million dollars, you will have at least ten to fifteen things you need to take a picture of and text out for correction immediately each day. If you’re not operating at that kind of speed, entropy on your project will outpace you to the point that it’s going to hurt you. You deserve better and you need to treat yourself better.

Create two communication channels using GroupMe or WhatsApp. One to your foreman. One to your GC carpenters, logistics foreman, and laborers. These two systems communicate in text and visually with videos and pictures what needs to be taken care of throughout the project. WhatsApp is better at quickly uploading pictures and videos. GroupMe is better if you want to keep history of the chat and the ability to like comments, which creates positive reinforcement when people respond.

When you do your job walks every day, stay focused on what you’re doing. But when you see a pile of trash that needs to be dealt with, when you see a piece of handrail that needs repair before it falls down, when you see steps that need treads, when you notice weeds near the fence, when you spot anything that needs attention, you deal with it right then. You either fix it yourself, text it to your foreman, text it to your GC carpenters, put it on your personal to-do list, or add it to a meeting agenda. It does not rattle around in your mind.

When you text pictures or videos, you’re helping everyone learn to see like you see. You’re raising their mental set point. You’re teaching them what cleanliness looks like, what organization looks like, what safety looks like, what your standards are. You’re scaling excellence through visual communication that everyone receives simultaneously. If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow.

The Practical Requirements for Daily Correction

Here’s how this works in practice. As a superintendent, you should be doing three things every day: reading the drawings for thirty minutes, being in the schedule in a meaningful way for thirty minutes, and doing a reflection walk. Hopefully you get to do a reflection walk by yourself at least once throughout the day, but you’re probably taking walks two or three times per day.

When you walk and see something that needs correction, you take a picture or video with your phone. You dispatch it immediately to either the foreman group chat or the GC carpenters group chat. Each item should have a picture or video, address the person that needs to fix it, address the company that needs to fix it, clearly state where it’s located, and define what done looks like once it’s corrected.

You need to raise your mental set point. Perfect is the standard. Perfect cleanliness. Perfect safety. Perfect organization. We’re striving for perfection. We’re striving for excellence. Everyone needs to have the eight wastes memorized. Overproduction creates excess inventory. Excess inventory creates excess motion and transportation. That creates defects. Defects require over-processing. Over-processing creates waiting. All of it was waste because we could have used the genius of the team.

Once you know what is not according to your standards for safety, cleanliness, organization, and these other metrics, when you see it, it should annoy you enough that you’re going to do something about it. You’re going to capture it. You’re going to communicate it. You’re going to get it fixed within twenty-four hours.

Build a culture where corrections happen within twenty-four hours. If you send a text and walk that project again and see the same issue, you’re going to remind them gently the first time that these need to be taken care of within twenty-four hours. If it continues to happen, you have a problem within your team that needs addressing. Don’t rely on software like Procore to hold people accountable. You hold people accountable by walking again, seeing what needs to be seen, and dealing with situations that weren’t fixed.

The remarkable moment comes when foreman start sending back pictures of corrected items. When you like or comment on those pictures creating a feedback loop. That’s when you’ve locked this system in. That’s when the culture shifts from you finding problems to everyone finding and fixing problems as their normal way of operating.

Why This Protects People and Projects

We’re not just building projects. We’re creating environments where workers can succeed. And when we don’t have daily correction systems, we’re letting small problems accumulate into big problems that make work harder, more dangerous, and more frustrating.

Every item that doesn’t get fixed makes someone’s job harder. Trash in the way slows down installation. Damaged handrails create fall hazards. Missing treads cause trips. Material in the wrong location creates congestion. Weeds near the fence look unprofessional and create perception problems with owners and neighbors. Each small problem compounds with others to create chaos.

Eric Thomas has a great video where he says if you let people treat you any kind of way, that’s going to become a culture. And when it becomes a culture, you’ve got a problem. You can’t let anyone do you any kind of way. You’ve got to absolutely one hundred percent set the standard and the expectation.

Every project has problems. Every person has problems. Those need to be fixed daily. The prize goes to the team who can see and fix them daily. The prize goes to the team who can see and fix them daily on the most addictive, practical, and relevant communication system.

When you get your project management team daily doing this with you and assigning items to the right people, that’s when you wildly outpace the entropy and chaos of a project. Every item should have a picture or video, address the person that needs to fix it, address the company that needs to fix it, clearly state where it’s located, and define what done is once it’s corrected.

The Decision in Front of You

You can keep walking projects hoping people notice problems. You can keep relying on memory to remember what needs fixing. You can keep making mental notes that never get communicated. You can keep letting entropy outpace your correction efforts. You can keep wondering why your project looks chaotic despite walking it every day.

Or you can build a daily correction system. You can create two group chats—one for foreman, one for GC carpenters. You can capture ten to fifteen items per day with pictures and videos. You can dispatch them immediately to the right people. You can build a culture where corrections happen within twenty-four hours. You can create feedback loops when items get completed. You can teach everyone to see like you see.

The projects that stay clean, safe, and organized aren’t the ones with the best trades. They’re the ones with the most systematic daily correction processes. Where problems get captured in the moment. Where communication happens visually and immediately. Where responsibility is clear. Where urgency is built into the culture. Where feedback loops reinforce excellence.

This system allows you to focus on roadblocks. Which allows you to implement zero tolerance. Which allows you to grade your contractors. Which allows you to have a continuous improvement system on your project. Which creates an environment where workers and foreman can succeed.

If you’re on a three hundred fifty million dollar hospital, you should have three or four projects that make up the whole. Each project needs to have their own system like this. This is going to make the difference for you. Let’s get it done. Let’s start by next Monday. On we go.

Frequently Asked Questions

What apps work best for daily correction systems?

GroupMe or WhatsApp are recommended. WhatsApp is better at quickly uploading pictures and videos. GroupMe is better for keeping chat history and the ability to like comments, which creates positive reinforcement. By the time you read this, new apps may exist—the key is visual communication with immediate dispatch to the right people, not the specific platform.

How many items should you correct daily on a typical project?

Ten to fifteen items minimum per day for projects from five million to eighty million dollars. If you’re not operating at that speed, entropy will outpace your correction efforts. Every project has natural decay—you must systematically outpace it with daily identification and correction of problems.

How do you track whether items actually get corrected without software?

Walk the project regularly and see with your own eyes. If you walk three times per day, you’ll know if the same issue appears again. The culture should be that corrections happen within twenty-four hours. If you have to text the same item twice, remind them gently the first time, then address the team accountability issue if it continues.

What if you’re not on a software system like Procore for tracking?

You don’t need software to hold people accountable—you need culture. Software can’t hold people accountable. You hold people accountable by walking again, seeing what needs to be seen, and dealing with situations that weren’t fixed. The visual group chat creates the record and the urgency without requiring additional tracking systems.

How long does it take for trades to start self-correcting using this system?

About two months. After that period of getting texts throughout the day with pictures and videos, foreman start learning to see like you see. They develop the same standards. They begin sending pictures to each other and correcting items before you notice them. They send back pictures of completed corrections creating feedback loops. That’s when you know the culture has shifted and the system is self-sustaining.

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

Fanatical Roadblock Removal

Posted on by Danny Jiménez⁩
Read 27 min

Why Roadblock Removal Should Be Your Only Priority (And PPC Should Come Down Off Your Wall)

Your project tracks percent plan complete religiously. Every week, you measure what got done. You hold accountability meetings. You review variances. You ask why activities weren’t completed. You update the schedule. You report numbers to executives. And work keeps getting delayed. The same problems repeat. Materials arrive late again. RFIs sit unanswered again. Areas aren’t made ready again. Trades wait for information again. You’re measuring what didn’t happen without ever fixing what prevented it from happening.

Here’s what you’re missing. Percent plan complete is a lagging indicator. It tells you the score after the game is already over. It measures outcomes without addressing causes. It tracks whether you won or lost without helping you win differently next time. Roadblock removal is a leading indicator. It identifies problems before they impact production. It clears the path for work before work starts. It makes work ready so flow can continue. It’s the difference between managing what already happened versus preventing what might happen. You’re optimizing the wrong metric. And until you shift focus from tracking completions to removing roadblocks, your project will keep fighting the same battles while wondering why nothing improves.

The Problem Hiding Behind All Those Metrics

Walk into any project meeting and watch what gets discussed. Percent plan complete from last week. Variance analysis. Why activities didn’t finish. What needs to catch up. How far behind schedule the project is running. Everyone focused on measuring what already happened. Then ask what’s being done to prevent next week from repeating this week’s problems. Ask how many roadblocks were identified and removed. Ask what system exists to surface problems before they impact production. Ask how the team is making work ready for what’s starting in the next six weeks.

Silence. Confusion. Maybe someone mentions they’re “working on it” or “following up.” But no system. No tracking. No fanatical focus on removal. Just vague assurances that people are handling things as they come up. Most projects treat roadblock removal as reactive problem-solving that happens when issues surface. Material didn’t arrive? Call the supplier. RFI didn’t get answered? Follow up with the architect. Area wasn’t made ready? Push crews to work around it. Every problem gets addressed individually, reactively, after it’s already caused delay.

What’s missing is a proactive system that identifies roadblocks before they impact production and removes them systematically as the highest priority. Instead of asking “why didn’t this get done last week?” the question becomes “what will prevent work from flowing next week and how do we remove it now?” Instead of tracking completions, you track removals. Instead of lagging indicators, you focus on leading indicators.

The Field Reality: When Roadblocks Stay Hidden

I’ve seen this pattern everywhere. Projects run visual scheduling systems. They use Last Planner. They do Takt planning. They create make-ready look-aheads. They hold weekly work planning meetings. And roadblocks still don’t surface until they’ve already caused delays. Here’s why. Trade partners don’t identify roadblocks until they’re committed to specific work at specific times. When you’re using CPM and telling trades to “follow the schedule,” they can’t see where they’re supposed to be or what they’re supposed to be doing. So when you ask “what are your roadblocks?” they say “I don’t know, we’ll just show up every day and figure it out.”

But when trades see the rhythm on a Takt plan in a visual scheduling system, when they participate in pull planning and create make-ready look-aheads, when they commit together to weekly work plans, they start bringing up issues. People don’t find reasons why they can’t get married unless somebody asks them to marry. Once someone’s committed, they start identifying problems. “Oh, I need materials here by Thursday or I can’t start Friday. I need this RFI answered or I don’t know what to install. I need layout before I can begin. This area needs cleaning before I can work safely.” Commitment surfaces roadblocks. Visual systems create commitment. Roadblock removal systems capture those surfaced problems and eliminate them before they impact production. Without all three pieces, you’re managing reactively instead of proactively.

Why This Matters More Than Percent Plan Complete

When you focus on percent plan complete without focusing on roadblock removal, you’re measuring the scoreboard without coaching the game. You know the score. You don’t know how to change it. You track outcomes without improving the system that creates outcomes. Think about what percent plan complete actually tells you. Did the work get done? Yes or no. That’s useful information. But it’s backward-looking. It tells you what already happened. It doesn’t tell you what prevented work from flowing. It doesn’t identify the roadblocks that caused delays. It doesn’t help you make different decisions next week.

Now imagine focusing on roadblock removal instead. Track the number of roadblocks found at any given time. Track the average time duration before each roadblock would have made an impact to production. Track the average time from identification to resolution. Make this a science. Become fanatical about it. Suddenly you’re managing leading indicators. You’re identifying problems before they cause delays. You’re clearing the path for work before work starts. You’re making work ready so flow can continue. You’re coaching the game instead of just reading the scoreboard.

The shift is profound. Instead of asking “what didn’t get done last week?” you ask “what roadblocks exist for next week’s work and how do we remove them now?” Instead of reacting to delays, you prevent them. Instead of tracking completions, you track removals. Instead of lagging indicators that tell you you’re losing, you focus on leading indicators that help you win.

The Framework: Building a Fanatical Roadblock Removal System

Roadblock removal must become the primary focus of your team. Not percent plan complete. Not schedule updates. Not variance analysis. Roadblock removal. If a project manager or superintendent asks “what’s my main job?” the answer is roadblock removal. If the project executive or general superintendent asks their main job, it’s roadblock removal. Create a visual roadblock map in a location where foremen and the project management team see it and huddle daily. This isn’t a spreadsheet hidden in the office. This is a visual board in the trailer or on the wall where everyone walks past it multiple times per day. Where it’s impossible to ignore. Where it creates urgency just by existing.

Track three critical metrics. First, the number of roadblocks found at any given time. How many are currently identified and waiting for removal? Second, the average time duration before each roadblock would have made an impact to production. How far ahead are you catching them? Third, the average time from identification to resolution. How fast are you removing them once identified? Use the six-week make-ready look-ahead to identify work that’s not ready and bring roadblocks to the surface. Don’t wait for problems to appear. Look ahead systematically at what’s starting in the next six weeks and ask what’s not ready. What materials haven’t been ordered? What RFIs haven’t been submitted? What layout hasn’t been completed? What coordination hasn’t happened? Surface these as roadblocks now, not when they impact production.

Ensure the team collects roadblocks in both the afternoon foreman huddle and the morning worker huddle. Foremen bring them from the field. Workers identify them at point of work. Everyone’s watching for problems that haven’t surfaced yet. Then bring them to the daily team huddle as the first priority. Not the third agenda item. Not something you get to if there’s time. First. Every day. Focus most efforts on removing roadblocks before implementing other systems on site. This is the foundation. Without it, everything else struggles. You can’t have continuous improvement without stable environments. You can’t have stable environments without roadblock removal. Make this your obsession before worrying about perfect Takt plans or advanced lean tools.

Signals Your Project Lacks Roadblock Removal Focus

Watch for these patterns that reveal you’re tracking completions instead of removing roadblocks:

  • Meetings focus on why last week’s work didn’t finish instead of what will prevent next week’s work from flowing, keeping everyone reactive instead of proactive
  • The same problems repeat weekly because nobody’s identifying and removing the root causes systematically, just reacting to symptoms as they appear
  • No visible roadblock tracking exists, so nobody knows how many problems are waiting to impact production or how long they’ve been sitting unresolved
  • Trade partners don’t bring up issues until work starts and problems surface, revealing they’re not committed to specific plans that would surface roadblocks early

The Practical System for Daily Removal

Here’s how this works in practice. Every project has problems. You need all of them to come to the surface. The afternoon foreman huddle collects roadblocks from trades. The morning worker huddle surfaces problems from the field. Then at eight or nine AM, have your fifteen-minute stand-up meeting with the project management team—PM, PEs, office engineers—where roadblocks found in huddles get brought to the team for removal on a daily basis. If you’re a PM with multiple jobs, this gives you the opportunity to check in with your people daily and clear the path for work. When systems like this exist and the PM, super, and executive all work daily to remove roadblocks, work gets made ready and flow continues throughout the project.

Escalate appropriately based on severity. Some roadblocks get handled at the location level. The foreman identifies it, the foreman removes it. Done. No escalation needed. Other roadblocks need superintendent and PM involvement. The problem’s bigger, requires coordination, needs office support. Escalate to that level. The most severe roadblocks need project executive, project director, or general superintendent involvement. These are the big problems that will destroy schedule if not removed immediately. Call in the big dogs. Widen your circle. Scale. Make sure you’re getting this done.

Think of it as three levels of response. Handle what you can at the location level. Escalate medium problems to superintendent and PM level. Bring major roadblocks to the executive team. The key is matching response to severity and moving fast at every level. Roadblocks don’t wait. Neither should removal. If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow.

Why This Changes Everything

We’re not just building projects. We’re clearing the path for workers so they can succeed. And when we focus on roadblock removal instead of completion tracking, we shift from reactive management to proactive leadership. Workers need to know every day what they’re building, how to install it, where to put it. They need materials, equipment, a clean and safe and organized environment. They need stability. Clearing work for workers in that kind of environment is where we make money. That’s where we protect families. That’s where we honor the craft.

Roadblock removal creates that stability. It removes the chaos before chaos impacts production. It eliminates the interruptions before they interrupt flow. It makes work ready so workers can focus on installation instead of problem-solving around missing information, late materials, and incomplete coordination. Companies that become fanatical about roadblock removal will dominate their markets. Companies that keep tracking percent plan complete without identifying and removing roadblocks will keep fighting the same battles wondering why nothing improves. This isn’t theoretical. This is survival. The projects that finish fast aren’t the ones with the best tracking systems. They’re the ones with the most aggressive roadblock removal.

The Challenge in Front of You

You can keep tracking percent plan complete. You can keep measuring what got done last week. You can keep holding accountability meetings about variances. You can keep managing the scoreboard after the game is over. You can keep reacting to problems instead of preventing them.

Or you can build a fanatical roadblock removal system. You can create visual tracking. You can collect roadblocks from foremen and workers daily. You can bring them to team huddles as the first priority. You can track how many exist, how far ahead you’re catching them, how fast you’re removing them. You can make this a science. You can shift from lagging indicators to leading indicators.

The projects that succeed aren’t the ones with the prettiest percent plan complete charts. They’re the ones where roadblock removal is the obsession. Where every level of leadership from foreman to executive focuses on identifying problems before they impact production and removing them systematically. Where make-ready means actually ready, not theoretically ready. Where flow continues because the path was cleared before work started.

Remember: roadblock removal systems are leading indicators. Tracking percent plan complete and other metrics are lagging indicators. You want both, but leading indicators drive lagging indicators, not the other way around. When you ensure work is made ready through fanatical roadblock removal, percent plan complete takes care of itself. When you only track completions without removing roadblocks, nothing improves no matter how much you measure. Call out a hit on roadblocks before they affect you. Make removal your obsession. Clear the path for work. Create flow. Protect your people by protecting their ability to succeed. On we go.

Frequently Asked Questions

What’s the difference between roadblock removal and regular project management?

Regular project management reacts to problems after they appear and impact production. Roadblock removal proactively identifies problems before they impact production and eliminates them systematically. It’s the difference between tracking what didn’t get done last week versus preventing next week from having the same problems. Leading indicators versus lagging indicators.

How do you get trade partners to actually identify roadblocks ahead of time?

Trade partners identify roadblocks when they’re committed to specific work at specific times in visual systems. When they can see the rhythm on Takt plans, participate in pull planning, and commit to weekly work plans, they start bringing up issues. People don’t find reasons why they can’t until they’re committed to when they will. Commitment surfaces roadblocks.

What metrics should you track for roadblock removal?

Track three critical metrics: number of roadblocks found at any given time, average time duration before each roadblock would have made an impact to production, and average time from identification to resolution. Make this a science. Track it daily. Make it visual. Become fanatical about improving all three numbers.

When should roadblocks get escalated versus handled locally?

Handle what you can at the foreman level without escalation. Escalate medium problems to superintendent and PM level when coordination or office support is needed. Bring major roadblocks that will destroy schedule to project executive or general superintendent level. Match response to severity and move fast at every level.

Can you focus on roadblock removal while still tracking percent plan complete?

Yes, but roadblock removal takes priority. Roadblocks are leading indicators that drive future performance. Percent plan complete is a lagging indicator that measures past performance. Track both, but focus most effort on identifying and removing roadblocks before they impact production. When you make work ready through removal, completions improve automatically.

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

Zero Tolerance

Posted on by Danny Jiménez⁩
Read 33 min

Zero Tolerance Isn’t About Punishment—it’s the Most Respectful Thing You Can Do (And Why you’re Too Afraid to Implement It)

Your electrician isn’t wearing safety glasses. You see it. You walk past. You tell yourself you’ll mention it later. You don’t want to create conflict. You don’t want to seem like a hardass. You want to maintain good relationships. And you just disrespected that electrician more than if you’d yelled at him.

Here’s what you’re missing. When you walk past a safety issue without correcting it, you’re not being kind. You’re not preserving relationships. You’re sending a message that you don’t think that person is capable of following rules. That they’re not smart enough to do the right thing. That your standards don’t apply to them because you’ve decided they can’t meet them.

You’re tolerating bad behavior. And in doing so, you’re creating an unsafe, disorganized, chaotic project where nobody knows what winning looks like because you’re too afraid to enforce standards. You think you’re being nice. You’re actually destroying your project and disrespecting your people. Zero tolerance isn’t about punishment. It’s about respect. And until you understand that distinction, you’ll never create the stable environment where workers can actually succeed.

The Problem Every Superintendent Faces

Walk any project and watch what the superintendent does when he sees a problem. Worker without fall protection. Materials staged in the wrong location. Delivery showing up unscheduled. Area left dirty at the end of the day. Safety glasses missing. The superintendent sees it all. And does nothing. Or mentions it casually without actually correcting it. Or lets it slide because he doesn’t want conflict. Or makes excuses about why this particular person or situation gets a pass. The standards exist on paper but not in practice. Everyone knows the rules but nobody follows them consistently because enforcement is selective and weak.

Most superintendents think zero tolerance means being harsh. Mean. Punitive. Command and control. So they avoid it. They manage through relationships instead of standards. They play savior with trade partners, doing favors hoping favors come back. They let things slide to keep the peace. They walk past problems telling themselves they’re being understanding and flexible. And the project descends into chaos. Nobody knows what’s actually required versus what’s suggested. Standards become negotiable. Underperformers drag down top performers. Safety incidents happen. Quality suffers. The schedule slips. And the superintendent wonders why nothing changes despite constant conversations about expectations.

Here’s what’s happening. Without zero tolerance for bad behavior, there’s no consequence for deviation and no clarity about what’s actually required. The project operates in a fog where everyone’s guessing what standards apply today based on the superintendent’s mood or who’s asking. Top performers get frustrated seeing others violate standards without correction. Workers lose respect for leadership that won’t enforce what it claims to value. And the superintendent burns out trying to manage this chaos through personal relationships and emotional capital instead of building systems that make standards clear and enforcement consistent.

The System That Creates Tolerance for Bad Behavior

This isn’t about lazy superintendents or bad workers. This is about an industry that never taught people that high expectations are respect and that enforcing standards is caring for people, not punishing them. Construction culture treats enforcement like it’s mean. We’re told to build relationships. To be flexible. To understand that construction is hard and people are doing their best. To not be the hardass who makes everyone miserable. So superintendents avoid confrontation. They lower expectations. They make excuses for deviations. They tolerate bad behavior in the name of being understanding.

But here’s what that creates. When you tolerate someone working unsafely, you’re telling them you don’t think their life is worth protecting. When you tolerate dirty areas, you’re telling crews you don’t think they’re capable of cleanliness. When you tolerate unscheduled deliveries, you’re telling trades you don’t think they can plan properly. When you tolerate low standards, you’re telling everyone you don’t respect them enough to expect excellence.

The law of thirds suggests one-third of the project will be bought in, another third will be undecided, and the remaining third will not be bought in. By incentivizing good behavior and having positive culture on site, most will transition to being bought in. But for those who won’t, there needs to be a pay-to-play minimum standard that elevates behavior and triggers the removal of those who won’t conform. Without that, your A-players get dragged down by D-players who face no consequences. Your safety culture degrades. Your cleanliness standards slip. Your delivery coordination falls apart. And the whole project suffers because you were too afraid to enforce the standards you claim to value. The system failed them. It didn’t fail the workers.

A Story From the Field That Proves Zero Tolerance Works

At the research laboratory in Phoenix, we implemented zero tolerance from day one. Not as punishment. As respect. The project management team decided together that we would hold the line on cleanliness, safety, organization, and just-in-time deliveries. I had my shoulders back. Chest out. Confident. When people wanted to whine and complain, I held strong. We implemented zero tolerance together as a team, and I had control of the environment so workers could succeed.

For cleanliness, I never had a composite cleanup crew. If they made a mess, they cleaned it. People said that’s hard. It’s only hard if you’re not confident. When it came to safety, if it was in the orientation, in the OSHA training, something they knew to do but chose not to, I sent them to a safe location. Home. Not as punishment. As respect. To show them this matters. To protect them from themselves until they’re ready to work safely. When deliveries came unscheduled and someone else was in the queue, we turned them back. No exceptions. The schedule said when they could come. That’s when they come. Everyone else planned around it. Respecting that plan meant respecting everyone’s coordination.

And we had the most operational project site I’ve ever experienced or seen in the construction industry. Ask people who were there. The director of construction, actually vice president of the owner’s organization, said the project felt like going to Disneyland. Hard-nosed C-suite executives saying my project felt like Disneyland. You can’t argue with those results. Zero tolerance created the stable environment where everyone could succeed. Because everyone knew the standards. Everyone saw them enforced consistently. Everyone understood what was required. And everyone elevated to meet those standards because they were clear and non-negotiable.

Why This Matters More Than Being Nice

When you tolerate bad behavior, you’re not being nice. You’re being disrespectful and you’re destroying your project’s ability to create the stable environment where continuous improvement can happen. Think about what happens when you walk past a safety issue. You see a worker without safety glasses. You know the rule. They know the rule. It was in orientation. It’s on every safety poster. Everyone on the project knows safety glasses are required. But you walk past without correcting it.

What message did you just send? That you don’t think that worker is capable of following rules. That the standard doesn’t actually matter. That enforcement is optional. That their safety isn’t worth the uncomfortable conversation. You just disrespected that worker and every other worker who saw you walk past without correction. Now multiply that across the project. You tolerate dirty areas from some trades but not others. You enforce delivery schedules sometimes but not always. You correct safety issues when you’re in the mood but let them slide when you’re busy. You create selective enforcement based on relationships, mood, or convenience instead of consistent standards applied equally to everyone.

The project descends into chaos because nobody knows what’s actually required. Your best contractors get frustrated following rules while watching others ignore them without consequence. Workers lose respect for leadership that won’t back up its stated values with action. Safety incidents increase because people learn safety is negotiable. Quality suffers because standards aren’t enforced. The schedule slips because coordination falls apart. All because you were too afraid to enforce standards consistently. You thought you were being nice. You were actually creating the chaos that makes everyone’s job harder and puts people at risk.

The Framework: What Zero Tolerance Actually Means

Zero tolerance is never about punishment. It’s always about respect. High expectations equal respect. If you expect yourself to put on safety glasses and you wouldn’t tolerate yourself working without them, why are you tolerating it from other people? Either you have low standards for yourself or you have disrespectful assumptions about others’ capabilities.

Everyone on your project can follow the rules. Black, white, male, female, military veteran, any background, any language, anyone. All of us can put on safety glasses. All of us can stage materials in the right location. All of us can schedule deliveries properly. All of us can clean our areas. All of us can stay organized. These aren’t impossible standards. These are basic requirements that every human is capable of meeting.

When you lower expectations for certain people or groups, that’s discrimination. Not reverse discrimination. Actual discrimination. You’re deciding that person isn’t capable of meeting the same standards you expect from everyone else. That’s classist, racist, sexist, disgusting, prejudiced, and discriminatory. You’re playing savior and thinking in your mind they’re incapable, unable, not smart enough.

The foundation for lean in Japanese culture, Toyota, throughout the United States, everywhere, comes down to respect for people and resources. If you’re being a wimpy leader and playing savior and not expecting excellence from human beings, you are the problem. You do not respect people and you will never be lean.

Zero tolerance means training people. Orienting them. Giving them every opportunity. Giving them a second chance. Coaching them. Mentoring them. But not tolerating deviations from standards. When someone violates a safety rule after training, you don’t remind them. You correct it. You send them to a safe location. You make it clear this matters. Not as punishment. As protection. As respect.

Signals You’re Tolerating Bad Behavior

Watch for these patterns that indicate you’re avoiding enforcement instead of protecting people:

  • You see safety violations multiple times per day but only correct them occasionally when you feel like it, teaching workers that safety is negotiable based on your mood
  • The same contractors leave areas dirty week after week because you mention it but never enforce consequences, so they learn your standards are suggestions
  • Deliveries arrive unscheduled regularly and you accept them to avoid conflict, destroying the coordination that protects everyone’s schedule
  • You make excuses for why certain workers or trades get passes on standards, revealing your belief that they’re not capable of meeting the same expectations as everyone else

The Practical Path to Implementation

Here’s the uncomfortable truth. You need six weeks of enforcing standards before trade partners buy in. Not six weeks of suggesting. Six weeks of actual enforcement. Six weeks where the culture rejects deviations. Six weeks where only bought-in people thrive and people who won’t conform cannot survive on your project.

This isn’t command and control. This isn’t yelling. This is a group of people deciding together: this is what we’re doing. Let’s go. You put your shoulders back, chest out, and enforce the standards the team agreed to. You send unsafe workers to safe locations. You turn back unscheduled deliveries. You require trades to clean their areas. You make it clear these aren’t suggestions.

After six weeks of experiencing cleanliness, organization, safety, and just-in-time deliveries, you give them the choice. Do you want to go back to the old system or stay with us? You had the choice now. You didn’t before. They will always choose the lean way. But they can’t know what to decide until they’ve seen it. And they won’t do it until you enforce it. And it can’t be enforced without zero tolerance.

The success of any organization is determined by the worst behavior the leader is willing to tolerate. If you tolerate unsafe work, that becomes your standard. If you tolerate dirty areas, that becomes your standard. If you tolerate unscheduled deliveries, that becomes your standard. Whatever you walk past without correction becomes the new normal. If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow.

Why This Takes Courage You Might Not Have Yet

Implementing zero tolerance requires the same courage it takes to push experienced construction veterans out of their comfort zone in a training boot camp. The same grit it takes to stand in front of three hundred people on your project when everyone’s clamoring for you to be lenient and let it go. The same resolve it takes to stop work, correct a situation, and hold the line as the most confident person on site.

Most superintendents don’t have that yet. They haven’t developed the interpersonal skills. They haven’t learned to give one hundred percent with emotion, passion, enthusiasm. They haven’t done the hard work of professional development that teaches you how to enforce standards with respect instead of punishment.

That’s why zero tolerance fails on most projects. Not because it’s wrong. Because leaders don’t have the courage to implement it. They cave under pressure. They make exceptions. They avoid confrontation. They let things slide. And the project suffers.

You will not have an organization with superintendents who implement zero tolerance until you have professional development training where people learn interpersonal skills and how to give one hundred percent. You need to develop leaders who can enforce standards with confidence, clarity, and respect. Who can hold the line when tested? Who can create environments where only excellence survives?

Connecting This to Why We’re in Construction

We’re not just building projects. We’re protecting people. And when we tolerate unsafe work, when we tolerate chaos, when we tolerate low standards, we’re failing to protect the workers who depend on us to create stable environments where they can succeed. A worker needs to know every day what they’re building, how to install it, where to put it. They need materials, equipment, a clean and safe and organized environment. They need stability. Clearing work for workers in that kind of environment is where we make money. That’s where we protect families. That’s where we honor the craft.

Zero tolerance creates that stability. It removes the chaos that makes work dangerous. It eliminates the waste that makes work frustrating. It establishes the standards that make work predictable. It protects people by making expectations clear and enforcing them consistently. When you walk past a safety issue, you’re not just risking that worker’s life. You’re risking their family. Their kids who need them home safe. Their spouse who depends on them. Their future that gets destroyed by one preventable accident. If you are walking past safety issues without correcting them for fear of offending somebody, you do not respect those people. You are only protecting yourself.

People who don’t say the things that need to be said for fear of offending somebody are only thinking of themselves. Zero tolerance is never about you. It’s about protecting the people who trust you to create safe environments where they can work without fear.

The Decision in Front of You

You can keep walking past problems. You can keep tolerating bad behavior in the name of being nice. You can keep playing savior with people you’ve decided aren’t capable of excellence. You can keep avoiding confrontation to preserve relationships. You can keep managing through personal influence instead of clear standards. Or you can implement zero tolerance. You can expect excellence from everyone because you respect everyone enough to believe they’re capable of it. You can enforce standards consistently. You can create environments where only bought-in people thrive. You can protect workers by making their safety non-negotiable.

The projects that succeed aren’t the ones with the nicest superintendents. They’re the ones with the clearest standards, the most consistent enforcement, and the strongest resolve to protect people through zero tolerance. Where everyone knows what’s expected. Where everyone sees standards enforced equally. Where excellence is required and mediocrity cannot survive. Jim Collins taught this clearly: get the right people on the bus and the wrong people off. Toyota doesn’t tolerate bad behavior. Paul Akers doesn’t tolerate bad behavior. No lean company with their act together tolerates bad behavior. They implement zero tolerance. Not as punishment. As respect. As the foundation that makes everything else possible.

Stop tolerating bad behavior. Find a way to get this done. You will never grade contractors effectively. You will never create continuous improvement systems. You will never achieve the operational control needed for production. Until you stop tolerating bad behavior and implement zero tolerance as the respect your people deserve. On we go.

Frequently Asked Questions

Isn’t zero tolerance too harsh and likely to damage relationships with trade partners?

Zero tolerance isn’t harsh when implemented as respect rather than punishment. You train people, orient them, give them opportunities, coach them, mentor them. Then you enforce standards consistently. After six weeks of experiencing the benefits of cleanliness, safety, organization, and coordination, they choose to stay because it makes their work better. Clear expectations strengthen relationships by eliminating confusion.

How do you enforce zero tolerance without creating a command-and-control environment?

The project management team decides standards together as a group, not imposed from above. You’re enforcing what the team agreed to, not dictating unilaterally. When someone violates a safety rule, you send them to a safe location for protection, not punishment. When deliveries arrive unscheduled, you turn them back to protect coordination for everyone. You’re protecting the system the team built together.

What if enforcing zero tolerance causes workers to quit or trades to walk off?

Most will transition to being bought in when they experience the stability and respect that zero tolerance creates. Some won’t, and that’s fine—they invite themselves to work somewhere else. The conscientious wonderful workers appreciate clear standards and consistent enforcement. You lose people who weren’t making production anyway. Your A-players stay and thrive because the environment protects excellence.

How do you implement zero tolerance without appearing discriminatory toward certain groups?

Zero tolerance means holding everyone to the same standards regardless of background, language, experience, or any other factor. The discrimination happens when you lower expectations for certain people because you’ve decided they’re not capable. Everyone can put on safety glasses, clean areas, schedule deliveries, and follow basic safety rules. Expecting excellence from everyone is respect. Lowering standards for some is discrimination.

What’s the first step to implementing zero tolerance if you’ve been tolerating bad behavior?

Decide with your project management team what standards matter most—typically safety, cleanliness, organization, and delivery coordination. Announce the change clearly with advance notice. Then enforce consistently for six weeks without exception. Send unsafe workers to safe locations. Turn back unscheduled deliveries. Require clean areas. Make deviations impossible to ignore. After six weeks, people will have experienced the benefits and choose to maintain the standards themselves.

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

Contractor Grading

Posted on by Danny Jiménez⁩
Read 29 min

The Feedback Loop Nobody’s Building: Why Your Continuous Improvement System Isn’t Improving Anything

Your project has morning huddles. You coordinate daily. You track commitments. You measure percent plan complete. You review variances weekly. Everyone knows what they’re supposed to do tomorrow. Everyone reports what they did today. And nothing actually improves. The same problems repeat. The same roadblocks appear. The same waste happens. Week after week, month after month, you’re coordinating without improving. Measuring without learning. Tracking without changing.

Here’s what’s missing. You don’t have a feedback loop at your most critical point in the system. You’re measuring whether work got done. You’re not measuring why it didn’t. You’re tracking production during installation. You’re not tracking interruptions between installations. You’re coordinating tomorrow’s plan. You’re not improving today’s process. You’re running a coordination system disguised as continuous improvement. And coordination without improvement is just organized chaos that repeats indefinitely.

The Problem Every Superintendent Faces

Walk into any afternoon coordination meeting and watch what happens. Foremen report where they’ll be tomorrow. The superintendent reviews the schedule. Everyone coordinates locations and sequences. Conflicts get identified. Plans get adjusted. The meeting ends. Everyone leaves knowing the plan for tomorrow. And nobody talked about why today didn’t go as planned. Nobody discussed what interrupted the work. Nobody identified which of the eight wastes caused the delays. Nobody planned specific improvements to prevent tomorrow from repeating today’s problems. Nobody created a feedback loop that actually changes anything.

Most projects treat huddles as coordination meetings. Get everyone on the same page about tomorrow. Make sure trades don’t conflict. Ensure areas are ready. Review the schedule. Those are important. But they’re not continuous improvement. They’re coordination. Coordination keeps chaos from getting worse. Improvement makes things actually better. The difference is critical. Coordination asks “where will you be tomorrow?” Improvement asks “what held you up today and how do we prevent it tomorrow?” Coordination focuses on commitments. Improvement focuses on waste removal. Coordination maintains the current state. Improvement changes it.

The System That Creates Coordination Without Improvement

This isn’t about lazy superintendents or uncommitted foremen. This is about an industry that confuses coordination with continuous improvement and measures the wrong metrics. Construction culture celebrates commitments made. Did you do what you said you’d do? Did you hit your production targets? Did you finish the areas on schedule? We measure percent plan complete obsessively. We track variances religiously. We hold people accountable to commitments.

But we don’t teach people to see waste. We don’t train them to identify which of the eight wastes caused interruptions. We don’t create systems that capture why work stopped, not just whether it finished. We don’t build feedback loops with short enough latency to actually change behavior. Last Planner tracks why activities weren’t done, mostly on a weekly basis in aggregate. That’s useful data. But it doesn’t have short enough latency to create real improvement. By the time you review variances from last week, the crew has moved on. The foreman has forgotten details. The moment to learn and adjust has passed. The feedback loop is too slow to change behavior.

So the same waste repeats. Materials arrive late again. RFIs interrupt work again. Areas aren’t made ready again. Piles need moving again. The same problems cycle through the project because nobody built a feedback loop fast enough to actually stop them. The system failed them. It didn’t fail the workers.

A Story From the Field That Proves the Difference

At the research laboratory in Phoenix, we implemented something different. We gave everybody five-S and eight-wastes cards. Pocket-sized. Laminated. A couple hundred bucks for thousands of cards printed. Every worker had them. Every morning in the worker huddle, we’d review the eight wastes. We’d talk about how they work together. How to see them. What was in our way. We’d say “everybody hold up your cards” and replace missing ones. We trained on the eight wastes constantly until people could see them everywhere.

Then workers would go into crew preparation huddles where foremen took them through stretch and flex, reviewed the pretest plan, and prepared for the day. But here’s the critical piece: throughout the day, whenever something interrupted work, foremen tracked it. They shot a video right away or wrote it down or texted it. They connected the interruption to one of the eight wastes.

In afternoon foreman huddles, we didn’t just coordinate tomorrow. We discussed what held each crew up today. We collectively asked “how can we create more flow for each other tomorrow?” We planned specific improvements tied to lean principles. We recorded them on video. We deployed the training the next morning to prevent repeating the same waste.

I got one hundred sixty lean improvement videos on that project. Looking back, we could have gotten six or eight hundred if I’d doubled down on the system. But even at one hundred sixty, the improvement was dramatic. Production increased. Waste decreased. Money got made. Because we built a feedback loop at the critical point: the moment when work stopped and we asked why.

Why This Matters More Than Percent Plan Complete

When you don’t have a feedback loop at the point of interruption, improvement becomes theoretical. You know you should get better. You want to improve. You talk about continuous improvement in meetings. But nothing changes because you’re not capturing and acting on the information that would actually drive change. Think about what most projects track. Did the crew make their production target? Yes or no. Did they finish the area on schedule? Yes or no. What was percent plan complete for the week? Ninety percent? Eighty-five percent? Those are outcome measures. They tell you whether you won or lost. They don’t tell you how to win differently tomorrow.

Now imagine tracking the in-betweens instead. How many times did work stop today? What caused each interruption? Which of the eight wastes was it? Overproduction? Excess inventory? Transportation? Motion? Defects? Over-processing? Waiting? Not using the genius of the team? What specific improvement would prevent this waste tomorrow? Those are process measures. They tell you how to win. They identify exactly where the system is failing. They point directly to what needs to change. They create a feedback loop that actually improves things instead of just measuring whether things happened.

The shift is profound. Instead of asking “did you make your numbers?” you ask “what interrupted your flow and how do we remove it?” Instead of tracking whether work finished, you track why it stopped. Instead of measuring outcomes, you measure the causes that create outcomes. Instead of coordination, you get improvement.

The Framework: Building Feedback Loops That Actually Improve

Continuous improvement requires everyone knowing the eight wastes by memory. Not theoretically. Not “yeah, I’ve heard of those.” By memory. Overproduction, excess inventory, transportation, motion, defects, over-processing, waiting, and not using the genius of the team. They need to know how they connect. Overproduction creates excess inventory. Inventory requires transportation. Transportation creates motion. Motion and distraction create defects. Defects require over-processing. Over-processing creates waiting. All of it wastes the genius of the team.

People cannot improve what they cannot see. If foremen don’t know the eight wastes, they can’t identify them when they happen. If workers don’t recognize waste, they can’t flag it for removal. If superintendents don’t speak the language of waste, they can’t build systems to eliminate it. Everyone must learn the eight wastes. This is non-negotiable.

Everyone must three-S or five-S daily to see problems. Sort, straighten, sweep. Remove what’s not needed. Organize what remains. Clean the area in detail. This isn’t about cleanliness for aesthetics. This is about creating conditions where problems become visible. You cannot see missing materials in a cluttered area. You cannot identify defects in dirty work. You cannot spot waste in chaos. Three-S creates the stable environment where waste becomes obvious.

Foremen must track interruptions throughout the day, not just production totals. When work stops, that’s the critical moment. Not hours later in a meeting. Not days later in a variance review. Right then. The foreman shoots a video, writes it down, texts the superintendent. They identify which waste caused the interruption. They capture the specific problem. They create the data that drives improvement.

Afternoon foreman huddles must shift from pure coordination to improvement planning. Yes, coordinate tomorrow’s work. But spend equal time discussing what held each crew up today. Ask collectively “how do we create more flow for each other tomorrow?” Plan specific improvements. Record them. Make sure every foreman leaves knowing exactly what they’re going to do differently to win more tomorrow.

Morning worker huddles must deploy yesterday’s improvements. This closes the feedback loop. The interruption got identified yesterday. The improvement got planned yesterday afternoon. The training gets delivered this morning. The change gets implemented today. The loop runs daily, not weekly or monthly. That’s fast enough to actually change behavior and prevent waste from repeating.

Signals Your Project Lacks Real Continuous Improvement

Watch for these patterns that indicate you’re coordinating without improving:

  • Huddles focus on where crews will be tomorrow and what they need, but never discuss why yesterday didn’t go as planned or what specific waste caused interruptions
  • The same problems repeat week after week because nobody’s building feedback loops fast enough to identify root causes and prevent recurrence
  • Percent plan complete gets tracked religiously but nobody can name the eight wastes or connect interruptions to specific waste categories that could be systematically removed
  • Workers and foremen can recite tomorrow’s plan perfectly but can’t explain what improvement they’re implementing today based on yesterday’s learning

The Practical System for Daily Improvement

Here’s how this works in practice. Every worker gets a card with the eight wastes and five-S principles. Not optional. Not “if they want one.” Everyone gets one. You review them every morning in worker huddles until people know them by memory. You offer substantial rewards, two to five hundred dollar gift cards, if someone can stand and deliver a presentation on the eight wastes and why they’re created.

Throughout the day, foremen track interruptions. Every time work stops, they identify which waste caused it. They don’t wait for end of day. They don’t rely on memory. They capture it in the moment. Video, text, written note. Whatever works. But they capture the waste and the specific problem.

Afternoon foreman huddles run in two parts. First thirty minutes: coordinate tomorrow and discuss what held each crew up today. Collectively problem-solve how to create more flow tomorrow. Second thirty minutes: superintendent works one-on-one with each foreman to ensure they have target production for tomorrow, improvements they’ll make for their crews, things they’ll teach their workers to make better production. Each foreman shows their completed plan before leaving.

When crews don’t meet production, they must connect why with the eight wastes. Track the in-betweens. Create before-and-after lean improvement videos. These aren’t optional nice-to-haves. This is how learning gets captured and scaled. The video shows what was wrong, what changed, what improved. It gets shared with other crews. It prevents the same waste from happening elsewhere.

Next morning, worker huddles deploy yesterday’s improvements. The foreman trains the crew on what they’re changing based on yesterday’s learning. This can be done at crew level, company level, or project level. For companies with multiple projects, broadcast morning training through a YouTube channel or group messaging. The improvement gets implemented immediately, not weeks later after it’s been analyzed to death. If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow.

Why This Matters Beyond One Project

We’re not just building projects. We’re building people who build things. And when we create systems where people learn daily from their own work, where waste gets identified and removed in real-time, where improvements get implemented immediately, we’re respecting people by making their work easier tomorrow than it was today.

The current condition wastes people. We make them repeat the same problems because we don’t build feedback loops fast enough to prevent recurrence. We burden them with waste we could eliminate if we just captured and acted on the data we already generate. We frustrate them by coordinating tomorrow without learning from today.

Continuous improvement done right protects people. It removes the waste that makes their work harder. It eliminates the interruptions that create frustration. It prevents the problems that force overtime and weekend work. It makes tomorrow better than today in specific, measurable, repeatable ways.

Companies that build daily feedback loops will dominate their markets. Companies that keep coordinating without improving will slowly lose ground to competitors who actually learn and adapt. This isn’t theoretical. This is survival. The construction industry is facing constraints on labor, materials, and resources. Companies that continuously improve will thrive. Companies that keep repeating the same waste will fail.

The Challenge in Front of You

You can keep running coordination meetings disguised as improvement. You can keep tracking percent plan complete without identifying waste. You can keep measuring outcomes without improving processes. You can keep coordinating tomorrow without learning from today. Or you can build feedback loops at the critical point. You can teach everyone the eight wastes by memory. You can track interruptions, not just production. You can plan specific improvements based on identified waste. You can deploy training the next morning. You can create a system that actually improves instead of just measuring.

The projects that get faster and cheaper over time aren’t the ones with the best coordination. They’re the ones with the tightest feedback loops. The shortest time from problem identified to improvement implemented. The clearest connection between waste observed and waste removed. The most consistent daily learning and adaptation.

Eliyahu Goldratt said it clearly: “Tell me how you measure me, and I will tell you how I will behave.” If you measure commitments made, people will focus on making commitments. If you measure waste removed and improvements implemented, people will focus on removing waste and implementing improvements. The feedback loop you build determines the behavior you get. Build the loop. Track the waste. Improve daily. Make tomorrow better than today in specific, measurable ways your people can see and feel. On we go.

Frequently Asked Questions

How do you get everyone to memorize the eight wastes?

Review them every morning in worker huddles until people know them by memory. Post signs about them everywhere. Give pocket cards to every worker. Offer substantial rewards like two to five hundred dollar gift cards for anyone who can stand and deliver a presentation on the eight wastes and explain how they connect. Make it unavoidable and worth learning.

What if foremen resist tracking interruptions throughout the day?

Start with your own self-performed crews to prove the system works, then expand to trade partners who see the results. Make it easy with simple tools like video, text, or quick written notes. Show foremen how this makes their job easier by removing recurring waste instead of fighting the same problems repeatedly.

How is this different from Last Planner’s variance tracking?

Last Planner tracks why activities weren’t done weekly in aggregate, which is useful but has too much latency to change behavior quickly. Daily tracking captures interruptions in the moment, connects them to specific wastes, and deploys improvements the next morning. The feedback loop runs daily instead of weekly, which is fast enough to actually change behavior.

What do you do with the lean improvement videos once they’re created?

Share them immediately with other crews to prevent the same waste from happening elsewhere. Build a library organized by waste type so people can learn from past improvements. Use them in morning huddles to deploy training. Make them searchable and accessible so any crew facing similar problems can see how others solved them.

Can this work if you’re only a trade partner on someone else’s project?

Absolutely. Start with your own crews regardless of project structure. Track your interruptions, identify your waste, plan your improvements, deploy your training. The system works at crew level, company level, or project level. You don’t need the GC’s permission to improve your own processes and remove your own waste.

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

Continuous Improvement

Posted on by Danny Jiménez⁩
Read 29 min

The Feedback Loop Nobody’s Building: Why Your Continuous Improvement System Isn’t Improving Anything

Your project has morning huddles. You coordinate daily. You track commitments. You measure percent plan complete. You review variances weekly. Everyone knows what they’re supposed to do tomorrow. Everyone reports what they did today. And nothing actually improves. The same problems repeat. The same roadblocks appear. The same waste happens. Week after week, month after month, you’re coordinating without improving. Measuring without learning. Tracking without changing.

Here’s what’s missing. You don’t have a feedback loop at your most critical point in the system. You’re measuring whether work got done. You’re not measuring why it didn’t. You’re tracking production during installation. You’re not tracking interruptions between installations. You’re coordinating tomorrow’s plan. You’re not improving today’s process. You’re running a coordination system disguised as continuous improvement. And coordination without improvement is just organized chaos that repeats indefinitely.

The Problem Every Superintendent Faces

Walk into any afternoon coordination meeting and watch what happens. Foremen report where they’ll be tomorrow. The superintendent reviews the schedule. Everyone coordinates locations and sequences. Conflicts get identified. Plans get adjusted. The meeting ends. Everyone leaves knowing the plan for tomorrow.

And nobody talked about why today didn’t go as planned. Nobody discussed what interrupted the work. Nobody identified which of the eight wastes caused the delays. Nobody planned specific improvements to prevent tomorrow from repeating today’s problems. Nobody created a feedback loop that actually changes anything.

Most projects treat huddles as coordination meetings. Get everyone on the same page about tomorrow. Make sure trades don’t conflict. Ensure areas are ready. Review the schedule. Those are important. But they’re not continuous improvement. They’re coordination. Coordination keeps chaos from getting worse. Improvement makes things actually better.

The difference is critical. Coordination asks “where will you be tomorrow?” Improvement asks “what held you up today and how do we prevent it tomorrow?” Coordination focuses on commitments. Improvement focuses on waste removal. Coordination maintains the current state. Improvement changes it.

The System That Creates Coordination Without Improvement

This isn’t about lazy superintendents or uncommitted foremen. This is about an industry that confuses coordination with continuous improvement and measures the wrong metrics. Construction culture celebrates commitments made. Did you do what you said you’d do? Did you hit your production targets? Did you finish the areas on schedule? We measure percent plan complete obsessively. We track variances religiously. We hold people accountable to commitments.

But we don’t teach people to see waste. We don’t train them to identify which of the eight wastes caused interruptions. We don’t create systems that capture why work stopped, not just whether it finished. We don’t build feedback loops with short enough latency to actually change behavior. Last Planner tracks why activities weren’t done, mostly on a weekly basis in aggregate. That’s useful data. But it doesn’t have short enough latency to create real improvement. By the time you review variances from last week, the crew has moved on. The foreman has forgotten details. The moment to learn and adjust has passed. The feedback loop is too slow to change behavior.

So the same waste repeats. Materials arrive late again. RFIs interrupt work again. Areas aren’t made ready again. Piles need moving again. The same problems cycle through the project because nobody built a feedback loop fast enough to actually stop them. The system failed them. It didn’t fail the workers.

A Story From the Field That Proves the Difference

At the research laboratory in Phoenix, we implemented something different. We gave everybody five-S and eight-wastes cards. Pocket-sized. Laminated. A couple hundred bucks for thousands of cards printed. Every worker had them. Every morning in the worker huddle, we’d review the eight wastes. We’d talk about how they work together. How to see them. What was in our way. We’d say “everybody hold up your cards” and replace missing ones. We trained on the eight wastes constantly until people could see them everywhere.

Then workers would go into crew preparation huddles where foremen took them through stretch and flex, reviewed the pretest plan, and prepared for the day. But here’s the critical piece: throughout the day, whenever something interrupted work, foremen tracked it. They shot a video right away or wrote it down or texted it. They connected the interruption to one of the eight wastes.

In afternoon foreman huddles, we didn’t just coordinate tomorrow. We discussed what held each crew up today. We collectively asked “how can we create more flow for each other tomorrow?” We planned specific improvements tied to lean principles. We recorded them on video. We deployed the training the next morning to prevent repeating the same waste.

I got one hundred sixty lean improvement videos on that project. Looking back, we could have gotten six or eight hundred if I’d doubled down on the system. But even at one hundred sixty, the improvement was dramatic. Production increased. Waste decreased. Money got made. Because we built a feedback loop at the critical point: the moment when work stopped and we asked why.

Why This Matters More Than Percent Plan Complete

When you don’t have a feedback loop at the point of interruption, improvement becomes theoretical. You know you should get better. You want to improve. You talk about continuous improvement in meetings. But nothing changes because you’re not capturing and acting on the information that would actually drive change. Think about what most projects track. Did the crew make their production target? Yes or no. Did they finish the area on schedule? Yes or no. What was percent plan complete for the week? Ninety percent? Eighty-five percent? Those are outcome measures. They tell you whether you won or lost. They don’t tell you how to win differently tomorrow.

Now imagine tracking the in-betweens instead. How many times did work stop today? What caused each interruption? Which of the eight wastes was it? Overproduction? Excess inventory? Transportation? Motion? Defects? Over-processing? Waiting? Not using the genius of the team? What specific improvement would prevent this waste tomorrow?

Those are process measures. They tell you how to win. They identify exactly where the system is failing. They point directly to what needs to change. They create a feedback loop that actually improves things instead of just measuring whether things happened. The shift is profound. Instead of asking “did you make your numbers?” you ask “what interrupted your flow and how do we remove it?” Instead of tracking whether work finished, you track why it stopped. Instead of measuring outcomes, you measure the causes that create outcomes. Instead of coordination, you get improvement.

The Framework: Building Feedback Loops That Actually Improve

Continuous improvement requires everyone knowing the eight wastes by memory. Not theoretically. Not “yeah, I’ve heard of those.” By memory. Overproduction, excess inventory, transportation, motion, defects, over-processing, waiting, and not using the genius of the team. They need to know how they connect. Overproduction creates excess inventory. Inventory requires transportation. Transportation creates motion. Motion and distraction create defects. Defects require over-processing. Over-processing creates waiting. All of it wastes the genius of the team.

People cannot improve what they cannot see. If foremen don’t know the eight wastes, they can’t identify them when they happen. If workers don’t recognize waste, they can’t flag it for removal. If superintendents don’t speak the language of waste, they can’t build systems to eliminate it. Everyone must learn the eight wastes. This is non-negotiable.

Everyone must three-S or five-S daily to see problems. Sort, straighten, sweep. Remove what’s not needed. Organize what remains. Clean the area in detail. This isn’t about cleanliness for aesthetics. This is about creating conditions where problems become visible. You cannot see missing materials in a cluttered area. You cannot identify defects in dirty work. You cannot spot waste in chaos. Three-S creates the stable environment where waste becomes obvious.

Foremen must track interruptions throughout the day, not just production totals. When work stops, that’s the critical moment. Not hours later in a meeting. Not days later in a variance review. Right then. The foreman shoots a video, writes it down, texts the superintendent. They identify which waste caused the interruption. They capture the specific problem. They create the data that drives improvement.

Afternoon foreman huddles must shift from pure coordination to improvement planning. Yes, coordinate tomorrow’s work. But spend equal time discussing what held each crew up today. Ask collectively “how do we create more flow for each other tomorrow?” Plan specific improvements. Record them. Make sure every foreman leaves knowing exactly what they’re going to do differently to win more tomorrow.

Morning worker huddles must deploy yesterday’s improvements. This closes the feedback loop. The interruption got identified yesterday. The improvement got planned yesterday afternoon. The training gets delivered this morning. The change gets implemented today. The loop runs daily, not weekly or monthly. That’s fast enough to actually change behavior and prevent waste from repeating.

Signals Your Project Lacks Real Continuous Improvement

Watch for these patterns that indicate you’re coordinating without improving:

  • Huddles focus on where crews will be tomorrow and what they need, but never discuss why yesterday didn’t go as planned or what specific waste caused interruptions
  • The same problems repeat week after week because nobody’s building feedback loops fast enough to identify root causes and prevent recurrence
  • Percent plan complete gets tracked religiously but nobody can name the eight wastes or connect interruptions to specific waste categories that could be systematically removed
  • Workers and foremen can recite tomorrow’s plan perfectly but can’t explain what improvement they’re implementing today based on yesterday’s learning

The Practical System for Daily Improvement

Here’s how this works in practice. Every worker gets a card with the eight wastes and five-S principles. Not optional. Not “if they want one.” Everyone gets one. You review them every morning in worker huddles until people know them by memory. You offer substantial rewards, two to five hundred dollar gift cards, if someone can stand and deliver a presentation on the eight wastes and why they’re created. Throughout the day, foremen track interruptions. Every time work stops, they identify which waste caused it. They don’t wait for end of day. They don’t rely on memory. They capture it in the moment. Video, text, written note. Whatever works. But they capture the waste and the specific problem.

Afternoon foreman huddles run in two parts. First thirty minutes: coordinate tomorrow and discuss what held each crew up today. Collectively problem-solve how to create more flow tomorrow. Second thirty minutes: superintendent works one-on-one with each foreman to ensure they have target production for tomorrow, improvements they’ll make for their crews, things they’ll teach their workers to make better production. Each foreman shows their completed plan before leaving. When crews don’t meet production, they must connect why with the eight wastes. Track the in-betweens. Create before-and-after lean improvement videos. These aren’t optional nice-to-haves. This is how learning gets captured and scaled. The video shows what was wrong, what changed, what improved. It gets shared with other crews. It prevents the same waste from happening elsewhere.

Next morning, worker huddles deploy yesterday’s improvements. The foreman trains the crew on what they’re changing based on yesterday’s learning. This can be done at crew level, company level, or project level. For companies with multiple projects, broadcast morning training through a YouTube channel or group messaging. The improvement gets implemented immediately, not weeks later after it’s been analyzed to death. If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow.

Why This Matters Beyond One Project

We’re not just building projects. We’re building people who build things. And when we create systems where people learn daily from their own work, where waste gets identified and removed in real-time, where improvements get implemented immediately, we’re respecting people by making their work easier tomorrow than it was today. The current condition wastes people. We make them repeat the same problems because we don’t build feedback loops fast enough to prevent recurrence. We burden them with waste we could eliminate if we just captured and acted on the data we already generate. We frustrate them by coordinating tomorrow without learning from today.

Continuous improvement done right protects people. It removes the waste that makes their work harder. It eliminates the interruptions that create frustration. It prevents the problems that force overtime and weekend work. It makes tomorrow better than today in specific, measurable, repeatable ways. Companies that build daily feedback loops will dominate their markets. Companies that keep coordinating without improving will slowly lose ground to competitors who actually learn and adapt. This isn’t theoretical. This is survival. The construction industry is facing constraints on labor, materials, and resources. Companies that continuously improve will thrive. Companies that keep repeating the same waste will fail.

The Challenge in Front of You

You can keep running coordination meetings disguised as improvement. You can keep tracking percent plan complete without identifying waste. You can keep measuring outcomes without improving processes. You can keep coordinating tomorrow without learning from today. Or you can build feedback loops at the critical point. You can teach everyone the eight wastes by memory. You can track interruptions, not just production. You can plan specific improvements based on identified waste. You can deploy training the next morning. You can create a system that actually improves instead of just measuring.

The projects that get faster and cheaper over time aren’t the ones with the best coordination. They’re the ones with the tightest feedback loops. The shortest time from problem identified to improvement implemented. The clearest connection between waste observed and waste removed. The most consistent daily learning and adaptation. Eliyahu Goldratt said it clearly: “Tell me how you measure me, and I will tell you how I will behave.” If you measure commitments made, people will focus on making commitments. If you measure waste removed and improvements implemented, people will focus on removing waste and implementing improvements. The feedback loop you build determines the behavior you get. Build the loop. Track the waste. Improve daily. Make tomorrow better than today in specific, measurable ways your people can see and feel. On we go.

Frequently Asked Questions

How do you get everyone to memorize the eight wastes?

Review them every morning in worker huddles until people know them by memory. Post signs about them everywhere. Give pocket cards to every worker. Offer substantial rewards like two to five hundred dollar gift cards for anyone who can stand and deliver a presentation on the eight wastes and explain how they connect. Make it unavoidable and worth learning.

What if foremen resist tracking interruptions throughout the day?

Start with your own self-performed crews to prove the system works, then expand to trade partners who see the results. Make it easy with simple tools like video, text, or quick written notes. Show foremen how this makes their job easier by removing recurring waste instead of fighting the same problems repeatedly.

How is this different from Last Planner’s variance tracking?

Last Planner tracks why activities weren’t done weekly in aggregate, which is useful but has too much latency to change behavior quickly. Daily tracking captures interruptions in the moment, connects them to specific wastes, and deploys improvements the next morning. The feedback loop runs daily instead of weekly, which is fast enough to actually change behavior.

What do you do with the lean improvement videos once they’re created?

Share them immediately with other crews to prevent the same waste from happening elsewhere. Build a library organized by waste type so people can learn from past improvements. Use them in morning huddles to deploy training. Make them searchable and accessible so any crew facing similar problems can see how others solved them.

Can this work if you’re only a trade partner on someone else’s project?

Absolutely. Start with your own crews regardless of project structure. Track your interruptions, identify your waste, plan your improvements, deploy your training. The system works at crew level, company level, or project level. You don’t need the GC’s permission to improve your own processes and remove your own waste.

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

Lean Beliefs

Posted on by Danny Jiménez⁩
Read 27 min

The Lean Beliefs That Make or Break Projects: Why Your Team Needs to Get on the Same Page Before Starting

Your superintendent schedules work to keep every piece of equipment running. Your project manager batches submittals to maximize office efficiency. Your trade partners load crews to maintain utilization. Everyone thinks they’re being lean. Everyone’s working hard. Everyone’s optimized their own piece. And the project is hemorrhaging money because nobody’s on the same page about what lean actually means.

Here’s what happens when teams aren’t aligned on fundamental beliefs. One person prioritizes resource efficiency while another prioritizes flow efficiency. One person thinks waste means idle equipment while another thinks waste means interrupted work. One person batches tasks for individual efficiency while another pushes for one-piece flow. Everyone uses the same words but means completely different things. The result? Chaos disguised as productivity. Systems working against each other. Money lost in the gaps between misaligned beliefs. Projects that look busy but don’t flow.

The Problem No One Wants to Name

Walk into any project meeting and listen to the conflicts that never get resolved. The superintendent wants to start work everywhere to keep crews busy. The scheduling consultant wants to limit work in progress. The trade partner wants to deliver all materials at once for efficiency. The lean advisor wants just-in-time delivery. Everyone argues. Nobody wins. The project suffers.

This isn’t about disagreement on strategy. This is about fundamental misalignment on what principles govern success. When your team doesn’t share core beliefs about flow, waste, respect for people, and how systems actually work, every decision becomes a battle. Every conversation rehashes the same arguments. Every improvement attempt gets sabotaged by someone operating from completely different assumptions.

Most teams never establish shared beliefs. They assume everyone understands lean the same way. They jump straight into tools and tactics without aligning on principles. Then they wonder why Last Planner doesn’t work. Why Takt planning creates conflict. Why continuous improvement stalls. Why the culture never shifts. The tools fail because the beliefs aren’t aligned. The system fails because people are operating from contradictory assumptions about how construction actually works.

The Field Reality: When Beliefs Collide

I recently worked with a team preparing to implement an integrated production control system. Before we started, I asked them to define lean. The answers revealed everything wrong with their approach. One superintendent said lean means keeping everyone working all the time, no idle resources, maximum utilization. A project manager said lean means eliminating waste by batching similar tasks together for efficiency. A trade partner said lean means delivering materials in bulk to minimize transportation costs. The owner’s rep said lean means finishing faster by working overtime when needed.

Every single answer was wrong. Or more accurately, every answer optimized one piece while destroying the whole. The superintendent’s focus on resource utilization would create work in progress everywhere. The project manager’s batching would delay information flow to workers. The trade partner’s bulk delivery would pile materials on site creating congestion. The owner’s overtime push would reduce productivity while inflating costs.

They weren’t aligned. They couldn’t be successful until they got on the same page about what principles actually govern construction productivity. About what flow means. About what waste looks like. About how systems work. About what respect for people requires.

Why Misaligned Beliefs Destroy Projects

When teams operate from different fundamental beliefs, the damage compounds in ways most people never track. Decisions that seem locally optimal destroy global flow. Systems designed for resource efficiency interrupt flow efficiency. Waste gets created in one area while being eliminated in another. Improvements in one department create problems in three others.

Think about how this plays out practically. If half your team believes keeping equipment busy is the priority, they’ll schedule work to maximize utilization. If the other half believes flow is the priority, they’ll limit work in progress and sequence carefully. These approaches are incompatible. One creates chaos the other is trying to prevent.

Or consider beliefs about waste. If someone thinks waste means idle time, they’ll push crews to stay busy even when work isn’t made ready. If someone else thinks waste means interruptions to flow, they’ll accept idle time to maintain proper sequence. The first person sees the second as inefficient. The second sees the first as destructive. Neither can succeed because they’re optimizing for contradictory outcomes.

The same pattern repeats everywhere. Beliefs about just-in-time delivery versus bulk ordering. Beliefs about batching versus one-piece flow. Beliefs about holding start dates versus advancing wherever possible. Beliefs about quality at the source versus pushing work down the line. Every misalignment creates conflict, waste, and lost margin.

Signals Your Team Isn’t Aligned on Lean Beliefs

Watch for these patterns that indicate fundamental misalignment:

  • Team members use the same lean terminology but argue constantly about what it means in practice, revealing they’re operating from completely different definitions of core concepts
  • Improvement efforts stall because half the team thinks the problem is one thing while the other half thinks it’s something else, and nobody realizes they’re not even diagnosing the same issue
  • Tools like Last Planner or Takt planning get implemented but create more conflict than clarity because people are using the tools to optimize contradictory outcomes based on misaligned beliefs
  • Meetings rehash the same arguments repeatedly without resolution because the real conflict is about unstated fundamental beliefs, not the surface-level decisions being discussed

The Framework: Core Beliefs That Must Align

Before implementing any lean system, your team must align on fundamental principles. Flow is the single most important condition we strive for in construction. Not busyness. Not utilization. Flow. It’s the path to increasing profits, employee satisfaction, customer delight, and reduced durations. Everything else serves flow.

Resource efficiency versus flow efficiency must be understood clearly. Resource efficiency maximizes the use of individual resources and attaches work to people, equipment, and crews. Flow efficiency focuses on the flow of work to the customer and attaches resources to flow units. We attempt both, but we always prioritize flow efficiency. This isn’t negotiable. This is the foundational choice that determines everything else.

Waste, overburden, and unevenness must be recognized as the enemies of flow. The eight wastes are overproduction, excess inventory, transportation, motion, defects, over processing, waiting, and not using the wisdom of the team. Overproduction and inventory are the mother and father of all other wastes. When we overproduce, we create inventory that must be transported, creating motion, causing defects, requiring over-processing, and generating waiting. Overburden happens when workers work too fast or systems are overutilized. Unevenness is variation that causes waste. All three destroy flow and must be eliminated.

The place of work governs where we focus. We don’t manage from reports at a distance. We observe at the place of work, close to the work, where people can see what winning looks like. Visual management makes problems visible so teams can see, know, and act together. Without this, continuous improvement becomes theoretical instead of practical.

Buffers are required for reality. We never plan for one hundred percent efficiency with materials, capacity, or time. Material buffers prevent waiting without creating excessive inventory. Capacity buffers acknowledge that equipment, workers, and systems need margin because things break down. Time buffers account for supply chain interruptions, weather, and adverse conditions. Without buffers, teams work in frenzied mode creating waste, pushing creates increases in manpower and material inventory, and profits decrease while costs increase.

One-piece flow and limiting work in progress are non-negotiable. Workers finish one piece or phase at a time from beginning to end instead of in batches. Flow units move from step to step on the shortest path to customers. The more work in progress, the more capacity gets consumed, so we always limit work in progress and finish as we go. Holding start dates, especially when multiple trades work in sequence, ensures just-in-time deliveries, encourages one-piece flow, and reduces work in progress.

Quality at the source means we notice defects, stop the work, correct the problem, and retrain crews before proceeding. We do not push bad work down the line. We fix things as we go. Pull means work and workers get pulled behind the preceding process once complete and done with quality. When pull doesn’t happen, crews get pushed on top of each other, slowing production and causing safety and quality defects.

Respect for people and resources governs everything. Everything we do must align with the highest standards of respect for people and respect for resources. We cannot be wasteful simply because we live in an economy of abundance. The definition of lean in construction is: respect for people and resources, stable environments with flow in a culture that sees and fixes problems, total participation with visual systems, and continuous improvement with fanatical quality. If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow.

The Practical Path Forward

Start by establishing shared language. Before implementing any system or tool, gather your team and define core terms together. What does flow mean? What is waste? What’s the difference between resource efficiency and flow efficiency? What does respect for people require? Get everyone aligned on definitions before moving forward.

Test beliefs through scenario discussion. Present common project situations and ask how the team would respond. If answers reveal misalignment on fundamentals, address it directly. Don’t move forward until beliefs align. The time spent establishing shared understanding prevents months of conflict later.

Teach principles before tools. Don’t jump to Takt planning or Last Planner without first teaching why flow matters, what waste looks like, how buffers work, why one-piece flow beats batching. Tools only work when people understand the principles the tools serve. Otherwise they use the tools to optimize the wrong things.

Make beliefs visible and reinforce them constantly. Post core principles in the trailer. Reference them in meetings. Use them to resolve disagreements. When someone wants to batch for efficiency, remind them we prioritize flow efficiency. When someone wants to keep equipment busy, remind them we attach resources to work, not work to resources. Constant reinforcement prevents drift.

Hold people accountable to shared beliefs. Lean cultures don’t succeed without accountability, sometimes radical accountability. If someone consistently acts against agreed-upon principles, address it directly. There can be no tolerance of dissension from systems that respect people and resources. Either get aligned or get out.

Why This Matters Beyond One Project

We’re not just building projects. We’re building cultures that either respect people and create flow or burn people out and create chaos. When teams align on lean beliefs, they create systems where workers succeed, families stay intact, and companies thrive. When teams stay misaligned, they create systems where heroic effort is required just to achieve mediocrity.

The construction industry is facing a gift disguised as a crisis. We don’t have enough workers. We don’t have unlimited resources. Inflation forces efficiency. Material constraints require better planning. This forces us to respect people and resources the way Japan had to on an island with limited resources and workers paid fifty-four times what they’re paid in China.

Companies that align on lean beliefs and implement systems based on flow will thrive. Companies that keep blaming people instead of fixing processes will fail. This isn’t theoretical. This is survival. The constraints are here. The question is whether you’ll respond by getting your team aligned on what actually works or keep fighting internal battles based on misaligned beliefs.

The Challenge in Front of You

You can keep assuming everyone on your team understands lean the same way. You can keep implementing tools without aligning on principles. You can keep having the same arguments without resolving the underlying belief conflicts. You can keep losing money in the gaps between misaligned understanding.

Or you can get your team on the same page. You can establish shared beliefs about flow, waste, respect, buffers, and how systems actually work. You can teach principles before deploying tools. You can create alignment that turns your team into a unified force instead of a collection of people working at cross-purposes.

The projects that succeed aren’t the ones with the best tools. They’re the ones where everyone shares core beliefs about what matters and why. Where flow is the priority everyone agrees on. Where waste is defined the same way by everyone. Where respect for people means the same thing to the superintendent and the project manager and the trade partner.

Perfect is easy. Good is hard. Mediocre is hard and destructive. Bad goes out of business. Although not always attainable in human systems, we strive for perfection and never settle. It’s the easiest way to run a project because you achieve self-sustaining systems.

Jeffrey Liker’s fourteen principles from The Toyota Way apply directly to construction. Base decisions on long-term philosophy. Create continuous process flow. Use pull systems. Level out workload. Build a culture of stopping to fix problems. Standardize as foundation for improvement. Use visual control. Grow leaders who understand the work. Develop exceptional people and teams. Respect partners and suppliers. Go and see for yourself. Make decisions slowly by consensus, implement rapidly. Become a learning organization through relentless reflection and continuous improvement.

These aren’t slogans. These are the beliefs that must align before any system can succeed. Get your team on the same page. Then watch what becomes possible. On we go.

Frequently Asked Questions

What’s the most common misalignment about lean beliefs?

Resource efficiency versus flow efficiency. Half the team optimizes individual resource utilization and keeps everyone busy, while the other half optimizes flow and accepts some idle time to maintain sequence. These approaches are incompatible and create constant conflict until teams align on prioritizing flow efficiency.

How do you get a team aligned on lean beliefs when people have different backgrounds?

Start with definitions before tools. Gather the team and define core terms together: flow, waste, respect, buffers, one-piece flow. Present scenarios and discuss responses. Address misalignment directly before moving forward. The time spent establishing shared understanding prevents months of conflict later.

What if someone on the team refuses to align with lean beliefs?

Hold them accountable with radical clarity. Lean cultures don’t succeed without accountability. If someone consistently acts against agreed-upon principles after clear teaching and discussion, address it directly. There can be no tolerance of dissension from systems that respect people and resources. Either align or exit.

Can you implement lean tools without first aligning on beliefs?

No. Tools fail when people use them to optimize contradictory outcomes based on misaligned beliefs. Last Planner fails when people batch for efficiency. Takt fails when people prioritize resource utilization over flow. Teach principles first, then tools work because everyone understands what the tools serve.

How do you know when your team is truly aligned on lean beliefs?

Decisions become faster and clearer because everyone operates from shared principles. Arguments shift from what to do to how to implement what everyone agrees matters. People self-correct when they catch themselves acting against shared beliefs. The culture reinforces alignment without constant supervision.

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

Flow Efficiency

Posted on by Danny Jiménez⁩
Read 29 min

Resource Efficiency vs. Flow Efficiency: Why Keeping Equipment Busy Is Destroying Your Schedule

Walk any construction site and ask the superintendent how things are going. You’ll hear the same answer everywhere. “We’re good. Equipment’s running. Crews are working. Everyone’s busy.” Then ask when the work will be finished. When the customer can take occupancy. When the flow unit will actually reach completion. And suddenly the answer gets vague. Maybe three weeks. Could be six. Depends on a lot of things.

Here’s what’s happening. The superintendent optimized resource efficiency. He made sure every piece of equipment stayed busy. Every crew had work. Every department was loaded. Individual resources are operating at maximum utilization. But the work isn’t flowing. Materials pile up between operations. Crews wait for handoffs. Areas sit incomplete while everyone moves on to keep busy. The project looks productive but nothing’s actually finishing. You optimized the wrong thing.

The Problem Hiding Behind All the Busyness

Here’s the pattern on most projects. A superintendent looks at idle equipment and thinks “waste.” He sees a crew without work and thinks “inefficiency.” He notices a department with downtime and thinks “poor utilization.” So he loads them up. He keeps everyone busy. He optimizes resource efficiency. And work slows down. Because keeping individual resources busy isn’t the same as getting work to flow. In fact, they’re often opposites. When you optimize resource efficiency, you create inventory between operations. You create waiting. You create handoffs. You create complexity. All of which slow down the flow of work from start to finish.

Think about Ford versus Toyota. Ford used to keep assembly lines running at maximum capacity, producing cars whether customers ordered them or not. Keep the equipment busy. Maximize resource utilization. The result? Massive inventory. Storage costs. Defects. Overproduction. Transportation waste. All because they optimized individual resource efficiency instead of flow efficiency.

Toyota said we have limited space, limited money, limited resources. We can’t waste anything. So if we get an order for three hundred seventy-five cars, we’ll produce four hundred, switch the tools, and make something else. We’ll reduce changeover times. We’ll only produce what the customer wants when they want it. We won’t keep equipment busy for the sake of being busy. We’ll attach people and resources to work that needs to flow, not attach work to people to keep them busy.

The System That Trains Us to Optimize the Wrong Thing

This isn’t about lazy superintendents or bad decisions. This is about an industry that measures the wrong metrics and rewards the wrong behaviors. Construction culture celebrates utilization. The superintendent who keeps every crew working. The project manager who loads every department. The company that bills maximum hours. We measure resource efficiency obsessively and barely track flow efficiency at all. So people do what gets measured. They optimize individual resource utilization. They keep equipment running. They batch work to maximize crew efficiency. They level workload within departments instead of leveling flow across the entire system.

And work piles up. Between the grading crew and the pipe crew. Between the architect’s review and the supplier’s fabrication. Between submittal approval and material delivery. Between overhead rough-in and wall framing. Everywhere you look, work in process accumulates because everyone optimized their own individual efficiency instead of optimizing the flow of work through the entire system. The system failed them. It didn’t fail the workers.

A Story That Reveals the Difference

I worked with a civil contractor in Jacksonville, Florida, that has some of the most advanced business systems in construction. They measure everything. They support field workers extensively. They’re deep into their lean journey. A team recently told me they were having trouble on a project. They just felt like work wasn’t flowing. So they all stood outside and watched the work. They took videos. They did a flow analysis. They got the team working together to make sure work was actually flowing instead of just keeping resources busy. They quadrupled their production.

Not by adding more equipment. Not by increasing crew sizes. Not by working longer hours. By optimizing flow instead of optimizing individual resource utilization. By attaching people to work that needed to flow instead of attaching work to people to keep them busy. They sent the results back to corporate with their production numbers. The president said “This is exactly what we need.” Because seeing flow, actually watching whether work is moving through the system efficiently, is what changes everything.

Why This Matters More Than Equipment Utilization

When you optimize resource efficiency over flow efficiency, work gets stuck everywhere. Think about submittals. Most projects treat the submittal process as a series of individual departments each optimizing their own efficiency instead of a flow that needs to move quickly to get information to workers.

The trade partner batches all submittals and sends them at once because that’s efficient for their detailer. The general contractor queues them up according to when it’s convenient for the project engineer to review them. The architect prioritizes them based on their own workload instead of when workers need the information. The supplier processes them according to their production schedule. Every department optimizes its own individual efficiency. And the submittal sits for weeks. The information doesn’t reach the worker when needed. The material doesn’t arrive in time. Work stops waiting for approvals that are stuck in queues designed for resource efficiency, not flow efficiency.

Now imagine the same submittal process optimized for flow. Don’t batch all submittals at once. Send them one package at a time according to when workers need them in sequence. Don’t queue them for review when convenient. Swarm them when they arrive so they move through quickly. Don’t wait weeks for architect review. Invite them to tabletop reviews or virtual sessions to turn them around in real time. Don’t let them sit in supplier queues. Track them and push them through. The second approach might feel less efficient for individual departments. The detailer can’t batch everything. The project engineer might have uneven workload. The architect has to coordinate schedules. But the submittal flows to the worker faster. The information arrives when needed. Work doesn’t stop waiting. That’s flow efficiency.

Signs Your Project Is Optimizing the Wrong Thing

Watch for these symptoms that you’re prioritizing resource efficiency over flow efficiency:

  • Equipment stays busy grading entire sites or working everywhere at once, but areas sit incomplete for weeks waiting for the next trade to start because work in process accumulated instead of flowing
  • Crews jump between multiple areas to stay utilized, but nothing finishes completely because everyone’s optimizing individual efficiency instead of completing flow units
  • Submittals batch in large packages to maximize detailer efficiency, then sit in queues for weeks because every department optimized its own workload instead of information flow to workers
  • Project teams level workload within offices to keep everyone equally busy, but RFIs and procurement requests stack up waiting for review because internal efficiency destroyed external flow
  • Materials arrive in bulk orders to maximize delivery efficiency, then pile up on site creating congestion and damage because supplier scheduling ignored installation sequence

The Framework: What Flow Efficiency Actually Means

Flow efficiency means optimizing how fast work moves from start to finish through the entire system. Resource efficiency means optimizing how busy individual resources stay. You want both, but when you have to choose, flow efficiency wins.

Here’s why. In the book The Goal, a factory has equipment operating at full individual efficiency. But it creates bottlenecks because it’s overproducing inventory between machines. When they stop focusing on keeping every machine maximally utilized and start focusing on flow through the entire system, production increases dramatically. They slow down some machines to match the bottleneck. They reduce work in process. They optimize the whole instead of the parts.

Construction works the same way. When a contractor says “I want to order, deliver, and install all the ductwork at once because that’s efficient for my crew,” they’re optimizing resource efficiency. They’re not worried about burying other trades under materials. They’re not worried about creating work in process. They’re not worried about flow through the entire building. They’re keeping their crew and equipment busy.

When that same contractor says “How can I sequence my work to optimize flow for the entire project?” they’re thinking differently. Maybe that means delivering materials just-in-time in smaller batches. Maybe that means smaller crew sizes working in sequence instead of large crews working everywhere at once. Maybe that means coordinating with other trades to maintain flow even if it creates slight inefficiency for individual resources.

The Japanese principle is clear: don’t attach work to people, attach people to work. Don’t load up resources to keep them busy. Focus resources on work that needs to flow. Everything should flow to the worker.

Practical Examples of Prioritizing Flow Over Resource Efficiency

Think about how this plays out on actual projects. A grading contractor has sixteen pieces of equipment and wants to keep them all running. So they grade the entire five-hundred-acre site at once to maximize equipment utilization. Resource efficiency looks great.

But now you’re maintaining five hundred acres. Running water trucks across massive areas. Managing SWPPP everywhere. Regrading damaged pads. Dealing with rain exposure. You created work in process everywhere instead of focusing equipment on the areas where pipe installation is ready to start. You optimized resource efficiency and destroyed flow efficiency.

Or think about project management teams. The project manager levels workload within the office, making sure all engineers stay equally busy. Resource efficiency within the department looks optimized. But submittals sit in queues. RFIs wait for review. Procurement gets delayed. Information doesn’t flow to workers when needed because the office optimized its own efficiency instead of optimizing flow to the field.

The shift is simple. Instead of asking “Is this equipment busy?” ask “Is work flowing to completion?” Instead of “Are my crews fully utilized?” ask “Is the flow unit moving through the system efficiently?” Instead of “Is my department loaded evenly?” ask “Is information reaching workers when they need it?”

Takt planning lets you see both resource efficiency and flow efficiency simultaneously. You can watch work flow through areas while also seeing how crews flow from area to area. But even with Takt, you prioritize flow efficiency. If you have to choose between keeping a crew busy in the wrong area or accepting slight downtime to maintain proper flow sequence, you choose flow.

The Paradigm Shift: Everything Flows to the Worker

Here’s the fundamental shift in thinking. Right now, most people focus on their own area of responsibility and optimize efficiency within that silo. Superintendents optimize their field operations. Project engineers optimize their office workflow. Trade partners optimize their crew utilization. Equipment operators maximize machine time. Everyone optimizes locally. Nobody optimizes globally. And work gets stuck at every handoff because the handoffs weren’t designed for flow. They were designed for individual resource efficiency.

The new paradigm is everything should flow to the worker. Not to the department. Not to the equipment. To the worker at the point of production who actually installs the work. Every decision gets filtered through: does this help work flow to that worker faster with higher quality? If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow.

This changes how you think about everything. Layout doesn’t optimize the surveyor’s efficiency. It flows to workers when they need it. Quality information doesn’t optimize the engineer’s schedule. It flows to crews before work starts. Materials don’t optimize the supplier’s delivery routes. They arrive just-in-time to support installation flow. Safety briefs don’t optimize the superintendent’s meeting schedule. They happen when and where workers need the information.

You can’t manage fifty flow units simultaneously. But you can focus on what’s starting in the next two to six weeks and make sure layout, information, quality processes, safety protocols, materials, workers, and equipment all flow to those starting scopes without interruption. That’s why Last Planner’s six-week make-ready and weekly work planning is genius. That’s why Takt planning works. They’re designed for flow efficiency first, resource efficiency second.

The Decision in Front of You

You can keep measuring equipment utilization, crew hours worked, and department loading. You can keep optimizing how busy individual resources stay. You can keep attaching work to people to prevent idle time. You can keep batching tasks for individual efficiency.

Or you can start measuring flow. How fast work moves from start to finish. How quickly information reaches workers. How efficiently materials arrive when needed. How smoothly handoffs happen between operations. How short the timeline is from raw material to installed work.

The projects that finish fast aren’t the ones with the highest resource utilization. They’re the ones with the best flow efficiency. They attach people to work instead of work to people. They optimize the whole instead of the parts. They watch work flow and remove anything that interrupts it.

The Shifts Required to Prioritize Flow

Making this transition requires changing how you think about several key areas:

  • Stop batching submittals to maximize detailer efficiency and start sending packages one at a time according to when workers need information in sequence, even if it means the detailer has uneven workload
  • Stop grading entire sites to keep equipment running and start grading just ahead of installation to reduce work in process, even if it means some equipment sits idle between phases
  • Stop leveling workload evenly within office departments and start swarming critical path items to push them through quickly, even if it creates temporary uneven loading across project engineers
  • Stop optimizing delivery routes for supplier efficiency and start delivering materials just-in-time to match installation sequence, even if it means more frequent smaller deliveries with higher per-unit transport costs

Nicholas Modic teaches this brilliantly in This Is Lean. Read that book. Watch his YouTube videos. Understand that everything you’ve been taught about maximizing resource utilization might be slowing you down. The goal isn’t keeping equipment busy. It’s getting work to flow.

Like juggling. A professional juggler doesn’t focus on all six balls at once. They focus on the ones in their hands and make sure handoffs are perfect. The balls in the air are self-sustaining because the transitions were managed well. Same with construction. You focus on work starting in the next short interval and make sure handoffs are clean. The work already flowing takes care of itself if you designed the system for flow.

Buy a red car and suddenly you see red cars everywhere. Learn about flow and suddenly you see every place it’s missing. Stop measuring busyness. Start measuring flow. Attach people to work, not work to people. Optimize the whole, not the parts. On we go.

Frequently Asked Questions

What’s the difference between resource efficiency and flow efficiency?

Resource efficiency optimizes how busy individual resources stay, like keeping equipment running or crews fully loaded. Flow efficiency optimizes how fast work moves through the entire system from start to finish. You want both, but flow efficiency takes priority because keeping resources busy while work sits stalled destroys schedules and costs.

How do you measure flow efficiency on a construction project?

Track how long it takes work to move from initiation to completion through the entire system. For submittals, measure days from package sent to information in workers’ hands. For materials, measure days from order to jobsite delivery. For areas, measure time from make-ready complete to work fully installed and inspected. Shorter timelines with less waiting mean better flow.

What’s an example of prioritizing resource efficiency destroying flow?

A grading contractor keeping sixteen machines busy by grading an entire five-hundred-acre site at once instead of grading just ahead of pipe installation. Equipment utilization looks great, but you’re maintaining massive areas, regrading damaged pads, managing SWPPP everywhere, and creating work in process instead of flow.

How does Takt planning help balance resource and flow efficiency?

Takt lets you see work flowing through areas left to right and crews flowing from area to area top to bottom. You can optimize both simultaneously, but Takt is designed to prioritize flow, so if crew utilization requires breaking flow sequence, you maintain sequence and accept slight resource inefficiency.

What’s the practical first step to shift from resource to flow focus?

Stop asking “Is this resource busy?” and start asking “Is work flowing to completion?” Watch work move through the system. Do a flow analysis like the Jacksonville team: stand outside, observe, take videos, identify where work stalls. Then remove those stalls even if it means accepting slight resource downtime to maintain flow.

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 Truth about Overtime

Posted on by Danny Jiménez⁩
Read 29 min

The Overtime Illusion: Why Working More Hours Delivers Less Work (And Costs You More)

Your project is behind. The owner is pushing. The schedule is slipping. So you do what every superintendent has done since construction began. You add hours. You schedule Saturday work. You push crews to sixty-hour weeks. You tell yourself it’s temporary, just until you catch up. You convince the team it’s necessary. You absorb the overtime costs because getting back on schedule is worth it.

And three months later, you’re further behind than when you started. Your costs have doubled. Your crews are exhausted. Quality is slipping. Safety incidents are up. And you have no idea what went wrong. Here’s what went wrong. Overtime doesn’t work the way you think it does.

The Problem Every Project Manager Faces

Walk any project that’s behind schedule and you’ll see the same solution being deployed. Crews working ten-hour days. Saturday shifts. Seven-day weeks. Superintendents convinced that more hours equals more production. Project managers approving overtime costs without questioning whether they’re actually getting return on investment.

Everyone knows overtime is expensive. The premium pay, the burden, the inefficiencies. But they justify it with simple math: if we work sixty hours instead of forty, we get fifty percent more production. If we work seven days instead of five, we get forty percent more output. The math seems obvious. Except it’s completely wrong.

Here’s what actually happens. Productivity drops immediately when overtime starts. It drops sharply in the first week, recovers slightly in weeks two and three, then begins a steady decline that continues for months. By week six on sixty-hour weeks, your crews are operating at seventy-five percent capacity. By week twelve, sixty-two percent. You’re paying premium wages for crews producing less than two-thirds of their normal output.

The costs inflate exponentially. At sixty-five hours per week sustained over time, you end up paying roughly twice the original unit labor cost. Not just for the overtime hours. For all the hours. Because fatigue, absenteeism, injuries, and morale destruction affect the entire work week, not just the extra hours.

And here’s the part that destroys the justification for overtime entirely: when you work sixty-plus-hour weeks for more than two months, the cumulative effect of decreased productivity delays your completion date beyond what you could have achieved with the same crew size on a forty-hour week. You’re not catching up. You’re falling further behind. And you’re paying double to do it.

The System That Makes Overtime Feel Necessary

This isn’t about superintendents making bad decisions. This is about an industry that never taught them what overtime actually does to productivity, costs, and schedules. Construction culture treats overtime as the default recovery tool. Project behind? Add hours. Owner pushing? Work weekends. Schedule slipping? Tell crews they’re working sixty-hour weeks until we catch up. It’s the first tool everyone reaches for because it’s the only tool most people know.

Nobody questions it because the math seems intuitive. More hours should equal more work. And in the short term, the first week or two, it does. You see an initial spike in production. People feel like heroes grinding it out. The project looks busy. Progress seems to accelerate.

But that spike is temporary. And what comes after destroys any gains you made. Because humans don’t work like machines. You can’t just add twenty hours to the week and expect linear increases in output. Mental discipline runs out. Physical capacity depletes. Morale crumbles. The rider gets exhausted trying to push the elephant down a difficult path, and eventually both give up. The system failed them. It didn’t fail the workers.

What a 1980 Industry Report Reveals That Most People Ignore

There’s a construction industry cost-effectiveness task force report from November 1980 that lays this out with brutal clarity. Most people have never read it. The ones who have usually ignore it because admitting overtime doesn’t work means admitting they’ve been doing it wrong for decades. Here’s what the report found. Placing field construction operations on scheduled overtime disrupts the economy of the affected area, magnifies any apparent labor shortage, reduces labor productivity, and creates excessive inflation of construction labor costs without material benefit to the completion schedule.

Translation: overtime makes everything worse. It doesn’t just cost more. It attracts workers away from other projects, creating bidding wars that inflate wages across the entire area. It pulls in less-qualified permit workers to fill the gaps. It reduces productivity for everyone, not just the overtime crews. And it doesn’t actually improve your schedule.

The data on productivity decline is devastating. In an eight-hour day, a crew produces one hundred twenty pieces per hour. In a nine-hour day consistently, that drops to one hundred pieces per hour. For hours above eight per day and forty-eight per week, it takes three hours of work to produce two additional hours of output for light work. For heavy work, it takes two hours to produce one hour of additional output.

You’re working fifty percent more hours to get twenty-five percent more production. Or working one hundred percent more hours to get fifty percent more production. The math doesn’t work. It never worked. We just never calculated it correctly.

The Field Reality: What Happens When Crews Work Extended Hours

I learned this from a field director who was exceptional at concrete. He told me something I’d never heard before: you have to right-size the crews and work them the right hours. Some people say we need to go faster, let’s put eight people on that wall crew and work them overtime. He said no. Get five really good carpenters on that wall crew with the labor, get them working in a flow, work them forty-eight hours, and you’ll get better production than eight people at sixty hours.

He’d run massive projects and knew that you might need an overall influx in manpower across the project, but you have to right-size individual crews and work them the right hours. That was a game changer. Because it revealed what most people miss: bigger crews and more hours don’t solve productivity problems. Flow solves productivity problems.

The US military found the same thing. They discovered statistically that soldiers could walk fifty to one hundred percent farther in a day if they gave them a ten-minute break every hour. Not less breaks. More breaks. Because human capacity has limits, and pushing past those limits without recovery reduces total output.

Construction crews work the same way. When you schedule seven-day weeks, a study showed substantially higher productivity during the week following an off Sunday than the week following a work Sunday. Breaks increase capacity. Rest improves performance. The relentless grind destroys both.

Why This Destroys More Than Just Your Schedule

When overtime extends past a few weeks, the damage compounds in ways most people never track. Absenteeism increases. The longer the hours, the more scheduled work time gets lost through people not showing up. You thought you were getting sixty hours per person. You’re actually getting fifty-five because absenteeism ate the rest.

Injuries increase, not just in absolute numbers but in rate of incidents. More hours means more opportunities for accidents, but it also means more accidents per hour because fatigue impairs judgment and reaction time. Your safety record deteriorates. Your EMR climbs. Your insurance costs increase.

Quality suffers because tired people make mistakes. They misread drawings. They install things wrong. They skip steps. They don’t catch errors. The rework from quality problems created by fatigue often exceeds any production gains from the extra hours.

Morale collapses because people feel trapped in an endless grind with no relief in sight. The best workers leave for jobs with better work-life balance. You’re left with whoever’s desperate enough or unqualified enough to stay. Your crew quality degrades over time, further reducing productivity.

And costs inflate beyond the premium overtime wages. Unit labor costs balloon because you’re paying more per hour for less production per hour. At sixty-five hours per week sustained, you pay roughly twice the original unit labor cost. You’re not just paying overtime premium. You’re paying for dramatically reduced efficiency on all hours.

The Data on Return on Investment

Here’s what the 1980 report found about return on investment for overtime under average operations. Working sixty hours per week, there is no return on investment after six weeks. Working fifty to sixty hours per week, no return after seven and a half weeks. Working above forty hours per week, no return after nine weeks.

And those timeframes don’t mean overtime is fine until then. All the negative effects still happen within those periods. Productivity still drops. Costs still inflate. Injuries still increase. Absenteeism still climbs. The “no return” point just marks when even the desperate math trying to justify overtime completely falls apart.

At week six working sixty-hour weeks, crews are at seventy-five percent capacity. At week twelve, sixty-two percent capacity. You’re paying time-and-a-half wages for people producing less than two-thirds their normal output. The math doesn’t just fail. It inverts. You’re actively losing money and time.

And here’s the killer data point: where a work schedule of sixty or more hours per week is continued longer than about two months, the cumulative effect of decreased productivity causes a delay in the completion date beyond what could have been realized with the same crew size on a forty-hour week. Read that again. Extended overtime doesn’t catch you up. It pushes your completion date farther out than if you’d never worked overtime at all. You paid premium wages to finish later than you would have with standard hours.

Watch for These Signals You’re Destroying Value With Overtime

Your overtime strategy is backfiring when:

  • Productivity per hour is declining week over week even though crews are working more total hours
  • Absenteeism is increasing, with crews calling out more frequently as fatigue accumulates
  • Safety incidents are climbing, with more accidents per hour worked than during standard schedules
  • Quality problems and rework are increasing because tired crews are making mistakes they wouldn’t make fresh
  • Your best workers are leaving for jobs with better hours while less-qualified workers replace them

The Framework: When Overtime Might Be Necessary and How to Minimize Damage

There are limited situations where overtime may be unavoidable. Remote projects where workers are housed on-site and want to maximize earning time. Maintenance shutdowns where the window is fixed and work must compress. Specific short-duration pushes with clear endpoints.

But even in those cases, management actions can minimize the damage. Use additional shifts with different crews instead of extending hours for the same crews. This avoids the fatigue factor while adding capacity. Schedule periodic shutdowns for a Sunday or weekend to give crews recovery time. Even in seven-day schedules, the week following a day off shows substantially higher productivity than consecutive work weeks.

Employ travel or subsistence payments to attract qualified workers instead of relying on whoever’s desperate enough to work extreme hours. Right-size crews instead of just throwing bodies at problems. Five highly skilled carpenters in a flow at forty-eight hours will outproduce eight mediocre carpenters at sixty hours every single time.

Use breaks strategically. Ten-minute breaks every hour increase total daily output. Shorter days with more intensity beat longer days with declining performance. Design systems that create flow instead of relying on brute-force hours to overcome poor planning.

And most importantly, set clear endpoints for any overtime. Not “we’ll work overtime until we catch up.” That never ends. Specific timeframes: “We’re working fifty-hour weeks for the next four weeks to complete this phase, then returning to forty.” If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow.

The Practical Path Forward

Stop treating overtime as your primary recovery tool. Before scheduling extended hours, ask whether the problem is actually lack of hours or lack of flow. Most schedule problems stem from poor planning, inadequate make-ready, roadblock buildup, or chaotic sequences. Adding hours to broken systems just creates expensive chaos instead of cheap chaos. Fix the flow first. Remove roadblocks. Make work ready. Stabilize crew sizes. Create predictable sequences. Then assess whether you genuinely need more hours or whether flow solved the problem.

If you do need overtime, calculate the real cost. Not just the premium wages. The productivity loss across all hours. The increased absenteeism. The safety incidents. The quality rework. The morale destruction. The loss of good workers. When you calculate the true cost, overtime almost never pencils out beyond a few weeks.

Set strict time limits and stick to them. Four weeks maximum for extended overtime. Then mandatory return to standard schedules with recovery time. If four weeks of overtime didn’t solve the problem, more overtime won’t either. You need a different solution. Track productivity per hour, not just total hours worked. If productivity per hour is declining, overtime is destroying value regardless of total output. Stop immediately and find a different approach.

Why This Matters Beyond One Project

We’re not just building projects. We’re building people who build things. And when we grind crews into the ground with endless overtime that doesn’t even improve schedules, we’re destroying people for no benefit.

Extended overtime breaks families. Workers miss their kids’ lives. Marriages suffer. Health deteriorates. Mental capacity depletes. And they’re making that sacrifice for overtime that research proves doesn’t work. That’s not respect for people. That’s system failure.

The construction professionals who finish on time and on budget aren’t the ones working their crews eighty hours a week. They’re the ones who create flow, remove roadblocks, make work ready, and let crews operate at full capacity during standard hours. They protect their people while protecting their schedules.

The Decision in Front of You

You can keep using overtime as your default recovery tool. You can keep scheduling sixty-hour weeks and wondering why productivity keeps dropping. You can keep paying premium wages for reduced output and delayed completions. Or you can acknowledge what the data shows. Overtime destroys productivity. It inflates costs. It delays completions. It breaks people. And it doesn’t solve the problems you’re using it to fix.

Fix flow instead. Remove roadblocks instead. Make work ready instead. Right-size crews instead. Create systems that let people produce at full capacity during standard hours instead of grinding them down with extended hours that reduce capacity. The projects that finish on time aren’t the ones working the most hours. They’re the ones working the right hours with the right crews in the right flow.

The 1980 report was clear: placing field operations on scheduled overtime disrupts economies, magnifies labor shortages, reduces productivity, and creates excessive cost inflation without material benefit to completion schedules. That was true in 1980. It’s true today. It will be true tomorrow. Stop throwing money and hours at problems. Start creating flow. Your schedule, your budget, your people, and your families will thank you. On we go.

Frequently Asked Questions

What’s the maximum overtime duration before you start losing money?

Return on investment disappears at roughly six weeks for sixty-hour weeks, seven and a half weeks for fifty-hour weeks, and nine weeks for anything above forty hours. But all the negative effects (reduced productivity, increased injuries, higher absenteeism) happen throughout those periods, not just after them.

How much does productivity actually drop on extended overtime?

At week six on sixty-hour weeks, crews operate at seventy-five percent capacity. By week twelve, sixty-two percent. For hours above eight per day or forty-eight per week, it takes three hours of work to produce two hours of output for light work, two hours for one hour on heavy work.

What’s better: bigger crews at standard hours or smaller crews at overtime?

Smaller, highly skilled crews in flow at forty-eight hours consistently outproduce larger, less-qualified crews at sixty-plus hours. Right-sizing crews and creating flow beats throwing bodies and hours at problems every time.

When is overtime actually justified?

Limited situations: remote projects with on-site housing where workers want to maximize earnings, fixed-window maintenance shutdowns, short-duration pushes (under four weeks) with clear endpoints and recovery periods built in. But even these require management actions like additional shifts and periodic shutdowns to minimize damage.

What should you do instead of scheduling overtime to catch up?

Fix flow first. Remove roadblocks, make work ready, stabilize crew sizes, create predictable sequences. Most schedule problems stem from poor planning and broken systems, not insufficient hours. Adding hours to broken systems just creates expensive chaos instead of solving the underlying issues.

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

    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

    • Introduction to Takt Production System® principles
    • CPM vs TAKT comparison
    • Macro planning, zoning, and density analysis
    • Quantities and production rates
    • Hands-on application to participants’ projects with LeanTakt PM experts

    day2

    Norm Planning & Flow Optimization

    • Review and refinement of Day 1 work
    • Pull planning and sequence optimization
    • Work packaging for balanced flow
    • Project integration session with LeanTakt PM coaching

    day3

    Advanced Tools & Comparisons

    • Macro work packaging and example walkthrough
    • Calculator Norm for production optimization
    • Stacking comparison to avoid trade conflicts
    • Hands-on application to participants’ own schedules

    day4

    Buffers, Controls & Finalization

    • Review of Day 3 implementation
    • Buffer management strategies and placement
    • Takt control principles and steering methods
    • Project plan finalization with expert guidance

    day5

    Control Systems & Presentations

    • Takt steering, control systems, and real project examples
    • Participant project presentations with LeanTakt PM feedback
    • Wrap-up, feedback, and action planning for post-training implementation

    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

    • Intro to Camp
    • Set Expectations
    • Morning Routine
    • Plan Day
    • Explain "Why"
    • Teams Intros + Yells + Expectation
    • Focus, Physiology, Words + Yells
    • Blocks to Leadership
    • 50 Million
    • Biggest Thing
    • Choose Your Word
    • Marketing Exercise
    • Interview for the Project
    • PO Homework and Close the Day

    Outcomes

    • Understand how to get into a proper state to lead
    • Understand how to dig deep to find the confidence to lead
    • Team work and collaboration
    • Understand marketing
    • Understand how to interview for and win a project

    Day 2

    Agenda

    • Morning Routine
    • Day Planner
    • Plus & Delta
    • Macro Takt planning
    • Setup jobs + Signs + Logistics
    • Explain the IPCS™
    • Detailed logistics training
    • Team balance & health training

    Outcomes

    • Learn the IPCS™ understand how to integrate the entire project from start to finish with First Planners™ and Last Planners® through the Takt Production System®
    • Learn how to review a project
    • Learn advanced logistics
    • Learn team balance and health

    Day 3

    Agenda

    • Morning Routine
    • Day Planner
    • Plus & Delta
    • Review How Big Things Get Done
    • Review IPCSTM
    • Fix (Schedule, zone, logistics, trailer, org & procurement)
    • Fresh Eyes Meeting
    • Pre-Con Overview
    • TAKT SIMULATION
    • Recap and Review

    Outcomes

    • Understand why and how to plan
    • Understand the benefits of using a Takt production plan
    • Learn the steps to proper pre-con that sets the project up for success
    • Learn how to review a project in a Fresh Eyes Meeting
    • Learn flow from Takt planning

    Day 4

    Agenda

    • Morning Routine
    • Day Planner
    • Plus & Delta
    • Opposing Squares
    • Pull Plan
    • Takt Remaining
    • Norm Update
    • Re Zoning
    • Risks & Pre-Con Align
    • Meeting System
    • Problems
    • Recap

    Outcomes

    • Understand the Norm level Takt plan for weekly/daily planning
    • Benefits and outcomes of rezoning strategies
    • Using meetings to feed information through the system and to the Foremen

    Day 5

    Agenda

    • Morning Routine
    • Day Planner
    • Plus & Delta
    • Huddle I.D.S
    • Day Plan
    • Worker Huddle
    • Norm Update
    • Team Huddle
    • Lean Systems Recap
    • Feedback Exercise
    • Final & Close

    Outcomes

    • Know what information is needed and how to get it to the Workers
    • Better understand how to give feedback and why it’s crucial for everyone
    • How to problem solve as a team
    • Understand how all systems tie together
    • Know how the information gets all the way to the worker
    • Have perfect clarity on the individual’s personal organization planner