Elevate Construction official logo
Contact us

Month: March 2026

Calumet “K” – Chapter 5, Part 2

Posted on by Jason Schroeder
Read 12 min

The Superintendent Who Fought Back and Lost Everything

There is a superintendent who gets challenged by a walking delegate. The delegate shows up on site and starts making demands. And the superintendent has had enough. He is tired of union interference. He is tired of people questioning his authority. He is tired of being pushed around. So he pushes back. He argues. He gets in the delegate’s face. He tells him to get off the site. And within an hour, the entire crew walks off. The project stops. The owner is furious. And the superintendent loses his job. Not because he was wrong about the facts. But because he fought a battle he could never win. He let his emotions override his strategy. And he destroyed the project to prove a point that nobody cared about.

Here is what happens when leaders fight back instead of thinking strategically. A union representative shows up and demands changes to crew sizes or work hours or pay. The superintendent knows the demands are unreasonable. So he refuses. He digs in. He makes it personal. And the delegate responds by calling the crew off the job. Work stops. Materials sit on the ground. Trains get blocked. And the project falls behind because the superintendent treated a chess match like a fistfight. He won the argument and lost the war. And the entire team paid the price for his ego.

The real pain is the chain reaction. One person’s bad behavior creates a domino effect that cascades through the entire project. Peterson gets angry at the delegate and tries to prove a point by carrying a massive timber alone. The delegate gets offended and calls the crew off. The tracks get blocked with abandoned materials. A train gets stopped. The railroad gets angry and revokes track access. And now the entire project is paralyzed because one person could not control his temper. This is not just a setback. This is a complete breakdown of the system. And it started with one emotional reaction that turned a small problem into a project-killing crisis.

The failure pattern is predictable. Someone challenges your authority. You take it personally. You fight back to prove you are in control. The situation escalates. Other people get involved. The problem multiplies. And what started as a small dispute becomes a war that nobody can win. The superintendent who started the fight feels justified because he was defending his project. But justification does not matter when the project is stopped and the owner is demanding answers. The system failed them by never teaching leaders that some battles are not worth fighting and that winning wars requires losing battles strategically.

In Calumet K, Bannon faces exactly this situation. A walking delegate named Grady shows up on site and starts making demands. He wants more men on the heavy timbers. He wants crews relieved every two hours. And when Bannon’s foreman Peterson tries to prove the demands are unreasonable by carrying a massive timber with just one other man, Grady calls the entire crew off the job. Materials block the tracks. A train gets stopped. And the railroad threatens to revoke access. Bannon has every reason to fight back. He could argue. He could punch the delegate. He could throw his hard hat and start cussing. But he does none of those things. Because Bannon knows that fighting back would make everything worse. So instead he stays calm. He agrees to the delegate’s demands. He clears the tracks. He gets the train moving. And then he finds a creative solution to keep working despite the restrictions. He does not win the argument. But he wins the war. Because he understands that the goal is not to prove he is right. The goal is to finish the project. And finishing the project requires strategic thinking, not emotional fighting.

This matters because construction is full of situations where fighting back feels right but destroys everything. Difficult owners. Unreasonable inspectors. Aggressive trade partners. Hostile union representatives. Incompetent designers. And every time, the superintendent has a choice. Fight back and prove a point. Or stay calm and win the war. The superintendents who succeed are the ones who can swallow their pride, stay strategic, and focus on the mission instead of the battle. The superintendents who fail are the ones who let ego override strategy and burn the project down to prove they were right.

Why Fighting Back Always Loses

Fighting back feels powerful. It feels like leadership. It feels like standing up for yourself and your team. But fighting back is the opposite of leadership. Leadership is staying calm when everyone else is losing their minds. Leadership is thinking ten moves ahead while others are reacting emotionally. Leadership is winning wars by losing battles. And the leaders who understand this are the ones who succeed. Because they know that most battles are not worth fighting. And the ones that are worth fighting require strategy, not emotion.

Here is what happens when you fight back. The other person escalates. They call in reinforcements. They make it personal. They use every tool at their disposal to win. And suddenly you are not fighting about crew sizes or work hours anymore. You are fighting about power and control and ego. And those fights never end well. Because even if you win the argument, you lose the relationship. You lose trust. You lose cooperation. And you create an enemy who will look for every opportunity to sabotage you moving forward. That is the cost of fighting back. You win the battle and lose the war.

Bannon understood this perfectly. When Grady demanded ten men on the heavy timbers instead of eight, Bannon did not argue. He did not present data showing that eight men was sufficient. He did not challenge Grady’s authority. He just said alright. That simple agreement defused the entire situation. Grady expected a fight. He was ready for one. And when Bannon refused to give it to him, Grady had nothing to push against. The tension deflated. And Bannon got what he actually needed, which was to keep the project moving. He gave up crew sizes. But he kept momentum. And momentum is what finishes projects, not being right about crew sizes.

Watch for These Escalation Triggers

Pay attention to situations that tempt you to fight back when strategy would serve you better:

  • Someone challenges your authority in front of your team and your instinct is to assert dominance
  • A union representative makes demands you know are unreasonable but enforcing them is cheaper than fighting
  • An inspector writes up violations that feel personal and you want to argue instead of fixing them
  • A trade partner blames you for their mistakes and you want to prove it was their fault
  • An owner changes scope without acknowledging cost and you want to force them to admit they are wrong
  • A designer makes errors that create rework and you want them to take responsibility publicly

These are all moments where fighting back feels justified. But justified does not mean effective. And effective is what wins.

How to Win Wars without Fighting Battles

Start by separating ego from outcome. Ask yourself what I am actually trying to accomplish here. Am I trying to prove I am right? Or am I trying to finish the project? Because those are different goals. And most of the time, proving you are right costs more than it is worth. The project does not care if you were right. The project cares if you finished on time and on budget. So let go of being right and focus on being effective. If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow.

Next, give ground strategically. When someone makes a demand, ask yourself what does this actually cost me? If the cost is minor, give it to them. If a union delegate wants ten men on a timber instead of eight, put ten men on it. The cost is two workers for a few hours. The benefit is keeping the entire crew working. That is a trade worth making. But most superintendents cannot make that trade because their ego gets in the way. They need to prove the delegate is wrong. And that need costs them the project.

Then find creative solutions within the constraints. Bannon could not use the tracks after the railroad revoked access. So he rigged a cable system to move materials over the tracks instead. He did not fight the constraint. He worked within it. And he kept the project moving. That is strategic thinking. Most leaders spend their energy fighting constraints instead of solving problems within them. And that energy is wasted because constraints do not care about your arguments. Constraints just exist. So accept them and find solutions.

Finally, play chess not checkers. Think ten moves ahead. When Grady called the crew off, Bannon could have fought back. But he knew that fighting back would turn Grady into a permanent enemy. And Grady had the power to shut down the project anytime he wanted. So Bannon stayed calm. He gave Grady what he wanted in the moment. And he preserved the relationship for later. That is chess. You sacrifice a pawn to protect the king. You lose a battle to win the war. And you focus on the endgame instead of the current move.

Signs You Are Fighting When You Should Be Strategizing

Watch for these patterns that signal you are letting emotion override strategy:

  • You feel the need to prove you are right even when winning the argument costs more than conceding
  • You make decisions based on how they make you feel instead of what outcome they produce
  • You escalate conflicts to assert dominance instead of defusing them to preserve momentum
  • You refuse to compromise on small things because you see it as weakness instead of strategy
  • You burn bridges with people who have power over your project because you cannot swallow your pride
  • You spend more time fighting battles than solving problems

These are not signs of strength. These are signs of ego. And ego kills projects.

The Cost of One Bad Reaction

Peterson tried to prove the delegate wrong by carrying a massive timber with just one other man. It was a display of strength. It was meant to show that the delegate’s demands were unreasonable. And it worked. Peterson proved his point. But the cost was catastrophic. The delegate got offended. He called the crew off. Materials blocked the tracks. A train stopped. The railroad revoked access. And the entire project nearly collapsed. All because Peterson needed to prove he was strong. That is the cost of one bad reaction. One emotional decision. One moment of ego. And it creates a chain reaction that destroys everything.

The lesson is simple. Control your reactions or your reactions will control the project. Peterson could not control his. And Bannon spent the rest of the night fixing the damage. He had to negotiate with the delegate. Clear the tracks. Move the train. Rig a cable system. And work through the night to recover the lost time. All of that could have been avoided if Peterson had stayed calm. But Peterson fought back. And the entire team paid the price.

So here is the challenge. The next time someone challenges your authority, take a breath. Ask yourself what I am actually trying to accomplish here. And choose strategy over emotion. Give ground where it costs little. Find creative solutions within constraints. And play the long game instead of reacting to the current moment. As Bannon demonstrated, you do not need to win every battle to win the war. You just need to stay calm, think strategically, and keep the project moving. That is leadership. Not fighting back. Not proving you are right. But focusing on the mission and letting everything else go. On we go.

Frequently Asked Questions

Why is fighting back a bad strategy even when you are right?

Because being right does not matter if fighting destroys the project, relationships, or momentum. Strategic concessions keep things moving while fighting creates enemies and delays.

How do you know when to fight and when to concede?

Ask what the actual cost is. If conceding costs little but fighting risks major delays or damage, concede strategically and focus energy on solving problems instead.

What if giving in makes you look weak to your team?

True strength is staying calm under pressure and thinking strategically. Teams respect leaders who finish projects, not leaders who win pointless arguments and lose wars.

How did Bannon handle the delegate situation strategically?

He agreed to demands instead of arguing, cleared the tracks to move the train, then found creative solutions to work within new constraints without fighting the restrictions.

What is the domino effect Peterson created?

His emotional reaction angered the delegate, who called the crew off, which blocked tracks, stopped a train, angered the railroad, and nearly collapsed the project.

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

Posted in All

Dealing with Emotional People

Posted on by Jason Schroeder
Read 11 min

Why Logic Loses When Someone Is Emotional

There is a superintendent who runs a tight ship. He is logical. He is organized. He solves problems with data and facts. And when someone on his team gets emotional, he does what seems obvious. He explains the situation. He presents the facts. He appeals to reason. And the person gets more upset. The conversation escalates. Voices rise. And the superintendent walks away frustrated because he did everything right and it made everything worse. The problem is not what he said. The problem is he fought emotion with logic. And logic cannot win that fight.

Here is what happens when someone brings an emotional problem to a logical person. A foreman walks into the trailer visibly upset. He says I feel like nobody on this team respects me. The superintendent responds with facts. You got the promotion. You run the best crew. Everyone says good things about you. The foreman hears those words and feels worse. Because the superintendent just told him his feelings are invalid. He just said your emotions do not match reality so your emotions are wrong. And the foreman shuts down. He leaves feeling unheard. And the problem that caused the emotion never gets addressed because the superintendent was so busy proving the emotion was illogical that he never stopped to understand what caused it.

The real pain is the missed connection. That foreman was not asking for data. He was asking to be heard. He was asking for validation. He was asking for someone to say I hear you and I understand why you feel that way. And instead he got a lecture about why his feelings do not make sense. And now he feels worse than before because not only does he feel disrespected, he also feels stupid for having those feelings in the first place. This destroys trust. It damages relationships. And it creates distance between leaders and teams because people learn that bringing emotional problems to logical leaders is pointless.

The failure pattern is predictable. Someone gets emotional. A leader responds with logic. The emotional person gets more upset because they feel unheard. The leader gets frustrated because the facts are not working. The conversation escalates. And both people walk away angry because they were speaking different languages the entire time. One person was speaking emotion. The other was speaking logic. And neither understood that fighting emotion with logic is like bringing a hammer to fix a computer. Wrong tool. Wrong approach. And guaranteed to make things worse. The system failed them by never teaching leaders that emotional problems require emotional solutions, not logical ones.

I have been the emotional person. My wife Katie has lived through years of me getting upset about something and her responding with logic and me getting more upset because she was not listening. And the cycle repeated. I would feel hurt. She would explain the reality of the situation. I would say you are not listening to me. She would say I am explaining what happened. And we would escalate because she was using logic and I was using emotion and neither of us realized we were speaking different languages. And it only stopped when one of us finally said I hear you and I understand why you feel that way. That validation was the key. Once I felt heard, the emotion deflated. And then we could talk about solutions. But not before.

This matters because construction teams are full of emotional people. And most leaders have no idea how to handle them. So they fight emotion with logic. They dismiss feelings as illogical. They shame people for being too sensitive. And they create cultures where people stop bringing problems forward because they know they will not be heard. This affects projects because unresolved emotional issues turn into conflict. Conflict turns into poor communication. Poor communication turns into mistakes. And mistakes cost time, money, and safety. Knowing how to handle emotional people is not soft. It is essential. And leaders who refuse to learn this skill are limiting their own effectiveness and damaging their teams.

How Emotional People Actually Work

The first thing to understand is that the demons are not real. When someone is emotional, the fears they are expressing do not make logical sense. A foreman says nobody respects me when everyone clearly respects him. A project manager says I am going to get fired when his performance is excellent. A worker says the team hates me when everyone likes him. These statements are not rational. They are emotional. And trying to fight them with logic is pointless because emotion does not operate on logic. Emotion operates on fear, insecurity, and past trauma. And those things do not respond to data.

The second thing to understand is that 80 percent of the demons go away when spoken out loud. The act of verbalizing the fear starts to defuse it. But only if the person on the receiving end responds with empathy instead of logic. When someone says I feel like nobody respects me, they are not asking you to prove them wrong. They are asking you to go there with them emotionally. They are asking you to say I hear you and I can see why you would feel that way. That validation is what allows the emotion to deflate. And once the emotion deflates, clarity can enter. But if you respond with logic, you block the healing process. You tell the person their feelings are invalid. And the emotion intensifies instead of deflating.

The third thing to understand is that emotional people need empathy, not solutions. When someone is upset, the first response should not be here is how to fix this. The first response should be I hear you. I understand. That is hard. Once the person feels heard, they can start to think clearly. And once they can think clearly, they can solve the problem themselves. But if you jump straight to solutions, you skip the validation step. And without validation, the person cannot move forward because they are still stuck in the emotional loop trying to be heard. If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow.

Signs Someone Needs Empathy Not Logic

Watch for these signals that someone is operating from emotion and needs empathy instead of logic:

  • They repeat the same concern even after you have explained the facts multiple times
  • Their words do not match reality but they insist their feelings are valid anyway
  • They escalate when you present logical explanations instead of calming down
  • They say things like you are not listening or you do not understand what I am saying
  • The problem they describe seems illogical or disproportionate to the actual situation
  • They seem more upset after you have tried to help than they were before

These are not signs of irrationality. These are signs that the person needs emotional validation before they can process logical information.

How to Actually Help Emotional People

Start by listening without fixing. When someone brings an emotional problem, resist the urge to solve it immediately. Just listen. Let them talk. Let them get it out. And do not interrupt with logic or solutions. The act of speaking the fear out loud starts to heal it. But only if you let them finish. If you cut them off with logic, you stop the healing process before it can start. So listen first. Fix later.

Next, validate their feelings without agreeing with their conclusions. You can say I hear you and I understand why you would feel that way without saying you are right about the facts. Validation does not mean agreement. It means acknowledgment. It means I see that you are hurting and I take that seriously. That validation is what allows the person to move from emotion to clarity. Once they feel heard, they can start thinking clearly. And once they can think clearly, they can see the situation more accurately.

Then help them get clarity. Once the emotion has deflated through validation, you can start asking questions that help them see the situation differently. What do you think caused that feeling? Is there evidence that supports or contradicts it? What would help you feel better about this? These questions guide them toward clarity without telling them their feelings are wrong. And clarity is the key. Once they have clarity, the fear loses power. And the problem becomes solvable.

Finally, do not shame them for being emotional. If you respond with frustration or dismissiveness, you teach them that bringing emotional problems to you is unsafe. And they will stop. They will start hiding problems. They will internalize emotions instead of processing them. And those unresolved emotions will show up later as conflict, disengagement, or turnover. So treat emotional problems with the same seriousness you treat technical problems. Because they are just as real and just as damaging when ignored.

What Happens When You Get It Wrong

When you fight emotion with logic, you make the person feel worse. They start thinking I am just crazy. I do not deserve understanding. I am a burden. We are not compatible. I do not fit on this team. Nobody cares that I am here. I am not making progress. I am not good enough. I am ashamed for being emotional. And those thoughts create a spiral that is harder to escape than the original problem. You do not just fail to solve the problem. You create new problems by making the person feel broken and unworthy.

I used to keep a list called the CDAA list. Cannot Do Anything About. I would write things like I am worthless, I cannot do my job, the owner is disappointed in me, I am going to tank this project. These were fear-based garbage thoughts. And a mentor said if you are going to have a list like that, reframe it to get clarity. So I started writing I felt worthless today because of this, but here is the reality. And eventually the CDAA list went away because I stopped reinforcing those neural pathways with garbage stories. But that only happened because someone taught me how to get clarity instead of shaming me for being emotional.

The Challenge

Walk into your next interaction with an emotional person armed with empathy instead of logic. Listen first. Validate their feelings. Help them get clarity. And watch what happens when you stop fighting emotion with logic and start meeting people where they are. Most emotional people are not broken beyond repair. They are just stuck in fear. And fear loses power when it is spoken out loud and met with empathy. As the song says, “I know you are choking on your fears. I already told you I am right here.” Be the person who stays. Be the person who listens. And be the person who helps them find clarity instead of telling them their feelings are wrong. That is leadership. On we go.

Frequently Asked Questions

Why does fighting emotion with logic make things worse?

Logic tells emotional people their feelings are invalid, which makes them feel unheard and intensifies the emotion instead of deflating it.

What should you do when someone brings an emotional problem?

Listen without fixing, validate their feelings without agreeing with conclusions, and then help them get clarity through questions once the emotion has deflated.

How do you validate feelings without agreeing with false conclusions?

Say I hear you and I understand why you would feel that way, which acknowledges their pain without confirming inaccurate beliefs about reality.

What happens if you shame someone for being emotional?

They learn bringing emotional problems to you is unsafe, so they hide issues, internalize emotions, and create bigger problems that show up as conflict or disengagement.

How do you know if someone needs empathy instead of logic?

They repeat concerns after you explain facts, their words do not match reality but they insist feelings are valid, or they escalate when you present logical explanations.

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

Posted in All

Where Are You in the Process? Feat. Jake Williams

Posted on by Jason Schroeder
Read 12 min

The Superintendent Who Polished Himself into a Bottleneck

There is a superintendent who spends three weeks perfecting a schedule. He reviews every activity. He adjusts every duration. He color-codes every trade. He cross-references every milestone. And when he finally presents it to the team, the trade partners look at it and say you have no idea what you are talking about. Three weeks wasted. Not because he lacked skill. But because he did not understand where he was in the process. He was early. He was supposed to create the rough framework and get input. But he treated it like the final deliverable. And that perfectionism created a bottleneck that delayed the entire project.

Here is what happens when leaders do not know where they are in the process. An assistant superintendent creates lift drawings. But he waits to release them because he does not have the sleeve drawings from MEP yet. He does not have the embed details from the curtain wall shop drawings. So he holds the drawings waiting for perfection. Meanwhile, the foreman needs to see the layout to plan crane picks. The field engineer needs to coordinate reinforcement. And the project manager needs to price the work. But nobody gets anything because one person is waiting for perfection when he should have released a draft with big black letters that say DRAFT DO NOT USE. That delay cascades through the schedule. And the project falls behind because someone did not understand their position in the process.

The real pain is the wasted time. Time spent polishing something that will go through three more people before it becomes final. Time spent perfecting details that someone else is better suited to refine. Time spent creating a finished product when what was needed was a rough framework to start the conversation. And the tragedy is that this perfectionism feels responsible. It feels thorough. It feels like quality work. But it is the opposite. It is a bottleneck disguised as diligence. And it costs projects speed, collaboration, and results.

The failure pattern is predictable. Someone early in the process treats their work like the final deliverable. They spend days or weeks perfecting something that should take hours. They do not involve others because they want to present the finished product. And when they finally hand it off, it either needs major revisions because they missed critical input or it sits on a shelf because it arrived too late to be useful. Either way, the perfectionism backfired. The system failed them by never teaching them to ask where I am in the process and what does well enough look like at this stage.

I watched a project engineer struggle with this exact problem. He was facilitating pre-installation meetings. But he felt like he needed to have all the answers before the meeting. So he spent days researching how to install the work. He prepared presentations. He created detailed sequences. And then he presented all of this to 30 and 40 year experts who looked at him like he was wasting their time. The problem was not his effort. The problem was his misunderstanding of his role. He was not there to teach experts how to do their job. He was there to facilitate the meeting. Get the right people in the room. Make sure the documents are available. And let the experts share their knowledge with each other. Once he understood where he was in the process, the meetings accelerated and the quality improved because he stopped trying to be the expert and started unlocking the expertise already in the room.

This matters because knowing where you are in the process determines what good looks like. If you are at the beginning, good means rough framework that invites collaboration. If you are at the end, good means polished final product ready for delivery. And the people who succeed are the ones who can shift their definition of good based on where they are. The people who fail are the ones who apply end-of-process standards to beginning-of-process work. And that mismatch creates bottlenecks, delays, and wasted effort.

Where You Are Determines What Good Looks Like

The key insight is this. Perfection is a moving target. What perfection looks like at the beginning of the process is completely different from what it looks like at the end. At the beginning, perfection means getting the rough framework out fast so others can contribute. At the end, perfection means polishing the final details so the deliverable is ready for use. And the mistake most people make is applying end-of-process perfection to beginning-of-process work. They spend days perfecting a draft when what was needed was hours creating a framework.

Here is how to know where you are. Ask yourself how many people will touch this before it becomes final. If the answer is three or four, you are early in the process. Your job is not to perfect it. Your job is to create the rough framework and get it to the next person. If the answer is zero or one, you are late in the process. Your job is to polish it because you are the last quality check before delivery. This simple question changes everything. Because once you know where you are, you know what good looks like. If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow.

The envelope game illustrates this perfectly. Give someone 20 pieces of paper, 20 envelopes, and 20 stamps. Tell them to fold all the papers first. Then stuff all the envelopes. Then seal all the envelopes. Then stamp all the envelopes. That is batching. Now give someone else the same materials. Tell them to take one piece of paper, fold it, stuff it, seal it, stamp it, and set it aside. Then repeat. That is one-piece flow. And every single time, the one-piece flow person finishes two to three minutes faster even though it looks slower. Why? Because batching creates inventory. And inventory creates delays. The person batching cannot hand off the first envelope until all 20 are done. The person flowing can hand off the first envelope immediately. And that speed matters when you are early in the process and others are waiting for your output.

How to Operate at the Right Level

Start by labeling your work with DRAFT when you are early in the process. Put it in the subject line of emails. Put it in big letters on drawings. Put it at the end of schedule activities. The word DRAFT is liberating. It tells people this is not final. This needs your input. And it gives you permission to release work faster because you are not claiming it is perfect. You are inviting collaboration. And that invitation accelerates the process because others can start contributing while you are still refining.

Next, communicate your position in the process. When you hand something off, say this is a rough draft to make sure I am headed in the right direction. I value your input. Help me get this right. That language changes the dynamic. It signals you are early in the process. It invites feedback. And it prevents people from assuming you think you have all the answers. One owner said it perfectly. When you work in a silo and hand me the finished product, it makes me feel like you do not value my input. And it comes across as arrogant. Once you understand that handing off drafts is actually more respectful than handing off finished work, you will never go back to perfectionism.

Then delegate appropriately based on where you are. If you are a senior superintendent, your job is to create the rough framework of the schedule and let assistant superintendents fill in the details. If you are a project manager, your job is to outline the approach and let project engineers develop the specifics. And if you are a field engineer, your job is to coordinate the inputs and let the trades refine the execution. The higher you go in leadership, the earlier in the process you operate. And early in the process means rough drafts that invite contribution, not finished products that shut people out.

Signs You Are Operating at the Wrong Level

Watch for these patterns that signal you are misunderstanding where you are in the process:

  • You spend days or weeks perfecting something that gets major revisions from the first person who reviews it
  • People tell you they wish you had involved them earlier instead of presenting the finished product
  • Work sits on your desk waiting for perfect information instead of going out as a draft for others to review
  • You feel overwhelmed and over-committed because you are doing work others should be contributing to
  • Trade partners or team members say you do not value their input because you present instead of collaborate
  • Deliverables arrive late because you spent too long polishing instead of releasing early for feedback

These are not quality standards. These are bottlenecks. And the fix is understanding where you are in the process and adjusting your definition of good accordingly.

The Power of Early and Often

One author spent six years drafting a book because he could not release it. The pressure of creating the final publishable version paralyzed him. But when his publisher said you can call this a draft if you want and revise it later, the pressure lifted. He released the book. It became a bestseller. And he realized the perfectionism was not protecting quality. It was preventing progress. The same thing happens on construction projects. Perfectionism feels responsible. But it is actually fear disguised as diligence. Fear of being wrong. Fear of looking incompetent. Fear of losing control. And that fear creates bottlenecks that delay projects and frustrate teams.

The antidote is releasing early and often. Get the rough framework out. Label it DRAFT. Invite feedback. Incorporate input. Release the next version. And keep iterating until it becomes final. This approach is faster. It produces better results because more people contribute. And it builds trust because people feel valued instead of bypassed. The teams that succeed are the ones who understand that speed early in the process creates quality at the end. The teams that fail are the ones who sacrifice speed for perfectionism and end up with neither.

Ask Yourself Where You Are

Here is the checkpoint. Look at your current workload. What are you working on right now? And ask yourself where I am in the process. Am I early and creating rough frameworks? Or am I late and polishing final deliverables? If you are early, release it. Label it DRAFT. Get feedback. Move it forward. If you are late, polish it. Make it right. And deliver quality. But do not apply late-process standards to early-process work. And do not hold onto work that others are waiting for because you are chasing perfection that does not exist yet.

Then ask what should I be doing that other people cannot or will not do. And what can I hand to someone else that would give them the opportunity to contribute. These two questions unlock delegation. They help you assess your place in the line. And they ensure you are performing where your position has the most impact. The current condition is leaders are overwhelmed, over-committed, and under-utilizing people around them. The challenge is to know where you are in the process and operate at the right level. Get rough drafts out early. Invite collaboration. And stop bottlenecking your team with perfectionism that belongs at the end, not the beginning. As Jake’s father said, “We are seldom if ever able to achieve perfection with our work. But if we set our sights on anything else, we often miss the mark completely.” Aim for perfection. But release drafts along the way so others can help you get there. On we go.

Frequently Asked Questions

What does it mean to know where you are in the process?

It means understanding if you are early creating rough frameworks or late polishing final deliverables, and adjusting your definition of good accordingly.

How do you know if you are operating at the wrong level?

If you spend days perfecting something that gets major revisions immediately, or if deliverables arrive late because you waited for perfect information instead of releasing drafts.

What is the power of labeling work as DRAFT?

It gives you permission to release work faster, invites collaboration, and prevents people from assuming you think you have all the answers or do not value their input.

How does this relate to delegation?

Understanding where you are in the process helps you know what to delegate. Early-process work should be rough frameworks that others refine, not finished products that shut people out.

Why does perfectionism early in the process create bottlenecks?

Because it delays handoffs to people who are waiting for your output, wastes time polishing details others are better suited to refine, and prevents collaboration.

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

Posted in All

Lean Facilitation – Lean, IPD Series

Posted on by Jason Schroeder
Read 12 min

Why Lean Dies Without a Facilitator

Most teams try lean and quit within six weeks. They read a book. They attend a conference. They get excited about last planner or pull planning or daily huddles. And then they go back to the jobsite and try to implement it on their own. The superintendent tries to run a pull planning session without knowing how to facilitate it. The project manager tries to start daily huddles without understanding how to create buy-in. And the team resists. They roll their eyes. They say this is a waste of time. And within a month, the entire effort collapses. The team blames lean. They say it does not work in construction. But the truth is lean did not fail. The facilitation failed. And without facilitation, lean never had a chance.

Here is what happens on a typical project. Leadership decides to implement lean. They send the superintendent to a one-day training. He comes back with a binder full of materials and a head full of concepts. And then he is expected to change the culture of the entire project by himself. No support. No coaching. No facilitation. Just figure it out. So he tries. He schedules a pull planning session. But he does not know how to run it. He does not know how to ask the right questions. He does not know how to get buy-in from trades who have never done this before. And the session falls apart. People leave frustrated. They say this lean stuff is a joke. And the superintendent gives up because he was set up to fail from the beginning.

The real pain is not the failed pull planning session. It is the missed opportunity. That team had the talent to solve their own problems. They had the experience to coordinate the work better. They had the ideas to improve flow and eliminate waste. But nobody facilitated those talents out of them. Nobody created the environment where people felt safe speaking up. Nobody asked the right questions to unlock the genius that was already in the room. And the project continued operating the same chaotic way it always had because the system never gave the team the facilitation they needed to succeed.

The failure pattern is predictable. Leadership announces a lean initiative. They send one person to training. That person comes back and tries to implement lean alone. The team resists because they do not understand it or because they have been burned by poorly executed lean efforts in the past. The champion gets frustrated and gives up. And the company concludes that lean does not work for them. But the problem was never lean. The problem was the lack of facilitation. Because lean is not a set of tools you hand someone and say go implement this. Lean is a cultural shift. And cultural shifts require facilitation. They require someone who knows how to bring people together, create safety, ask powerful questions, and unlock the collective intelligence of the team.

I remember when I first started learning lean. A facilitator came to our project. He did not just hand us a book and walk away. He came out and showed us how to run last planner meetings. He showed us how to do morning huddles. He sat in our meetings and gave us feedback. He said Jason, here is how you can run this meeting better. Here is how you can get more participation. Here is how you can create buy-in. And those coaching moments were invaluable. They accelerated our learning by months. They gave us confidence. And they helped us avoid the mistakes that kill most lean implementations before they ever get started. That facilitation made the difference between success and failure.

This matters because lean works. But only when it is facilitated properly. The projects that succeed with lean are not the ones with the best tools or the fanciest software. They are the ones with facilitators who know how to bring out the best in people. Facilitators who create environments where trades feel safe speaking up. Facilitators who ask questions that unlock solutions the team already has. Facilitators who coach leaders on how to run meetings that people actually want to attend. And facilitators who stay engaged long enough for the culture to shift and the new behaviors to stick. Without that facilitation, lean is just another failed initiative that reinforces cynicism instead of creating transformation.

What Facilitation Actually Does

Facilitation is not about teaching people what to do. It is about bringing out the best in others. A facilitator does not solve problems for the team. A facilitator creates the conditions where the team can solve their own problems. And once the team learns how to solve their own problems, they do not need the facilitator anymore. That is the goal. Not dependency. Capability. The best facilitators make themselves unnecessary by building capability in the team.

The power of facilitation shows up in meetings. If you can get a team to perform well together in meetings, they can do anything. Most teams run terrible meetings. People show up late. They multitask on their phones. Sidebar conversations happen constantly. A few people dominate. Most people stay silent. And nothing gets decided. A facilitator changes that. They create structure. They set expectations. They get everyone participating. They ask open-ended questions that provoke thinking. They listen thoughtfully and paraphrase to ensure understanding. They encourage quieter voices to speak up. And they manage behavior so the meeting stays productive. Once a team experiences what a good meeting feels like, they never want to go back to the chaos.

A good facilitator also creates psychological safety. This is critical. Most construction teams operate in fear. Fear of looking stupid. Fear of being blamed. Fear of challenging authority. And that fear kills collaboration. People stay silent even when they see problems. They protect themselves instead of contributing. A facilitator breaks that pattern. They create environments where it is safe to speak up. Where questions are encouraged. Where dissent is valued. Where mistakes are learning opportunities instead of career-ending events. And once that safety exists, the team starts unlocking solutions that were always there but never surfaced because people were too afraid to share them. If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow.

Facilitators also stay neutral. They focus on process, not content. They do not push their own agenda. They serve the group’s objectives. And they have the authority to confront unproductive behavior without making it personal. When someone dominates the conversation, the facilitator redirects. When sidebar conversations derail focus, the facilitator stops them. When conflict arises, the facilitator manages it productively instead of letting it fester. This neutrality creates trust. The team knows the facilitator is there to help them succeed, not to advance a personal agenda or prove how smart they are.

Signs Your Team Needs Facilitation

Watch for these patterns that signal your team needs a facilitator to unlock their potential:

  • The team tried lean once and it failed, so now everyone is cynical about trying again
  • Meetings are chaotic with no structure, participation is low, and nothing gets decided
  • One or two people dominate every conversation while most of the team stays silent
  • Trades resist collaboration because they do not trust the process or the leadership
  • Problems surface late instead of early because people are afraid to speak up
  • The superintendent or PM is overwhelmed trying to implement lean alone without support
  • Training happened once but no one followed up to coach the team through implementation
  • The team has the talent to solve problems but no one is facilitating it out of them

These are not people problems. These are facilitation gaps. And the fix is bringing in someone who knows how to create the conditions where people can succeed.

What Good Facilitators Do

Effective facilitators demonstrate specific skills and behaviors that bring out the best in teams. Here is what separates great facilitators from mediocre ones:

  • Strong communication skills with distributed eye contact, use of participant names, and varied tone
  • Deep familiarity with the subject matter so they can ask impactful questions
  • Respect for all participants and ability to create a respectful environment
  • Asking open-ended questions that provoke thinking instead of yes-or-no answers
  • Listening thoughtfully and paraphrasing to ensure understanding before moving forward
  • Encouraging full participation from everyone, especially quieter voices who tend to stay silent
  • Demonstrating energetic and positive presence that makes people want to engage
  • Connecting with multiple learning styles so everyone can absorb the material
  • Managing the room by keeping participants focused, on task, and on time without being rigid

These skills are not innate. They are learned. And facilitators develop them through hundreds of hours of training, practice, and feedback. The best facilitators have attended certifications, read extensively, facilitated dozens of events, and received coaching themselves. They have invested in becoming excellent at bringing out the best in others. And that investment shows up in the results their teams produce.

How to Use Facilitation on Your Projects

Start by identifying what needs facilitation. Is it a pull planning session? A team meeting that has become unproductive? A conflict between trades that is affecting the project? A lean implementation that is stalling? Once you know what needs facilitation, bring in someone who has the skills and experience to create the conditions for success. Do not try to facilitate complex sessions yourself if you have never been trained. You will make mistakes that reinforce cynicism instead of creating transformation.

During the facilitated session, the facilitator should clearly state the purpose and expectations upfront. What are we trying to accomplish today? What does success look like? Then create structure. Use an agenda. Set time limits. Establish a code of conduct. Turn off phones. No sidebar conversations. Equal status for everyone to participate. And then ask powerful questions. Can you say more about that? What would it take to solve this problem? What is stopping us from moving forward? These questions unlock thinking instead of shutting it down.

After the session, the facilitator should coach the team on how to replicate the process themselves. The goal is not to create dependency on the facilitator. The goal is to build capability so the team can run these sessions on their own. Provide feedback. Point out what went well. Identify what could be improved. And give the team opportunities to practice with coaching until the new behaviors stick.

The Hard Truth about Training

Here is something that needs to be said. If your superintendents are not scheduling, not organized, and not problem-solving, they are not superintendents yet. That is not an insult. That is a reality check. Having the title does not make someone qualified. And the industry has done a terrible job of training people for these roles. So if you have someone with the superintendent title who lacks the skills, you have three choices. Train them. Do the work without them and force them to adapt. Or let them go and find someone who is interested in learning.

Training is not optional. It is foundational. And facilitation accelerates training by bringing the team along together instead of sending one person off to figure it out alone. Invest in personal organization training. Invest in scheduling training. Invest in leadership development. And invest in facilitation so the team can implement what they learn instead of letting it die in a binder on a shelf.

So here is the challenge. Stop trying to implement lean alone. Stop expecting one person to change the culture of an entire project without support. And stop accepting mediocre results because you think facilitation is too expensive or unnecessary. Bring in a facilitator who knows how to bring out the best in people. Let them create the conditions where your team can solve their own problems. And watch what happens when you unlock the collective genius that has been sitting in that room the entire time. As Bill Seed wrote in Transforming Design and Construction, facilitation is about “serving the group’s objective rather than his or her own personal objective.” That is the shift. Stop trying to be the hero. Start facilitating the team to become their own heroes. On we go.

Frequently Asked Questions

What does a facilitator actually do?

A facilitator brings out the best in others by creating conditions where teams can solve their own problems, not by solving problems for them or teaching what to do.

Why do most lean implementations fail?

They fail because one person tries to implement lean alone without facilitation, coaching, or support, and the team resists because no one created buy-in or safety.

What skills do good facilitators have?

Strong communication, deep subject knowledge, ability to ask open-ended questions, listening thoughtfully, encouraging participation, managing behavior, and staying neutral on content while focusing on process.

How do you know if your team needs facilitation?

If meetings are chaotic, participation is low, people stay silent, lean efforts failed before, or the team has talent but no one is unlocking it.

Can you facilitate your own team?

You can if you have been trained, but complex sessions require experienced facilitators who know how to create safety, ask powerful questions, and manage group dynamics effectively.

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

Posted in All

The Risk & Opportunity Register – Lean, IPD Series

Posted on by Jason Schroeder
Read 11 min

Why Projects Lose Money Waiting for Bad Things to Happen

Most project teams operate on hope. They hope the stone arrives on time. They hope the design does not change. They hope the trade partner delivers. They hope the materials do not escalate. And when those hopes do not materialize, they react. They scramble. They throw money at the problem. And the project bleeds budget because the team spent months hoping instead of minutes planning. This is not risk management. This is gambling. And it costs projects millions of dollars every single year.

Here is what happens on a typical project. The team meets for preconstruction. They talk through the scope. They identify some concerns. Someone mentions that the exterior stone looks complicated and the lead time might be tight. Someone else mentions that the tile package has design gaps that could cause issues later. And the team nods. They agree those are risks. And then they do nothing. They do not write them down. They do not assign dollar values. They do not assign ownership. They do not track them. And six months later, the stone arrives late and threatens the schedule. The tile package has errors and requires rework. And the project manager stands in front of the owner trying to explain why no one saw this coming. The answer is they did see it coming. They just never did anything about it.

The real pain is not the problem itself. It is the preventability. These were not surprises. They were identified risks that no one managed. The stone lead time was knowable. The tile design gaps were visible. The material escalations were predictable. But the team never translated those concerns into action. They never created a system to track risks, assign ownership, and prevent them from materializing. And when the risks became reality, the project paid the price. Schedule delays. Budget overruns. Stress. Panic. Late nights. Blame. All of it preventable if someone had taken fifteen minutes in preconstruction to create a risk and opportunity register.

The failure pattern is predictable. Teams identify risks informally. Someone mentions a concern in a meeting. Someone else agrees it could be a problem. And then the conversation moves on. The risk never gets documented. It never gets quantified. It never gets assigned. And it never gets tracked. So it sits in the back of everyone’s mind as a vague concern until it materializes as an expensive problem. And when it does, the team reacts instead of prevents. They throw money at it. They compress the schedule. They work overtime. They stress out. And they repeat the pattern on the next project because no one ever built a system to prevent the cycle. The system failed them by never teaching them that risk management is not reacting to problems. It is preventing them from happening in the first place.

I worked on a research laboratory project where we used a risk and opportunity register from day one. We identified every major risk we could think of. Scaffolding for the complex exterior. Floor flatness tolerances. Design changes for the added fourth floor. Material escalations. We wrote them down. We assigned dollar values. We assigned likelihood percentages. We projected contingency usage. And we set to work preventing those risks from materializing. We expedited long-lead items. We locked in pricing early. We coordinated design issues before they hit the field. And the project finished fantastically. On time. Under budget. With margin to spare. Not because we got lucky. Because we managed risks instead of hoping they would not happen.

Fast forward to another project. I recommended a risk and opportunity register. I told the team the exterior stone and tile were high-risk items that needed early attention. But I did not have ultimate authority. And the team did not prioritize it. So we never formalized the register. We never assigned ownership. We never tracked it. And six months later, the stone procurement was delayed and nearly affected the end date. The exact risk I had identified became the exact problem that stressed the team. And it could have been prevented if we had created a system to manage it. That failure is on me for not being more forceful. But it is also on the system for not requiring risk management as standard practice.

This matters because every project has risks. Design gaps. Long-lead materials. Weather delays. Trade partner performance. Unforeseen conditions. Price escalations. These are not surprises. They are predictable categories of risk that show up on every project. And the teams that succeed are the ones who identify those risks early, quantify them, assign ownership, and prevent them from materializing. The teams that fail are the ones who hope for the best and react when things go wrong. Hope is not a strategy. And reaction is expensive. Prevention is cheap. It takes fifteen minutes to create a risk register. It takes weeks to fix the problem that the register would have prevented.

What a Risk and Opportunity Register Actually Is

A risk and opportunity register is a simple Excel sheet or matrix that tracks every identified risk and opportunity on the project. It has columns for description, original conditions of satisfaction, probability, dollar amount, owner, and target dates. And it gets reviewed weekly in team meetings so the team can see what risks are on the horizon and take action to prevent them. This is not complicated. This is a spreadsheet. But it changes everything because it makes risks visible, quantifiable, and actionable. And once risks are visible, teams stop hoping and start managing.

The power of the register is in the quantification. When you write down a risk, it is vague. When you assign a dollar value and a probability percentage, it becomes real. If the exterior stone delay has a 60 percent likelihood of happening and a 200,000 dollar impact, the team suddenly pays attention. They calculate that risk into their financial projections. They see that if the risk materializes, the project loses margin. And they act to prevent it. Without the register, the stone delay is just a concern. With the register, it is a 120,000 dollar exposure that needs to be managed. That difference is everything.

The register also creates accountability. Every risk has an owner. Someone is responsible for monitoring it and taking action to reduce the likelihood or the impact. The owner tracks the risk weekly. They report on it in team meetings. And they implement mitigation strategies. If the stone lead time is the risk, the owner expedites procurement, locks in pricing early, and coordinates installation sequencing. The risk does not just sit there waiting to happen. Someone is actively working to prevent it. And that ownership changes outcomes. If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow.

The register should also be integrated into monthly status reports. Most projects report on financials, schedule, quality, and safety. But they do not report on risk exposure. They say we are projecting 96 percent margin. But they do not say if all identified risks materialize, we are projecting 81 percent margin. That second number is the truth. And the team needs to see it. Because if the gap between the projected margin and the risk-adjusted margin is too large, the team needs to act. They need to reduce risks. They need to increase contingency. They need to change the plan. But without visibility into risk exposure, the team operates on false confidence. They think they are fine when they are actually vulnerable. And when risks materialize, they are blindsided.

How to Build and Use a Risk and Opportunity Register

Start by creating the register in your fresh eyes meeting or preconstruction kickoff. Gather the team. Brainstorm every risk you can think of. Design gaps. Long-lead materials. Weather exposure. Trade partner performance. Unforeseen site conditions. Regulatory approvals. Material escalations. Coordination challenges. Write them all down. Do not filter. Do not dismiss. Get everything on the table. Then prioritize. Assign dollar values to each risk. Estimate the likelihood. Calculate the total exposure. And decide which risks need immediate action.

Next, assign ownership. Every risk needs a name next to it. Someone owns monitoring the stone procurement. Someone owns tracking the design coordination. Someone owns managing weather exposure. And that person reports on the risk weekly in team meetings. They update the likelihood. They update the dollar amount. They report on mitigation actions. And if the risk is no longer a concern, they remove it from the register. Ownership creates accountability. And accountability drives action.

Review the register weekly in your team meeting. Do not let it sit on a shelf gathering dust. Make it a standing agenda item. Start every meeting by reviewing risks. What changed this week? What new risks emerged? What risks were mitigated? What actions are needed? This keeps the team focused on prevention instead of reaction. And it creates a rhythm where risk management becomes habit instead of afterthought. The teams that succeed are the ones who talk about risks every single week. The teams that fail are the ones who create the register once and forget about it.

Signs You Need a Risk and Opportunity Register

Watch for these patterns that signal you are operating without proper risk management:

  • Risks are discussed informally but never documented or tracked
  • Problems surface late when they are expensive to fix instead of early when they are cheap to prevent
  • The team reacts to issues instead of preventing them from happening
  • Financial projections do not account for identified risks or contingency exposure
  • No one owns monitoring specific risks or taking action to mitigate them
  • Team meetings focus on current problems instead of future risks
  • The project gets blindsided by issues that were foreseeable and preventable

These are not bad luck. These are system failures. And the fix is simple. Create a register. Track risks. Assign ownership. Review weekly. And prevent problems before they cost money.

Integrate Risk into Financial Reporting

One of the most powerful uses of the risk register is integrating it into financial projections. Most projects report a single margin number. We are projecting 96 percent. But that number assumes nothing goes wrong. It assumes all risks stay theoretical. And that is unrealistic. A better approach is to report two numbers. Projected margin if nothing goes wrong. And risk-adjusted margin if identified risks materialize. The gap between those two numbers is the truth. And the team needs to see it.

If your projected margin is 96 percent and your risk-adjusted margin is 81 percent, you have a problem. You have 15 percent of margin at risk. And unless you reduce those risks or increase contingency, you are vulnerable. That visibility creates urgency. The team stops operating on false confidence and starts acting to protect the project. They expedite procurement. They lock in pricing. They coordinate design. They reduce exposure. And the project finishes with margin intact because the team managed risk instead of ignoring it.

The Challenge

Walk into your next preconstruction meeting with a blank risk register template. Gather the team. Brainstorm every risk you can identify. Assign dollar values. Assign ownership. Calculate total exposure. And integrate it into your financial projections. Then review it weekly in team meetings. Track progress. Update probabilities. Remove mitigated risks. Add new ones. And watch what happens when the team shifts from reacting to problems to preventing them. As Dr. Eli Goldratt said, “Every situation can be substantially improved. Even the sky is not the limit.” Risk management is not about accepting bad outcomes. It is about preventing them. Build the register. Track the risks. Act early. And turn risks into opportunities before they turn into disasters. On we go.

Frequently Asked Questions

What is a risk and opportunity register?

A simple Excel matrix that tracks every identified risk with columns for description, probability, dollar amount, owner, and target dates, reviewed weekly to prevent risks from materializing.

How do you quantify risks on the register?

Assign a dollar value for the potential impact and a percentage for likelihood, then multiply them to calculate total exposure and integrate into financial projections.

How often should the risk register be reviewed?

Weekly in team meetings as a standing agenda item, with owners reporting on changes, mitigation actions, and updated probabilities for each risk.

What should be included in the risk register?

Design gaps, long-lead materials, weather exposure, trade performance, unforeseen conditions, regulatory approvals, material escalations, and coordination challenges.

How does the risk register integrate with financial reporting?

Report both projected margin assuming no issues and risk-adjusted margin if identified risks materialize, showing the gap and creating urgency to mitigate exposure.

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

Posted in All

Distributed Leadership – Lean, IPD Series Feat. Spencer Easton

Posted on by Jason Schroeder
Read 11 min

The Boss Who Holds All the Cards Loses

There is a type of leader who hoards information. They keep the plan in their head. They make every decision. They require signatures on everything. They bottleneck the team because nothing moves without their approval. And when you ask them why they operate this way, they will tell you it is about control. It is about quality. It is about making sure things get done right. But the truth is simpler and uglier. They are afraid. Afraid of losing power. Afraid of being exposed. Afraid that if they let go, the team will realize they are not as essential as they pretend to be. And that fear costs projects speed, innovation, trust, and results.

Here is what happens on a project led by a hierarchical boss. The superintendent needs approval to make a decision. But the project manager is in a meeting. So work stops. A foreman sees a problem coming. But he does not speak up because the last time he challenged the plan, he got shut down. So the problem surfaces three weeks later when it is expensive to fix. A trade partner has a better way to sequence the work. But they do not suggest it because nobody asked for their input. And the project limps along behind schedule and over budget while the boss wonders why the team is not performing. The answer is the boss. The boss created a system where the team cannot perform because everything flows through one person. And that person is the bottleneck.

The real pain is not the delays. It is the waste of talent. Every person on that team has skills, experience, and ideas that could improve the project. But the hierarchical system tells them to shut up and do what they are told. So they stop thinking. They stop caring. They show up, do the minimum, and go home. And the project never reaches its potential because the leader never unlocked the genius of the team. This is happening on jobsites every single day. And it is destroying projects, burning out workers, and driving good people out of the industry.

The failure pattern is predictable. Leaders default to hierarchy because it feels safe. If I control everything, nothing can go wrong without my knowledge. But hierarchy does not create safety. It creates dependency. The team becomes dependent on the boss to make every decision. And when the boss is unavailable, work stops. Hierarchy also kills accountability. When there is a power imbalance in the room, people stop holding each other accountable. They defer to the boss. They stay quiet even when they see problems. Because challenging the boss feels risky. And if the boss is also the person who determines their paycheck, the risk is real. So people protect themselves by shutting down. The system failed them by creating a structure where honesty and accountability are punished instead of rewarded.

There is a story from World War II that illustrates the cost of hierarchy. During the Normandy invasion, the Germans had panzer units that could have been dispatched to push back the Allied forces. But Hitler was asleep. And his commanders needed his approval to move the tanks. So they waited. And while they waited, the Allies gained ground. The Germans lost valuable territory because their system required everything to flow through one person. And that person was unavailable. The same thing happens on construction projects every day. The boss is in a meeting. The boss is traveling. The boss is overwhelmed. And the team sits idle waiting for approval that should never have been required in the first place.

I worked on a project years ago where the project manager controlled everything. He reviewed every submittal. He approved every purchase. He made every decision about sequencing and coordination. And the team hated it. The superintendent could not move without approval. The foreman could not solve problems in real time. And the trades stopped offering suggestions because they knew the answer would be no unless it came from the PM. The project finished late and over budget. And when the post-mortem happened, the client said the biggest issue was the lack of responsiveness. Problems sat for weeks because everything had to go through one person. The PM thought he was protecting quality. But he was destroying velocity. And the team paid the price.

This matters because distributed leadership outperforms hierarchical leadership every single time. Companies that operate with horizontal structures where leadership is shared across the team move faster, innovate better, and produce higher quality results. DPR Construction is a perfect example. They went from zero to over six billion dollars in annual revenue in 30 years by building a culture of distributed leadership. Everyone has a voice. Everyone can challenge the plan. And decisions are made by the people closest to the work. That model scales. That model wins. And that model creates loyalty because people feel valued instead of controlled.

Why Hierarchy Kills Accountability

Hierarchy reduces conflict and accountability. This is not obvious. Most people assume that hierarchy creates accountability because the boss holds people responsible. But the opposite is true. When there is a power imbalance in the room, people stop holding each other accountable. They defer to the boss. They stay quiet. They protect themselves. Because challenging someone who controls your paycheck feels dangerous. And even if the boss says they want feedback, the team does not fully believe it until they see it rewarded. Until someone speaks up, gets thanked, and sees it reflected in their paycheck, the risk feels real.

This is why high-functioning teams need trust first. Trust is the foundation of the five dysfunctions model. When people trust each other, they can have conflict. When they have conflict, they can commit to decisions together. When they commit, they can hold each other accountable. And when they hold each other accountable, they produce results. But hierarchy short-circuits this process. It skips trust and conflict and goes straight to compliance. The boss decides. The team executes. And nobody holds anyone accountable because accountability requires safety. And hierarchy does not create safety. It creates fear. If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow.

What Distributed Leadership Looks Like

Distributed leadership means power is shared across the team. The leader sets the vision, sets the parameters, and provides autonomy. They do not make every decision. They create the conditions where the team can make decisions together. And they trust the team to execute within agreed boundaries. This requires specific skills. Leaders need to facilitate group discussions instead of dominating them. They need to delegate authority instead of hoarding it. They need to give people the resources, tools, time, and training they need to succeed. They need to allow roles and responsibilities to shift as the project evolves. And they need to give ongoing feedback and coaching instead of disappearing and hoping people figure it out.

The mindset shift is critical. Leaders have to believe that power is greatest in the collective team, not in themselves. They have to openly share information instead of keeping it locked in their head. They have to encourage suggestions and ideas from everyone. They have to facilitate brainstorming instead of dictating solutions. And they have to allow problems to surface without punishing people for raising them. This is the opposite of how most construction leaders were trained. Most leaders were taught to control. To have all the answers. To never show weakness. But that model does not scale. And it does not create high-performing teams.

One simple way to signal distributed leadership is to change your org chart. Stop using the pyramid with the boss at the top and everyone below. Create a horizontal structure that shows functional areas on equal footing. Put the office and the field side by side. Show that leadership is shared. And communicate that structure to the team. Language matters too. Stop saying I and start saying we. Stop saying I am going to have you do this and start saying we need to figure this out together. Stop playing boss even if you are the boss. Create an environment where people do not feel your thumb on their forehead all the time.

Signs You Are Operating in Hierarchy Instead of Distributed Leadership

Watch for these patterns that signal you are stuck in hierarchical thinking:

  • You control all the information and keep the plan in your head instead of sharing it visually
  • You require approval for every decision instead of giving people autonomy within clear boundaries
  • Team members say they do not want to bother you even when you tell them you are available
  • People hide problems instead of surfacing them because they are afraid of your reaction
  • You make decisions alone and then tell the team instead of facilitating decisions together
  • You hoard signatures and approvals instead of delegating authority to people who are capable
  • The team shuts down when you are in the room instead of speaking up freely
  • You spend more time controlling than coaching and developing your people

These are not leadership. These are control mechanisms. And control mechanisms destroy velocity, innovation, and trust.

Building a Horizontal Team

Start by creating psychological safety. Tell the team you want their input. Tell them you want to be challenged. Tell them you want problems surfaced early. And then prove it. When someone speaks up, thank them. When someone challenges your plan, engage with it. When someone makes a mistake, coach them instead of punishing them. And when performance reviews come, reward the people who contributed to the team, not just the people who made you feel comfortable. Actions prove culture. Words just announce it.

Next, share information transparently. Put the schedule on the wall. Make the plan visible. Use visual management so everyone can see what is happening today, this week, and this phase. Stop hiding information in the trailer. Bring it to the field where it matters. Leaders who refuse to make information visible are the ones who want control. Leaders who make everything transparent are the ones who want collaboration. The choice signals your values.

Finally, let people fail forward. Give them autonomy. Let them make decisions. And when they make mistakes, coach them. A leader once said why I would fire someone who just cost me a million dollars in training. That is the mindset of distributed leadership. You invest in people. You develop them. You give them room to grow. And you trust that the collective genius of the team will outperform your individual genius every single time.

So here is the challenge. Evaluate your leadership style. Are you hoarding control or distributing it? Are you bottlenecking the team or unleashing them? Are you creating dependency or building capability? And if you see yourself in the hierarchical patterns, make the shift. Set the vision. Set the parameters. Give autonomy. Share information. Facilitate decisions. Coach relentlessly. And watch what happens when you stop playing boss and start building a team. As Brené Brown said, “Clear is kind and unclear is unkind.” Distributed leadership requires clarity about where you are going and trust that the team can get there together. Give them both. And get out of their way. On we go.

Frequently Asked Questions

What is distributed leadership and how is it different from hierarchy?

Distributed leadership shares power across the team with the leader setting vision and parameters while giving autonomy. Hierarchy concentrates decision-making in one person who becomes a bottleneck.

Why does hierarchy reduce accountability on teams?

Power imbalances make people afraid to challenge authority or hold each other accountable because the boss controls their paycheck, so they stay quiet to protect themselves.

What skills do leaders need to practice distributed leadership?

Group facilitation, delegation, management and coaching skills, organizational systems, ability to let people fail forward, and willingness to share information transparently.

How do you create psychological safety in a hierarchical organization?

Tell the team you want input and prove it by thanking people who speak up, engaging with challenges, coaching mistakes instead of punishing, and rewarding collaboration.

What is an example of a company that uses distributed leadership successfully?

DPR Construction grew from zero to over six billion in revenue in 30 years by building a culture where everyone has a voice and decisions are made closest to the work.

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

Posted in All

Emotional Range Feat. Brandon Montero

Posted on by Jason Schroeder
Read 13 min

The One-Tool Leader Who Cannot Win

Most construction leaders have one tool in their toolbox. Anger. When a trade falls behind, they get angry. When a worker makes a mistake, they get angry. When the schedule slips, they get angry. And when the project finishes and everyone is burnt out and the team never wants to work together again, they wonder why. The answer is simple. They only had one tool. And one tool cannot build great projects or great teams. You need emotional range. And most construction leaders have never been taught what that means or how to develop it.

Here is what happens on a typical jobsite. A superintendent walks the site and sees rework. His first response is anger. He finds the foreman and unloads. The foreman gets defensive. The crew hears the yelling and shuts down. Morale drops. Communication stops. And the problem that caused the rework never gets addressed because everyone is too busy managing the fallout from the explosion. This happens every single day on jobsites across the country. And it destroys projects. Because anger is a tool. But it is not the only tool. And leaders who only know how to grab the hammer when they need a chisel or a tape measure or a level are sabotaging their own success.

The real pain is not the yelling. It is the emptiness that follows. Workers go home feeling beat up. They feel undervalued. They feel like failures. And they carry that feeling into their families. Superintendents go home exhausted from the emotional drain of being angry all day. They have nothing left to give their spouse or their kids. And the cycle repeats. Day after day. Project after project. Until people burn out and leave the industry or become the same angry leader they once resented. This is not just a work problem. This is a life problem. Because how you show up at work is how you show up at home. And if your only tool is anger, you are going to damage both.

The failure pattern is predictable. Leaders default to anger because it is fast and it feels like control. Anger creates immediate compliance. People jump when you yell. And for leaders who measure success by immediate results, anger seems effective. But anger does not create engagement. It does not create trust. It does not create learning. It creates fear. And fear produces the bare minimum. Workers do just enough to avoid getting yelled at. They do not innovate. They do not problem-solve. They do not care. And the project suffers because the team is operating from fear instead of commitment. The system failed them by never teaching their leaders that there are other tools available. And the leaders failed themselves by never seeking those tools out.

I watched a superintendent on a project years ago who only had one tool. Anger. When the drywall crew made a mistake, he yelled. When the electricians were behind, he yelled. When the owner asked a question, he got defensive and confrontational. And the project spiraled. Quality suffered. Safety incidents increased. Turnover was high. And by the end of the project, the client refused to work with that superintendent again. The tragedy was not that he lacked technical skill. He knew construction. He knew scheduling. He knew coordination. But he had zero emotional range. And without emotional range, his technical skills could not save him. He lost future work. He damaged relationships. And he went home every night empty and angry. That is the cost of being a one-tool leader.

This matters because construction is bleeding talent. Good people are leaving the industry because they are tired of being yelled at. They are tired of environments where anger is the default response to every problem. And they are finding jobs in other industries where leaders treat them like human beings. Meanwhile, projects are struggling because teams are disengaged, communication is broken, and nobody trusts each other. This affects schedules because fear-based teams move slower. It affects quality because people who do not feel valued do not care about the details. It affects safety because burnt out and stressed workers make mistakes. And it affects families because workers go home empty and have nothing left to give. Emotional range is not soft. It is foundational. And leaders who refuse to develop it are limiting their own success and destroying the people around them.

What Emotional Range Actually Means

Emotional range means having multiple tools in your emotional toolbox and knowing which tool to use in each situation. It is not about being emotional. It is about having the capacity to respond appropriately to any situation you face. A leader with emotional range can be firm when firmness is needed. They can be empathetic when someone is struggling. They can be vulnerable when building trust requires it. They can be direct when clarity is needed. They can hold the line when consequences are appropriate. And they can show compassion when someone needs grace. This is not weakness. This is strength. Because real power is not the ability to yell louder than everyone else. Real power is having the ability to yell and choosing not to because a better tool will produce a better outcome.

Think about what it takes to succeed in construction. You need to have vulnerable conversations with trade partners. You need to be direct with workers who are underperforming. You need empathy to understand why someone is struggling. You need patience to train people with different learning styles. You need toughness to hold the line on safety or quality. You need the ability to fire someone when necessary and do it with dignity. You need the capacity to absorb stress without exploding. And you need the humility to admit when you are wrong and ask for help. None of that happens if your only tool is anger. Anger shuts down vulnerability. It destroys empathy. It prevents learning. And it makes people hide problems instead of surfacing them. If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow.

The old school superintendent had one tool. Get mad. Throw the hard hat. Yell at people. Assert dominance. And when the project finished, pat yourself on the back for having what it takes. But that is not what it takes. What it takes is a wide range of tools. And the leaders who succeed today are the ones who have invested in developing that range. They have learned how to have hard conversations calmly. They have learned how to coach instead of criticize. They have learned how to create psychological safety so people surface problems early. They have learned how to absorb chaos without becoming chaotic. And they have learned that being in control of a situation requires being in control of yourself first.

How to Develop Emotional Range

Emotional range is not something you are born with. It is something you develop. And there are specific ways to build it. First, invest in learning. Read books on leadership, communication, and emotional intelligence. Take courses on conflict resolution and coaching. Attend trainings that stretch you beyond your comfort zone. The tools you need are out there. But you have to go get them. Nobody is going to hand you a toolkit and say here is how to be a better leader. You have to seek it out. Books like How to Win Friends and Influence People, Leadership and Self-Deception, and The Five Dysfunctions of a Team will teach you tools you did not know existed. Trainings like Power Communication will teach you how to build rapport and connect with people. Conferences and boot camps will expose you to new ways of thinking. Every investment in learning is an investment in expanding your capacity.

Second, practice. Learning the tool is not the same as knowing how to use it. You have to practice. When you learn about empathy, look for opportunities to practice it. When you learn about vulnerability, test it in low-stakes situations. When you learn about holding boundaries, apply it. The only way to build muscle memory with these tools is to use them repeatedly until they become natural. And you will fail. You will grab the wrong tool. You will use the right tool poorly. But failure is part of the process. Fail forward. Learn from it. Adjust. And try again. The people who develop emotional range are the ones who keep practicing even after they mess up.

Third, seek feedback. You cannot see your own blind spots. Ask trusted colleagues, mentors, or your spouse to tell you when you are defaulting to anger or shutting down or using the wrong tool. Create space for them to be honest. And when they give you feedback, listen without getting defensive. Their perspective is a gift. It shows you where you need to grow. And it accelerates your development because you do not have to figure it out alone. Therapy, coaching, and mentorship are all forms of feedback. They help you see patterns you cannot see yourself. And they give you new tools to try.

Fourth, put yourself in situations that stretch you. Marry someone. Have kids. Lead a team. Take on hard projects. Volunteer. Serve in your community. Every hard situation is an opportunity to develop emotional range. Being alone is easy. You do not have conflict. You do not have to manage emotions. But you also do not grow. Relationships force you to develop tools. Marriage teaches you patience, vulnerability, and forgiveness. Parenting teaches you empathy, boundaries, and unconditional love. Leadership teaches you how to coach, confront, and inspire. And every time you navigate a hard situation successfully, your capacity grows. You become a bigger vessel. And situations that used to overwhelm you no longer do because you have the range to handle them.

Signs You Are a One-Tool Leader

Watch for these patterns that signal you lack emotional range:

  • Your default response to problems is anger or frustration
  • You avoid hard conversations because you do not know how to have them calmly
  • People hide problems from you because they are afraid of your reaction
  • You shut down emotionally and disappear when situations get uncomfortable
  • You struggle to give feedback without criticizing or blaming
  • You cannot admit when you are wrong or ask for help
  • Your team walks on eggshells around you
  • You go home empty every night with nothing left to give your family

These are not character flaws. These are skill gaps. And skill gaps can be closed.

Being Your Own Environment

One of the most powerful concepts in emotional range is the idea of being your own environment. Most people let the environment around them dictate how they show up. If the jobsite is chaotic, they become chaotic. If the team is angry, they become angry. If the schedule is behind, they panic. But leaders with emotional range do not let the environment control them. They create their own environment. They decide how they are going to show up regardless of what is happening around them. And that decision changes everything.

Imagine walking onto a jobsite where everyone is stressed. The schedule is behind. The trades are frustrated. The owner is asking questions. And you show up calm. Collected. Clear. You are not ignoring the chaos. You are absorbing it without becoming it. You assess the situation. You select the right tool. You address the problem with the appropriate level of pressure at the right time. And because you are not reactive, the team follows your lead. The environment starts to shift. Not because you controlled everyone else. But because you controlled yourself. And your calm became contagious. That is the power of being your own environment.

This applies at home too. You walk in after a hard day. The kids are crying. There is a mess. Your spouse is overwhelmed. And you have a choice. You can let the chaos pull you in. Or you can be your own environment. You can show up with patience. With empathy. With help. And watch how the environment changes when you refuse to be pulled into the chaos. This is not about ignoring reality. It is about choosing how you respond to reality. And that choice determines whether you add to the chaos or create calm in the middle of it.

Decide to Be Happy

One of the tools in your emotional toolkit is happiness. And happiness is a decision. Not a reaction. Most people treat happiness like something that happens to them. If the project goes well, they are happy. If the project struggles, they are miserable. But leaders with emotional range decide to be happy regardless of circumstances. They pull happiness out of their toolkit and use it intentionally. This does not mean ignoring problems or pretending everything is fine. It means choosing joy as your set point and returning to it even when life is hard.

The people who decide to be happy are the people everyone wants to work with. They are the people who create great team cultures. They are the people who inspire others. And they are the people who succeed long-term because they do not burn out. Happiness is a tool. And when you learn how to use it, you change your life and the lives of everyone around you.

So here is the challenge. Evaluate your emotional toolkit. What tools do you have? What tools are missing? And what are you going to do to get them? Stop defaulting to anger because it is all you know. Invest in learning. Practice new tools. Seek feedback. Put yourself in situations that stretch you. And watch what happens when you show up with the full range of tools you need to handle any situation. As W. Edwards Deming said, “Learning is not compulsory. Neither is survival.” If you want to survive and thrive in construction and in life, you need emotional range. Go get it. On we go.

Frequently Asked Questions

What is emotional range and why does it matter in construction?

Emotional range means having multiple tools in your emotional toolkit and knowing which tool to use in each situation, not just defaulting to anger or shutting down.

How do you develop emotional range?

Invest in learning through books and training, practice new tools in real situations, seek feedback from trusted people, and put yourself in stretching situations like relationships and leadership.

What does it mean to be your own environment?

Being your own environment means deciding how you will show up regardless of the chaos around you, creating calm instead of reacting to chaos.

Why do leaders default to anger?

Anger is fast and feels like control because it creates immediate compliance, but it destroys trust, engagement, and long-term performance.

Can happiness really be a decision?

Yes. Happiness is a tool you can intentionally choose as your set point and return to even when circumstances are difficult, rather than waiting for circumstances to make you happy.

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

Posted in All

The 7 Wonders of the World Feat. Dr. Grennan

Posted on by Jason Schroeder
Read 13 min

The Seven Wonders Your Team Actually Needs

A teacher once asked her students to name the seven wonders of the world. Most students wrote down the Great Pyramid, the Taj Mahal, the Grand Canyon, and the Great Wall of China. But one little girl from Ecuador wrote something different. She listed touch, taste, see, hear, feel, laugh, and love. Not monuments. Not buildings. The fundamental human experiences that make life worth living. When the teacher asked why, the girl said these are the things people can do every day that make life wonderful. And she was right. But construction has forgotten this truth entirely.

Here is what happens on most jobsites. A superintendent shows up Monday morning. The crew is already there. He walks past them without making eye contact. He barks the day’s assignments. He criticizes yesterday’s work. He disappears into the trailer for three hours. The crew works in chaos because there is no visual plan. They eat garbage from a food truck because there is no time for a real break. They strain their bodies in awkward positions because that is just how the work gets done. Nobody laughs. Nobody feels appreciated. And at the end of the day, everyone goes home exhausted and empty. This is not an isolated incident. This is the norm. And it is destroying people.

The real pain is not the physical strain. It is the emptiness. Workers spend 50, 60, sometimes 70 hours a week on jobsites where they are treated like tools instead of human beings. They are not seen. They are not heard. They are not valued. And they feel it. They feel underappreciated. They feel disposable. They feel like a number on a schedule instead of a person with a family and a life. And that feeling follows them home. It affects their marriage. It affects their kids. It affects their health. And it affects their performance. Because you cannot separate the person from the worker. How someone shows up at work is directly connected to how they are experiencing the seven wonders that little girl identified.

The failure pattern is predictable. Leaders focus exclusively on outputs. Did the work get done? Did we hit the schedule? Did we stay on budget? But they ignore inputs. What is the worker seeing, hearing, tasting, touching, and feeling throughout the day? Are they laughing? Are they loved? And when those inputs are negative or absent, the outputs deteriorate. Workers become disengaged. They stop caring. They show up physically but not mentally or emotionally. The system starves people of fundamental human experiences and then blames them when performance suffers. But the truth is the system failed them. They did not fail the system.

I worked on a research laboratory project where the team culture was different. The superintendent knew every worker by name. He walked the site every morning and made eye contact. He asked how people were doing. He created visual communication so everyone could see the plan. He built a break room with real food and comfortable seating. He encouraged laughter. He celebrated wins. And the crew responded. They showed up early. They stayed late when needed. They cared about quality because they felt cared for. That project finished ahead of schedule with zero safety incidents and a client who became a raving fan. And the difference was not the technical skill of the team. The difference was that the superintendent created an environment where people experienced the seven wonders. They were seen. They were heard. They were valued. And they gave their whole heart in return.

This matters because construction is bleeding talent. Good people are leaving the industry because they are tired of being treated like machines. They are tired of the chaos, the disrespect, the lack of appreciation. And they are finding jobs in other industries where they feel valued. Meanwhile, projects are struggling to find qualified workers. Schedules are slipping. Quality is suffering. And safety incidents are increasing. All because leadership refuses to recognize that people are not machines. People need to experience touch, taste, sight, hearing, feeling, laughter, and love. And when those needs go unmet, everything else falls apart. This affects schedules because disengaged workers are slower. It affects quality because people who do not care do not produce great work. It affects safety because distracted and burnt out workers make mistakes. And it affects families because workers go home empty and have nothing left to give.

What You Take In Determines What Comes Out

Input equals output. This is true in every area of life. What you take in through your senses, your experiences, and your relationships directly affects what comes out in your behavior, your performance, and your results. If you are seeing garbage media all day, you will think garbage thoughts. If you are hearing negativity and criticism constantly, you will speak negatively. If you are tasting processed junk food, you will feel sluggish and unfocused. And if you are not experiencing touch, laughter, and love, you will show up empty at work. This is not soft. This is reality. And construction leaders who ignore this reality are sabotaging their own teams.

Think about what your team is taking in on a daily basis. What are they seeing when they arrive at the site? Chaos. Poor planning. Rework. Unsafe conditions. Frustration on faces. Or are they seeing visual communication that makes the plan clear? Are they seeing leadership walking the site and engaging with them? Are they seeing respect and organization? What are they hearing? Are they hearing blame, yelling, and unrealistic demands? Or are they hearing encouragement, constructive feedback, and appreciation? The tone you use matters more than you realize. A foreman can deliver the same message in two different tones and get completely different results. One tone inspires. The other demoralizes. What are they tasting? Fast food and energy drinks because there is no time for a real meal? Or are you creating space for proper breaks where people can fuel their bodies well? Nutrition affects cognitive performance, energy levels, and mood. A team that eats garbage feels like garbage.

What are they touching? Are workers bending, reaching, and straining in unsafe or awkward positions because that is just how construction is? Or are you designing the work to adapt to the worker instead of forcing the worker to adapt to the work? This is where prefabrication matters. Bring the work to a controlled environment where it can be done safely and efficiently. Eliminate unnecessary strain. And recognize that touch extends beyond the physical. A pat on the shoulder. A handshake. A gesture of connection. These small touches communicate care. And care builds loyalty. What are they feeling physically and emotionally? Are they in pain? Are they stressed? Are they burnt out? And if so, are you addressing it or ignoring it? People who do not feel good do not perform well. Period. If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow.

Are they laughing? Most construction sites are silent and joyless. But laughter creates connection. It relieves stress. It builds team cohesion. And it makes hard work bearable. If your site feels like a grind every single day with zero moments of joy, something is broken. Create space for humor. Celebrate small wins. Let people enjoy the work. And watch what happens when the environment shifts from grinding through the day to actually experiencing it together. Are they loved? Not romantic love. But the kind of love that says I care about you as a person. I see your value. I want you to succeed. I will invest in your growth. Leaders who love their people create the conditions where people give their whole heart, not just their hands. A 40-year-old retiree once said at his retirement party, for 40 years they had the work of my hands when they could have had the work of my hands, my mind, and my heart for no additional money. All they would have had to do was ask or create that environment.

How to Create an Environment Where People Thrive

Start with sight. Make the plan visible. Put it on the wall. Use visual management so everyone can see what is happening today, this week, and this phase. Stop hiding information in the trailer. Bring it to the field where it matters. Walk the site every morning. Make eye contact with your people. See them. Not just as workers. But as human beings. Notice their body language. Notice when someone is struggling. And respond with empathy instead of indifference. What workers see every day either builds confidence or creates chaos. Choose clarity.

Move to hearing. Pay attention to your tone. Are you barking orders or communicating with respect? Are you criticizing mistakes or coaching through them? The way you sound sets the tone for the entire project. Create space for your team to be heard. Ask questions. Listen to their input. Value their perspective. When someone makes a mistake, address it with curiosity instead of anger. What happened? What can we learn? How do we prevent it next time? That tone builds trust. The other tone builds resentment. Also recognize what silence communicates. If you never praise good work, your silence says you do not care. Speak up. Acknowledge effort. Celebrate wins.

Address touch and feel together. Eliminate unnecessary physical strain. Use prefabrication to bring work to controlled environments where it can be done safely. Stop forcing workers into awkward positions that damage their bodies. And recognize that emotional strain is just as real as physical strain. Check in with your people. How are you doing? How is your family? Is there anything you need? These small gestures communicate care. And when people feel cared for, they care back. Also recognize the power of physical connection. A handshake. A pat on the shoulder. A high five after a job well done. These touches build connection and show appreciation.

Fix taste by creating space for proper breaks. Stop expecting people to survive on fast food and energy drinks. Provide access to real food. Give people time to eat. Nutrition affects performance. And a team that eats well performs better than a team that eats garbage. This seems small but it matters. Also think about what tastes good beyond food. What experiences are you creating that people enjoy? What moments are worth savoring? Make the work something people want to taste, not something they have to choke down.

Signs Your Team Is Missing the Seven Wonders

Watch for these signals that your team is not experiencing the inputs they need:

  • Morale is low and people seem disengaged or emotionally checked out
  • Turnover is high and good people keep leaving for other opportunities
  • Safety incidents are increasing because workers are distracted or careless
  • Quality issues are surfacing because people do not care about the details anymore
  • Communication is poor and conflicts go unresolved for long periods
  • Nobody is laughing or enjoying the work, the site feels joyless every day
  • Workers show up physically but not mentally or emotionally

These are not people problems. These are leadership problems. And the fix starts with creating an environment where people can experience the seven wonders every day.

Build People First

Construction exists to build great things. But great things are built by great people. And great people are not machines. They are human beings with senses, emotions, families, and needs. When those needs are met, people thrive. They engage. They contribute. They care. And the project benefits. When those needs are ignored, people shut down. They disengage. They do the bare minimum. And the project suffers. The choice is yours. You can keep treating people like tools and wondering why performance is mediocre. Or you can invest in creating an environment where people experience the seven wonders and watch what happens when they give you their whole heart.

This is about dignity. Construction should be a place where people are respected, valued, and treated like the skilled professionals they are. This is about flow. When people feel good, work flows. When people feel terrible, everything grinds to a halt. This is about stability. Families need stability. And workers who go home empty because they spent the day being treated like garbage cannot provide that stability. The mission of construction should not just be building structures. It should be building people who build structures. And that starts with recognizing that the seven wonders that little girl identified are not soft. They are foundational.

So here is the challenge. Walk your project this week and evaluate the seven wonders. What are your people seeing, hearing, tasting, touching, and feeling? Are they laughing? Are they loved? And if the answers reveal gaps, fix them. Start small. Improve the tone you use. Add visual communication. Create space for breaks. Show appreciation. Build connection. And watch what happens when you stop treating people like machines and start treating them like human beings. You cannot separate the person from the worker. How someone shows up at work is directly connected to how they are experiencing life. And if you want better outputs, you need to invest in better inputs. As Dr. W. Edwards Deming said, “A bad system will beat a good person every time.” Stop blaming your people for poor performance and start building a system where they can experience the seven wonders every day. On we go.

Frequently Asked Questions

What are the seven wonders from the little girl’s perspective?

Touch, taste, see, hear, feel, laugh, and love. These fundamental human experiences matter more than physical monuments and directly affect how people show up at work.

How does input equal output in construction?

What people take in through their senses and experiences directly affects behavior and performance. Negative inputs like chaos, disrespect, and poor nutrition produce disengaged workers and poor results.

Why do construction cultures resist laughter and love?

Many leaders see these as soft or unprofessional, but laughter builds connection and relieves stress while love creates loyalty and inspires people to give their whole heart.

How can leaders improve what workers are seeing and hearing daily?

Use visual management for clarity, speak with respectful tone, listen to input, make eye contact, notice body language, and create an environment where people feel valued.

What is the difference between using people and loving people at work?

Using people treats them as tools for tasks. Loving people invests in their growth, values their contribution, and creates conditions where they give their whole heart instead of just their hands.

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

Posted in All

What Is Most Important in 2021 Feat. Charlie Dunn

Posted on by Jason Schroeder
Read 11 min

Why Construction Is 230 Years Behind Manufacturing

Most construction projects start the same way. Raw materials arrive at the site. Workers measure, cut, fit, and assemble everything in the field. They work in rain, heat, cold, and unsafe conditions. They bend, reach, and overextend to install components in awkward positions. They coordinate on the fly. They rework mistakes. They generate waste. And when the project finishes, everyone moves to the next site and does it all over again the exact same way. This is not progress. This is repetition. And it is costing the industry productivity, safety, quality, and the ability to attract the next generation of workers.

Here is the uncomfortable truth. Construction is about 230 years behind manufacturing. Manufacturing had its industrial revolution in the late 1700s and early 1800s when standardized interchangeable parts enabled assembly lines, automation, and focused study. Construction has not had that revolution yet. We are still adapting the worker to the work instead of adapting the work to the worker. We are still treating every project like a prototype instead of leveraging design reuse and standardization. And we are still defaulting to stick-building everything on site when prefabrication could solve most of the problems we complain about daily.

The failure pattern is predictable. Teams wait until design is 100 percent complete. Then they reverse engineer it, break it apart, and try to figure out how to build it. Sometimes they do a halfway decent job of that planning. Sometimes they are in the field trying to figure it out while the clock is running. Either way, the default assumption is that everything will be built stick by stick on site. And prefabrication, if it happens at all, is treated as the exception. A nice-to-have. An innovation. Something you consider if you have extra time or budget. This is backwards. Prefabrication should be the default. And stick-building should be the negotiated exception.

I worked on a research laboratory project where we prefabricated everything we could. We prefabricated all of the overhead MEP in spools on the first two floors around priority walls that were 80 percent complete. We pre-cut all of the studs, box headers, jams, and stud lengths. Everything came out pre-cut. We had drastically reduced waste. We did room kitting inside where we had people prefabricate the interiors. And when I look back on that project, prefabrication was the best thing we did. Not just because it improved safety and quality. But because it vetted the design issues earlier. If we could not build it on paper and prefabricate it in the shop, then we never had the right information to build it in place in the field. We were missing a dimension or a coordination issue or something else. Prefabrication pre-vets the design before it becomes a schedule impact. And it takes the work out of the chaotic field environment and puts it into a controlled environment where standard work, safety, and quality can actually be managed.

Why Prefabrication Matters More Than You Think

Prefabrication is not just about moving work offsite. It is about fundamentally changing the presumption of how construction happens. And there are three reasons why this shift matters more than most people realize. The first is empathy. The second is production design. And the third is design reuse. Together, these three shifts will create more value for construction over the next decade than any other innovation. And prefabrication is the engine that makes all three possible.

Empathy means beginning with the worker in mind instead of adapting the worker to the work. Construction has traditionally forced workers into unsafe conditions, awkward positions, and congested environments. Workers bend, reach, and overextend because that is just considered part of the challenge. But with prefabrication, we can adapt the work to the worker. We can create safe environments. Well-lit environments. Decongested environments. And we can provide super clear visual explanations like we are used to seeing in other industries. This is not just about being nice. This is about recognizing that the future of construction capital is threatened if we cannot grow the workforce, create excitement about the industry, and create safer and more inspiring working conditions. Vertically integrated owners with large portfolios of projects are starting to demand this. They are saying they will not accept the kind of safety numbers on construction sites that they would never tolerate in their manufacturing facilities. And prefabrication is one of the primary tools that enables that shift.

Production design means designing the building with the end in mind. In other industries like automotive or home appliances, you would never design a new product without strategically knowing how you plan to build it. But in construction, this is foreign. We get 100 percent design and then reverse engineer it to figure out if we can build it. Production design flips that. It starts with understanding what the supply chain can do, what factories can do, and what the workforce can do. And it designs the building with production design principles so that it can be delivered safely, with high quality, and with good productivity. This requires designers and builders to work together earlier. It requires integrated delivery methods. And it requires a mindset shift from designing in isolation to designing with production in mind.

Design reuse means not starting from zero on every project. Right now, every project goes through the same long runway of design, price, redesign, coordinate, price, and redesign. And that cycle repeats on every single project even when the building type is the same. Data centers, healthcare MOBs, pharmaceutical plants, and other building types with repetitive programs are still designed from scratch every time with different designers, different design components, and different coordination processes. This is wasteful. What if we could get to 70 percent design reuse? What if vertically integrated owners could say here is our standard design for this building type and we are only customizing the last 30 percent? That would eliminate years of rework. It would reduce chaos in the field. And it would allow teams to focus on the unique aspects of the project instead of reinventing the wheel every time. If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow.

Signs You Are Stuck in the Old Default

Here are the signals that your team is still defaulting to stick-building instead of prefabrication:

  • You reverse engineer the design after it is 100 percent complete instead of planning production during design
  • Workers are bending, reaching, and working in unsafe or awkward positions because that is just how the work has to be done
  • You generate significant waste from cutting materials on site instead of pre-cutting in a controlled environment
  • Design issues and coordination problems surface in the field instead of being caught during prefabrication planning
  • Every project feels like a prototype instead of leveraging standardization and lessons learned from previous projects
  • Prefabrication is treated as an innovation or exception instead of the default approach
  • You assume everything will be stick-built unless someone makes a compelling case for prefab

These patterns are not inevitable. They are choices. And they can be changed by shifting the default assumption.

How to Shift the Default

Changing the presumption from stick-building to prefabrication requires intentional effort. It requires leadership to make the case. It requires trade partners to adjust their approach. And it requires designers to think differently about how buildings are designed. Here is how to start. First, change the language. Stop saying we are going to try prefabrication on this project. Start saying everything will be prefabricated unless there is a compelling reason not to. Make stick-building the negotiated exception instead of prefabrication being the innovation. That language shift changes how teams approach planning.

Second, engage the supply chain early. Do not wait until design is complete to figure out what can be prefabricated. Bring trade partners and fabricators into the conversation during design so they can inform what is possible and what needs to be coordinated. This is production design in action. And it requires integrated delivery methods that allow the team to collaborate before the design is locked.

Third, invest in design reuse. If your organization builds the same building types repeatedly, stop designing from scratch every time. Develop standard designs that can be customized for specific sites and user needs. This does not mean cookie-cutter buildings. It means baking in the lessons learned, the coordination, and the production planning so you are starting from 50, 60, or 70 percent instead of zero. The time saved in design and coordination can be reinvested in making the unique aspects of the project better.

Fourth, create the right environment for prefabrication. Lean manufacturing works because the environment supports standard work, visual management, and continuous improvement. Construction has been trying to bring lean to the chaotic field environment. But prefabrication flips that. It brings the work to the controlled environment where lean principles can actually function. Safe, well-lit, decongested spaces with clear visual instructions enable workers to do better work faster with less waste.

Fifth, push through resistance. Some people will resist prefabrication because it requires them to think differently, plan earlier, and coordinate more intentionally. Do not let that resistance stop progress. As one lean manufacturing leader said when asked what to do when trade partners resist the plan, you whip them in the ass. That is not about being cruel. It is about being firm. Prefabrication will not work if it is optional. It has to be the expectation. And teams need to experience it for six weeks before they can truly choose. Until they have both options in front of them, they cannot make an informed choice. So push it down everyone’s throat until they see how great it is. Then it becomes self-sustaining.

The Challenge

Walk your next project and ask yourself this question. What are we building stick by stick on site that could be prefabricated in a controlled environment? What design decisions are we making without understanding how the building will be produced? What lessons are we learning on this project that we will have to relearn on the next one because we are not capturing design reuse? And what are we doing to our workers by forcing them to adapt to unsafe, inefficient, and chaotic conditions instead of adapting the work to the worker? If the answers to those questions reveal opportunities, you have a choice. You can keep doing what you have always done. Or you can shift the default. Default to prefabrication. Make stick-building the exception. And watch what happens when you stop treating every project like a prototype and start building with empathy, production design, and design reuse.

Construction’s industrial revolution is not in the past. It is in the future. And prefabrication is the engine that will get us there. As Charlie Dunne said, “Fall in love with your problems, not your solutions.” The problem is that we are 230 years behind manufacturing. The solution is prefabrication. And the time to shift the default is now.

On we go.

Frequently Asked Questions

Why is construction 230 years behind manufacturing?

Manufacturing adopted standardized interchangeable parts in the late 1700s, enabling assembly lines and automation. Construction still defaults to stick-building everything on site without standardization.

What are the three big shifts prefabrication enables?

Empathy for workers by adapting work to the worker, production design that plans how to build during design, and design reuse that eliminates starting from zero.

How do you overcome resistance to prefabrication?

Change the default assumption so prefabrication is expected and stick-building is the exception. Push through resistance by requiring teams to experience it before choosing.

What is production design?

Designing the building with understanding of how it will be built, including supply chain capabilities, factory capabilities, and workforce capabilities, rather than reverse engineering after design is complete.

What does design reuse mean for repetitive building types?

Starting from 50-70 percent standardized design instead of zero, eliminating the rework cycle of design, price, redesign, coordinate on every project for building types like data centers or healthcare.

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

Posted in All