Contact us

Author: Danny Jiménez⁩

Total Participation – Why You Need the Whole Team!

Posted on by Danny Jiménez⁩
Read 32 min

The Culture Problem Nobody Can Solve With a Poster

Here’s the deal. A project culture is not built by a slogan on the wall. It is not built by an email. It is not built by a memo. It is not built because one project manager knows the plan, one superintendent knows the plan, or a small group of leaders talks about the plan in a meeting. Culture is built when everybody participates.

That is the concept of total participation. It means the people on the project are not just receiving instructions from leadership. They are seeing the system, learning the system, improving the system, and acting as part of the system. They know where the project is headed. They understand what the site expects. They see the standards. They participate in the huddles. They improve the work. They help protect the environment.

That is very different from a traditional construction project where a few people know the plan and everybody else is expected to magically follow it. If the project has 380 workers, then the question is not whether 12 people in the jobsite trailer know the plan. The question is whether all 380 people understand the plan and the culture well enough to act together. That is total participation.

The Real Construction Pain

The real pain is that most projects are misaligned by design. The project manager may understand the owner’s expectations. The superintendent may understand the schedule. The foremen may know pieces of the plan. The workers may know what they are supposed to do today. The newest laborer may know almost nothing about the culture, the plan, the safety expectations, the quality standard, or the reason behind the site rules. Then leaders wonder why the project feels inconsistent.

One crew protects the bathrooms. Another crew destroys them. One trade understands the logistics plan. Another parks in the wrong place. One foreman knows the staging area. Another crew blocks the walkway. One group follows the cleanup standard. Another group leaves materials scattered. One person sees waste and fixes it. Another person walks past it because nobody ever taught them what good looks like.

That is not a people problem. That is a participation problem. If only the leadership team knows the expectations, then the leadership team will spend the entire project policing behavior instead of building culture. And that is exhausting. It creates frustration. It creates blame. It creates inconsistency. It creates an environment where people are told what to do, but never really brought into the system.

The Failure Pattern

The failure pattern is simple. Leaders create a plan, but they do not scale the plan. They talk about culture, but they do not create daily mechanisms for culture. They want clean, safe, organized sites, but they do not teach the workers why cleanliness matters. They want respect for people, but they do not design bathrooms, lunch areas, huddles, signage, walkways, and communication systems that actually show respect. Then they get frustrated when people do not act as a group.

You cannot get total participation from a partial communication system. You cannot expect the field to follow a culture they do not see. You cannot expect workers to protect standards that have not been taught, reinforced, modeled, and rewarded. You cannot expect a project to flow when the majority of the people on site only know a fraction of the plan. That is the failure pattern. A few people know. A few people care. A few people push. A few people remind. And everybody else is expected to follow along without the visibility, proximity, training, or rhythm needed to truly participate.

The System Failed Them, Not the People

The system failed them; they didn’t fail the system. That matters because total participation must be built with respect, not blame. If workers are not participating, we should not start by assuming they do not care. We should ask whether the system invited them in.

Did they get oriented into the culture? Did they see the visual standards? Did they hear the message from leadership? Did they know why the bathrooms matter? Did they know why clean walkways matter? Did they know what the owner expects? Did they know what the schedule is? Did they know where to stage materials? Did they know where to park? Did they know how to identify waste? Did they know how to bring up improvements?

If the answer is no, then the system did not create participation. Respect for people means we do not expect people to guess. Respect for people means we create an environment where people can see, understand, and act. Respect for people means leaders make the plan visible and teach the culture repeatedly until the whole group begins to move together. That is not soft. That is how you build a winning site.

The Lesson From Paul Akers

Jason learned the concept of total participation from Paul Akers, especially through Paul’s teaching in Two Second Lean and Vanishing Sloppiness. Paul has a gift for taking Lean ideas and making them practical. He teaches respect for resources, respect for people, the eight wastes, 5S, morning huddles, before and after videos, and continuous improvement in a way that normal people can understand and use. But the power is not just in the tools. The power is in participation.

In Paul’s business, everybody participates. People clean bathrooms. People join teams. People participate in morning huddles. People take before and after videos of improvement ideas. People learn the language of waste. People improve the work. It is not a memo. It is not one department. It is not a side initiative. It is how work is done.

That is why the culture holds. Total participation means the culture is not optional. It is not something a few motivated people practice while everyone else watches. It is the operating system. If people participate, they become part of the team and part of the culture. If they refuse to participate, they do not fit that environment. Construction needs that same clarity, but applied with field reality, respect, and consistency.

A Field Story From the Bioscience Research Laboratory

Jason took this concept and decided to implement it on a construction project. At the Bioscience Research Laboratory, the team created a project environment built around visual systems and total participation. When a worker came to the site, the project told them what to do without requiring someone to explain every detail verbally.

There was signage showing the smoking area. There was signage showing the parking area. There were clear walkways. Gates were organized. Huddle areas were organized. Every floor had visual boards showing where valves were, what the schedule was, and where things should be staged. There were visual systems on the hoist. There were visuals throughout the site. That kind of environment sends a message.

It says, “We are organized here.” It says, “We respect your time here.” It says, “We care about safety here.” It says, “We want you to know what is happening here.” It says, “You are part of a system, not just a body on a project.” And one of the most powerful parts of that system was the morning worker huddle.

Not the foreman huddle. Not just the Last Planner daily huddle. A worker huddle. A real gathering of the workers on site where leadership talked directly to the people doing the work. Jason called those worker huddles one of the most impactful things he had ever done in his career. That is a big statement, and it makes sense. Because those huddles created proximity, connection, teaching, recognition, and alignment every single day.

Why Worker Huddles Matter

Worker huddles matter because they give the entire site a shared rhythm. They allow the project leadership to teach the plan, reinforce the culture, recognize good behavior, correct issues respectfully, and explain why the standards matter. In those huddles, the team taught what the owner expected. They explained why the site would be clean and safe. They talked about what went well yesterday. They talked about what needed improvement. They showed care for the workers. They talked about the bathrooms and why taking care of them mattered. They hosted barbecues. They provided food. They celebrated wins. They gave shout-outs. They created competitions. They rewarded participation.

That is culture creation. Culture is not just beliefs. Culture is shared beliefs and shared actions. If you want shared actions, you need repeated communication. If you want repeated communication to land, you need proximity. If you want proximity to create trust, leaders need to show respect. If you want trust to become culture, people need to participate. Worker huddles create the conditions for that to happen. Here are a few things worker huddles can reinforce when they are done well:

  • What the owner expects from the project
  • What the clean, safe, organized standard looks like
  • What went well yesterday and should be repeated
  • What needs improvement without blaming people
  • Why each worker matters to the success of the site

Those are not small things. Those are the daily inputs that create a project culture.

Total Participation Requires Visual Systems

Total participation does not happen through talking alone. It requires visual systems. People need to see the plan. They need to see the standard. They need to see where to go, what to do, what good looks like, and how the work is supposed to flow. Visual systems are one of the reasons Lean works. They remove guessing. They reduce friction. They make expectations clear. They allow people to self-correct. They make abnormal conditions easier to see. They help everyone on the site participate, not just the people who attended the planning meeting.

This is where a project begins to feel different. The parking is clear. The gates are clear. The walkways are clear. The hoist rules are clear. The staging areas are clear. The floor boards are clear. The schedule is visible. The logistics are visible. The rules are visible. The culture is visible. That visibility creates alignment.

If you want total participation, do not hide the plan in the trailer. Do not hide the logistics in a file. Do not hide the culture in leadership conversations. Put it where the workers can see it. Teach it where the workers can hear it. Reinforce it where the workers can act on it. That is how the site starts to move as one group.

The Role of Respect in Participation

Respect for people is not a slogan. It is a production strategy. If you want people to participate, they need to feel respected by the system. That means clean bathrooms. Real lunch areas. Organized walkways. Clear signage. Morning huddles. Good communication. Safe conditions. Proper staging. Time to set up the day. Recognition for good work. Training that helps people understand the system.

People are more willing to participate in a culture that first shows them dignity. At the Bioscience Research Laboratory, the team did things that showed workers they mattered. They provided food. They celebrated. They gave shout-outs. They paid for people to take time after the huddle to set up their day. They taught the eight wastes. They taught 5S. They used cards. They showed videos. They created connection.

That matters because participation cannot be forced by signs alone. You can enforce standards, and you should, but the best cultures combine respect and accountability. They teach first. They support first. They make the environment clear first. Then they hold the standard. That is stability before accountability.

From Knowing the Plan to Acting the Plan

Jason gives a useful way to think about total participation. Imagine a percentage graph. How much of the plan and culture does the project manager know? Maybe 80 percent or 90 percent. How much does the superintendent know? Maybe 90 percent or 100 percent. How much do the project engineers and field engineers know? Maybe 60 percent or 70 percent. How much do the foremen know? Maybe 50 percent. How much do the workers know? Maybe 10 percent, 15 percent, or 30 percent. That is the gap. Total participation is about increasing both the number of people who know the plan and the percentage of the plan they understand. It is also about creating systems that help people act according to that plan and culture.

Knowing is not enough. Acting matters. A worker may hear the standard once and forget it. A crew may understand the logistics plan but drift under pressure. A foreman may agree with the cleanup standard but fail to reinforce it. That is why the culture needs repeated teaching, visual reminders, kind accountability, and respect-based enforcement. The goal is not compliance through fear. The goal is alignment through clarity, training, repetition, and follow-through.

Practical Ways to Build Total Participation

Total participation starts with the decision that everyone on site matters. Not just the leadership team. Not just the foremen. Not just the trades with the biggest scope. Everyone. The newest worker pushing a broom should know the culture. The person unloading trucks should know the logistics plan. The person walking through the gate for the first time should know what the site values. That requires intentional design.

Start with orientation. Teach the project culture immediately. Explain the owner’s expectations. Explain the clean, safe, organized standard. Show people where things are. Show them what good looks like. Then reinforce that message daily through huddles and visuals. Create worker huddles that are short, useful, and consistent. Do not use them to lecture people. Use them to connect, teach, recognize, and align. Talk about what matters today. Talk about what the team did well. Talk about what needs to improve. Make the message practical.

Build visual systems throughout the project. Put the plan where people can see it. Put logistics where people need it. Put standards at the point of use. Make the site understandable to someone who just arrived. Then reward participation. Recognize improvement ideas. Celebrate crews who protect the standard. Give shout-outs. Share before and after examples. Let workers see that their participation matters. A few practical moves can change the culture fast:

  • Hold daily worker huddles with clear teaching and recognition
  • Use visual boards on every floor to show schedule, staging, and key information
  • Teach the eight wastes and 5S in simple field language
  • Give workers time to set up their day after the huddle
  • Recognize improvement ideas publicly and consistently

Those moves help the whole site see the same picture. And when people see the same picture, they can start acting as one group.

Total Participation and the Takt Production System

Total participation connects directly to flow. The Takt Production System depends on teams moving through zones with rhythm, clarity, and reliable handoffs. But Takt cannot be carried by the superintendent alone. It cannot be carried by the scheduler alone. It cannot be carried by a color-coded plan hanging in the trailer. The people doing the work need to understand the system.

They need to know the zones. They need to know the sequence. They need to know the rhythm. They need to know the handoff expectations. They need to know where to stage. They need to know what roadblocks to report. They need to know how their work affects the next crew. That is total participation in production control.

LeanTakt is not just about creating a beautiful plan. It is about creating a plan the field can see, understand, and follow. It is about creating flow with people, not around people. The more people understand the plan and culture, the more stable the flow becomes. That is why total participation is not just a culture concept. It is a scheduling concept. It is a safety concept. It is a quality concept. It is a flow concept.

Connect Back to the Mission

Elevate Construction exists to build remarkable people and systems that build the world. Total participation is one of the ways that mission becomes real on a jobsite. It brings people into the system. It teaches them. It respects them. It gives them visibility. It allows them to contribute. It helps the project move from a small leadership plan to a shared field culture. If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow.

That sentence belongs here because total participation is exactly how teams stabilize. When everyone can see the plan, the site becomes calmer. When everyone understands the culture, the standards become stronger. When everyone participates, the project becomes more predictable. When the project becomes more predictable, people go home with more dignity and less chaos. That is the point.

Conclusion: Everyone Needs to Know the Plan

So here is the challenge. Do not settle for a project where only the trailer knows the plan. Do not settle for a project where only the foremen understand the culture. Do not settle for a project where workers are expected to comply with standards they were never invited to understand. Build total participation.

Use huddles. Use visuals. Use teaching. Use recognition. Use respect. Use kind accountability. Use consistent standards. Create a site where everyone can see as a group, know as a group, and act as a group. Jason said it clearly: “See as a group, know as a group, act as a group.” That is the heart of total participation. When the whole site sees the plan, knows the culture, and acts together, the project changes. Plan it first, build it right, finish as you go.

On we go.

Frequently Asked Questions

What is total participation in construction?

Total participation means everyone on the project understands the plan, knows the culture, and participates in the systems that support safety, quality, flow, and improvement. It is not limited to leadership or foremen. It includes workers, lead persons, trade partners, and support roles.

Why are worker huddles important for total participation?

Worker huddles create daily alignment with the people doing the work. They allow leaders to teach expectations, recognize good behavior, correct issues respectfully, explain the plan, and build connection with the workforce.

How do visual systems support total participation?

Visual systems make expectations clear without relying on memory or word of mouth. Signage, floor boards, logistics maps, staging visuals, and schedule boards help everyone see what is expected and act consistently.

How does total participation improve flow?

Flow improves when more people understand the plan and culture. Workers can make better decisions, report roadblocks sooner, protect handoffs, follow logistics, and support the rhythm of the Takt Production System.

How can a project start building total participation?

Start with daily worker huddles, clear visual systems, strong orientation, simple Lean teaching, recognition of improvement ideas, and respect-based accountability. The goal is to bring everyone into the culture, not just communicate to the leadership team.

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.

CYA vs. Finding & Fixing Problems

Posted on by Danny Jiménez⁩
Read 30 min

The Problem We Need to Bring to the Surface

Here’s the deal. Every construction project has problems. Every project has roadblocks. Every project has constraints. Every project has things that are not ready, not clear, not coordinated, not installed correctly, not procured, not approved, not staffed, or not communicated.

That is not the problem. The problem is when people hide them. The problem is when the culture teaches people to protect themselves instead of protecting the project. The problem is when project managers, superintendents, project engineers, directors, executives, or anyone on the team spends more energy covering their own backside than finding and fixing what is blocking flow.

That is where projects get hurt. Not because someone found a problem. Not because a roadblock showed up. Not because reality happened. Projects get hurt when the team does not bring reality to the surface fast enough to do something about it. If we want flow, we need transparency. If we want trust, we need problems visible. If we want to protect the field, we need leaders who are obsessed with finding and fixing problems, not hiding them.

The Real Construction Pain

The pain is that too many teams are afraid of problems. They treat a problem like a personal failure. They treat a roadblock like a threat to their reputation. They treat a missed detail like something that must be buried, explained away, or covered with documentation so nobody can blame them later. And when that happens, the project loses.

The field keeps moving without the truth. The team keeps planning without the truth. Leaders make decisions without the truth. Trade partners get impacted by things that should have been surfaced earlier. Foremen inherit roadblocks they did not create. Workers lose flow because someone upstream was more focused on self-protection than system protection. That is not respect for people.

Respect for people means we tell the truth early. Respect for people means we make the work visible. Respect for people means we surface the ugly, the unclear, the late, the broken, the missing, and the risky before it damages the field. Respect for people means we do not let fear create silence. When a problem stays hidden, it grows. When a roadblock stays buried, it spreads. When a team avoids transparency, they trade short-term comfort for long-term chaos.

The Failure Pattern

The failure pattern is easy to spot. Someone says, “We have it under control,” but they cannot show the log. Someone says, “It is not a big deal,” but the field is about to be impacted. Someone says, “I am not sure I am allowed to share that,” when the team needs the information to make a decision. Someone keeps a private list, a private tracker, a private issue, a private risk, or a private problem because they do not want to look bad. That is CYA culture.

CYA culture says, “Protect yourself first.” Lean culture says, “Find the problem and fix the system.” Those two mindsets cannot live together for very long. One will eventually win. If CYA wins, the project becomes defensive. People stop telling the truth. Meetings become performances. Reports become polished versions of reality. The team wastes energy looking good instead of getting better. Problems show up late, usually when they are expensive, emotional, and harder to solve. If problem finding wins, the project becomes honest. People tell the truth early. Roadblocks are visible. Leaders can help. The team can adjust. The system can improve. Flow has a chance.

The System Failed Them, Not the People

The system failed them; they didn’t fail the system. That matters because this topic can get sharp quickly. It is easy to point at someone and say, “They are hiding things.” But Jason Schroeder’s lens is system-first. We do not start by attacking people. We start by asking what environment created the behavior.

Did the company punish people for surfacing bad news? Did leaders react emotionally when problems were brought forward? Did the project culture reward looking good more than telling the truth? Did people learn that transparency gets them in trouble? Did the team confuse accountability with punishment instead of clarity, training, and follow-through?

If people believe problems are a reflection of their worth, they will hide problems. If people believe roadblocks make them look weak, they will hide roadblocks. If people believe leadership wants polished reports instead of reality, they will polish the report. That is a system problem.

A healthy Lean system teaches the opposite. Problems are not shameful. Problems are gold. Problems are signals. Problems tell us where flow is breaking. Problems show us where training is missing, where planning was weak, where make-ready failed, where procurement is late, where logistics are unclear, or where a standard is missing. The only real problem is pretending there are no problems.

A Field Story About CYA

Jason was walking a construction site when someone said something that hit the mark. They wished project managers would worry more about finding and fixing problems than hiding problems and protecting themselves. That comment opened up the whole topic.

Because when you think about it, so much of construction energy gets wasted in CYA. People hide information. They hold back. They delay transparency. They do not want to share finances. They do not want to show the log. They do not want to admit the issue. They do not want help. They do not want the team to see what is really happening. And the sad part is that all of that energy could have gone toward solving the problem.

Imagine if the same effort used to hide a roadblock was used to remove it. Imagine if the same energy used to protect an image was used to protect flow. Imagine if the same time spent building backup excuses was spent building a better plan. That is the leadership shift we need.

We need builders who want the problems. We need leaders who say, “Give me the roadblock. Give me the ugly. Give me the issue. Give me the risk. Give me the thing that is blocking flow so we can solve it together.” That is not negative. That is Lean.

Why It Matters to Flow

Roadblocks are not just annoyances. They are flow blockers. They stop the train. They interrupt handoffs. They force crews into waiting, searching, stacking, rework, and workarounds. They take a beautiful plan and turn it into daily improvisation. In the Takt Production System, flow depends on stable movement through zones. Trades need the right information, materials, tools, equipment, layout, approvals, access, and decisions. If those are missing, the wagon cannot move cleanly. If the wagon cannot move cleanly, the train gets disrupted. If the train gets disrupted, the schedule starts absorbing chaos.

That is why roadblocks must come to the surface early. A roadblock is not something to hide. A roadblock is something to remove. A constraint is something to plan around. Mixing those up creates confusion, but hiding either one creates damage. LeanTakt, Last Planner System, Scrum boards, make-ready planning, daily huddles, and visual controls all exist to make reality visible. They are not paperwork systems. They are transparency systems. They allow the team to see as a group, know as a group, and act as a group. CYA destroys that.

The Real Cost of Hiding Problems

When a team hides problems, the cost is not only schedule. The cost is trust. The cost is safety. The cost is quality. The cost is morale. The cost is the emotional weight people carry home to their families. A hidden roadblock does not stay small. It grows downstream. Missing information becomes delayed work. Delayed work becomes stacking. Stacking becomes unsafe conditions. Unsafe conditions become stress. Stress becomes mistakes. Mistakes become rework. Rework becomes overtime. Overtime becomes burnout. And then people wonder why the project feels heavy. The project feels heavy because the truth is not flowing. Here are some signs that CYA culture is blocking flow:

  • People delay sharing bad news until it is unavoidable
  • Logs exist privately instead of visually with the team
  • Meetings sound positive, but the field feels chaotic
  • People spend more time explaining issues than solving them
  • Leaders react to problems with blame instead of curiosity

Those are not small signals. They are warnings. They show that the culture is not safe enough, clear enough, or disciplined enough to bring problems to the surface early.

The Lean Pattern: Find and Fix Problems

Lean, in Jason’s lens, is a people-first production system that makes work predictable by designing the environment, not by pushing people harder. It is built on respect for people, visual control, stable workflows, and continuous improvement. That means Lean is not hiding problems. Lean is finding them. One of the most practical ways to think about this is the simple rhythm of improvement. Learn to see waste. Organize your area. Make the work visible. Find what bugs you. Fix what bugs you. Then repeat. That sounds basic, but it is powerful.

When you organize a project visually, problems become easier to see. When you clean and stabilize the environment, abnormalities stand out. When the team can see roadblocks, they can remove them. When the team can see commitments, they can support them. When the team can see the plan, they can improve it. The goal is not to pretend the project is clean. The goal is to make the project honest. That is why transparency is not a soft value. Radical transparency is a production strategy. It allows teams to focus energy where it actually belongs.

Growth Mindset vs. Fixed Mindset

CYA culture is usually tied to a fixed mindset. A fixed mindset says, “If there is a problem, it means I failed.” A fixed mindset says, “If people see the issue, they will think less of me.” A fixed mindset says, “I need to protect my image.” That mindset will suffocate improvement.

A growth mindset says, “Every project has problems.” A growth mindset says, “Problems are the pathway to improvement.” A growth mindset says, “Bring it up early so we can solve it.” A growth mindset says, “This is not about looking perfect. This is about creating flow.” That is the mindset construction needs.

Great builders are not problem-free. Great builders are problem finders. Great builders are problem solvers. Great builders do not hide roadblocks. They hunt them. They pull them out into the open. They put them on a board. They assign ownership. They remove them. Then they improve the system so the same roadblock does not keep returning. That is professional construction leadership.

How Leaders Should Respond to Problems

If leaders want transparency, they must respond correctly when problems are surfaced. This is where culture is created. Not in the mission statement. Not in the poster. Not in the kickoff meeting. Culture is created in the moment someone brings bad news. If the leader reacts with blame, the team learns to hide. If the leader reacts with panic, the team learns to delay. If the leader reacts with sarcasm, the team learns to protect themselves. If the leader reacts with curiosity, clarity, and support, the team learns to surface problems early. That is leadership.

When someone brings a roadblock, the first response should be something like, “Thank you for bringing it up. What do we know? What do we need? Who can help? What is the next action?” That response teaches the team that problems are welcome because solutions are expected. We are not saying there are no standards. We are not saying people can be careless. We are saying stability must exist before accountability. Clarify expectations. Train people. Create the visual system. Follow through. Then hold the standard respectfully. That is how you build trust.

Practical Guidance for Teams

If you want to remove CYA from your project, start by making problems visible in a safe, structured way. Do not rely on side conversations, private notes, hidden logs, or memory. Put roadblocks where the team can see them. Talk about them daily. Assign owners. Track due dates. Follow up. Remove them before they hit the field.

This is where a Scrum board, roadblock log, make-ready process, and daily huddle become powerful. The goal is not to create more admin. The goal is to create visibility that protects flow. Here are practical moves that help shift the culture:

  • Ask for roadblocks before asking for progress
  • Thank people publicly when they surface problems early
  • Put roadblocks on a visible board with owners and dates
  • Separate problem finding from blame
  • Review repeat problems and fix the system behind them

That is how you teach the team what matters. You are saying, “We do not hide problems here. We find them. We fix them. We learn from them. We move forward.” That is the environment where people can win.

Stop Spending Energy Looking Good

Think about how much energy it takes to hide a problem. You have to manage the story. You have to control who knows. You have to delay the conversation. You have to protect the appearance. You have to create backup explanations. You have to remember what you said. You have to hope nobody finds out before you solve it. That is exhausting. Now imagine spending that energy on solving the problem instead. Bring it up. Name it. Put it on the board. Ask for help. Remove it. Learn from it. Move on. That is lighter. That is faster. That is healthier.

No one should have to be a hero to win. No one should have to hide reality to survive. No one should have to spend their day managing appearances instead of managing flow. If the culture requires people to look perfect, the culture is broken. A real production culture wants the truth.

Connect Back to the Mission

Elevate Construction exists to build remarkable people and systems that build the world. That cannot happen in a CYA culture. Remarkable systems require transparency. Remarkable people require trust. Flow requires honesty. Stability requires visible problems. If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow.

That sentence matters here because stabilization starts with truth. You cannot stabilize what you cannot see. You cannot schedule around what is hidden. You cannot create flow if roadblocks are buried under fear, ego, or self-protection. Construction becomes better when leaders create environments where people can tell the truth early and fix problems together. That protects the trades. That protects the customer. That protects the team. That protects families.

Conclusion: Bring the Problems Up

So here is the challenge. Stop rewarding CYA. Stop tolerating hidden roadblocks. Stop letting people spend their energy protecting appearances instead of protecting flow. Create a culture where problems are brought to the surface quickly, respectfully, and visually. Ask your team this week: “What are we hiding? What are we afraid to say? What problem do we already know about that needs to be on the board?”

Then respond well when they answer. Jason says it clearly: “Bring all problems to the surface.” That is the standard. Not because we love drama. Not because we want negativity. Because problems brought to the surface can be solved. Problems hidden in the dark will keep blocking flow. Find the problems. Fix the problems. Improve the system. Protect the people.

On we go.

Frequently Asked Questions

What does CYA culture mean in construction?

CYA culture means people spend their energy protecting themselves instead of surfacing and solving problems. It often shows up through hidden logs, delayed bad news, vague updates, and reluctance to share real risks with the team.

Why is hiding problems so damaging to flow?

Hidden problems become late problems. Late problems disrupt handoffs, create waiting, cause stacking, increase rework, and force crews into panic. Flow depends on visibility, so anything hidden becomes a threat to the production system.

How should leaders respond when someone brings up a problem?

Leaders should respond with calm curiosity and action. Thank the person for bringing it up, clarify what is known, identify what is needed, assign ownership, and remove the roadblock. The response should teach the team that truth is safe and solutions are expected.

Is surfacing problems the same as complaining?

No. Complaining circles around frustration without ownership. Surfacing problems names the roadblock, makes it visible, and moves toward action. The difference is whether the team is using the information to improve the system.

How can a project start reducing CYA behavior?

Start by making roadblocks visible in daily huddles and planning meetings. Use a shared board or log, assign owners, track due dates, and separate problem finding from blame. Over time, consistent respectful follow-through will build trust and transparency.

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.

Quality Control is a Flow System

Posted on by Danny Jiménez⁩
Read 31 min

The Schedule Problem Nobody Wants to Admit

Here’s the deal. Most people in construction do not really believe quality saves time. They say they do. They nod their heads when someone says, “Do it right the first time.” They have quality control plans. They have inspections. They have checklists. They have pre-install meetings written into the process somewhere. But when the project starts feeling pressure, when the schedule gets tight, when the owner is asking questions, and when the field starts getting nervous, quality is often treated like something that slows the job down.

That is the problem. We hear things like, “Just pour it.” “Just bury it.” “We do not have time for the mock-up.” “We will fix it later.” “We need to keep moving.” “We are behind schedule, so we cannot stop for a quality check.” And every time that happens, the project is not actually going faster. It is borrowing time from the future and creating a much bigger problem for the people who will have to fix it.

Quality is not a separate system from the schedule. Quality is not paperwork. Quality is not something the inspector does after the work is installed. Quality is a flow system. Let me say it another way. If you install it right the first time, you protect flow. If you skip quality and install it wrong, you destroy flow. That is the truth. And once a team really understands that, the way they look at schedule pressure changes forever.

The Real Construction Pain

The real pain is that projects often treat quality as a department instead of a production strategy. The schedule team is trying to go fast. The field team is trying to install. The quality team is trying to verify. The project management team is trying to document. And too often, those groups feel separated.

That separation creates waste. The field feels pressure to move. The quality team feels pressure to catch problems. The project team feels pressure to explain misses. Trade partners feel pressure to work around issues that should have been prevented. And then the project starts carrying rework, delays, stacking, frustration, inspections that fail, material waste, and stress that never should have existed.

This is not because workers do not care. This is not because foremen are trying to do poor work. This is not because trade partners want to rework things. The system did not protect them. The system did not make quality part of the flow. The system allowed speed to be defined as motion instead of right first time installation.

That is where construction hurts people. When crews are rushed, they get overburdened. When work is pushed without readiness, teams lose stability. When quality steps are skipped, the job does not become faster. It becomes fragile. And fragile systems always break at the worst time.

The Failure Pattern

The failure pattern is predictable. A team gets behind schedule, so they start cutting out the steps that would actually protect the schedule. They skip the pre-install meeting. They skip the mock-up. They skip the first-run study. They skip the quality conversation in the huddle. They skip the check before the pour, the check before the cover, the check before the install, the check before the handoff.

Then the work goes in wrong. Now the team has to stop. They have to investigate. They have to write an RFI. They have to remove installed work. They have to re-order material. They have to re-coordinate crews. They have to bring someone back. They have to re-inspect. They have to explain the delay. They have to absorb the cost. And then everyone stands around wondering how the project lost flow.

It lost flow because the system skipped the very steps that create flow. This is why the mindset has to change. When a project is behind, the answer is not to lower the quality standard. The answer is to strengthen the quality system so the work can move without stops and restarts. The faster you need to go, the more disciplined you must be with quality.

The System Failed Them, Not the People

The system failed them; they didn’t fail the system. That is important because quality conversations can get personal fast. Someone wants to know who installed it wrong. Someone wants to know who missed the check. Someone wants to know who approved the work. And before long, the room starts drifting toward blame. That is not the way Jason Schroeder teaches. That is not the way Elevate Construction looks at the field. We diagnose the system first.

Did the team have a pre-install meeting? Did the workers see the standard? Was there a mock-up? Was the first-run study completed? Did the foreman have the right information? Were the materials correct? Was the layout verified? Were the inspection requirements understood? Was the handoff clear? Was quality discussed before the work started, or only after it failed?

Those are system questions. Respect for people means we do not send crews into unclear work and then criticize them when the system breaks. Respect for people means we create the conditions for right first time installation. Respect for people means quality at the source, where the work is actually happening, not quality as an afterthought after the damage is already done.

A Takt Simulation That Proved the Point

Jason was doing a Takt simulation in Indianapolis with Spencer for a great company. They were using the 3D printed building model, and the first round was like a traditional push system. It took around 16 minutes. It was chaotic. It had the feel of a CPM-driven push environment where everyone is trying to move but the system is not really flowing.

Then they moved into a Takt system, and the time dropped to around 9, 10, or 11 minutes. That alone is a big deal. But then they leveled the work, optimized the Takt sequence, and used the math to improve the flow. The team got the simulation down to 4 minutes and 55 seconds.

That is a massive reduction in overall time. But the important lesson was not just that Takt made it faster. The important lesson was how they made it faster. In the third round, they used huddles between every Takt time. They used first-run studies. They used mock-ups. They used pre-install meetings. They stopped between cycles and asked the right questions.

Are you ready for your week? Do you need to do a first-run study? How are you going to install that? What does it look like when you install that as a mock-up? That is quality. But it was not quality sitting off to the side as a separate department. It was quality embedded into the production system. Quality became part of the rhythm. Quality became part of the huddle. Quality became part of the flow. That is when the idea landed. Quality is a flow system.

Why It Matters to Schedule, Safety, and Families

Quality matters because rework is brutal. Rework steals time, money, focus, trust, and energy. It interrupts crews that were supposed to be flowing. It forces people to return to zones they already left. It creates stacking. It creates frustration. It creates schedule panic. It increases safety risk because crews are now working under pressure, in the wrong sequence, with less room, less clarity, and more fatigue.

That is not a small issue. If a floor is poured at the wrong elevation, how long does it take to fix it? If an embed is placed wrong, how long does it take to get the RFI response, shim it, modify it, or work around it? If waterline is installed before the pre-construction meeting with the city and then has to be ripped out, how much flow did that really create? None.

It looked like progress for a moment, but it was fake progress. The project was moving, but it was moving toward rework. That matters because people pay for that chaos. Workers pay for it through overtime, frustration, and unsafe conditions. Foremen pay for it through broken plans and lost credibility. Superintendents pay for it through firefighting. Project managers pay for it through cost exposure and owner pressure. Families pay for it when people come home exhausted, irritated, and mentally stuck on problems that should have been prevented. If the plan requires burnout to succeed, the plan is broken, not the people.

Quality Control Belongs Inside the Production System

Quality control should not be viewed as something that slows down production. Quality control is what allows production to keep moving. That is a major shift. A pre-install meeting is not a delay. It is a flow protection move. A mock-up is not extra. It is a visual standard that prevents confusion. A first-run study is not overkill. It is how the team confirms production rate, method, sequence, and quality before the work scales. A huddle is not a meeting for the sake of a meeting. It is where readiness and quality become visible.

This is exactly why LeanTakt and the Takt Production System matter. Takt creates rhythm, but rhythm without quality will not hold. A train of trades cannot flow through zones if the work behind them is incomplete, defective, unclear, or failed. Quality at the source protects handoffs. Clean handoffs protect the next wagon. Protected wagons protect the train. The train protects the schedule. That is flow.

When quality is embedded into the production system, the team starts asking better questions before the work begins. They are not waiting for defects. They are preventing them. They are not hoping the install works. They are testing the install. They are not relying on memory. They are creating visual standards. They are not pushing people. They are making the work ready. That is the difference between motion and flow.

What Quality as Flow Looks Like

When quality becomes a flow system, it shows up before installation, during installation, and immediately after installation. It is not saved for the end. It is not discovered in a punch walk. It is built into the rhythm of work. A team that understands this will use quality steps as production controls. They will stop long enough to make sure the work can move. They will prepare before they install. They will validate the method before scaling it across zones. They will bring the foremen into the conversation so the people closest to the work can help define the standard. Here are the quality moves that protect flow:

  • Pre-install meetings that clarify the standard before work begins 
  • Mock-ups that show the team what right looks like 
  • First-run studies that test the method, timing, and quality 
  • Huddles that confirm readiness before each Takt time 
  • Checks at the source so defects do not travel downstream 

These are not bureaucratic steps. They are flow steps. They keep the train moving. They reduce variation. They protect the crews from rework. They help the project go faster because the work does not have to be done twice. That is the part we have to believe.

The Mindset Shift Under Schedule Pressure

The old mindset says, “We are behind, so we do not have time for quality.” The right mindset says, “We are behind, so we must protect quality.” That shift changes everything. When the team feels pressure, the answer is not to skip the standard. The answer is to tighten the system. If you really need to hurry up, stop and do the quality check. If you really need to recover schedule, pause and make sure the work is ready. If you really need the project to complete on time, do the pre-install meeting. If you really need the work to flow, do the mock-up. If you really need production speed, do the first-run study.

That sounds backwards only if you think speed means activity. Speed is not activity. Speed is completed work moving through the system without stops, restarts, defects, and rework. Quality creates that. Quality makes speed possible. This is where leaders have to hold the line. There will always be pressure to skip something. There will always be someone who wants to move now and fix later. There will always be a moment where quality feels inconvenient. But the leader has to know the truth. The inconvenience of checking is smaller than the cost of rework. Always.

Practical Guidance for the Field

If you want to use quality as a flow system, start by connecting it to your schedule. Do not let quality live in a separate binder. Put quality into the production plan. Tie it to zones. Tie it to wagons. Tie it to the lookahead. Tie it to the weekly work plan. Tie it to the daily huddle. Make it visible before work starts.

Ask the trade partners what they need to install it right the first time. Ask what information is missing. Ask what inspection is required. Ask what standard needs to be seen. Ask what can go wrong. Ask what needs to be mocked up. Ask what the first run will teach the team. Ask how the work will be checked before it moves downstream.

This is not about controlling people. It is about controlling the environment so people can succeed. Superintendents should treat quality as part of make-ready. Project managers should support the resources, information, and procurement needed to meet the standard. Foremen should be included because they understand the work. Field engineers should remove friction and help make the checks visible. The whole team should see quality as part of flow, not a department that comes in after the fact. That is how you stabilize the project.

How Leaders Should Talk About Quality

Language matters. If leaders talk about quality like it is an obstacle to schedule, the team will treat it like an obstacle. If leaders talk about quality like it is the path to schedule, the team will begin to see it differently. Instead of saying, “We do not have time for this,” say, “We do not have time to do this twice.” Instead of saying, “Skip the mock-up,” say, “We need the mock-up so the install can flow.” Instead of saying, “Just get it in,” say, “Let’s make it ready and install it right the first time.” Instead of saying, “Quality is holding us up,” say, “Quality is how we prevent the next delay.”

That kind of language teaches the team how to think. It keeps the project from drifting into panic. It protects people from being pushed into bad decisions. And it reinforces the truth that the system creates the result. Here are a few phrases worth using on the job:

  • “We need to go fast, so we are going to do the quality check.” 
  • “We are behind, so we are going to make sure we do this once.”   
  • “The mock-up protects the handoff.”  
  • “The first-run study protects the train.”  
  • “Quality is how we keep flow.”   

That is the tone. Calm. Direct. Respectful. Practical. No blame. No panic. Just leadership.

Connect Quality Back to the Mission

Elevate Construction exists to build remarkable people and systems that build the world. Quality is right in the middle of that mission because quality protects people from chaos. It protects the craft. It protects the next trade. It protects the customer. It protects the schedule. It protects families. When quality is treated as a flow system, everyone wins. Workers get clarity. Foremen get support. Superintendents get stability. Project managers get reliability. Owners get better outcomes. The project gets cleaner handoffs. The team gets fewer surprises. And the field gets to operate with dignity instead of panic.

If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow. That is not just a service line. That is the work. Stabilize the system. Protect the flow. Build people. Respect the trades. Make construction better for the people who actually build the work.

Conclusion: Stop Separating Quality From Flow

So here is the challenge. Stop looking at quality control as a separate project management system. Stop treating it like paperwork. Stop treating it like something you do when there is time. Stop treating it like the opposite of schedule. Quality is a scheduling system. Quality is a production system. Quality is a flow system.

The next time your project is under pressure, do not ask, “What quality steps can we skip?” Ask, “What quality steps must we protect so we do not lose flow?” That one question can save your project from rework, frustration, and fake progress. Jason said it clearly: “Quality is a flow system.” Believe that. Build that. Teach that. And the next time someone says, “We do not have time for the quality check,” remind them that we definitely do not have time to install it twice. Plan it first, build it right, finish as you go.

On we go.

Frequently Asked Questions

Why is quality control a flow system?

Quality control is a flow system because right first time installation prevents rework, failed inspections, trade stacking, and schedule interruptions. When quality is built into the rhythm of work, crews can move through zones with cleaner handoffs and fewer stops.

Do quality checks slow down the schedule?

Quality checks may feel like they slow down the moment, but they protect the overall schedule. A short pause for a pre-install meeting, mock-up, or first-run study is far less expensive than removing and reinstalling defective work later.

What are the most important quality steps before installation?

The most important steps include pre-install meetings, mock-ups, first-run studies, readiness checks, and clear huddles with the people doing the work. These steps clarify the standard and help the team install correctly the first time.

How does Takt connect to quality control?

Takt depends on clean handoffs between zones and wagons. If work is defective or incomplete, the train of trades loses flow. Quality protects the Takt rhythm by making sure each handoff is ready for the next trade.

What should leaders do when the project is behind schedule?

Leaders should strengthen quality, not skip it. When a project is behind, the team must prevent rework, protect handoffs, and install correctly the first time. The fastest path is disciplined readiness, not rushed installation.

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.

Your Work Does NOT Speak for Itself!

Posted on by Danny Jiménez⁩
Read 27 min

The Hard Truth Builders Need to Hear

Here’s the deal. There is a phrase that sounds humble, sounds professional, and sounds like something a good builder would say: “My work speaks for itself.” It sounds right. It sounds grounded. It sounds like the kind of thing someone says when they do not want to brag, show off, or make the work about them.

But it is not true. Your work does not speak for itself if nobody sees it. Your work does not speak for itself if nobody learns from it. Your work does not speak for itself if it stays trapped inside your project, inside your files, inside your head, or inside one small circle of people who already know what you do. In construction, good work must be communicated. Good work must be taught. Good work must be shared. Otherwise, it helps one project and dies there.

That is not leadership. That is hidden value. This matters because construction needs builders who are not only technically good, but also influential, trusted, communicative, and generous with what they know. We do not need more silent heroes. We need systems that make good work visible so others can use it, improve it, and pass it on.

The Real Construction Pain

The pain is that we have a lot of talented people in this industry who are doing great work in silence. They are solving problems, helping the field, removing roadblocks, improving schedules, mentoring people quietly, and protecting the project from chaos. But because they are not communicating those wins, nobody else can see the system behind the success. So the company does not learn. Other projects do not benefit. Younger builders do not get trained. Leaders do not see the full picture. The person doing the work gets frustrated because they feel unseen, and the organization gets weaker because the learning never spreads.

You have probably seen this before. A strong superintendent wants to become a general superintendent, but they are only known on their own project. A project engineer wants to become a project manager, but they never step into meetings, present information, mentor the next person, or show they can lead beyond tasks. A project manager wants to grow, but they stay behind the computer, answer emails, and never become the person scaling clarity across the team. The issue is not that these people are bad. The issue is that the system never taught them that communication is part of the work.

The Failure Pattern

The failure pattern is simple. People confuse silence with humility. They think sharing their work is bragging. They think teaching others is showing off. They think visibility is politics. They think if they just keep their head down, someone will eventually notice and reward them.

That is a dangerous belief. If it is not written down, it did not happen. If it is not communicated, people cannot trust it. If it is not shared, it cannot help anyone else. This is true in safety. This is true in quality. This is true in scheduling. This is true in leadership. If OSHA shows up and you say, “I checked that,” but it is not documented, it does not count. The same principle applies to leadership. If the organization cannot see what you are doing, learn from what you are doing, or repeat what you are doing, then your work is not speaking. It is whispering. And whispers do not scale.

Respect for People Means Sharing What Works

The system failed them; they didn’t fail the system. That matters because I do not want anyone reading this to think the message is, “Go promote yourself harder.” That is not the point. This is not about ego. This is not about fame. This is not about becoming the loudest person in the room.

This is about respect for people. Respect for people means we do not make other teams suffer through the same problem we already solved. Respect for people means we do not bury good ideas because we are uncomfortable sharing them. Respect for people means we help the next project, the next foreman, the next project engineer, the next superintendent, and the next leader.

When you share a lesson learned, you reduce waste. When you communicate a risk, you protect flow. When you teach a process, you build capacity. When you make your work visible, you help the system improve. That is not bragging. That is service.

A Field Story About Influence

There was a senior superintendent who wanted to become a general superintendent. From the outside, you would think he was ready. He had the technical skills. He had experience. He understood the work. He had the ability to run a project. But the feedback he received was direct. He was not out there showcasing his work. He was not supporting others at scale. He did not have the influence needed for the next role.

That is a hard message to hear, but it is an important one. Leadership at the next level is not only about doing your own job well. It is about helping others do their jobs well. It is about scaling knowledge, building trust, communicating clearly, and moving the company forward.

There was also a project engineer in downtown Phoenix who wanted to become a project manager. The advice was simple. Get in there. Ask to run portions of the team meeting. Present in the OAC when appropriate. Mentor other project engineers so they can grow into your seat. Show that you can communicate, coordinate, and lead. The response was, “That is not really me. My work speaks for itself.” That mindset will hold people back. Not because they lack talent, but because trust and influence do not grow in silence.

Why It Matters to Projects and Families

This matters because projects run on trust. Trust runs on communication. Communication supports flow. Flow protects people. When a team does not know what is happening, they guess. When they guess, they miss. When they miss, roadblocks linger. When roadblocks linger, trades get stacked, crews get rushed, quality drops, safety risk increases, and people take stress home.

This is why communication is not soft. It is not extra. It is not a personality preference. Communication is a production strategy. LeanTakt, Takt Production System, Last Planner System, Scrum boards, lookaheads, daily huddles, and visual controls all exist for a similar reason. They make the work visible. They make the plan visible. They make roadblocks visible. They make promises visible. When things are visible, people can coordinate. When people coordinate, flow improves.

Your leadership works the same way. If your work is hidden, the system cannot learn from it. If your learning is hidden, the next team repeats the same mistake. If your warnings are hidden, the next project walks into the same roadblock. Hidden knowledge is waste, and waste should annoy us.

The Framework: Communication Builds Trust

The framework is simple. Low communication creates low trust. High communication creates high trust. You may be a high performer, but if nobody knows what you are doing, when it will be done, what risks you are carrying, what you have learned, or what help you need, the team cannot fully trust the system around you. That is not a character attack. That is production reality. Think about a kitchen team. If one person is cooking but never speaks, never calls out timing, never confirms what is ready, and never tells the team what is happening, the rest of the team has to guess. They may be talented, but they are still creating uncertainty. And uncertainty lowers trust.

Construction is no different. The project team needs to know what is happening. The field needs to know what is ready. Leaders need to know where the risks are. Trade partners need clarity. Younger builders need teaching. Other projects need lessons learned. Here are some ways builders create trust through communication:

  • Share lessons learned before another team hits the same roadblock
  • Give clear updates on risks, procurement, schedule, and readiness
  • Teach improvements without making yourself the hero
  • Invite others to see what is working on your project
  • Document wins so the system can repeat them

Notice the spirit behind those actions. They are not about attention. They are about usefulness. The goal is not, “Look at me.” The goal is, “Here is something that helped us, and I want it to help you too.” That is the right posture.

Sharing Is Not Bragging

One of the biggest mindset shifts builders need is this: sharing is not bragging when the motive is service. Bragging points attention back to you. Sharing points value toward the team. Bragging says, “Look how great I am.” Sharing says, “Here is what we learned.” Bragging makes the person the center. Sharing makes the improvement the center.

That difference matters. If you found a better way to handle a long lead item, share it. If your team created a cleaner logistics setup, share it. If a foreman helped solve a sequence problem, give them credit and share the lesson. If your project improved flow because of better zoning, work packaging, or daily huddles, teach the pattern. If you learned something the hard way, help someone else learn it the easier way.

That is how a company gets better. That is how a builder becomes a leader. A person who says, “I do not want the fame and glory,” may be trying to stay humble. That can be sincere. But sometimes that phrase hides discomfort. Sometimes it means, “I do not want to think beyond my own project.” Sometimes it means, “I do not want to invest in other people.” Sometimes it means, “I do not want to get uncomfortable.” Leadership requires discomfort. Teaching requires discomfort. Influence requires discomfort. Growth requires discomfort.

Practical Guidance for Builders

Start small. You do not need to become a public speaker tomorrow. You do not need to start a channel. You do not need to be flashy. You just need to be useful. If you are a project engineer, ask to present a small part of the meeting. Share a lesson learned with another PE. Offer to train someone on a process you understand. Ask your PM where you can take more ownership. Communicate what you are doing before someone has to pull it out of you.

If you are a superintendent, invite others to walk your project. Share procurement warnings. Send out field observations that help people prepare. Teach the next superintendent what you are seeing. Talk about what is working in your huddles, logistics, make ready, and scheduling systems.

If you are a project manager, scale clarity. Build the team. Help the superintendent. Communicate risks. Teach the owner’s priorities. Make sure the people doing the work have what they need. And when a system works, document it so the next team can use it. Do not make it complicated. Make it consistent.

How to Share Without Ego

There is a right way to do this. Keep the tone humble, practical, and team focused. Give credit. Name the system. Share the lesson. Make it useful. You do not need to say, “I solved this.” You can say, “Here is what our team learned.” You do not need to say, “My project is better.” You can say, “This helped us improve flow.” You do not need to say, “Look at my idea.” You can say, “This may help another team avoid the same issue.” In final third of your career growth, these habits compound:

  • Write down one lesson learned each week
  • Share one helpful warning with another project
  • Mentor one person who is coming behind you
  • Give public credit to the team that helped create the win
  • Turn one improvement into a repeatable process

That is how you become trusted. That is how you become influential. That is how you build people who build things. And that is how the work finally begins to speak, because you gave it a voice.

Connect Back to the Mission

Elevate Construction exists to build remarkable people and systems that build the world. That mission cannot happen if the best ideas stay hidden. It cannot happen if lessons learned stay on one project. It cannot happen if leaders stay silent because they are afraid of being seen. We need builders who communicate. We need builders who teach. We need builders who share. We need builders who make the work visible so the next person can win.

If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow. And that matters because stability is not only a scheduling issue. It is a people issue. When teams communicate, trust grows. When trust grows, flow improves. When flow improves, people get to go home with more energy for their families. That is the point.

Conclusion: Give Your Work a Voice

Your challenge this week is simple. Find one thing you are doing that could help someone else, and share it. Share a lesson. Share a warning. Share a process. Share a field story. Share a mistake in a way that helps someone avoid it. Share the good work of your team. Do not bury your talent. Do not wait for someone to magically discover the value you are creating. Do not confuse silence with humility. Be generous. Be useful. Be clear. Jason Schroeder said it directly: “Your work does not speak for itself.” That is not a criticism. That is a call to lead. Communicate the work. Teach the work. Improve the work. Give the work away so others can win.

On we go.

Frequently Asked Questions

Why doesn’t good work speak for itself?

Good work only helps at scale when people can see it, understand it, and repeat it. If the work stays hidden, the result may help one project, but the process does not help the organization. Leadership means making lessons visible so others can learn from them.

Is sharing my work the same as bragging?

No. Bragging makes the person the center of attention. Sharing makes the lesson useful to others. When you give credit, focus on the system, and teach what helped the team, you are serving people, not promoting yourself.

How does communication build trust on a construction project?

Communication removes guessing. When people know what is ready, what is blocked, what has changed, and what needs action, they can coordinate with confidence. Low communication creates uncertainty, and uncertainty lowers trust.

What should I share with other builders?

Share lessons learned, procurement warnings, schedule risks, quality improvements, safety practices, LeanTakt insights, meeting improvements, and anything that helps another team create flow. The goal is to reduce waste and help others avoid preventable pain.

How can I start if sharing feels uncomfortable?

Start with one small action. Send one helpful note, mentor one person, document one process, or offer one short lesson in a meeting. You do not need to be loud. You just need to be useful, consistent, and willing to help others win.

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.

Profoundities – An Interview of Jason Schroeder

Posted on by Danny Jiménez⁩
Read 16 min

What Lean Construction Actually Means: The Interview That Explains It All

Jesse from the Operational Excellence Platform sat down with Jason Schroeder to get the foundational truth about lean construction. What followed was one of the most direct conversations about what lean actually is, why so many people get it wrong, and what the connection between Takt planning, respect for people, and organizational culture actually looks like in practice.

The Four Layer Definition of Lean Construction

Jason has been refining this definition for years, and the pattern holds everywhere lean is successfully implemented.

Layer one: respect for people and resources. This is the foundation. Nothing else works without it.

Layer two: stability, capacity, and flow. Stable environments, teams with the capacity to do the work, and work that flows without interruption.

Layer three: total participation with visual systems. Every person in the organization engaged, with information visible enough to act on.

Layer four: continuous improvement and fanatical quality. Not possible without the first three layers. Not sustainable without them.

The problem Jason observes repeatedly is that lean consultants go sell layer four to organizations that have not built layers one through three. They sprinkle improvement methodologies onto unstable, disrespectful environments and wonder why nothing sticks. It is not possible. You cannot build a building without a foundation, and you cannot build continuous improvement without the foundational layers of respect and stability.

The Paul Akers Lesson

Paul Akers runs a wood tools manufacturing company in Washington State and has a well known YouTube channel about two second lean improvements. People watch his content and conclude that all they need to do is learn the eight forms of waste and start making small improvements.

What they miss is what Paul Akers actually enforces at his facility. Fanatical cleanliness. Total organization. Zero tolerance for disrespect. No one works at capacity beyond what is sustainable. Everyone works together, and that collaboration is not optional. Jason experienced this firsthand during a podcast interview with Paul, who interrupted to point out that Jason was being wasteful with his preparation process and would need to get faster if he wanted to work with him.

The improvement methodology is visible. The culture that makes it work is invisible to the casual observer. And that invisible culture of discipline, respect, and total participation is what most lean implementations fail to build before attempting the visible tools.

What Command and Control Actually Got Wrong

The lean community frames command and control as the primary cause of construction’s performance problems. Jason is not buying it.

Projects used to finish. When he was early in his career, one project failing at a major GC was famous across the country. Everyone else was finishing on time with full fee. That ratio has completely inverted. Now one or two projects finishing well is notable. The majority are mediocre, late, or financially troubled.

What changed? The 2007 to 2010 economic crash stopped training. A generation of experienced builders retired. The development programs that would have prepared their replacements went dark. The industry is still paying for that in project performance.

The command and control superintendents of 20 years ago were finishing projects. They were not doing it by collaborating in the modern sense. But they knew what they were doing. The problem was not their leadership style. The problem is that the people who replaced them were not given the education, the mentorship, or the development they needed. The lean community is criticizing good and better while not naming the actual enemy: untrained builders without plans who do not collaborate with anyone.

Takt Is the Missing Backbone

Jason describes the relationship between Takt planning and the Last Planner system using the car manufacturing analogy. In a Toyota plant, the assembly line runs on Takt time, a production rhythm where every vehicle moves forward on a consistent beat. The pull systems that supply materials to the line are organized around that rhythm. But the line itself is the backbone.

In construction, the industry has largely adopted pull planning and the Last Planner system without establishing the Takt backbone. Short interval scheduling is being applied to a non rhythmic production sequence driven by CPM scheduling. The result is a better organized version of the same chaos, not the flow based production system the Last Planner system was designed to serve.

As Jason puts it: talking about pull systems in construction without Takt planning is like wanting to bake without an oven. The ingredients can be organized beautifully. Without the oven, nothing is baked.

The Takt production system maps flow through rhythm, continuity, and consistency. It shows all three types of flow on one page. It creates buffers using Little’s Law. It levels work across the project in both time and space. Without it, you cannot comply with the fundamental requirement of both high workflow and high resource efficiency simultaneously, because in construction, unlike manufacturing, the product is stationary and the workers move through it. Resource efficiency and flow efficiency are inseparable.

Why Givers Implement Lean and Takers Do Not

Jesse asked the honest question: why is not everyone doing this if it works? Jason’s answer is unvarnished.

The people who have genuinely transformed their projects and companies through lean came to him not because they wanted better profit margins. They came because they wanted a better environment for their people. The profit was the outgrowth. No one who started by asking “what’s in it for me financially” has produced a meaningful lean transformation.

Jason’s framework is simple: givers implement lean, takers do not. A lean culture requires every person in the organization to benefit. It requires the leader to invest their energy outward, toward developing people and building systems, rather than filtering resources upward. Takers can make money in disrespectful environments. For them, the additional effort required to actually build a lean culture has no obvious personal return, so they do not do it.

What is changing is the labor market. The great resignation has made it clear to workers that disrespectful environments are optional. The companies that have been relying on the extraction model are now finding that the workers they need are no longer staying. The competitive advantage of genuine respect for people is becoming visible in recruiting, retention, and performance at a pace that is accelerating.

What Running a Project Without Lean Actually Costs

A construction project is a system. It requires a certain amount of energy to get completed. If the project is run inefficiently, with waste, chaos, and disrespect, that energy has to come from somewhere. The owner does not pay for the waste. The company absorbs some of it. But the rest is extracted from the personal time, health, and family life of the workers and leaders who build it.

The workers go home depleted, not because construction is inherently punishing, but because the system is consuming energy it should not need to consume. Their families absorb the cost of that.

If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow. The foundation of that work is always the same: respect, stability, capacity, and flow, built in that order, before any tool or methodology is introduced.

On we go.

Frequently Asked Questions

What is the difference between lean and Takt planning?

Lean is the broader philosophy: respect for people, stability, total participation, and continuous improvement. Takt planning is the production scheduling methodology that creates the rhythmic backbone for construction projects. Lean without Takt in construction lacks the structural foundation needed to achieve genuine flow and resource efficiency simultaneously.

Why does lean fail when consultants apply it without the cultural foundation?

Because the tools of lean are designed to surface and solve problems in an environment where people feel safe raising them, where the work is stable enough to analyze, and where leadership is genuinely invested in the outcomes. Without that environment, the tools become performance without substance.

What makes Takt planning different from CPM scheduling?

CPM builds a network of activities based on dependencies and durations. It does not plan for even workflow or resource efficiency. Takt planning organizes work on a rhythmic beat through zones, creating buffers by design, leveling trades across the project, and making both workflow and resource flow visible on a single page. CPM generates a plan. Takt generates a production system.

Is lean construction more expensive to implement than traditional approaches?

The upfront investment in training, systems, and cultural development is real. The return comes in reduced rework, better schedule performance, improved trade partner relationships, and lower turnover. Companies that have made the investment consistently report that the net financial outcome is significantly better.

What is the first concrete step for a company that wants to start implementing lean correctly?

Establish basic respect before introducing any tool or process. Clean the job site. Provide real facilities for workers. Build a morning huddle habit. Establish a safety and quality standard that is enforced consistently. Get the environment stable. Then introduce the planning systems and improvement processes that lean methodology depends on to function

 

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.

Reactive vs. Proactive

Posted on by Danny Jiménez⁩
Read 16 min

Stop Firefighting and Start Leading: The Reactive vs Proactive Distinction Every Foreman Needs to Hear

Here is what reactive looks like on a construction project. A piece of equipment breaks down and the foreman is on the phone with the shop. The dumpster fills up and the foreman is calling the trash company. A worker is absent and the foreman is scrambling to reorganize. Someone needs to interpret a drawing and the foreman drives across the site to explain it. Materials are missing and the foreman runs to Home Depot. Traffic control is not in position and the foreman is sorting it out.Every one of those things. One after another. Eight hours. Ten hours. Twelve hours.

And at the end of the day, the foreman feels genuinely busy. They feel needed. They feel like they are doing their job. They are not doing their job. They are doing everyone else’s job while their actual job sits undone.

What Reactive Mode Actually Costs

Reactive management is not a personality type. It is a system failure. Every single item on that list should have a standard system behind it so that it does not require the foreman’s personal intervention.

Equipment maintenance and breakdown response can be on a system. Dumpster fill levels can trigger a call from a crew member, not the foreman. Worker absence protocols can be pre planned with backup options identified. Drawing interpretation should be handled by workers who have been trained to read and act on the plans in front of them. Materials should arrive ahead of when they are needed so that no one is making a same day run to Home Depot. Traffic control positions should be part of a standard site setup that is checked at the start of shift.

When these things are on stable systems, they do not require the foreman’s attention. When they are not on stable systems, they consume the foreman entirely. And the foreman’s actual job, planning production, tracking actuals against targets, preparing for the next day, coaching the crew, surfacing roadblocks before they affect the schedule, never gets done. The $100 an hour work gets buried under $10 an hour work, and the project pays for it.

The Proactive Standard

A proactive foreman has set up the game so that 80 to 90% of each day runs on stable systems and standard processes. The materials are staged. The next day’s plan is communicated. The crew knows what winning looks like before they start. The huddle is tight and purposeful. The production targets are visible. The foreman is out in the field watching, comparing actuals to plan, and catching deviations early enough to correct them before they compound.

The remaining 10 to 20% of the day is genuine variation, the unexpected problem that could not have been anticipated. That is manageable. One or two phone calls a day is manageable. Eight phone calls an hour is chaos. And the difference between those two states is almost entirely a function of planning and system development.

Jason uses the analogy of taking 11 children to a Walmart bathroom without anyone touching the wall or floor. That sounds difficult until you hear the system: everyone goes in with a buddy, shoes are tied, there is a regrouping spot in the middle away from the walls, hands are washed, and the door handle is handled with a paper towel on the way out. The chaos is impossible when the plan is complete. The chaos is inevitable when there is no plan.

What Sun Tzu Actually Said About This

The best generals win the war before going to battle. Amateurs go to battle and then attempt to win the war.

The foreman or superintendent who shows up to the site and starts their day reacting to whatever arrives is going to battle without a plan and hoping for the best. The one who has planned the day before, staged the materials, confirmed the crew, set up the equipment, coordinated the logistics, and started the huddle on time has already won the morning before a single block of work is laid.

The difference in output between those two people on the same crew is not small. It is the difference between a crew that makes production and one that does not, between a project that finishes on time and one that crash lands in the final six weeks trying to make up for every reactive day that preceded it.

Standard Systems Replace Reactive Firefighting

Here is what standard systems look like for the most common reactive triggers:

  • Equipment: a daily pre shift check by the operator, a clear protocol for calling in breakdown coverage, and a contact number posted on the equipment itself. The foreman is not in the loop until the system has failed to resolve it
  • Dumpster: a fill level indicator and a designated crew member responsible for calling for pickup. Not the foreman
  • Worker absence: a pre planned crew composition adjustment for a one person absence, communicated at the beginning of the week so no one is scrambling on the morning it happens
  • Materials: a procurement log with buffer windows so materials arrive ahead of need. No same day trips for anything that was foreseeable
  • Traffic control: a standard setup diagram included in the daily plan, checked at shift start by a designated crew member

When these systems are in place, the foreman’s morning starts with a huddle, a production review, and a preparation conversation for the next day. That is the job. Everything else is the consequence of not having done the job in the planning phase.

If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow. Building proactive leaders at the foreman and superintendent level is the foundation of every successful Elevate Construction field transformation program.

The Challenge for Every Foreman and Superintendent

Track your interruptions tomorrow. Every time you stop what you should be doing to respond to something reactive, write it down. At the end of the day, look at the list. For each item, ask: could a standard system have handled this? If yes, build the system this week.

Do that for 30 days and your day will look completely different. The firefighting will not disappear entirely. But it will drop from 100% of your day to 10 to 20%, and the other 80 to 90% will finally be available for the work that actually builds the project.

On we go.

Frequently Asked Questions

How do you build standard systems when the project is already underway and everything feels reactive?

Start with the highest frequency interruptions. The things that pull the foreman away most often are the highest return targets for standardization. Pick the top two or three and build the system for those this week. You cannot fix everything at once, but you can fix the biggest ones, which will free up enough time to fix the next ones.

What does a proactive morning huddle actually look like?

Short, structured, and purposeful. Ten minutes maximum. The plan for the day is visible, the production target is stated, any potential constraints are flagged, and each crew member knows exactly where they are going and what they are doing. The foreman does not run the huddle by answering questions. They run it by having done the preparation the day before so that the answers are already in the plan.

How do you get workers to take ownership of standard system tasks rather than defaulting to the foreman?

Make the responsibility explicit and visible. Assign specific people to specific system tasks. The person responsible for the dumpster call is not the foreman. It is a named crew member with a clear trigger and a clear action. Accountability for the system task is tracked in the same way production is tracked.

Is there a version of proactive leadership that applies to project managers as well as foremen?

Yes, and the principle is identical. A project manager who is constantly fielding calls from trade partners about missing information, late approvals, and unresolved RFIs is in reactive mode. A project manager who has a six week look ahead driving submittal reviews, a procurement log preventing material surprises, and a weekly coordination rhythm that surfaces constraints before they arrive is operating proactively.

What is the most common reason foremen stay in reactive mode even when they know it is not effective?

The adrenaline and significance that comes from being needed. Reactive firefighting generates visible busyness, immediate gratitude from people whose problems get solved, and a constant sense of importance. Proactive planning generates stability, which is less viscerally satisfying even though it produces far better outcomes. The shift from reactive to proactive requires the foreman to give up the identity of the person everyone calls, which is psychologically harder than it sounds

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.

What is Your Product?

Posted on by Danny Jiménez⁩
Read 14 min

What Is Your Product? The Question That Changes Everything About Construction Workforce Development

Most construction companies think of their product as the finished building. Some say it is the customer experience. Some say it is their expertise. All of those are defensible answers. But Jason Schroeder wants to focus on one that most companies overlook, and that changes everything about how a construction business operates.What if your product is the foreman?

Why Foremen and Workers Are the Product

A beautiful finished building can be produced through pain, rework, and exhaustion. You can deliver the structure and still have failed at the full experience of what construction should look like for the owner, the trade partners, and the people who built it. The finished product is not the differentiator. The capability, discipline, and culture of the field supervision and workforce that produces it is.

When you define your foremen and workers as the product, the framing shifts entirely. Products are developed, packaged, researched, and improved. Products are protected from defect. Products are valued, invested in, and showcased. Products are not mixed together carelessly, interchanged randomly, or allowed to deteriorate without intervention.

That framing applied to your field workforce produces a set of decisions that most construction companies are not making.

Green, Yellow, and Red Crews

Jason uses a three tier classification for crew performance: green, yellow, and red.

Green crews are making production targets, maintaining safety records, staying together, and performing at a level that makes the company money. These are the crews a company should be doing everything to retain, protect, and keep intact.

Yellow crews are performing at an acceptable but not high level. There are gaps in production, consistency, or culture that could be addressed through training, better composition, or more direct coaching.

Red crews are underperforming. Production targets are being missed, safety incidents are occurring, or the culture of the crew is not functional. These crews need active intervention, not more time to sort themselves out.

The key metrics for evaluating crew status: how many days the crew has been together, production average against target, safety record, whether the foreman runs a morning huddle, and whether incremental improvements are being made.

What Product Thinking Does to Your Company

If foremen and workers are the product, the company’s responsibilities shift.

Research and development means investing in training programs, coaching, professional development, and the tools and technology that make the workforce more effective. This is not overhead. It is product R&D.

Packaging means keeping crews together. A crew’s culture, rhythm, and communication patterns take time to develop. It takes roughly seven days for a new person to be fully onboarded to a crew. Every time a crew is broken apart and reshuffled, that investment resets. Keeping green crews intact is product protection.

Quality control means knowing which crews are green, yellow, and red, and acting accordingly. Pulling three workers from a green crew to bolster a red crew does not make one good crew and one improving crew. It makes two yellow crews. Product integrity requires protecting the composition that is producing results.

Marketing and sales means showcasing your people. Owners who see a project run by a highly competent, engaged field team tell other owners. The superintendent who builds a clean site, runs tight huddles, and produces predictably is the advertisement.

The Crew Development System

The practical implication is that every construction company needs a visible map of its crew status. Not to shame underperforming crews, but to direct development resources accurately.

Keep green crews together and make them feel valued enough that they would never consider leaving. Move yellow crews toward green through targeted training, better foreman development, and active coaching. Assign a development resource to the specific crew and stay with them until they are green.

Invite red crews and red foremen to improve with support, or to exit. A company that tolerates red crews indefinitely is not being kind to anyone. The workers deserve better leadership. The company deserves better performance.

The Crew Composition Rule

Reduce context switching. Crews perform best when they know each other, know their rhythm, and know their foreman’s expectations. Every change to the crew composition resets part of that knowledge base.

Ideal crew size is around four. Larger crews are sometimes required, but beyond that size, communication complexity increases and performance per person tends to decline. Adding one additional person to a four person crew for swing capacity is reasonable. Building ten person crews for tasks that four could handle is inefficiency disguised as resource allocation.

If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow. Treating the foreman and the workforce as the product is the shift that makes every other improvement in training, culture, and production actually compound over time.

The Challenge for Your Company

Do you have a current map of your green, yellow, and red crews? Not in your head. On paper or on a visual board, with the data to support each classification.

If you do not, you are managing your most important product without a product development system. And no business would tolerate that for anything else it sold.

On we go.

Frequently Asked Questions

How do you classify a crew as green, yellow, or red without it feeling like surveillance or shaming?

Frame the system around support, not judgment. A yellow crew means the company has an opportunity to invest more development resources in that group. A red crew means something in the system around those people is failing them. The classification should trigger a coaching and support response, not a punishment response.

What is the minimum you need to track to run a crew status system?

Days the crew has been together, production average against target for the last four to six weeks, safety record, and the foreman’s basic planning behaviors: running morning huddles, tracking production daily, and requesting support when needed. Those four inputs will accurately classify almost any crew.

How do you prevent a high performing green crew from burning out if they are consistently producing at a high level?

Manage their workload deliberately. Green crews should not be the default answer to every project problem. Their performance is an asset that needs protecting, which includes protecting them from overuse. Build sustainable capacity at the yellow crew level so that green crews are not constantly covering for underperforming groups.

Is it ever appropriate to move a worker from a red crew to a green crew?

In specific circumstances, yes: when the individual worker is being held back by the red crew’s culture rather than contributing to it, and when there is a clear plan for bringing them into the green crew’s standard rather than disrupting it. The test is whether the move improves both situations or just redistributes the problems.

What does showcasing your field workforce as a product actually look like in a business development context?

It looks like bringing owners onto active job sites that are clean, organized, and running on a visible production rhythm. It looks like having foremen and superintendents articulate what they are building and how to customers who visit the site. It looks like tracking and sharing production performance data with owners as evidence of management capability.

 

Lorem ipsum dolor sit amet, consectetur adipiscing elit. Ut elit tellus, luctus nec ullamcorper mattis, pulvinar dapibus leo.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.

Ordering Materials is The GC’s Job!

Posted on by Danny Jiménez⁩
Read 15 min

The GC’s Job Is Not Done Until the Materials Are There: A Final Word on Supply Chain Ownership

Jason Schroeder has covered just-in-time deliveries. He has covered procurement logs. He has explained why the supply chain is not in Procore. This episode exists because the same conversation keeps happening on project visits, and the answer keeps being wrong.

“That’s the trade partner’s job.” It is not.

The Walmart Distribution Model Applied to Construction

Walmart does not stock its stores directly from manufacturers. The supply chain runs through distribution centers, which buffer inventory between production and retail. The distribution centers receive large shipments from manufacturers, organize them by product category, and dispatch to individual stores on a schedule that maintains adequate inventory at the point of sale without creating excess that goes to waste.

The grocery store itself is the final supermarket buffer: a staging location that holds enough inventory for customers to pull what they need, replenished from the distribution center on a rhythm that prevents stockouts without creating overstocking.

This is the model that just in time construction procurement mirrors. Materials are ordered and tracked through the supply chain. They arrive at the project’s designated lay down area, the construction supermarket, buffered ahead of when each zone needs them. Crews pull materials from the supermarket to the work face just in time, without having floors pre stocked with materials that create tripping hazards and congestion.

The system works when it is actively managed. It fails when it is assumed to happen on its own.

What Active Supply Chain Management Actually Looks Like

The procurement log is the instrument. Not the submittal register in Procore. The procurement log tracks the full supply chain from executed contract to material in the supermarket.

For a given scope, that log needs to capture: the submittal status, the PO status at the manufacturing plant, whether the order is in fabrication, shipping status including customs clearance for overseas materials, expected delivery date, buffer duration between delivery and planned installation, and the supermarket location where the material will land on site.

For long lead items like curtain wall, exterior metal panels, or elevators, where supply chains can run five to nine months, the log needs to capture multiple intermediate release points. When were samples approved? When were dies released? When were shop drawings approved and the fabrication order placed? When does field measuring need to happen in order to maintain the delivery timeline? Each of those dates should be on the team’s shared calendar, tracked actively, and reviewed weekly.

Jason makes the point directly: if there is one long bar in a schedule that says “exterior curtain wall procurement” without intermediate milestones, the team does not have procurement management. They have a procurement placeholder.

Breaking Materials Out by Zone

One of the most common procurement failures is receiving materials by building rather than by zone. The entire floor plate of a material category arrives at once, creating a staging problem that affects production for weeks.

Jason’s experience is that breaking materials out by zone is almost always possible if the conversation with the supplier is had early enough and with enough specificity. He has successfully pieced out door frames by zone. Millwork and casework by zone. Metal panels and curtain wall by zone based on the Takt plan sequence.

The objection is usually cost: additional deliveries cost money. Jason’s response is to run the analysis. What does it cost to receive everything at once in lost production time, in congestion, in material damage, in labor to move materials repeatedly? That number has almost never been calculated by the teams making the claim that zone deliveries cost too much.

The German Model and What It Reveals

When Jason visited construction projects in Germany, he found that in some cases at least half of the materials were procured directly by the general contractor rather than by the trade partners. The trade partner brings labor and expertise. The GC brings the material.

This model has trade offs. But Jason’s observation is that the failures caused by this trade off are far less costly than the failures caused by having each trade partner manage their own procurement in a silo, with no GC visibility or coordination.

The lesson is not that GCs should procure everything. The lesson is that the GC’s active participation in procurement is not optional regardless of who ultimately places the orders. Just as a GC does not delegate safety to the safety manager and call it done, and does not delegate quality to the QC manager and call it done, a GC does not delegate procurement to trade partners and call it done.

If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow. Supply chain ownership is one of the clearest markers of a project team that is actually in control versus one that is reacting to the consequences of delegated chaos.

The Challenge for GC Teams This Week

Pull up your procurement log. If you do not have one, that is the answer. If you do have one, check whether it has intermediate release point milestones for your long lead items. Check whether your materials are being tracked by zone. Check whether the last weekly procurement meeting happened and what decisions came out of it.

A GC that is not in a weekly procurement meeting with a functioning procurement log is not managing the supply chain. They are hoping it works out.

As the principle holds: amateurs study tactics, armchair generals study strategy, and the real generals study logistics. If you can get things where they need to go, you can build a remarkable project. If you cannot, the rest of the plan does not matter.

On we go.

Frequently Asked Questions

How do you establish a procurement meeting rhythm that actually produces decisions?

The meeting should run weekly with the superintendent leading, the project manager and project engineers in the room, and trade partner points of contact available by phone when their scope is being reviewed. The agenda follows the procurement log: current status, upcoming release points, any delivery risks, and corrective action items with owners and dates. The meeting is not a status report. It is a decision making session.

What is the GC’s role when a trade partner is managing their own procurement?

Active oversight and verification, not passive acceptance. The GC should know the trade partner’s supply chain timeline, be receiving regular status updates, have direct contact with the supplier for critical items, and have identified the intermediate milestones that need to be hit to keep the delivery on track.

How do you handle a trade partner who resists sharing procurement information with the GC?

Address it contractually and in the preconstruction meeting. Procurement transparency is a project requirement, not a courtesy request. If the subcontract requires timely delivery in accordance with the project schedule, the GC has the right to verify that the supply chain is on track to meet that requirement.

What should a Takt aligned procurement log look like for a complex project?

It should show every scope in the Takt sequence, with columns for the current procurement status at each stage: contract executed, submittal submitted, submittal approved, PO placed, in fabrication, in transit, on site, in supermarket. For long lead items, add a column for each intermediate release milestone. The dates in the log should be driven by the Takt plan’s zone sequence, counting back from when each material needs to be in the supermarket.

What happens to projects that do not manage procurement actively?

The same thing that happens to ships that sail without checking the fuel gauge: they run out of what they need in the worst possible place at the worst possible time. Late materials cause production gaps. Production gaps create crew displacement. The cost of reactive procurement is always greater than the cost of proactive procurement management.

 

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.

Swing Capacity & Workable Backlog

Posted on by Danny Jiménez⁩
Read 15 min

Swing Capacity: The Buffer Concept That Separates Flow From Chaos

Most construction conversations about crew capacity land in one of two places: either we do not have enough people, or we have people standing around. Both of those feel like the problem. Neither of them is the solution. The solution is swing capacity, and understanding it changes how you think about crew composition, schedule buffers, and what to do when a bottleneck appears on your project.

Three States of Capacity

No capacity is exactly what it sounds like. Every worker and crew is fully committed, running at their maximum, with no margin for anything unexpected. If one person gets sick, one crew member has an off day, or one activity runs long, there is nothing available to absorb it. Projects in this state are one problem away from falling behind.

Free capacity is the other extreme. Workers are on the bench. People are standing around getting paid for doing nothing particularly useful. This is the state most field leaders instinctively try to avoid because it is visible and easy to criticize.

Swing capacity is the space between those two extremes. It is a crew or workforce composition that has just enough additional capacity, whether in people or in time, that can be redirected toward a bottleneck activity or a workable backlog task without disrupting the primary production sequence.

Hal Maykommer introduced this concept to Jason in a conversation about Takt systems, and it crystallized something that experienced field leaders have been doing intuitively for years without naming it.

How Time Buffers and Crew Buffers Work Together

In a Takt plan, the relationship between Takt time and cycle time is everything. If you have a five day Takt time and a cycle time of exactly five days, you have no buffer. Any variation in the work will immediately push you past the Takt boundary and into the next zone, disrupting flow for every subsequent trade.

If the cycle time is four or four and a half days within a five day Takt time, you have a half day to a full day of time buffer. That buffer absorbs the variation, the unexpected problem, the minor equipment issue, the late delivery. The project stays on rhythm. The trades stay in flow.

The same logic applies to crew size. A crew that needs four people and has exactly four has no swing capacity. If one person is unavailable, the crew is at 75% capacity and the work slows. A crew of five doing the work of four has one person with the ability to redirect their attention when the primary work is ahead of schedule, when preparation for the next area is complete, or when a bottleneck elsewhere needs additional support.

This is not free capacity. The fifth person is not sitting on a bench. They are working on workable backlog, and they are available to swarm a bottleneck when one appears.

What Is Workable Backlog?

Workable backlog is a concept that belongs on every project schedule. It represents work that is real, productive, and valuable, but not on the critical flow of the Takt sequence. It can be done at any point within a defined window on the project without disrupting the primary production sequence.

Think of it as a productive holding pattern. When a crew finishes their Takt zone ahead of schedule and the next zone is not yet ready, they do not start the next zone early, which would create congestion and interference. They do not send people home. They go work on the workable backlog.

The workable backlog gives crews a purposeful place to redirect their energy during buffer time. It keeps people productive, it advances the project, and it preserves the availability of those people to swarm a bottleneck when one is identified.

The Swarming Principle

In the Takt planning simulation that Elevate Construction uses in its boot camps, the secondary beams consistently become the bottleneck. They require more coordination and time than other elements of the structure. The team leaders who navigate the simulation successfully start saying it early: when you have capacity, swarm the secondary beams.

Swarming is not the same as throwing more people at a problem indiscriminately. Swarming means using existing, onsite project resources to support the bottleneck activity in the ways that actually help it move faster: staging materials ahead of the crew, clearing access, making sure the forklift is available to the bottleneck trade instead of tied up elsewhere, ensuring the crane or hoist gives that trade priority.

Here is what swing capacity activation looks like in the field:

  • A trade partner with a five person crew finishes their Takt zone ahead of schedule and shifts one person to workable backlog while the other four prepare for the next zone
  • The superintendent identifies that the secondary beam install is running behind and directs the workable backlog person to stage materials for that crew and clear the hoist schedule to prioritize their lifts
  • The bottleneck gets support from within the existing project team without onboarding a new subcontractor, renegotiating contracts, or disrupting any other active workflow

That is swing capacity producing flow.

Why This Matters on Every Project

The projects that crash land in the final weeks are almost always projects where no swing capacity was maintained. Every crew was running at 100% capacity all the time. There was no workable backlog. When bottlenecks appeared, the only option was to throw new resources at the problem, which created congestion, coordination overhead, and rework.

Planning swing capacity into the project from the beginning is what prevents that scenario. It requires discipline: the discipline to not fill every crew to maximum, the discipline to maintain a workable backlog that crews can be directed to, and the discipline to redirect swing capacity to bottlenecks rather than letting it drift into free capacity over time.

If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow. Swing capacity and workable backlog are standard components of Takt planning and integrated control.

On we go.

Frequently Asked Questions

How do you identify what qualifies as workable backlog on a specific project?

Workable backlog is work that is ready to be performed, is within the skill set of the crew being redirected, and can be done at any point in a defined window without affecting the Takt sequence. It might be prefabrication of assemblies, installation of items ahead of the primary sequence, punch list correction of completed areas, or site cleanup and logistics tasks that advance the project without entering the active production zones.

How much swing capacity is appropriate for a project?

There is no universal answer, but the goal is just enough to absorb normal variation and respond to a bottleneck without tipping into free capacity. For crews, one additional person per four to six core crew members is a reasonable starting point. For time buffers, a cycle time of 80 to 90% of the Takt time gives enough room to absorb routine variation.

What is the difference between swing capacity and having too many people on a project?

Free capacity is people with no defined place to direct their energy who are effectively being paid to wait. Swing capacity is people with a productive workable backlog assignment who are also available to redirect to a bottleneck. The difference is in whether the additional capacity has a purposeful place to go at all times.

How does the workable backlog concept integrate with Last Planner and the weekly work plan?

The workable backlog should be identified in the pullplan and maintained in the weekly work plan as a standing set of tasks available to crews with buffer time. Superintendents and foremen then direct crews to the backlog when buffer time appears rather than improvising on the spot.

Can swing capacity be used at the superintendent level as well as the crew level?

Yes. A superintendent who has enough systems and prepared planning that they are not in constant firefighting mode has their own form of swing capacity. That capacity can be directed to coaching a struggling crew, supporting a bottleneck trade partner, or conducting quality inspections. The principle applies at every level of the project hierarchy.

 

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.

You Are the Captain! – Keep the Ship Afloat!

Posted on by Danny Jiménez⁩
Read 18 min

Are You the Captain of Your Ship? Seven Things Every Senior Superintendent Must Own

If you were the captain of a ship, what would your responsibilities actually be? Not the inspirational version. The operational version. What would you have to own, manage, and maintain to keep that vessel and everyone on it moving safely toward the destination?

Jason Schroeder has been developing this framework for the Elevating Construction Senior Superintendents book, and it is one of the clearest maps yet of what a senior superintendent’s job actually requires.

One: Stock the Ship

No captain would let a ship leave port without verifying that every provision was loaded. Food. Water. Fuel. Safety equipment. Everything needed to sustain the crew and the mission for the full duration of the voyage.

On a construction project, that is procurement. Materials are not optional, and they are not the project manager’s or project engineer’s primary responsibility. They are the superintendent’s. The superintendent has to make sure that every material needed to build the project is identified, ordered, tracked through fabrication and shipping, received on site with adequate buffer, and staged in the supermarket where it needs to be when the crew needs it.

Not “I delegated that to the PE.” Not “the subcontractor handles their own material.” The superintendent is ultimately responsible for making sure the ship is stocked. A procurement meeting weekly with a functioning procurement log is not overhead. It is navigation.

Two: Make Sure Teams Function at Every Level

A ship that has a functioning bridge but malfunctioning engine rooms, broken communications below deck, and untrained crew in critical departments does not sail well. The senior superintendent’s job is to make sure that every team on the project, at every fractal level, is functioning.

That means the leadership team. The area superintendents. The foremen. The crews. The administrative support. Every layer of the project organization has to be built, maintained, and held to a standard. Dysfunctional teams at any level will eventually surface as project problems, whether or not they are visible from the top.

Three: Make Sure People Are Trained

A ship captain does not accept poorly prepared crew and blame the admiral for sending them. The captain’s job is to make sure that everyone on the ship knows how to do their job and can fill in for their backup when needed. Training is not optional. It is the captain’s responsibility.

On a construction project, this means the senior superintendent ensures that their team members, including foremen, assistant superintendents, and field engineers, are trained to the standard the project requires. It means making sure that trade partner crews understand expectations, safety requirements, and quality standards before they begin work. It means building a project culture where training happens continuously, not just at onboarding.

Accepting undertrained people and hoping for the best is not leadership. It is abdication.

Four: Make Sure Systems Are Working

Every critical system on a ship must function: propulsion, communications, navigation, sanitation, electrical. Each requires maintenance, monitoring, and a backup.

On a construction project, the systems are different but the principle is identical. The logistics system. The safety system. The quality system. The Last Planner system or Takt planning system. The parking and site access system. All of them must be operational, maintained, and effective. A superintendent who allows critical project systems to degrade because they are busy with other things has allowed the engine room to go dark while managing the bridge.

Five: Know Where the Ship Is Going

The captain knows the destination, the course, and the mission. They do not leave port with a vague sense of direction.

The senior superintendent’s equivalent is the master schedule, expressed through a Takt plan. Every person on the project must know the substantial completion date and understand their role in getting there. Long range planning is the senior superintendent’s responsibility. If no one on the project can describe the production sequence from now to turnover, the ship does not have a course.

Six: Make Sure People Know How to Get There

Knowing the destination is not enough. The crew needs to know how each watch, each day, each week connects to the overall mission. The captain ensures that the navigational plan translates into action at every position on the ship.

On the project site, this is the translation of the master schedule through the six week look ahead, through the weekly work plan, down to the day plan. Each person on the project needs to be operating in a planning rhythm that connects their daily work to the overall trajectory. If that rhythm does not exist, the project is being navigated by feel.

Seven: Keep the Ship Afloat

This is the one that matters most in the moment of crisis. The MS Estonia, a ferry crossing from Tallinn to Stockholm, sank in September 1994 with 852 people on board. Investigators found that the bow door locks had failed in a storm. The water entered slowly, out of the field of view from the captain’s position. By the time the list was evident, recovery was impossible.

The lesson is not about storms. It is about visibility. The Estonia’s leaders could not see what was happening below the waterline. They did not know the ship was taking on water until it was too late to correct.

Construction projects take on water the same way. A team gets out of balance. Design changes accelerate. Two or three trade partners begin to fail simultaneously, which is manageable, but three or four failures at once overloads the recovery capacity. The superintendent who is not productively paranoid about early signals of imbalance will not see the list until the project is already in crisis.

Here is what that looks like in practice:

  • The team is taking on too much administrative work relative to its size, which is a sign that capacity is being overwhelmed
  • Three or more trade partners are simultaneously behind or failing, which is a sign that the support system cannot absorb the correction burden
  • The schedule is being driven by reactive heroics rather than systematic planning, which is a sign that flow has broken down
  • RFI and submittal volumes are spiking beyond what the team can process without falling behind, which is a sign that design completeness is affecting production

Each of these is a bow door signal. The superintendent who sees them early can correct course. The one who does not will be explaining a crash landing when it is too late to prevent one.

If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow. The seven responsibilities of the captain are the foundation of what Elevate Construction teaches and develops in senior superintendents and project leaders across the industry.

The Challenge for Every Superintendent

Walk through the seven responsibilities right now against your current project. Is the ship stocked? Are teams functioning at every level? Are people trained? Are systems operational? Does everyone know where you are going? Does everyone know how to get there day by day? And are you watching for the signals that the ship is taking on water before it lists?

Honest answers to those seven questions will tell you where your next 30 days of leadership energy needs to go.

On we go.

Frequently Asked Questions

Why is procurement specifically the superintendent’s responsibility and not the project manager’s?

Because the superintendent is accountable for field production, and field production stops without materials. The project manager supports procurement, but the person who owns the outcome of whether crews have what they need to build must be the person accountable for building. Delegating procurement ownership away from the field leader creates a gap in accountability that shows up as material delays and production loss.

What does a functional six week look ahead actually contain?

It identifies all the work that needs to be made ready in the next six weeks: materials that need to arrive, submittals that need to be approved, trade partners that need to be mobilized, design questions that need to be answered, inspections that need to be scheduled, and any constraint that could prevent work from proceeding as planned. The six week look ahead is a constraint removal tool, not a progress report.

How do you know when your project team is approaching its capacity limit?

When the speed of reactive problems is outpacing the team’s ability to address them. When the same fires are recurring rather than being permanently resolved. When team members are consistently working beyond sustainable hours without a corresponding increase in outcomes. When simple things start taking longer than they should. These are the signals of a team approaching its limit.

What is the most common system failure on construction projects?

The quality system. Most projects have a quality program on paper that does not translate into consistent field behavior. First in place inspections get skipped under schedule pressure. Ongoing inspection cadence breaks down. Closeout inspections are rushed. The result is punchlist scope that could have been prevented, and an owner experience that does not match the effort the team put in.

Is the captain of the ship metaphor specific to senior superintendents, or does it apply to project managers as well?

It applies to both, with different emphasis. The senior superintendent’s ownership is focused on the field: procurement, crew training, site systems, production rhythm, and team health. The project manager’s ownership is focused on the commercial environment: contract, financials, owner relationship, design, and trade partner agreements. Together they are the dual command of the ship. Either one operating without the other creates a gap that will surface as a project problem.

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.

    Related Books

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

    Related Books

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

    Related Books

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

    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