Contact us

Month: May 2026

Am I Wounded? Feat, Katie Schroeder

Posted on by Danny Jiménez⁩
Read 32 min

The Story You’re Telling Yourself: Why Wounded Leadership Destroys Construction Teams

Katie Schroeder is on this conquer the world with education and continuous improvement coaching, self-improvement program, really doing a lot of great things. She’s been sharing a lot of things with Jason, and she sent him a feminine and masculine divine identity versus wounded identity or behaviors chart. Jason thought this was too good to not share. Katie can’t remember where she found it, but she’ll think about it as they go. Why did she think it was really cool?

“I think it’s cool because this chart basically lists the feminine characteristics and masculine characteristics and kind of helps us identify when we’re feeling a certain way, or perhaps when our spouse or someone that we’re interacting with is feeling a certain way. We can kind of see where they’re at on the chart and then maybe lead from a more compassionate space. Seeing that maybe they’re just coming from a wounded place.”

Which goes back to Brene Brown’s podcast with Russell Brand where she talked about how everybody is doing their best. When you can recognize that sometimes people are just really deeply wounded, that it’s nothing personal, and maybe there’s even something you can do to help them or at least be compassionate.

When Katie sent it to Jason, he kind of took it as a way to identify where somebody was and not to be so defensive about it. But now he sees that this is a tool to kind of show up in a way where you can connect.

The Divine Feminine vs. The Wounded Feminine

The divine feminine qualities, the best version of the qualities you possess, would be attributes you would find in divine parents. The divine feminine qualities are intuitive, grounded, receptive, reflective, strong with boundaries, empathetic, compassionate, magnetic, supportive, vulnerable, authentic, flows through life effortlessly surrendered, open, trusting, creative.

The characteristics you find in the wounded feminine are insecure, needy, codependent, manipulative, inauthentic, over emotional, victim mentality. When do people go towards their divine nature and when do they show up in the wounded? Why is it important for us to know?

Katie thinks about it for herself. When she feels herself acting in one of these wounded spaces, she’s allowing others to affect her and giving her power away, letting someone else be in control of her emotions. Therefore she shows up in a way that is not her most empowered self.

For Katie, not over emotional, but definitely insecure or manipulative would be traits she relates to and exhibits. While she’s talking, Jason thinks it’s okay to feel these things. It’s okay if you feel insecure and needy or whatever, but it’s nice to know where home is.

Here’s what Jason was thinking: there are people who would define their ideal woman as codependent, really needy. “I want my woman to really need me, you know?” And then on the man side, wounded masculine, this is somebody who’s speaking from a wounded standpoint: aggressive, withdraws, avoids people, competitive. Some of those words would describe what you would call the typical rugged American male.

Where you hear like toxic masculinity, which is an overused buzzword and oversimplified, in all reality there is a form of masculine that is divine, that is your best self, your most empowered masculine self. Or there is when a male is wounded and he comes across in that way.

Why This Matters for Construction Leadership

The reason this was important to Jason, you’re probably wondering why this makes sense to have on a construction podcast. He really wants to do away with as much as possible the concept that superintendents have to be these controlling, aggressive, withdrawn, non-emotional, evasive, non-approachable, competitive, somewhat abusive person. Get away from that towards the divine masculine.

Jason will read them since this is the male part. Our divine nature as masculine humans is deeply present, doesn’t judge, supportive, has discipline, focused, logical, confident, protective, honest, accountable, has integrity, humble, has boundaries, offers stability and security, responsible.

If we can move from the controlling, aggressive, withdrawn, unapproachable, competitive, abusive, somewhat unstable, bipolar image that some superintendents have, well most superintendents quite frankly, and project managers and leaders in construction have, and realize that we’re probably acting in that way because of a woundedness or an abuse or bad circumstances, and realize that we have permission to show up and love and realize we’ve got our light shine, Jason thinks that would really help in creating connection and encouraging collaboration and communication on project sites.

What do we do from here? Now that we know our divine nature is really one of transparency and openness and vulnerability, and it’s not this wounded negative behavior, and we don’t have to stay in that space, what do we do with this information? What would the challenge be for people?

Katie thinks the very basic thing is when we feel like, and nobody wants to be diagnosed. We hate that when someone’s trying to coach us just because they’re getting coached. Katie comes home, she’s going through these coaching programs, and she starts telling Jason coaching stuff, and he immediately chooses to get triggered. “Don’t you coach me.”

The one Jason’s been pushing back on most is when Katie tells him “Well, that’s just a story you’re telling yourself in your head” and he flips out. However, they’re going to talk about it in the second part of this podcast.

Leading With Compassion Instead of Reacting to Wounds

Nobody wants to be diagnosed by their spouse or someone they’re in a relationship with. But Katie thinks if you can, when you see behavior that is from the wounded side of male or female, and obviously each of us has a mix, it’s not just black and white, lead in a way that you’re not just reacting to their behavior and not allowing their woundedness to trigger you. Allow it to trigger something compassionate in you.

If you could see what everyone was going through behind the scenes, maybe somebody’s wife is going to be induced early or it’s stressful, you would automatically feel compassionate. You would give them so much grace and so much love. But we do not walk around with all the labels right on our chest like “Oh, hey, I’m dealing with an eating disorder or I’m dealing with a spouse that’s abusive.”

To close this section down and get into the next one, the words for the wounded feminine are insecure, needy, codependent, manipulative, inauthentic, over emotional, being a victim. We have the opportunity to step out of that space and show up differently, get coaching, get therapy, go to different programs.

Same thing with the masculine for these characteristics. If we’re controlling, aggressive, withdrawn, unapproachable, avoiding interactions with other people, too competitive, abusive, unstable, that means it’s coming from a wounded place and there’s an opportunity for healing. Jason’s purpose on the podcast is let’s not let these things define us or define roles or the image that we have, specifically in construction.

The Story We’re Telling Ourselves

Katie is in a coaching program and the model they teach is that things happen and they’re just circumstances. The circumstance itself is pretty neutral. But what happens is because of our past experiences and our thoughts about ourselves and our thoughts about others, we start to assign meaning to things that didn’t necessarily have that meaning. We kind of build up this little story.

Here’s an example. Jason did a training for some Norwegians last night. So he was working all night. This morning Katie had to take her girls to early morning seminary for church. She went to get the car keys and they weren’t there, the keys to Jason’s truck. They were on the key ring in his office.

Katie’s like “How rude are you to take your keys to your office knowing that I have to take these girls to seminary in the morning and I have to drive the van.” Do you see? She just created this story. When she knows in her heart, he’s just thoughtless. He just wasn’t thinking of her. But she’s turned it into “You’re not considerate. You never think about me. You don’t think about my feelings. You don’t care that I had to drive.” Katie’s cool wife, who’s cooler than Jason, gets to drive this big clunky 15 passenger van because he holds the keys in his office.

Here’s what happens with these stories:

  • Something simple happens and we start to tell ourselves these stories and we get mad and then we pretty soon want to hold them accountable.
  • Katie wants to go to Jason banging on the door while he’s doing his meeting and be like “Why would you take the keys? You’re rude. You’re not a good person, bro.”
  • That’s just the story she’s told herself about these keys when she genuinely knows if she can stop and calm down and come from an empowered space that he really is super thoughtless.
  • He just was walking around with his keys and took them out to his office, which is in the backyard at midnight.

If you can get to that point of clarity, then you can be like no emotions, move on, do the right thing. Which is the same concept they had in Leadership and Self-Deception. If you can go back and get clarity on any situation from a non-emotional standpoint, then you have the opportunity to do the right thing and respond right. That’s a huge thing. And maybe Jason’s too focused on construction, but just in his world, that’s something we really have to get better at. Not only in our relationships, but in our interactions at work.

Katie gives one more example. She told Jason the other day they don’t lock the bedroom door because the lock is broken and he forgot. That’s something applicable across the board. He forgot. She could tell herself he forgot because she’s not important to him or he forgot because he doesn’t care. When in all reality, he just got busy or wasn’t listening. Jason doesn’t even remember this.

In any situation, you can start telling yourself a story. “This behavior means this to me. And now I’m going to react in a way that’s ugly and I shouldn’t react that way.” Katie wants to be somebody that acts and is not acted upon. She always wants to be in charge of her emotions and in control of who she is and how she shows up and not be affected by someone who forgot something or who she thinks maybe didn’t care about her.

The Rats in the Barrel: Why We Pull Each Other Down

Jason totally agrees. He thinks it’s really helpful because you either can find out maybe what the other person’s story is and respond accordingly and then build from there. When it descends into chaos, it’s like “Why did you do this?” “Well, I didn’t do that.” And then it just starts an argument. Nobody’s listening. But if we started to realize that we’re most of the time just telling each other stories and we’re pulling each other down like rats in a barrel.

Jason loves this story. He has no idea if it’s true or not. But a story was told to him that people back in the day would fill up a barrel three quarters of the way full, put some fruit on the top and have a little board tilted up to the top of the barrel. When rats would come in to eat the rotten fruit, there was just a layer of fruit and water underneath. If you got one or more rats in there, as soon as one of them tried to crawl out, the other ones would grab hold and pull them back down.

Essentially, that’s what we’re doing if that story is true. Even if it’s not, it’s a good image. Emotionally, if somebody’s down or in a spot, we’re just pulling down all of the other people who aren’t there. We’re just in a negative spot and negative mentally. The people who are in a good spot, we’re letting people drag us down when we go to their space. Katie brings up the Max Lucado book You Are Special. These little wooden dolls would get little dots on them. The dots basically represented criticism or self-doubt or just little negative things.

Katie also saw a social media post the other day where somebody was rude and then the other person walked away and was really grumpy too. Out of nowhere, a little black ball showed up in their hand and then they passed that rudeness and that little black ball. It just keeps passing to other people. How do we stop the cycles? We stop telling each other stories. If your wife or your husband is emotional and ranting, that’s their story. That’s their reality. You don’t have to automatically absorb that. Katie thinks you have to walk that fine balance where you don’t want to be dismissive where it’s like “Oh, you’re just telling yourself a story. Here he goes again.”

But to try and look into your divine feminine because that’s where you have the empathy or the compassion or supportive or vulnerable. Same with masculinity. You’re maybe seeing your wife act in a manipulative way or needy and that frustrates you. But if you could see she needs some support right now or maybe she needs to feel protected.

Why Construction Leaders Are Wounded and What to Do About It

Katie totally agrees. And then tying it back to construction. Nobody knows the stress that a superintendent, a project superintendent goes through or a director or a PM or some of these foremen. Some of these people that are just in critical positions in construction, they literally get backed up into a wall and there’s no wonder. It’s really not a surprise that women and men in this crazy industry can become wounded.

This is an opportunity for us to get help, to get coaching, to get therapy. But also for each of us to be understanding and to be compassionate, to realize that everyone’s doing their best, even if somebody hurt you.

This is an extreme example, but if somebody robs your house, it’s still done from a positive intent. They’re getting money to support themselves. Even though that’s a radical concept and a radical example, most of the time anybody, even if they’re doing something that’s morally or ethically wrong, they’re doing something for a positive intent. It might not be ethical, it might not be moral, it might not be just, it might just be for survival. But the point is nobody woke up and said “Oh, I’m going to go be evil and mess with somebody today.”

Well, except for maybe five. Satan’s on the list. So there’s some bad people, but most of the people, would you agree that most people are doing their best? Katie agrees that most people are doing their best and sometimes their best is something that the rest of us might find horrific or damaging.

Jason’s not a Marxist and he doesn’t believe in communism and he doesn’t believe in the teachings of Karl Marx and circumstances in the environment. He’s not particularly fond of Freud. However, there are just so many different circumstances and pieces of our environment that shape who we are. We just don’t know what somebody is going through unless we’ve walked in their footsteps. If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow.

FAQ

Q: What’s the difference between divine masculine and wounded masculine leadership?

Divine masculine is deeply present, doesn’t judge, supportive, has discipline, focused, logical, confident, protective, honest, accountable, has integrity, humble, has boundaries, offers stability and security, responsible. Wounded masculine is controlling, aggressive, withdrawn, unapproachable, competitive, abusive, somewhat unstable. Most superintendents and project managers show up in wounded masculine because of stress, abuse, or bad circumstances. But we have permission to show up and love, to let our light shine, which helps create connection, collaboration, and communication on project sites.

Q: How do the stories we tell ourselves create conflict?

Things happen and they’re just circumstances. The circumstance itself is pretty neutral. But because of our past experiences and thoughts, we assign meaning that wasn’t necessarily there and build up a story. Katie’s example: Jason took his keys to his office at midnight. She created a story: “How rude are you, you never think about me, you don’t care I had to drive the van.” When in reality, he was just thoughtless, walking around with keys at midnight. That story makes her want to bang on his door and hold him accountable for being rude when he just forgot.

Q: What should I do when I see someone acting from a wounded place?

Don’t just react to their behavior and don’t let their woundedness trigger you. Allow it to trigger something compassionate in you instead. If you could see what everyone was going through behind the scenes, you would automatically feel compassionate and give them grace and love. But we don’t walk around with labels on our chest. Lead from empathy and compassion. Look into your divine feminine or masculine traits: empathetic, supportive, protective, offers stability. They might just need support or to feel protected.

Q: Why do construction leaders end up wounded?

Nobody knows the stress that a superintendent, project superintendent, director, PM, or foreman goes through. People in critical positions in construction literally get backed up into a wall. There’s no wonder, it’s really not a surprise that women and men in this crazy industry can become wounded. There are so many different circumstances and pieces of environment that shape who we are. We don’t know what somebody is going through unless we’ve walked in their footsteps. This is an opportunity to get help, coaching, therapy, and for each of us to be understanding and compassionate.

Q: What does it mean that everyone is doing their best?

Most people, even if they’re doing something morally or ethically wrong, are doing something for a positive intent. It might not be ethical, moral, or just. It might be for survival. But nobody woke up and said “I’m going to go be evil and mess with somebody today.” Most people are doing their best and sometimes their best is something the rest of us might find horrific or damaging. If you can get clarity from a non-emotional standpoint, you have the opportunity to do the right thing and respond right instead of reacting to the story you’re telling yourself.

On we go.

If you want to learn more we have:

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

Discover Jason’s Expertise:

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

On we go

Project Engineer Guide to Payments & Contracts (Pay Apps, Subcontracts, and Risk)

Posted on by Danny Jiménez⁩
Read 21 min

Payments and Contracts: Why Getting Trades Paid Is One of the Most Important Things a PE Does

There is a version of project administration that believes its job is to be thorough. Every step documented. Every requirement verified. Every submission reviewed against a checklist before it moves forward. And there is nothing inherently wrong with thoroughness. The problem is when thoroughness becomes a mechanism for delay when the documentation standard, the billing cycle, the review process, or the submission requirement becomes a tool that sits between a trade partner and the payment they have already earned by performing the work.

The average wait time for payment, for a consultant working with some of the largest general contractors in the industry, is nine months. Not ninety days. Nine months. On $5 million of annual revenue, with diligent accounts receivable management and proactive follow-up, the average accounts receivable sits at $1.3 million. The average bank account balance runs between $5,000 and $150,000. Payroll is $180,000 per month.

That is not a cash flow problem. That is a system that has made trade partners and service providers into involuntary lenders for projects they are not financing. And the PEs and PMs who allow that to happen through inattention, through complexity, through negotiation games, through letting pay applications sit in an email inbox are failing the people who do the actual work of building.

What Contracts Are Actually For

A contract is not a defensive document. It is not a liability shield. It is the agreement that allows a trade partner to come to the project and do their work with clarity about what is included, what is excluded, what they will be paid, and when. A well-written contract protects both parties by eliminating ambiguity before ambiguity becomes a dispute. A poorly written contract one with vague scope, unclear inclusions and exclusions, or a schedule of values that does not tie money to the work being done is a dispute waiting to happen, and the dispute will cost more than the writing would have.

The PE’s responsibility in contracting starts with making sure the scope of work is clearly identified. Inclusions and exclusions need to be spelled out specifically enough that both parties can look at the same piece of work and agree on whether it is in the trade’s scope. The schedule of values needs to be broken out in enough detail that money can be tied directly to progress not in broad lump sums that make payment disputes inevitable, but in line items that reflect the actual sequence and components of the installation.

When that work is done properly at the front end, the rest of the payment process is cleaner because there is no ambiguity to exploit and no gaps to fill with negotiation. The contract becomes the document that enables the trade rather than the document that constrains them.

Why Paying on Time Is a Production Strategy

Here is the argument that tends to get missed in conversations about construction payment. Paying trades on time is not an ethical nicety layered on top of the production system. It is a production system requirement. When trades are not paid on time, their cash flow breaks. When cash flow breaks, their labor force gets thin. When their labor force gets thin, their crew productivity drops. When crew productivity drops, the handoff to the next trade slips. When handoffs slip, the Takt plan erodes. When the Takt plan erodes, the buffers get consumed. When the buffers are gone, the schedule is exposed.

The financial health of the trade partner is the operational health of the project. A general contractor that treats its trades as involuntary bankers is not protecting its own interests. It is undermining the production system it depends on to deliver the project. The money the GC holds past due is not savings it is a hidden cost being paid in productivity, schedule risk, and trade partner relationships that will be harder to rebuild on the next project.

And beyond the production logic, there is a human reality that never shows up on a financial statement. Trade partners are small businesses run by people who made the same choice that any entrepreneur makes to bet on their own craft and build something. Banks are reluctant to lend to them. Their margins are thin. Their overhead is real. When a GC holds their payment for ninety days, or six months, or nine months, those business owners are managing that gap with personal credit, lines they cannot easily obtain, and constant stress that follows them home to families who depend on those paychecks flowing. Retainage compounds the problem by withholding a percentage of earned money well past the point where the risk it was supposed to manage has passed.

This is not a rant against the system. It is a description of what the system currently does to people, so that the PEs and PMs who can change it at the project level understand what is actually at stake.

The PE’s Specific Responsibilities in Payment Management

The project engineer, working with the PM, owns the payment process from the trade’s first invoice through the final retainage release. That means proactive management of every step not reactive processing after someone follows up.

Pay applications need to be set up in a format that makes submission and approval straightforward. The schedule of values should be built with the trade’s input so it reflects the actual sequence of their work. The billing cycle should be communicated clearly at the start of the project so there are no surprises about when invoices are due or when payment is expected. When a pay application comes in, it should be processed promptly. Not held. Not failed for formatting issues that do not affect the substance of the payment request. Not sat on in an email inbox waiting for the next cycle because nobody followed up.

When a pay application has a genuine issue missing backup, scope that is overbilled relative to progress, an executed change order that has not been incorporated the PE’s job is to communicate that issue specifically, clearly, and promptly, so the trade can correct it and resubmit without losing a billing cycle unnecessarily. Using technical requirements as delay mechanisms is not administration. It is disrespect in paperwork form.

Change order management is equally important. Change orders should be written, priced, and executed as close to the event as possible not batched at the end of the project when the scope is hard to verify, the pricing is inflated by uncertainty, and the negotiation has become adversarial. A PE who manages change orders proactively, keeping them current with the work as it happens, protects both the trade and the owner from the disputes that late reconciliation always produces.

And retainage should be released as fast as the contract and the lien waiver process allow. The standard practice of holding retainage until the very end of the contractual window, when the trade’s risk to the project has been over for months, is not a protection mechanism. It is a habit that keeps trade partners in the banking business long past the point when they should have been paid and moved on.

Warning Signs That the Payment System Is Failing the Trades

Before the cash flow crisis compounds into a production crisis, watch for these signals that the payment process has drifted from enabling the trades to burdening them:

  • Pay applications are sitting in an email inbox for more than a few days without action or a specific response identifying the issue.
  • Billing cycle timing is being used to defer payments by weeks when the pay application arrived on time and had no substantive errors.
  • Trades are following up more than once on the same payment before receiving a response or a resolution.
  • Change orders are accumulating without being executed because the negotiation is being deferred to the end of the project.
  • Retainage is being held past the contractual requirement or the practical risk window without proactive communication about when release will occur.

Every one of those signals is a trade partner absorbing a cost that belongs to the project administration system. Every one of them is a PE and PM choice that could be made differently.

Lean Administration: The Bare Minimum That Actually Works

The right amount of administration is the bare minimum required for clear communication, legal compliance, and trade enablement. Not more. Lean thinking applied to project administration means: every step in the payment process should add value to the outcome of getting the trade paid accurately and on time. Steps that add complexity without adding accuracy or protection should be eliminated. Requirements that create rework for the trade without improving the owner’s position should be examined. Documentation that nobody will ever read should not be required.

A PE who runs a Lean payment process is not cutting corners. They are respecting the trades enough to design a system that serves them rather than one that protects the GC at the trade’s expense. The goal is the simplest, most direct path from “trade submitted” to “trade paid” that maintains the legal and financial integrity the project requires. Every unnecessary step between those two points is waste and it lands on the trade partner’s cash flow, not on the project’s.

We are building people who build things. Getting them paid for what they build, on time, without games, is one of the most direct ways a PE or PM demonstrates that the people doing the work are valued. If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow and build the payment culture that treats trade partners as partners rather than lenders.

A Challenge for Builders

Open your current project’s accounts payable status this week and look at every trade partner invoice that is more than thirty days old. For each one: does the trade know exactly what is holding it up? Is the issue specific and correctable? Is there a date by which it will be resolved? If the answers are weak, the payment system is burdening your trades instead of enabling them. Fix it this week, not next billing cycle. They already did the work.

As Jason says, “Respect for people is not soft it’s a production strategy.”

On we go.

Frequently Asked Questions

Why does late payment from a GC affect the production system on the project?

Because trade partners’ financial health directly determines their operational capacity. When cash flow breaks, labor force thins, crew productivity drops, handoffs slip, and the Takt plan erodes. The money held past due is not savings it is risk transferred onto the production system that the GC depends on to deliver the project.

What is a PE’s specific role in managing trade partner payments?

The PE works with the PM to ensure contracts are set up with clear scope and a detailed schedule of values, that pay applications are processed promptly without unnecessary delay, that change orders are executed as close to the event as possible, and that retainage is released as fast as the contract and lien waiver process allow.

What does “Lean administration” mean in the context of payments and contracts?

It means the bare minimum required for clear communication, legal compliance, and trade enablement no more. Every step in the payment process should add value toward getting the trade paid accurately and on time. Steps that add complexity without improving accuracy or protection should be eliminated. The simplest, most direct path from submission to payment is the goal.

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.

Project Engineer Information Management: How to Stay Organized on a Construction Project.

Posted on by Danny Jiménez⁩
Read 21 min

Project Engineer Information Management: Getting the Right Information to the Crew in Their Zone

Picture the scene that every successful project moment starts with. A crew in their zone. A foreman with their team ready to install. Materials staged. Equipment available. Labor in place. And in the foreman’s hand or posted visibly in the work area a single, clear, visual installation work package that shows exactly what gets installed, in what sequence, to what standard, with all the relevant details from the drawings, specs, change orders, manufacturer requirements, and owner preferences consolidated into one coherent document.

That picture is the ultimate end of everything a project engineer does. Not the RFI log. Not the submittal tracker. Not the filing system on the project management platform. Those are all mechanisms. The destination is a crew with full kit in their zone, information included, who can complete their work package without stopping to hunt for something that should have already been in their hands.

When that moment happens cleanly, a PE did their job. When it does not happen when the foreman is calling the trailer for a detail, searching three locations in the project management software, asking the super to dig out a meeting minute from four weeks ago the information system failed, and that failure traces back to a PE who has not yet oriented their role around the crew.

What Advanced Work Packaging Actually Means

Advanced work packaging is a concept that carries a lot of weight in industry conversations and less clarity than it deserves. The simplified version is this: find the path of construction, break that path into component assemblies or work packages, and link the design, engineering, procurement, and construction activities together as a single integrated production system. The output is an installation work package an IWP that gives the crew in the field the equivalent of an IKEA kit of parts. Every component is identified. The assembly sequence is clear. The information and the materials arrive together, and the crew assembles the work on site from a prepared kit rather than from a scattered information environment.

That is the model. And the project engineer is the person responsible for building that kit from an information standpoint. Not once, at the start of the project. Continuously updating, clarifying, and consolidating as the design evolves, as RFIs get answered, as submittals get approved, as change orders get executed, and as the construction sequence moves through zones and phases. The IWP is a living document that reflects the current, accurate, complete information the crew needs for their specific scope in their specific zone.

The Real Problem: Information Scattered Across Thirty-Five Locations

Here is the conversation that happens when the IWP concept gets challenged. Someone says: we can’t provide that to the crews. They cannot haul information from zone to zone. And then comes the comment: it’s all on the project management platform. It’s all in one place. The crew just needs to know where to look.

No. It is not all in one place. The drawing is in one location. The spec section that governs that drawing is in another. The RFI that clarified the spec is in a third. The addendum that revised the drawing is in a fourth. The executed change order that modified the scope is in a fifth. The meeting minutes where the owner’s representative commented on the installation method are spread across three or four separate meeting records. The manufacturer’s installation requirements are attached somewhere in the submittal package. The owner’s top ten requirements are in a separate document entirely.

That is not information management. That is information storage passive, fragmented, and hostile to the crew that needs to use it. The project engineer’s job is to take everything from all thirty-five of those locations and consolidate the relevant portions into one installation work package for each work package the crew is about to execute. Highly visual. Properly summarized. Not too much text. A single front page that shows the crew what they are building and what the expectations are. And everything they need to do it correctly, in one place.

When the super and the field engineer are spending their day hunting through project management platforms to find information that should already be in the crew’s hands, the project will spiral into chaos. The information system failed them. The PE’s job is to make sure it does not fail them.

The Trade Partner Preparation Process as the Information Assembly System

The IWP does not get built in a single sitting. It gets assembled continuously through the trade partner preparation process every meeting, every coordination event, every RFI resolution, and every submittal approval is an opportunity to pull more information into the package.

The buyout and contracting phase establishes what the trade is contracted to build and what standards apply. The pre-mobilization meeting confirms the setup requirements and the information the trade needs before they can mobilize effectively. The pre-construction meeting gathers submittals, clarifies RFIs that are outstanding before work begins, establishes the quality and safety documentation requirements, and identifies what the owner requires in addition to what the contract specifies. Pull planning sessions identify what information needs to be in the crew’s hands by specific dates to keep the production system flowing. Lookahead reviews flag information gaps that could become zone stops if not closed before the crew arrives. Weekly work plan preparation confirms that the IWP for the upcoming scope is complete before the week starts.

Every one of those touchpoints is a PE adding information to the package. The cumulative result by the time the crew is standing in the zone ready to work is an IWP that reflects everything from the design, the contract, the coordination, the owner’s requirements, and the construction sequence. The crew should not have to ask a question that the IWP does not already answer.

What Breaks When the Information System Breaks

The damage from a broken information system travels fast and lands on everyone. When RFIs sit open without a Lean management system tracking their urgency against the construction sequence, design gaps arrive at the field as surprises instead of as resolved clarifications. The crew stops. The super improvises. The improvisation may or may not be consistent with what the engineer will eventually answer. Rework becomes likely.

When submittals are not tracked against procurement lead times, the approved product arrives late or the wrong product arrives because the submittal was never coordinated against the procurement log. The crew’s material is not there or is not the right material. Another stop. Another restart that costs more than the original schedule showed.

When drawings are not kept current with addenda, bulletins, and RFI revisions, the crew installs from outdated information. The quality issue surfaces at inspection or at closeout, and the rework cost is multiples of what a current drawing would have cost to maintain.

When permissions special inspections, fire marshal approvals, air barrier tests, commissioning signoffs are not tracked on a log against the construction sequence, the crew finishes the work and then waits to have it inspected before they can move on or close the zone. The buffer gets consumed not by production variation but by an administrative failure that should have been closed weeks earlier.

Every one of those failures has the same root. The PE was not managing information as a production system. They were managing it as a filing system, and filing systems do not protect crews.

Warning Signs That Information Management Is Failing

Before the schedule and quality consequences compound, watch for these signals that the PE’s information system is not oriented toward the crew:

  • The foreman is calling the trailer for details that should already be in the work package, more than once per week.
  • RFIs are open past the date when the construction sequence needs the answer, and nobody has escalated the urgency.
  • The drawing set in the field does not reflect current addenda, bulletins, or RFI revisions.
  • The procurement log is not being tracked against the Takt plan, and long-lead items are appearing as surprises rather than as managed risks.
  • Submittals are being processed on a review cycle timeline rather than a construction-sequence timeline, meaning approved products are arriving late for the zone that needs them.

Any one of those signals means the PE’s information system is serving the documents, not the crew. The fix is an orientation reset: every log, every system, every tracking tool exists to ensure that crew in that zone has full kit. That is the only measurement that matters.

The Maestro of Information

The project engineer is the maestro of project information not the archivist, not the document manager, not the platform administrator. The maestro. The person who knows what information exists, where it lives, what state it is in, and how to get the right piece to the right person at the right time in a form they can actually use.

That role requires a real system. A Lean RFI management process that tracks every open item against the construction sequence. A submittal log that is synchronized with the procurement log. Current drawings posted digitally in real time whenever an addendum, bulletin, or RFI revision changes the scope. A file structure that makes the right information findable in under a minute. Communication flows that tell trade partners exactly what they need to know, when they need to know it, without requiring them to dig. And project management tools that support the trades rather than becoming another place the information goes to get lost.

We are building people who build things. The project engineer who masters information management is building the environment in which every crew can perform at their best because what they need is already in their hands when they step into the zone. If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow including the PE information management systems that keep information moving from design to installation without a single unnecessary stop.

A Challenge for Builders

Pick one active work package on your current project and run a full kit check on the information. Is there a single document the crew can install from, or is the relevant information sitting in thirty-five different locations? Is the drawing current with all RFIs, addenda, and bulletins posted? Are the spec sections, manufacturer requirements, change orders, and meeting minute decisions that affect this scope consolidated into one place? If the answer is weak, the PE owns that gap, and it should be closed before the crew steps into the zone.

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

On we go.

Frequently Asked Questions

What is an installation work package and what should it contain?

An installation work package is a single, visual, crew-ready document that consolidates everything a crew needs to install their scope in their zone drawings current with all revisions, relevant spec sections, manufacturer requirements, change order scope, owner requirements, material lists, and installation instructions.

Why is having information “on the project management platform” not the same as having full kit?

Because project management platforms store information they do not consolidate it. Drawings, specs, RFIs, addenda, change orders, meeting minutes, and submittal packages live in separate locations. The PE’s job is to pull the relevant pieces from all those locations and assemble them into a single installation work package the crew can actually use in the field.

What happens to the project when PE information management breaks down?

The crew stops. Design gaps arrive as surprises. Wrong materials get installed from outdated drawings. Inspections get missed because permissions were never tracked against the schedule. Rework follows every one of those failures.

 

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.

Where Balance Comes From

Posted on by Danny Jiménez⁩
Read 20 min

Where Balance Actually Comes From: The Lean Truth Nobody Is Saying

The work-life balance conversation has produced a generation of misunderstandings. The message that people need rest, relationships, health, and a life outside of work is true. The conclusion that some people have drawn from it that the path to balance is commitment reduction, less mental focus, more distraction at work, and a general dialing back of engagement is false. And in construction specifically, where the field depends on people who show up fully present and technically sharp, that misunderstanding is doing real damage.

Balance does not come from less. It comes from Lean. And until more leaders say that clearly, directly, and without apology, the people who need to hear it will keep misinterpreting the message and producing the opposite of what the original intention was not more balance, but more chaos in both directions.

The Misinterpretation That Creates Non-Performers

Here is the scenario that plays out in organizations that have been communicating about balance without being specific about what produces it. A worker or a leader hears the message that work is not everything, that family matters, that rest matters, that relationships matter. They genuinely take that to heart. But without the Lean framework that explains how to actually create the time and mental space for those things, they draw the only available conclusion: I should do less at work. Focus less. Commit less. Be less mentally present during the hours I am there so that I can save some of myself for after.

The result is someone who is distracted at work, behind on their tasks, creating problems for the people downstream of them, and ironically more stressed, not less, because the backlog of undone work follows them home. The balance they were seeking is farther away than when they started. And the team around them is absorbing the cost of their reduced performance in rework, delays, and the friction of working alongside someone who is not there even when they are physically present.

That person was not told to become useless at work for the sake of their personal life. That is not what balance means. What they were told, or should have been told, is to become Lean which is a completely different path to the same destination.

What Actually Creates Balance

Balance comes from a personal organization system that allows a person to be fully present and fully productive during the time they are working, so that the time outside of work is genuinely free rather than secretly contaminated by unfinished business and unresolved mental loops.

The specific practices that build that system are not complicated, but they require discipline to implement. A to-do list that captures everything that needs to be done, so the brain is not spending energy trying to hold it all in working memory. Time blocking that assigns focused work to specific windows, so every hour has a purpose rather than being managed reactively. Email discipline that treats external communication as a scheduled activity rather than a continuous interruption. Buffers between meetings so that commitments have the room to land before the next one begins. One-piece flow that brings full focus to a single task through completion rather than batching and switching. Full kit before starting work so that the task can be finished in one cycle rather than stopping, gathering, and restarting.

These are Lean principles applied to personal productivity. They are the same logic that makes a zone on a construction project flow cleanly applied to a human brain and a work calendar. And the outcome they produce is the same: more actual output per unit of time and energy, which means the time outside of work is genuinely available for the things that make a life rather than filled with the spillover of a day that never achieved flow.

The Book That Names the System

David Allen’s Getting Things Done is one of the most complete articulations of personal productivity as a system. Its central insight is that the brain is not a reliable storage device for open loops every unfinished task, unresolved commitment, or uncaptured idea that lives in someone’s head is consuming working memory and generating low-level stress that follows them everywhere. The solution is to get everything out of the head and into a trusted system, so that the brain can focus fully on the work in front of it rather than managing the anxiety of everything it might be forgetting.

That principle is Lean thinking applied to the individual. It is the personal equivalent of a production plan: capture, prioritize, sequence, and execute in one-piece flow. The person who has built that system can close their laptop at the end of the workday and actually be present for their family because the open loops are closed or captured. The person who has not built that system brings every unfinished item home mentally, even when they are physically somewhere else.

Balance is not a time problem. For most people in demanding roles, it is a system problem. And the system is learnable.

Why Generation-Specific Messaging Makes This Worse

There is a specific communication pattern that has gained traction in conversations about younger workers a framing that treats high performance expectations as inherently problematic, that positions commitment as a form of exploitation, and that validates distraction and divided attention as forms of self-expression. Some of that conversation is responding to real problems: burnout, poor leadership, unreasonable expectations, work environments that genuinely do not respect people’s lives outside of work. Those problems are real and worth addressing.

But the response that teaches people to be less organized, less focused, and less committed to their craft as a form of self-protection is not a response to exploitation. It is a response that makes people worse at their work, more stressed overall, and less able to create the genuine balance they are seeking. The advocacy that matters is not “work less” it is “work Lean.” Protect your energy through systems, not through disengagement. Build the personal organization that makes you more effective per hour rather than just fewer hours. Demand the kind of leadership and environment that makes Lean possible. That is the message that actually serves people.

Balance on the Jobsite and in the Office

The same principles apply at both levels. A superintendent who has a personal organization system who time blocks their morning walk, who captures roadblocks immediately into the right system, who runs a clear daily routine and is not managing by email can leave the site at the end of the day without the project following them home. A PM who batches everything, responds to every email as it arrives, never finishes a task before starting the next one, and has no capture system for open items takes the project home every night even when they are trying to be present somewhere else.

The Lean operating system on the project is what makes the team’s balance possible. Takt plans, pull planning, standard work, the morning worker huddle these all reduce the cognitive load that workers and leaders would otherwise carry through their day and into their evening. The construction version and the personal version are the same underlying principle: design the system to protect the people inside it, so that performance during work time is sustainable and time outside of work is genuinely free.

Warning Signs That the Balance Message Got Misunderstood

Before the non-performance pattern compounds, watch for these signals that the balance conversation landed in the wrong place:

  • A team member is physically present but mentally managing personal tasks, relationships, or distractions during core work hours, and performance is suffering.
  • The work-life balance message has produced someone who has reduced their commitment to training and professional development rather than building the systems that would make development sustainable.
  • A leader is less engaged in the production system fewer walk-arounds, less attention to the weekly work plan, less presence in the morning huddle and framing the reduction as self-care.
  • Open loops are accumulating because there is no personal capture system, and the stress from those open loops is being interpreted as a sign to work less rather than a signal to get organized.

Every one of those situations calls for the same response: not more encouragement to disconnect, but direct coaching on the personal organization system that makes genuine disconnection possible.

Build the System First

The path to balance is not subtraction. It is construction building a personal organization system that allows full presence during work time and genuine freedom outside of it. Vision and clarity documents. A single trusted capture system. Time blocking. Email discipline. One-piece flow. Full kit before starting. Buffers between commitments. These are the tools. They work. And they are learnable by anyone willing to treat their own productivity with the same seriousness that good builders treat their production systems.

We are building people who build things. That includes building the people who have the personal discipline to show up fully, perform excellently, and leave at the end of the day without the job following them home. If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow including the personal organization discipline that makes balance real rather than aspirational.

A Challenge for Builders

Look honestly at your own productivity system this week. Do you have a single trusted list that captures every open loop in your professional life? Do you time block focused work so that each task gets full attention through completion? Do you have a practice for closing the day that signals to your brain that the work is done? If the answers are weak, the balance you are trying to create will stay out of reach regardless of how many hours you reduce. Build the system. The balance follows the system. It does not come from doing less of the work it comes from doing the work in a way that leaves you genuinely free when you step away from it.

As Jason says, “Flow over busyness.”

On we go.

Frequently Asked Questions

What does it mean that balance comes from Lean rather than from doing less?

It means that genuine work-life balance is produced by a personal organization system a clear capture process, one-piece flow, time blocking, and full kit that allows full presence during work hours and real freedom outside of them. Doing less without that system just spreads the same stress over fewer hours.

Why is distraction at work not a path to better balance?

Because distraction does not close open loops it creates more of them. Every unfinished task and divided attention event generates cognitive load that follows a person home. The path to being genuinely present outside of work is performing with full focus during work, not fragmenting attention across both.

What personal productivity practices produce the balance that Lean promises?

A trusted capture system for all open commitments, time blocking for focused work, one-piece flow that finishes tasks before starting new ones, full kit before beginning any task, email discipline that treats communication as a scheduled activity, and buffers between meetings that allow commitments to land cleanly before the next one begins.

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.

Letting Lower-Level People Make Key Decisions

Posted on by Danny Jiménez⁩
Read 20 min

Letting Lower-Level People Make Decisions: The Difference Between Delegation and Abdication

There is a LinkedIn post archetype that has convinced an entire generation of leaders they are doing something courageous. It usually features a six-panel image. Panel one: the confident leader who lets their team make all the decisions. Final panel: the leader with their head down because no decisions are getting made correctly. The caption celebrates autonomy. The subtext celebrates chaos. And in the construction industry, where Lean systems take years to build and can erode in weeks, that archetype is doing real damage.

Here is the truth that gets lost in the empowerment narrative. Letting people make decisions is not inherently good leadership. It is good leadership when the people making those decisions are trained, proven, and capable of holding others accountable for the same standards. It is abdication when they are not when decision-making authority gets handed to people who have not yet internalized the system they are now in charge of maintaining. The difference between those two things is not subtle. One builds culture. The other erodes it.

Lean Entropy: What Happens When Systems Outlive Their Builders

Here’s the pattern that shows up on projects and inside companies that have done the hard work of implementing Lean. The system takes hold. Productivity doubles. Projects finish early. People are healthier and happier. The culture is measurably different from what it was before. Leaders celebrate the win. And then, quietly, the entropy begins.

Not from outside. From inside. An untrained person gets promoted because the company is scaling and bodies are needed. They have never fully implemented the system themselves. They have never gone through complete Lean training. They have never held a crew, a trade partner, or a fellow leader accountable for the standards. And now they are in charge. Now they are the general superintendent, or the area general, or the regional operations manager. And because nobody held them accountable for mastering the system before they were promoted, they are free to run it their way.

Their way means pulling pieces out. Deciding the morning worker huddle takes too long. Deciding the zone cleanliness standard is impractical. Deciding the pull plan cadence is more than the team needs. Deciding to let the superintendent’s messy site slide because it’s their job to figure out. Every one of those decisions, made independently and without accountability, is a brick removed from the system. And within months, the system that took years to build is rubble dressed up as autonomy.

Why Western Culture Makes This Worse

The commenter who started this conversation had worked globally with leaders across multiple industries and came to a clear conclusion. In Japan, you do not get promoted until you are a master. Not until you understand the system thoroughly. Not until you have proven you can execute it yourself and hold others accountable for doing the same. The culture of being an honorable contributor to the excellence of the whole of the company, the family, the craft means that mastery is the prerequisite for authority, not a credential that comes after the promotion.

In the United States, the approach is nearly the opposite. The cultural programming favors independence, individualism, and the sink-or-swim model where people get thrown into roles before they’re ready and expected to figure it out. Culturally, we celebrate the person who makes decisions quickly. We are suspicious of processes that require extended mastery before authority gets granted. And we have wrapped that cultural value in the language of empowerment so thoroughly that holding someone accountable for a standard has come to feel like the problem rather than the solution.

That framing is costing us the Lean systems we have worked hardest to build. Every time a leader looks at a VP or a GS who is dismantling the operating system and says “I have to let them lead at their level,” they are not showing respect for their colleague’s autonomy. They are abandoning every person who built the system every superintendent who put in the discipline, every trade partner who trusted the environment, every worker who showed up to a clean, organized, safe site and felt what a Lean project actually produces to the consequences of untrained decision-making.

The Only Promotion Standard That Protects the System

Here is the standard that should govern every promotion decision in a company that is serious about Lean implementation. Nobody gets promoted until they have proven they can run clean, safe, and organized projects the Lean way themselves, and can hold another team accountable for doing the same. Both conditions are required. Not just demonstrating personal mastery. Demonstrating the ability to reproduce the standard in others, consistently.

That standard is not punitive. It is the only honest measure of whether a person is ready for the authority being handed to them. If they cannot hold a team to the system, they cannot protect the system at scale. If they cannot demonstrate the standard on their own project, they will not hold it across a region. The promotion that skips that test is not a reward. It is a transfer of risk from the company to the system and the system will absorb that risk in the form of entropy, erosion, and eventually the loss of every gain the Lean work produced.

The Difference Between Standards and Control

The argument that usually gets made against this standard is that it is command and control. That it does not trust people. That it does not allow the creativity and ownership that produces great work. That argument confuses the standard with the person. Holding someone to a Lean operating system is not telling them how to think or blocking their creativity. The Lean system is itself the vehicle for creativity for solving problems, for finding better approaches, for improving every process through the PDCA cycle. What it is not is optional. The standard is not optional. The zone cleanliness is not optional. The pull planning cadence is not optional. The morning worker huddle is not optional.

Allowing someone to dismantle those things and framing it as trust is not trust. It is the abdication of leadership dressed in the language of empowerment. And it communicates something devastating to every person who built the system: your effort does not matter. Your sacrifice in learning and implementing and holding the line does not matter. What matters is that the new person feels comfortable making decisions, regardless of whether those decisions are destroying what you built.

Warning Signs That Lean Entropy Is Already Underway

Before the damage compounds, watch for these signals that the system is eroding from within:

  • A newly promoted leader is pulling key components out of the Lean system without going through the training that would help them understand why those components exist.
  • Leaders are walking past dirty, disorganized, or unsafe sites and deciding it is “that team’s job to figure out” rather than holding the standard.
  • Pull planning sessions are getting compressed, abbreviated, or skipped at the discretion of individual leaders who have not been held accountable for the outcomes of doing so.
  • Morning worker huddles are disappearing from projects run by certain leaders without any accountability from above.
  • The phrase “let them run it their way” is being used to justify the removal of non-negotiable standards rather than the delegation of legitimate decision-making.

Every one of those signals is the Lean system calling for a leader to step forward and hold the line. The system cannot protect itself. The culture cannot reproduce itself. Leaders do that trained, accountable, Lean-minded leaders who understand what they have and are unwilling to let it erode because they prefer to be liked rather than to lead.

What Real Delegation Actually Looks Like

Real delegation is not the absence of standards. It is the presence of a trained person who holds the standards independently because they have internalized them, not because someone is watching. That is the goal of Lean leadership development not to create people who wait for direction, but to create people who have absorbed the system deeply enough that they protect it instinctively, hold others to it consistently, and teach it effectively to the next generation of leaders.

That kind of delegation requires investment. It requires that the company build a training pipeline serious enough to produce genuine mastery before authority is transferred. It requires that promotion decisions be based on demonstrated capability rather than years of tenure or need to fill a seat. And it requires that the leaders at the top of the system hold their directors and GS’s to the same standard they hold the foremen and supers because entropy does not start at the bottom. It starts wherever the accountability stops.

We are building people who build things. That includes building the leaders who will protect the system when nobody is watching. If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow and build the leadership pipeline that produces mastery before authority rather than after.

A Challenge for Builders

Look at the last three promotions your organization made. Were those people trained and proven in the Lean operating system before they moved into the new role? Can they run a clean, safe, and organized project the Lean way themselves? Have they ever held a team accountable to the same standards? If the answers are weak, the entropy is already starting quietly, at the decision level, in the places nobody is looking closely yet. Go look now. Fix the pipeline before the system pays the price for the promotion that was made too soon.

As Jason says, “Respect for people is not soft it’s a production strategy.” And nothing disrespects the people who built a Lean system more than allowing an untrained leader to dismantle it in the name of empowerment.

On we go.

Frequently Asked Questions

What is the difference between delegating decisions and abdicating leadership?

Delegation gives decision-making authority to people who are trained, proven, and capable of holding others to the same standard. Abdication gives that authority to people who are not ready, and then frames the resulting erosion of standards as trust. The difference is whether the person receiving the authority can protect the system they are now responsible for.

Why does Lean implementation erode even in companies where it worked?

Because untrained people get promoted before they have mastered the system, and once they have authority, they make decisions that pull key components out often without realizing what those components are protecting. Entropy starts not at the bottom but wherever the accountability for the system stops being enforced.

What is the right standard for promoting someone in a Lean organization?

They should be able to demonstrate that they can run clean, safe, and organized projects the Lean way themselves, and hold another team accountable for doing the same. Both conditions are required. Personal mastery alone is not enough they must be able to reproduce the standard in others before being given authority over a broader system.

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.

Stop Call Wait Is Not Waiting

Posted on by Danny Jiménez⁩
Read 20 min

Stop, Call, Wait Is Not Waiting: The Distinction That Changes How Teams Respond to Problems

Waiting is one of the most destructive words in construction. Not because stopping is wrong, but because most people use waiting as a cover for doing nothing when doing nothing is never the right answer. Waiting for full design before planning starts. Waiting for the trade to resolve a procurement question before the log gets updated. Waiting for someone else to figure it out before picking up the phone. That kind of waiting is passive. It is a choice to stop value flow and stand still rather than take the next natural step that is always available.

And then there is stop, call, wait the Andon-based problem response that Toyota built into its production system and that construction is starting to apply through the Takt Production System. And on the surface, it looks like waiting. Stop the crew. Call the team. Wait before restarting. But it is not waiting at all. It is one of the most active things a team can do when something has gone wrong.

Understanding the difference between those two things between passive waiting and active problem resolution is one of the more advanced concepts in production system thinking, and it matters enormously for how teams respond under pressure.

The Standing Tactical Order: We Do Not Wait

Here is the standing tactical order worth writing on the wall of every trailer in construction: any time we wait, we fail. Not pause. Not stop to solve. Wait meaning do nothing fail. Anytime we batch, we fail. Anytime we don’t work in one-piece flow, we fail. Anytime we don’t use full kit, we fail. These are not guidelines. They are production laws with consequences that show up in the schedule, the budget, and the people every single day.

Waiting shows up everywhere in construction, often disguised as something else. We are waiting for the full design before we start the procurement log but a napkin sketch is full kit enough to begin building a supply chain framework, because the supply chain information exists and AI can help close gaps in the interim. We are waiting for the trade partners to be contracted before we begin procurement planning but you can start planning before the contract is inked because the project exists and the work has to happen. We are waiting on a response before we take the next step but there is always a next step that does not require that response. The question is whether the team is trained to find it.

Patton’s principle is useful here. In the field, he did not want messages saying they were holding their position. He wanted to know what the advance looked like. The same logic applies to every project team. Holding the position, waiting to move, staying still those are failure states, not strategic ones. There is always a natural next step. Taking it is not optional.

What Stop, Call, Wait Actually Is

Here is where the concept gets precise and the distinction becomes critical. Stop, call, wait was named specifically in the context of quality-at-the-source production control. And it sounds like it conflicts with the standing tactical order about waiting. It does not. It is a completely different kind of action.

Stop means you see something wrong, hear something wrong, feel something wrong, or learn from someone else that something is not right. In manufacturing, you hit the Andon cord or the button the signal that tells the line to pause. In construction, you stop the crew. You stop the train of trades. You stop the process that is generating defects, creating safety risk, or moving in the wrong direction. You stop it because starting it back up without fixing the problem will only make the problem more expensive.

Call means you immediately assemble the people who can help solve it. You call the team leader. You call the coordinator. You call whoever has the authority, the information, or the skill to contribute to the fix. You do not stand there. You do not wait for someone to notice on their own. You pull the right people into the problem right now.

And what happens after the call is not waiting. What happens after the call is that a leader gets appointed to coordinate the response. Information gets gathered. A plan gets made. That plan gets communicated to the team. The plan gets executed. And then only then does the work restart. Not before. Not when the plan is half-formed. Not before full kit is confirmed. You do not start the line back up until you know it will not produce the same defect again.

That entire sequence stop, assemble, diagnose, plan, confirm full kit, restart looks nothing like waiting. Waiting is the absence of activity. Stop, call, wait is the presence of focused, purposeful activity directed at solving a problem before it scales. The word “wait” in that sequence means hold the restart, not hold your effort.

The Conceptual Reframe: Stop, Call, Figure It Out

If the term itself creates confusion, the concept is better named: stop, call, figure it out with the team. Or stop, call, take the next natural step. The core principle is that there is always a next natural step available, and it is always the team’s job to take it. When the crew is stopped, the team’s next natural step is to diagnose. When the diagnosis is done, the next natural step is to plan. When the plan is made, the next natural step is to communicate. When communication is clear, the next natural step is to confirm full kit. When full kit is confirmed, the next natural step is to restart.

There is never a moment in that sequence where doing nothing is the correct option. Never a moment where the team should be sitting still waiting for something external to happen before they can act. The external thing the missing material, the design answer, the trade coordination decision is itself the target of the team’s active pursuit during the stop. You do not wait for it to arrive. You go get it.

The Distinction That Separates Productive Stops from Passive Ones

The clearest way to understand the difference is to look at what the team is doing during the stop. In a productive stop, every person in the response has a specific next action. The coordinator is gathering facts. The first planner is reaching out to remove the roadblock. The superintendent is looking ahead to see what downstream work can proceed safely while the stopped zone is being resolved. The foreman is documenting the situation for the buffer log. The PE is confirming what full kit looks like for the restart.

In a passive wait, the team is standing around. Talking about the problem without solving it. Pointing at who is responsible without organizing a response. Watching the schedule slip without activating a recovery path. The difference is motion specific, directed, value-adding motion versus inertia.

Watch for these signals that a stop has become passive waiting rather than active resolution:

  • Nobody has been appointed as the coordinator for the problem. The team is assembled but there is no single person driving the response.
  • The conversation is about blame rather than next steps. Who caused this is receiving more energy than what we do about it.
  • People are waiting for a response from someone else before taking any action of their own, when an action is available that doesn’t require that response.
  • The restart is being delayed by uncertainty that could be resolved by making a decision rather than by gathering more information.
  • The buffer log is not being updated, which means the stop is not being used to build the documentation that protects the project later.

Every one of those signals means the stop has drifted into passive waiting. The fix is to get specific: who owns the next action, what is it, and when does it happen.

Never Go to Sleep on a Problem

This principle was named plainly by a project director whose standard was direct and consistent: don’t go to sleep on this. What he meant was exactly this. Do not let a problem sit unattended overnight. Do not accept that the right next step is to wait and see what tomorrow brings. Find the next natural step and take it before the day is done.

That standard reflects the underlying production logic. Every hour a problem sits unsolved is an hour of production capacity the project cannot recover. Every day a stopped zone stays stopped without active resolution is a day of buffer consumption that will eventually show up in the schedule. The team that treats every stop as an active challenge something to be solved, not waited through is the team that protects its buffers and its people.

We are building people who build things. That includes building the reflex to act, the instinct to find the next natural step, and the discipline to hold the line until full kit is confirmed before restarting. If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow and build the production discipline that turns every stop into a solved problem rather than a waiting game.

A Challenge for Builders

Walk your project this week and watch what happens the next time work stops. How quickly does the team assemble? How quickly does a coordinator get appointed? How quickly does the diagnosis produce a plan? And how quickly does that plan confirm full kit for the restart? If the answers are slow, the team has drifted into passive waiting rather than active resolution. The fix starts with naming the distinction, training the response, and making it a standing expectation that every stop is the beginning of a solution, not the beginning of a pause.

As W. Edwards Deming said, “It is not enough to do your best; you must know what to do, and then do your best.”

On we go.

Frequently Asked Questions

What is “stop, call, wait” and where does it come from?

It comes from the Andon system in Toyota’s production model, where workers are empowered to stop the line when they detect a defect or quality risk. In construction, it means stopping the crew when something is wrong, calling the team to solve it, and not restarting until full kit is confirmed. It is an active problem-solving sequence, not passive waiting.

What is the difference between productive stopping and passive waiting?

A productive stop has specific next actions, an appointed coordinator, active diagnosis, and a clear path to restart. Passive waiting is inertia standing still, pointing at blame, or sitting on a problem until someone else resolves it. The distinction is whether the team is doing something directed at the solution while the work is stopped.

When should a crew be restarted after a stop?

Only when full kit is confirmed meaning the condition that caused the stop has been resolved, the plan for restarting has been communicated, and the team is confident the work will not produce the same defect or safety risk again. Restarting before full kit is confirmed simply restarts the 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.

We All Have a Pull in Us That Wants to Be Better

Posted on by Danny Jiménez⁩
Read 20 min

We All Have a Pull That Wants to Be Better: The Leadership Invitation Construction Needs

There are two ways to tell someone their habits are hurting them. One is to point at the habit and call it dumb. The other is to remind them of the part of themselves that already knows there is a better way, and invite them toward it. Both can be honest. Only one actually works. And the construction industry with all of its urgency, all of its standards culture, and all of its legitimate frustration at the gap between how things could be and how they usually are has defaulted almost entirely to the first one.

This is a call for the second. Not because grace is softer than standards. Because grace actually produces the change that standards without relationship almost never do. We all have a pull in us that wants to be better. The leadership challenge is not convincing people that improvement is necessary. It is creating the conditions where the part of them that already knows it can finally answer.

The Clean Desk That Started a Fight

Here is the specific moment that cracked this open. An AI graphic about a clean, organized desk got posted on LinkedIn. And multiple superintendents came onto the thread to push back. The argument: if a super is cleaning their desk, they’re not out in the field where they belong. Full chest, confident, certain they were right.

Here’s why that thinking is wrong. Nobody is saying a superintendent should spend hours maintaining their desk. A desk overhaul takes forty-five minutes. Maintaining it after that is not a time expense it is a habit. The same habit that produces an organized trailer produces an organized site. The same discipline that keeps a workspace clean produces the discipline to maintain zero tolerance in zones, in cleanliness standards, in pre-task planning. The way a leader performs with their desk is the same way they perform everywhere else. That is the principle. Not the desk itself.

The supers who push back on clean desks are often the same ones whose projects are chaotic, whose zones are cluttered, and whose teams are in perpetual firefighting mode not because they are bad people, but because they have been taught that visible busyness in the field is the only legitimate measure of a superintendent’s value. That training is wrong, and it produces sites that reflect it.

The Better Response

The temptation when confronting wrong thinking is to name it plainly. And sometimes that is necessary. But the LinkedIn commenter who offered this response to that moment had something better: we all have a pull in us that wants to be better. That is not passive. It is not a retreat from standards. It is an acknowledgment that the person who needs to change is not an enemy of improvement they are a person who has been pointed in the wrong direction by the environment they came up in, and who has a part of them that, if reached, will choose differently.

The invitation reframes the entire conversation. Instead of: your way is wrong and here is why you’re dumb. It becomes: there is a version of you that already knows what this could look like, and I’d like to talk to that person. That reframe does not lower the standard. It changes the approach for getting there from shame into a place people close and defend, to invitation into a place people step toward.

Why This Matters for Leadership on Site

The practical implications of this principle run all the way through daily site leadership. A superintendent who leads through frustration and criticism creates a team that hides problems. Nobody wants to bring the bad news to someone who responds to bad news by making the person delivering it feel like a failure. So the foremen stop bringing it. The problems stay hidden until they are crises. The superintendent then has more reasons to be frustrated, and the cycle tightens.

A superintendent who leads through invitation who assumes the person in front of them has good instincts that got poorly directed, who asks questions instead of announcing conclusions, who connects the team member’s own desire to do good work with the standard being requested creates a completely different environment. People surface problems early because the response is curiosity and problem-solving, not anger. People step toward the standard because they have been shown how it connects to something they already care about, not because they fear the consequence of falling short.

This is not softness. This is production intelligence. The culture of any site is shaped by the worst behavior the leader is willing to tolerate, and the most important behavior to watch is the one the leader models in the moment of frustration. Frustration will come. The question is what the leader does with it.

Reaching for the Good When You’re in It

There is something honest and important in acknowledging that this principle is not abstract it applies to the leader themselves, not just to the people they are leading. There are moments in any role where the frustration becomes real and heavy. Accounts receivable that has ballooned into a cash crisis while people keep asking you to resend the invoice you already sent three times. A meeting where nothing moved. A project where the same problem keeps surfacing in new forms. A day where everything feels stuck and the pull toward anger is stronger than the pull toward clear thinking.

In those moments, the invitation applies internally too. Can you reach for the part of yourself that knows how to respond well? Not suppress the frustration that is not the goal. But find the thread that leads back to constructive movement. Ask for what you need. Let the people who care about you help reset the system. Put your hands up if that is what it takes. Feel the pull toward better, and follow it.

That is what leadership development actually looks like in practice. Not the polished version delivered on a stage. The messy real version where a person in a hard moment makes the choice to reach for better rather than stay in the worse. And the team that watches them make that choice learns something they could not have learned from a handbook.

What “Reaching for Better” Looks Like in Construction

The practical version of this principle shows up in the decision moments that happen on every project every day. Watch for these specific places where the invitation matters more than the critique:

  • A foreman who does not know the Takt plan and is improvising in the field. The invitation: here is how this sequence is supposed to flow, and here is why it will make your week easier than what you’re doing now.
  • A trade partner who has never experienced a pull planning session and sees it as paperwork. The invitation: you know better than anyone what your crew can realistically install in a zone. We want to hear that before we commit to a date.
  • A superintendent who keeps information in their head because that is how they have always operated. The invitation: when the plan is in their head, the crew is guessing. When it is visual, they can perform. Let me show you what that looks like on a board.
  • A PM who has been measuring success by getting materials to the site without checking whether the site was ready for them. The invitation: the trades need the materials at the right time in the right zone. Here is how that changes when we sequence delivery to the production plan.

None of those are comfortable conversations. All of them assume the person being invited has a part of them that wants the better outcome. Most of the time, that assumption is correct.

The Essence of Lean as an Invitation

This is not separate from Lean. This is the heart of it. The production tools Takt, Last Planner, pull planning, full kit, zone standards are invitations to a better way of working. They are not demands. They are demonstrations that the frustration most field teams carry is not inevitable, that the waste and the rework and the panic and the firefighting that define most projects are not construction’s natural state. They are the symptoms of a poorly designed system. And a better system is available.

The person who pushes back on a clean desk, on a Takt plan, on a morning worker huddle, on zero tolerance they are not pushing back on the idea of a better project. They are pushing back on an invitation they have not yet trusted. The answer to that is not a louder argument. It is a clearer, more patient, more honest invitation that assumes they have a pull toward better and tries to connect to it. We are building people who build things. That includes building the trust that makes people willing to take the step. If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow and build the culture where the pull toward better actually has room to answer.

A Challenge for Builders

Find the person on your team this week who pushes back on the standard the hardest the one who makes the excuse, who offers the counterargument, who comes on with full chest. Resist the instinct to counter them. Instead, ask them one question: what would it look like if this project went better than any project you’ve been on? Listen to the answer. Find the part of what they described that connects to what you’re asking of them. Start there. The pull is in there. It is in everyone. The leadership skill is learning to reach it rather than argue past it.

As Taiichi Ohno said, “Where there is no standard, there can be no improvement.”

On we go.

Frequently Asked Questions

What does “the pull toward better” mean as a leadership concept?

It is the recognition that most people already have an instinct toward doing good work and being part of something excellent. Effective leaders connect to that instinct with invitation rather than overwhelming it with criticism which produces defensiveness rather than change.

Why does a clean desk matter to a superintendent’s overall performance?

Because the discipline of maintaining an organized workspace reflects the same habits that produce an organized site. The desk is not the goal the habit is. A super who cannot maintain their own workspace is running on the same habits that produce chaotic zones, missed standards, and reactive leadership in the field.

How is invitation different from lowering the standard?

Invitation does not lower the standard it changes the path to it. Shame closes people off. Invitation opens them toward the thing you are asking for. The standard stays exactly where it is; the approach for getting there becomes one that the person being led can actually step into rather than defend against.

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 Does a Project Engineer Do? (Roles, Responsibilities, and Real Impact)

Posted on by Danny Jiménez⁩
Read 21 min

What Does a Project Engineer Do? The Foreman Enabler Role That Determines Project Flow

Walk any struggling construction project and you’ll find a pattern in the office trailer that mirrors the chaos in the field. A project engineer buried in submittals. An RFI log that’s grown into a second career. A procurement tracker nobody is quite sure is current. And somewhere in the field, a foreman standing in a half-finished zone waiting on information, materials, or a coordination decision that should have arrived days ago.

The project engineer is often right in the middle of that picture not because they aren’t working, but because nobody has been clear with them about what the work is actually for. When a PE believes their job is to process RFIs, they process RFIs. When they believe their job is to enable the trades, they use RFIs as a tool toward that end, which is completely different. The distinction determines whether a PE is contributing to flow or contributing to the friction that disrupts it.

The Enabling Hierarchy Nobody Draws Clearly Enough

The PM creates and runs the business of the project site from start to finish. Below that, three roles function as the primary trade enablers: the superintendent, the project engineer, and the field engineer. Each of them owns a different portion of what a trade partner needs to plan, build, and finish their scope cleanly. The superintendent handles the site environment, the sequence, the safety, and the coordination. The field engineer handles layout control, space management, and lift drawings. The project engineer handles information, materials, resources, and the coordination that flows through those channels.

The PM enables all three of those roles. The three of them together enable the foreman. The foreman enables the crew. The crew enables the value the hard cost, the installed work that the entire project exists to produce.

That chain only functions when each person in it understands who they are serving and what serving them actually requires. A PM who orders materials and dumps them on site without sequencing them to the production plan has checked a box and called it a job done. But the trades are now fighting a staging problem that didn’t need to exist, the seven wastes have all been triggered at once, and the foreman who needed those materials in the right zone at the right time got the opposite of what they needed. Checking boxes is not enabling. Enabling is a deliberate, continuous act of understanding what the person downstream needs and making sure they have it before they realize they need it.

What the Project Engineer Actually Owns

The project engineer is, at the core, the information manager and procurement leader of the project site. Those two functions making sure the right information flows to the trades and making sure the right materials arrive on the right rhythm are the engine of the PE role. Everything else is a mechanism that serves those functions.

Information management means RFIs get submitted, tracked, and closed fast enough that design gaps never become field stops. It means submittals move through the review cycle in time to release fabrication and procurement before lead times run out. It means coordination issues between trades get surfaced and resolved before they create the in-field conflicts that cost rework. It means the foreman has what they need to plan the work before the work starts, not while they’re trying to execute it.

Procurement leadership means the supply chain is visible, tracked, and managed against the production schedule not against a procurement log that sits in a spreadsheet nobody looks at until something arrives late. It means long-lead items are identified in the pull plan and ordered with enough lead time that expediting costs never appear. It means deliveries hit the site in rhythm with the Takt plan, so materials flow to the zone when the zone is ready, not before and not after. It means the PE is walking the field frequently enough to know whether what the foreman has in front of them matches what the plan shows they should have.

The Trade Partner Preparation Process Is the PE’s Operating Framework

The vehicle through which the project engineer serves the trades is the trade partner preparation process. This is not a list of administrative tasks. It is the full lifecycle of how a trade partner gets from contract to productive installation to clean closeout, and the PE is present and contributing at every stage.

The buyout and contracting phase is where the PE supports the PM in making sure the trade is set up correctly from the beginning scope is clear, terms are understood, submittals and RFI processes are established. The pre-mobilization meeting is where the PE works with the trade to confirm everything needed for a productive first day on site is in place before anybody mobilizes. The pre-construction meeting is where submittals, RFIs, safety requirements, quality documentation, and site-specific requirements get reviewed and owned. The first-in-place inspection is where the PE shows up alongside the trade to confirm the installation meets the standard before the scope scales. Follow-up inspections protect that standard as the work progresses. And final inspections, closeout, payment reconciliation, retainage release, and change order resolution are where the PE closes the loop cleanly.

Every one of those touchpoints is a plan, build, finish cycle for the trade partner. The PE helps them plan the scope. The PE resources and coordinates during the build. The PE closes out the finish. Repeat that for every trade on the project, in every phase, and what emerges is a project that moves because every foreman has the information, materials, and coordination they need at every stage, and nobody is standing in a zone waiting.

When PEs Lose Sight of the Mission

The drift pattern for project engineers is specific and recognizable. A new PE comes onto the project and gets handed a list of tasks: manage the RFI log, track submittals, process pay applications, coordinate with the permitting authority, update the procurement tracker. Those tasks are real and they matter. But they are tools. They are mechanisms that serve the mission of enabling the trades. When the PE starts to treat them as the mission itself, the mission disappears.

The PE who defines success as “my RFI log is current” is measuring the tool, not the outcome. The question that matters is whether the trades have the design answers they need to install the work without stopping. A current RFI log full of open items is not a success. A closed RFI log that got the answers to the field on time is. The difference is orientation toward the tool or toward the person the tool serves.

The same drift happens with submittals, procurement, and pay applications. When these become the focus, the PE disappears into paperwork and the field loses the proactive support that a good PE provides. The foreman’s problems stop being caught early and start surfacing as field crises. The supply chain stops being managed against the production schedule and starts being managed against a spreadsheet. And the information that trades need to stay in flow starts arriving late, incomplete, or in the wrong sequence.

Signs the PE Role Is Running Correctly

When a project engineer is properly oriented toward trade enablement, the evidence is visible in the field rather than just in the trailer. Look for these markers:

  • Foremen are not calling the trailer for information that should have already reached them, because the PE is getting ahead of those needs rather than responding to them reactively.
  • Materials are arriving on rhythm with the production schedule, at the right location, at the right time, because the procurement log is being managed against the Takt plan rather than against a milestone calendar.
  • First-in-place inspections are happening before the scope scales, not after, because the PE is present and engaged in quality at the point where it is cheapest to catch problems.
  • RFIs are being submitted and closed on a timeline that serves the construction sequence, not on a timeline that serves the reviewer’s convenience, because the PE is actively managing the cycle.
  • Pay applications are processing on time and change orders are being reconciled without drama, because the PE has been tracking the documentation throughout the work rather than assembling it at the end.

When those things are happening, the trades are flowing. When they are not, the PE has drifted from the mission.

Seventeen Things a Trade Needs, and Who Provides Them

There are seventeen things a trade partner needs to plan, build, and finish their scope successfully, and the superintendent, field engineer, and project engineer divide responsibility for providing all of them. The superintendent owns the site environment, the sequencing, and the production rhythm. The field engineer owns the spatial accuracy layout, control points, lift drawings, and spatial constraints. The project engineer owns the information flow and the material supply chain, with the full weight of coordination and communication that those require.

No single role provides everything. All three have to function well for the foreman to have everything they need. That interdependence is why the enabling chain matters and why a PE who retreats into paperwork creates a gap that the superintendent cannot fill alone and the field engineer cannot reach across.

We are building people who build things. A project engineer who understands that orientation goes to work every morning thinking about the foreman, not the submittal register. They ask what the trades need to win this week and then they go get it. If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow including the project engineering discipline that keeps information and materials moving to the value creators in the field.

A Challenge for Builders

Walk through your current project’s trailer this week and ask every PE one question: what does your most stretched trade partner need from you this week that they do not yet have? If the answer is a list of pending RFIs or submittals, the PE is tracking tools. If the answer is a specific material arriving Tuesday that needs to hit Zone 4 instead of Zone 2, or a design answer due by Thursday that releases the concrete pour on Friday, the PE is tracking the trades. That distinction is the whole game.

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

On we go.

Frequently Asked Questions

What is the primary job of a project engineer in construction?

The PE exists to enable the trades to make sure the foreman has the information, materials, and coordination they need to plan, build, and finish their scope without stopping. RFIs, submittals, procurement logs, and pay applications are all tools in service of that mission, not the mission itself.

How is a project engineer different from a project manager?

The PM creates and runs the entire business of the project site and enables the superintendent, PE, and field engineer to do their jobs. The PE operates within that structure as the information manager and procurement leader, focused specifically on making sure the trades have what they need to execute their scope in flow.

What does it mean when a PE “loses sight of the trades”?

It means the PE has started treating their tools the RFI log, the submittal tracker, the procurement spreadsheet as the mission rather than as mechanisms that serve the trades. The signal is when the PE measures success by whether the log is current rather than by whether the foreman has what they need.

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 A Sprint In Project Management?

Posted on by Danny Jiménez⁩
Read 22 min

What Is a Sprint in Construction? Why Full Kit Is the Only Way to Run One

Construction teams have been running sprints for decades without calling them that. Every weekly work plan is a sprint. Every lookahead that gets built is a sprint backlog being prepared. Every pull plan session is a sprint planning event. The language is different, but the underlying logic is identical and understanding that connection gives every superintendent, foreman, and PM a sharper mental model for why the weekly work plan either works or collapses, and what determines which outcome you get.

The concept of a sprint comes from agile project management, specifically the Scrum framework. But once you understand what it actually means, you realize it is not a tech industry idea that got borrowed into construction. It is a production principle that the construction industry was already using informally, and the Scrum framework just gave it a name, a structure, and a discipline that makes the difference between planning that protects crews and planning that sets them up to fail.

The Problem: Weekly Work Plans That Are Not Actually Ready

The failure pattern on most construction sites is consistent and recognizable. A weekly work plan gets built on Monday morning. It lists the activities the team intends to complete in the next five days. It looks complete on paper. By Wednesday, half the listed work is stalled because the materials did not arrive, because the RFI is still unanswered, because the preceding trade did not finish the handoff, because somebody assumed the prerequisite was done when it was not.

This is not a scheduling problem. It is a readiness problem. The work was put into the weekly plan before it was made ready, and the crew paid for that gap with idle time, frustration, and stops and restarts that nobody budgeted for because nobody wanted to say out loud that the work was not actually ready to be executed. The sprint concept fixes that problem by making readiness the entry requirement, not an afterthought.

What a Sprint Actually Is

A sprint is the amount of work a team plans to complete within a defined time period one week, two weeks, three weeks that is in the right order of priority, made ready, and full kit before the sprint begins. The hiking analogy makes this tangible. You are hiking to the top of a mountain. If all you can see is the peak, every step feels like no progress. But if you identify the next base camp, sprint to it, arrive, and then identify the next segment, you feel the win at every stage. Motivation holds. Effort is focused. Progress is visible.

In Scrum, a sprint board has three columns: backlog, sprint backlog, and complete. The sprint backlog is the specific subset of the full backlog that the team commits to completing in the current sprint not the whole project, not everything that could possibly be done, just this week’s work in this week’s window, at a volume the team can actually execute without overloading capacity. A buffer lives in the sprint so the team is not operating at 100% theoretical capacity with no room for variation.

The sprint backlog is made ready before the sprint begins. Every item is assigned. Every definition of done is clear. Every dependency is resolved. The story behind each task is understood. And the work is full kit meaning every resource the crew needs to execute it is confirmed available before the sprint starts.

How This Maps Directly to Construction

In construction, the weekly work plan is the sprint. The lookahead plan typically covering the six weeks ahead is the sprint preparation system. The pull plan, built three months before the phase begins, is where constraints get identified, discussed, and optimized so they do not become surprises inside the sprint window. These three layers are not separate tools. They are one integrated readiness system that ensures the weekly work plan is a real sprint rather than a wish list with a Monday date on it.

The pull plan handles the constraint layer Takt time, zone leveling, sequence logic, bottleneck identification. By the time work shows up in the six-week lookahead, those structural constraints should already be resolved. The lookahead handles the roadblock layer missing approvals, unanswered RFIs, unordered materials, uninspected work, unresolved coordination conflicts between trades. Between week six and week two, those roadblocks get owned, tracked, and closed. By the time work enters the weekly work plan, it should be roadblock-free and full kit.

That last phrase is the whole concept. Full kit means every input needed for the crew to execute the work without stopping is confirmed in place before the work starts. The materials are on site. The information is resolved. The preceding work is complete. The equipment is available. The inspection is scheduled. The drawings are coordinated. Full kit is not a nice-to-have. It is the entry requirement for the sprint. Nothing goes into the weekly work plan that is not full kit.

Why “We’ll Figure It Out in the Field” Is Not a Sprint

The most common violation of sprint discipline in construction is exactly this: work gets moved into the weekly plan before it is ready because the team wants to look productive, because the schedule says the work should start, or because nobody wanted to have the uncomfortable conversation about what is actually missing. The instinct is understandable. The result is predictable.

When work enters the sprint that is not full kit, one of two things happens. Either the crew starts the work anyway and hits the missing resource mid-task creating a stop, a restart, a quality compromise, and a demoralized team that has learned not to trust the weekly plan. Or the super finds out at the morning huddle that the work cannot proceed, improvises a substitute activity, and the team spends the week reacting instead of executing. Neither outcome serves the project. Both of them erode the trust in the planning system that makes everything else function.

The principle is the one that applies everywhere in production planning: we do not start until we are ready to finish. A sprint that is not full kit is not a sprint. It is a hope list. And hope lists do not protect crews.

Warning Signs That the Sprint Is Not Being Run Properly

Before the damage from incomplete readiness compounds into a schedule problem, watch for these signals on your own project:

  • Work from the previous week’s plan carried forward more than once because it was not actually ready when it was committed.
  • The lookahead review is identifying roadblocks inside the two-week window, which means the six-week readiness system is not catching them early enough.
  • Crews are starting activities without all the inputs confirmed, and stops and restarts are being treated as normal rather than as system failures.
  • The weekly work plan is being built in the field rather than from a prepared lookahead, which means the work is being committed without the readiness checks having been run.
  • Percent promises complete at end-of-week is consistently below 80%, and the root cause analysis is producing the same causes week after week with no systemic fix.

Every one of those signals points to the same root. Work is entering the sprint before it is full kit. The fix is not to lower the commitment count. The fix is to run the readiness system properly so that every commitment that enters the weekly plan has passed the full kit check before it gets there.

The Motivation Benefit Nobody Talks About

There is a production benefit to running real sprints that goes beyond the mechanics of readiness, and it is one of the most underappreciated aspects of the Last Planner System when it is working correctly. When the team commits to a sprint that is full kit and actually completes it, they win. They feel the win. Foremen walk into the weekend knowing their crew delivered what they said they would deliver. Workers end the shift knowing the zone is ready for the next trade. The superintendent can look at the percent promises complete number and see it reflect real production.

That win compounds. Teams that win regularly at the sprint level hold their commitment standard tighter because they have experienced what it feels like to hit it. They start protecting the full kit check because they know what happens to the week when something gets through without it. They start owning their roadblocks in the lookahead because they have felt the difference between a week where everything was ready and a week where it was not. The sprint discipline builds the culture of commitment that makes the Last Planner System function as a production control mechanism rather than a reporting exercise.

Build the Readiness System, Not Just the List

The sprint concept is only useful if the readiness system behind it is actually running. That means pull planning three months out to optimize constraints. It means lookahead management from six weeks to two weeks to identify and close roadblocks before they enter the sprint window. It means a weekly work plan that gets built from a prepared lookahead, not constructed from scratch on Monday morning by a team that is already late.

It also means a Scrum master or in construction language, a first planner who owns the readiness check. Somebody whose job it is to look at what is in the upcoming sprint and confirm, specifically, that every item is full kit. Not assume it. Not hope it. Confirm it, with the specific resources, information, and predecessor conditions verified before the sprint starts. That role is what closes the gap between planning that looks like a sprint and planning that actually functions as one.

If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow including the sprint readiness discipline that makes the weekly work plan a real production commitment instead of a list that hopes for the best. We are building people who build things. That includes building the planning systems that give those people a real chance to win every week.

A Challenge for Builders

Look at this week’s work plan before Monday morning and run a full kit check on every item. Not a general check a specific one. Are the materials confirmed on site? Is the RFI answered? Is the preceding trade finished? Is the inspection scheduled? Is the equipment available? Is the crew count matched to the scope? If any item fails that check, it does not go into the sprint. It stays in the lookahead with an owner and a close date. Run that check every week for a month and watch what happens to your percent promises complete, your crew morale, and your end-of-week confidence. The system works. The discipline to run it is what separates teams that feel it working from teams that wonder why it does not.

As Taiichi Ohno said, “Where there is no standard, there can be no improvement.”

On we go.

Frequently Asked Questions

What is a sprint in construction project management?

A sprint is the specific amount of work a team commits to completing in a defined time window typically one week that is prioritized, assigned, and full kit before the sprint begins. In construction, the weekly work plan is the sprint, and the lookahead and pull plan are the systems that make it ready.

What does “full kit” mean and why does it matter?

Full kit means every resource, information, and predecessor condition required to execute a task without stopping has been confirmed in place before the work enters the weekly work plan. It is the entry requirement for the sprint. Work that is not full kit belongs in the lookahead, not the weekly commitment.

How does the lookahead plan support the sprint?

The lookahead typically covering six weeks is where roadblocks get identified, owned, and removed before they enter the sprint window. By the time work appears in the weekly work plan, every roadblock in the lookahead should already be closed. That readiness chain is what makes the sprint actually executable rather than aspirational.

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.

Trying To Get Better As A Leader

Posted on by Danny Jiménez⁩
Read 19 min

Trying to Get Better as a Leader: Why Imperfect Leaders Build the Strongest Teams

Here’s something most leadership content won’t say directly. The people writing it are imperfect too. They have reactions they’re not proud of. They have sensitivities that get in the way. They have moments where their impact on the people around them lands differently than they intended, even when they didn’t technically do anything wrong. The honest version of leadership development is not about eliminating those things. It is about naming them, owning the impact, and showing the people around you that you are genuinely trying to close the gap between who you are and who the role requires you to be.

That’s what this conversation is actually about. Not a framework for perfect leadership. A real account of what growth looks like when you’re inside it messy, uncomfortable, and more valuable to the people around you than any polished performance ever could be.

The Honest Starting Point

Jason Schroeder describes himself as a highly sensitive person someone who loathes criticism, can go cold when pushed, and sometimes makes the people around him uncomfortable through the sheer visibility of his emotional state even when no words have been said and nothing technically wrong has been done. He names it as something close to narcissism, then clarifies the distinction: not the dark version that weaponizes sensitivity against others, but the kind that makes criticism feel threatening and exclusion feel unbearable.

Most leaders have a version of this. Some are micromanagers who genuinely believe they are helping. Some are emotionally flat in ways that read as dismissive or cold when they are simply processing differently. Some have ADHD that makes focus in meetings hard, or brains that visually frown when thinking deeply, or standards so high that they project intensity in settings that call for patience. None of those things are character failures. They are the particular shape of a human being trying to lead other human beings, and every single one of them can do damage if the leader does not know it is there and refuses to own the impact.

The first honest step in getting better is the same step every strong recovery program starts with. Naming the thing. Not as a confession of worthlessness. As an accurate inventory of what you are working with, so you can work with it instead of against it.

Why “I Didn’t Do Anything Wrong” Is Not Enough

There is a specific trap that technically skilled leaders fall into regularly. Something goes sideways in a conversation. The leader reviews the replay in their head and confirms: no names were called, no inappropriate words were used, no formal breach of conduct occurred. And from that confirmation, they conclude they have nothing to address. The impact on the people in that room is treated as their problem to manage, not the leader’s responsibility to own.

That conclusion is wrong, and it is costly. Intent and impact are not the same thing. A leader who walks away from a tense conversation thinking “I didn’t do anything wrong” while the team walks away shaken, guarded, and less willing to surface problems has still done damage. The fact that the damage was unintended does not make the team’s experience less real. It does not rebuild the trust that eroded. And it does not create the conditions for the next honest conversation.

The more productive frame is simple: my impact was negative, and I am responsible for it regardless of my intent. That is not self-flagellation. It is accurate accounting. And it is the starting point for the kind of accountability that actually heals teams instead of just closing incidents.

What Owning the Impact Actually Looks Like

Jason describes his own practice clearly. After a moment where something went sideways emotionally, the response is not to make excuses, not to normalize it, not to wait for it to pass as if it did not happen. The response is to go back to the team and say it directly: I know I got upset there for a minute. I apologize for my impact. I’m working on this.

That approach does several things simultaneously. It acknowledges the reality of what the people in the room experienced without requiring them to name it themselves. It separates the leader’s intent from the team’s experience, validating both. It demonstrates the self-awareness that makes people willing to follow a leader through difficulty. And it models the accountability standard that the leader wants the entire team to operate from. You cannot ask your foremen and crew leaders to own their mistakes while pretending your own were not mistakes.

What Jason has observed and what holds true across every high-functioning team is that people are extraordinarily forgiving and gracious toward a leader who is visibly trying their best. Not a leader performing effort. A leader actually in the work of improving, stumbling in visible ways, and getting back up with honesty rather than defensiveness. That visibility is not weakness. It is the relational infrastructure that makes trust possible.

The Trap of “Never Let Them Figure You Out”

There is old-school leadership advice that says a leader should remain mysterious never let the team figure you out, because predictability breeds contempt and power depends on mystique. That advice produces exactly the wrong outcome on any team that needs to function as a cohesive unit rather than as a collection of people managing around someone’s moods.

When a leader is unpredictable by design, the team spends energy managing the uncertainty instead of doing the work. People stop bringing problems because they cannot predict the response. Foremen start filtering information before it travels upward. The morning worker huddle happens but nobody says what they actually think. The culture becomes one of careful performance rather than honest collaboration, and the production system underneath it reflects the gap.

When a leader is transparent about their tendencies and honest about their impact, the opposite happens. The team knows what they are working with. They can plan around it, support around it, and eventually help close the gap because they trust the leader’s commitment to closing it. That transparency does not undermine authority. It deepens it because the team knows the leader’s authority is not fragile and does not need to be protected by mystique.

What Nobody’s Leadership Growth Actually Looks Like

Here’s what the real version of trying to get better as a leader actually includes not the version that gets shared on conference stages, but the one that happens before anyone is watching:

  • Catching the reaction before it lands and choosing differently than you did last time, even when it is hard and the instinct is strong.
  • Going back to someone after a difficult conversation and naming your impact without requiring them to initiate it.
  • Noticing the ways your particular brain, personality, or wiring affects the people around you, and taking responsibility for those effects without treating them as excuses.
  • Asking for honest feedback from people who will actually give it, and sitting with the discomfort of hearing it instead of going cold.
  • Being willing to say in front of the team that you got something wrong, that you are working on it, and that their patience with you is something you do not take for granted.

That list is not impressive from the outside. It does not look like bold leadership. It looks like a person doing the quiet, necessary work of becoming better than they were. And the people who watch it happen are the ones who will follow that leader anywhere.

Why This Is a Production Issue, Not Just a Personal One

Leadership character is not separate from project outcomes. It is one of the primary inputs that determine them. A leader whose emotional state is unpredictable creates a site where people manage upward instead of executing forward. A leader who cannot receive honest feedback creates an environment where problems stay hidden until they are crises. A leader who refuses to own their impact loses the moral authority to hold anyone else accountable for theirs.

On the flip side, a leader who is visibly trying who names their tendencies, owns their impact, and shows up the next day still committed to doing better creates the psychological safety that allows the production system to function. Teams with that kind of trust surface problems early. Foremen ask for help instead of covering up struggles. Workers participate in huddles as real stakeholders instead of as performance audiences. The culture of any organization is shaped by the worst behavior the leader is willing to tolerate and the most important behavior a leader tolerates or refuses to tolerate is their own.

If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow  including the leadership development that starts with the person in the seat before it reaches anyone on the team.

A Challenge for Builders

Think about the last time you had a negative impact on the people around you not the last time you technically did something wrong, but the last time someone in the room walked away carrying something you put there. Did you go back and name it? Did you own the impact without requiring them to raise it first? If not, it is not too late. That conversation is always available, and it almost always produces more trust than people expect. We are building people who build things. That starts with the willingness to be honest about the building that still needs to happen in ourselves.

As W. Edwards Deming said, “Learning is not compulsory. Neither is survival.”

On we go.

Frequently Asked Questions

Why does owning your impact matter even if you didn’t technically do anything wrong?

Because intent and impact are not the same thing. When a leader’s emotional state visible even without words leaves the team shaken or guarded, the damage is real regardless of intent. Owning that impact is what rebuilds trust and keeps the culture honest.

Does admitting flaws and mistakes undermine a leader’s authority?

The opposite is true. Visible effort and honest accountability deepen authority because they show the team the leader’s standards are not fragile and do not depend on performance. People follow leaders who are transparently trying far more reliably than leaders who project infallibility.

What is the most practical first step for a leader trying to get better?

Name the specific tendency sensitivity to criticism, emotional visibility, micromanagement, whatever the actual pattern is and start going back after difficult moments to own the impact directly. That one practice, repeated consistently, builds more trust than almost anything else a leader can do.

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.