The Levers You Can Pull for Change – Part 1

Read 9 min

A Lever, Not a Guess: Why Systems Thinking Changes How You Fix Construction Problems

A Lever, Not a Guess

Picture a balance scale. On one side sits the entire system you are trying to change, a project, a company, an industry. On the other side sits a row of twelve pressure points, ranked from weakest to strongest, that determine how much leverage you actually have to move that system.

That image comes from Donella Meadows, and it reframes something every builder eventually runs into. Change in a complex system almost never comes from randomly pulling on whatever lever is closest. It comes from knowing exactly which lever you are pulling, and how much weight it actually carries.

The Real Pain: Fixing Symptoms One at a Time

Most teams do not approach change this way. A schedule slips, so someone adds a meeting. Costs run over, so someone adds another approval step. Quality suffers, so someone adds another inspection.

Each fix feels reasonable in isolation. None of them ask the deeper question: what is this system actually designed to produce, and is that even the outcome we want? Without that question, teams end up making dozens of small adjustments that never touch the real source of the problem.

The Failure Pattern: Pulling the Weakest Levers

Meadows’ framework ranks leverage points from weak to strong for a reason. Numbers, parameters, and buffer sizes sit near the bottom. They are the easiest to change and the least powerful, which is exactly why most organizations default to them.

Paradigms and goals sit near the top. They are harder to touch, but they carry far more weight, because changing a goal changes everything beneath it: the rules, the structure, the information flows, all of it. Teams that only ever adjust the weak levers stay stuck making the same mistakes with slightly different numbers attached.

A few low-leverage habits tend to show up in teams stuck in this pattern, and they are worth naming honestly:

  • Adding more meetings or more approval steps instead of asking why the current process keeps producing delays.
  • Extending the schedule or adding manpower instead of examining whether the plan was ever realistic in the first place.
  • Changing a policy’s wording without changing the mindset or goal the policy was actually built to serve.

This Isn’t a People Problem, It’s a Leverage Problem

None of this means a team is careless or unwilling to improve. Most people were simply never taught to look at a system’s paradigm or goal before reaching for a fix. They were taught to solve the problem in front of them, which is a reasonable instinct, just not always the most effective one.

The system failed them by never showing them where the real leverage lives. Once a team understands that paradigms, mindsets, and goals sit at the top of that lever, the whole approach to problem solving changes.

The Delivery Rule and the Wallet Story

Here is what that looks like in practice. On one project, the rule was simple: if a delivery arrived late and got in the way of another trade, it got turned around, no exceptions. Some people on that job saw that rule and assumed leadership was simply being difficult.

So during a morning huddle, the response was to pull out a wallet and ask a direct question. If someone reached in and took a couple hundred dollars in cash, would that be acceptable? Everyone agreed it would not. Then came the connection: when a rogue delivery blocks another trade’s crew, and five or six workers sit idle for an hour at forty to eighty-five dollars an hour in burdened labor that is not an inconvenience that is real money taken from real people.

That single conversation did more to shift the mindset on that project than any written policy could have. It did not just enforce a rule, it changed how people saw the paradigm behind the rule, which is exactly the kind of high-leverage move Meadows describes.

Why It Matters: You Can’t Fix a Symptom the System Is Built to Produce

This distinction matters far beyond one delivery rule. It explains something much bigger about why construction, as an industry, keeps getting the same disappointing results year after year. As Jason likes to say, borrowing from his friend Hal Macomber, systems are perfectly designed to achieve the results that they are getting.

Look at how many projects in the United States finish late, and ask what goal the current system is actually optimized for. A schedule format that is dense, siloed, and hard to read in a courtroom does not accidentally survive for decades. It survives because an opaque, hard-to-litigate schedule serves the goal of shifting risk downstream rather than the goal of finishing on time. A visual, transparent plan like a Takt plan makes delays and responsibility obvious to everyone, which is precisely why systems built around avoiding accountability tend to resist it.

None of this is really about individual people being dishonest. It is about a contracting system whose actual goal, whether anyone admits it out loud or not, has quietly become risk avoidance rather than on-time delivery. Until that underlying goal changes, no amount of software, extra meetings, or schedule tweaks will fix it, because the system is already accomplishing exactly what it was built to accomplish.

Teach the Framework: Where the Real Leverage Lives

Meadows organizes twelve leverage points into a few categories: physical events like buffer sizes and constants, informational patterns like feedback loops and information flows, system structure like rules and structure itself, and, at the very top, the mindsets and paradigms a system springs from.

Paradigms are the deepest lever of all, the shared, often unstated assumptions a system is built on. A company whose paradigm is pure profit will make different decisions than a company whose paradigm is blessing the lives of the people it serves, even facing the identical problem. Mindsets are the individual beliefs people hold within that paradigm, and they can shift even when the paradigm itself stays the same, which is exactly what happened with the wallet story above. Goals sit just below paradigms and mindsets, and changing a goal cascades down through every rule, structure, and feedback loop beneath it.

Before touching any system, three questions are worth asking in order, and they are worth keeping close at hand:

  • What is the paradigm this system was built on, and do the people inside it actually share it?
  • What individual mindsets exist inside that paradigm, and could shifting them change the outcome?
  • What is this system’s actual goal, not the stated one, but the one its current results suggest it is really optimized for?

Turning This Into Daily Practice

The good news is that the highest-leverage tools available are often simple and already within reach. Morning huddles, orientations, and onboarding are not just administrative checkboxes, they are one of the most direct ways to shape mindset inside a project’s paradigm, the same way the wallet story did.

A simple plus-delta exercise illustrates this well. Asking “what did you like and dislike about this meeting” targets a completely different goal than asking “did we accomplish the purpose of this meeting, and where did we fall short.” Same format, same five minutes, but a different goal produces a different outcome entirely.

Connecting It Back to Building People, Not Just Projects

None of this happens without leaders who are willing to look past the nearest fix and ask harder questions about paradigm, mindset, and goal. That is a different kind of training than teaching someone to read a schedule, and it is just as important.

If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow, starting with the mindsets and goals that shape everything else on the job.

The Challenge

So here is the challenge worth carrying into your next team meeting: before you reach for another policy tweak or another meeting to fix a problem, stop and ask what your system’s actual goal seems to be, based on the results it keeps producing. As Jason likes to say, borrowing from his friend Hal Macomber, systems are perfectly designed to achieve the results that they are getting. If you do not like your results, the goal, not the schedule, is probably the place to start. On we go.

FAQ

What are Donella Meadows’ leverage points, in simple terms?

They are twelve places you can intervene in a complex system, ranked from weak to strong. The weakest are things like numbers and buffer sizes, and the strongest are the paradigm and mindset a system is built on, along with the goal it is actually pursuing.

Why do paradigms and goals carry more leverage than rules or numbers?

Because changing a goal or a paradigm cascades down through everything beneath it, including the rules, the structure, and the information flows a system uses. Changing a number or a buffer size only affects that one component, which is why it takes far more effort for far less lasting change.

What does it mean to say a system is “perfectly designed to get the results it’s getting”?

It means that current outcomes, good or bad, are not random accidents, they are the natural output of how the system is actually built and what it is actually optimized for. If the results are disappointing, the fix has to start with the system’s real goal, not just its surface-level processes.

How does the delivery rule story connect to systems thinking?

Simply announcing a rule changes very little if people do not understand or agree with the paradigm behind it. Reframing the rule around respect and real financial impact shifted people’s mindset within the existing paradigm, which is a much higher-leverage move than just repeating the rule louder.

How can a project team start applying this without reading the whole book?

Start with the three questions: what paradigm is this system built on, what mindsets exist inside that paradigm, and what is the system’s real goal based on its actual results. Asking those questions before reaching for a fix is often enough to reveal where the real leverage lives.

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.

Posted in All

The Key 3 for Finances!

Read 9 min

Your Business Needs a Production System Too: Why Every Builder Needs an Accountant, an Advisor, and a Lawyer

The Nightmare Accountant

When Elevate Construction first got off the ground, the accountant handling the books would call every month asking what specific expenses in QuickBooks were actually for. Nothing was ever reconciled. Nobody knew where the money was going, and there was no real tax plan in place.

It was a mess, plain and simple, the financial version of a project running with no schedule, no zones, and no plan. Just reacting, month after month, and hoping it worked out.

The Real Pain: Running a Business on Hope

That story is not unusual. A lot of builders and superintendents run their own businesses and personal finances the exact same reactive way they would never tolerate on a jobsite. No real plan, no dedicated professionals, no system, just hoping things work out at tax time.

It shows up in specific, familiar ways: a business owner who has no fiduciary financial advisor, no accountant who actually reconciles the books, and no lawyer in place before a contract or partnership needs one. The irony is that many of these same people run tight, disciplined systems on their projects, and then leave their own financial house completely unmanaged.

The Failure Pattern: Waiting Until It Costs You

The pattern is easy to spot once you see it. People wait until there is a tax problem, a lawsuit, or a lost opportunity before they ever bring in the right professionals. By then, the damage is already done.

One story makes this painfully clear: a business owner in Rich Dad Poor Dad had a great idea, real money, and real customers, but lost the whole business because the idea was never patented. He had the vision and the capital. He just never protected it legally, and it cost him everything.

A few warning signs tend to show up when a business or a family is running its finances the same reactive way:

  • Nobody can say clearly what the plan is for savings, investing, or taxes this year.
  • The accountant is asked what expenses were for instead of the other way around.
  • Legal agreements get signed or contracts get entered without anyone reviewing them first.

This Isn’t a Character Flaw, It’s a Missing System

None of this makes someone careless or bad with money. Most people were simply never taught to think about finances as a system that needs to be designed, the same way a production plan needs to be designed before boots hit the deck.

Financial mindset gets set early, often by whatever income level a person grew up around, and that set point sticks with people whether they realize it or not. Wanting more is not greed. It is simply recognizing that nobody handed you a plan, so you have to build one.

How One Bad Accountant Led to a Real System

After enough frustration with the first accountant, a good friend made an introduction to a high-level financial advisor, someone who normally worked with much bigger clients but agreed to help because the mission of the company resonated with him. The retainer was ten thousand dollars, real money for a startup with almost nothing in the bank, but it got paid anyway.

That decision changed the trajectory of the business. The advisor helped find a much better accountant, one who actually reconciles the books every month and builds a real tax strategy instead of scrambling at the deadline. The result was a business legally using every available strategy instead of guessing and hoping.

Why It Matters Far Beyond a Tax Return

This matters because the stakes are not just numbers on a spreadsheet, they are the stability of a family and the survival of a business. A missed tax strategy or an unprotected idea can undo years of hard work overnight.

Just like a project without a real plan eventually crashes into chaos, a business or a family without real financial systems eventually gets blindsided by something that could have been planned for. Protecting the business is protecting the people who depend on it.

Building the Three-Person Team That Keeps You Safe

The foundation is simple to name, even if it takes real effort to build: a great accountant, a fiduciary financial advisor, and a good lawyer. A fiduciary matters specifically because they are legally obligated to act in your best interest, unlike a broker who may be selling a product that benefits them more than you.

Each piece does a different job. The accountant reconciles the books, handles billing, and builds a tax strategy that actually gets used. The financial advisor helps direct where money goes, from retirement accounts to investments to bigger financial goals, and helps reprogram how you think about money in the first place. The lawyer protects the business before a contract gets signed or a partnership goes wrong, not after.

None of the three professionals can substitute for the other two. A great accountant without a lawyer still leaves the business exposed the moment a handshake deal goes sideways. A great lawyer without a financial advisor still leaves money sitting in the wrong places, earning far less than it could. The system only works when all three pieces are in place together, the same way a production system only holds up when planning, rhythm, and commitment are all connected.

Turning This Into a Daily and Yearly Practice

Building real financial systems does not require becoming a finance expert overnight. It starts with a few basic habits: spend less than you earn, automate savings so it happens without relying on willpower, and treat investing as something you revisit consistently rather than something you set and forget.

A few practical starting points make the difference between hoping and actually planning:

  • Choose a fiduciary advisor over a broker, and don’t be afraid to make a change if the current one is not working in your best interest.
  • Set a real savings target, ideally in the 10 to 20 percent range, and automate it so it happens every month.
  • Get professional coaching or training instead of trying to figure it out alone, the same way you would never run a first project without any training at all.

Connecting It Back to Building People, Not Just Buildings

None of this happens by accident, and it is not weakness to admit you never learned it. Builders spend years mastering schedules, safety, and quality, and it makes sense that financial systems for their own business or family would need the same intentional investment.

If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow, and that same systems-first thinking applies just as much off the jobsite as it does on it.

The Challenge

So here is the challenge worth sitting with: what part of your own financial house is running on hope instead of a plan? Is there a professional you have been putting off calling because it feels out of reach right now?

As Jason puts it plainly, “you’re never going to increase your range until you start hanging out with people that have more range than you do.” Find the accountant, the advisor, and the lawyer who can build that system with you, and stop treating your own finances with less discipline than you would ever accept on a jobsite. On we go.

FAQ

Why does Jason recommend a fiduciary financial advisor specifically, instead of any advisor?

A fiduciary is legally required to act in your best interest, while a broker may be selling a product that benefits them more than you. Choosing a fiduciary means the advice you get is actually built around your goals rather than someone else’s commission.

What is a “financial mindset set point,” and why does it matter?

It is the income or wealth level a person unconsciously expects for themselves, often shaped by how they were raised. People tend to drift back toward that set point even after a windfall or a setback, which is why shifting the mindset matters as much as shifting the numbers.

Why did a startup with very little money pay ten thousand dollars for a financial advisor?

Because the advisor helped build a real financial system, including finding a far better accountant and a workable tax strategy, and that system changed the business’s trajectory well beyond what the retainer cost. It was treated as an investment in stability, not an expense.

How does the Rich Dad Poor Dad story about a stolen idea connect to needing a lawyer?

The story is about an entrepreneur who had a great idea, real money, and real customers, but lost the entire business because the idea was never legally protected. It illustrates why legal protection has to be in place before a problem happens, not after.

What is the simplest place to start if all of this feels overwhelming?

Start with the basics: spend less than you earn, automate a savings percentage every month, and find one fiduciary professional to talk to first. Building the full system takes time, but it starts with one honest conversation and one habit put in place.

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.

Posted in All

Stupid & Dangerous Things! Feat. John Coffman

Read 9 min

Keep Your Brain On: What “Stupid and Dangerous” Moments Teach Us About Safety Culture

A Two-by-Ten, 220 Feet in the

Picture standing on top of a nuclear containment dome, twenty stories up, with no walk board and no handrail, just a two-by-ten plank of form work under your boots. That is exactly where one superintendent found himself early in his career, stepping over a handrail to get a better view of the work below.

The crane boom was swinging. The clouds were moving fast overhead. For a moment, disoriented by the motion, he looked down at the Ohio River far below, then at a row of exposed dowels sticking up behind him, sharp enough to be unsurvivable if he fell the wrong way.

That is when the math hit him: two hundred and twenty feet, on a two-by-ten, with nothing between him and the ground. He walked back to the bridge, rode the man lift down, shook it off on solid ground, and then, because he knew that if you do not go back you never go back, climbed right back up and walked the plank one more time. He never did it again.

The Real Pain: Shortcuts That Feel Small Until They Aren’t

That story is dramatic, but the everyday version of it plays out on jobsites constantly, usually much quieter. A carpenter foreman once walked into a superintendent’s office and mentioned he had chipped his glass eye.

Asked how, he explained he had been driving a nail without safety glasses, the nail popped back, and it struck him in the eye, the same way, it turned out, that he had lost the real eye years earlier. Nobody set out to get hurt that day. He just took his glasses off for one nail, on one job, one more time.

That is the real pain in construction. It is rarely the dramatic near-miss on a dome. It is the safety glasses left in the truck, the hand placed somewhere it should not be, the ladder used the wrong way, all small choices that feel harmless right up until they are not.

The Failure Pattern: Waiting Until Someone Gets Hurt

The failure pattern is simple to describe and painfully common: a culture that only reacts after something goes wrong instead of catching the moment before it happens. Hundreds of people watched that superintendent walk the top of that form work, twice a day, for six to eight weeks straight.

Not one of them said a word. Nobody stopped him. Nobody asked what he was doing up there. That silence is the real danger, more than the two-by-ten itself, because it means the culture had no mechanism for anyone to speak up. A real safety culture shows up in specific, observable ways, and it is worth checking your own project honestly against a few of them:

  • Workers and leaders both feel free to say “stop” the moment something looks unsafe, with no fear of being seen as difficult.
  • Near misses get talked about openly instead of quietly celebrated as a story of getting away with it.
  • New hires hear directly from leadership, in orientation, that safety is a two-way promise, not a poster on the wall.

Nobody Is Born Careless

Here is the part worth saying plainly: this is not a story about careless people. Everybody, at some point, is going to have a moment where their brain turns off, whether from fatigue, distraction, or simple habit. That is not a character flaw, it is being human. The problem is not that a moment like that will happen. The problem is a system and a culture that has no way of catching it when it does.

That is why the standard cannot just be “don’t do anything stupid.” The standard has to be a team that is actively watching for each other, so that when one person’s brain turns off for a second, somebody next to them is paying enough attention to say, “don’t put your hand there.”

The Cost of Waiting Too Long to Change

There is a heavier version of this same lesson that one superintendent carries with him. Years ago, his own boss, a man whose family he knew well and whose home he had stayed in, was killed instantly and accidentally by his own son’s equipment on a jobsite, a tragedy neither of them saw coming.

That loss became the moment everything changed. From then on, the choice was framed simply for every crew he led: you can learn safety from wisdom, or you can learn it from sad experience, but eventually every team has to choose which one it will be.

Why It Matters Beyond the Incident Report

This matters because the stakes here are not schedule delays or rework, they are fingers, eyes, and lives. A missed deadline can be recovered. A finger cannot. Every fatality statistic is somebody’s father, spouse, or friend, and in an industry as large as construction, the people affected are never really strangers. That is why safety culture cannot be treated as a compliance checkbox, it has to be treated as the first and most non-negotiable value on the project, ahead of schedule, ahead of cost, ahead of everything else.

Building a Culture That Catches the Moment

This is where zero tolerance earns its real meaning. Zero tolerance is not punishment, it is respect: when someone is caught being unsafe, the response is to send them home to reset, retrain, or refocus, and to explain clearly that it is because their life and their family matter too much to risk.

Culture, though, is set from the top, and it is set by what leadership is willing to tolerate. Whatever unsafe behavior exists on a project, whether it is skipped PPE, graffiti, or silence when something looks wrong, exists because leadership allowed it by not stopping it. If the standard were truly non-negotiable, it would already be different.

That is why a superintendent’s promise has to run both directions. It is not enough to promise the crew a safe place to work. Every worker has to promise back that they will do everything in their power to stay safe themselves, and that promise only means something when the whole team, not just leadership, is watching out for each other. A few practical markers separate a real safety culture from a poster on the wall, and they are worth naming directly:

  • Leadership personally participates in orientation and safety meetings instead of delegating them entirely.
  • The team uses a clear stop, call, wait habit the moment something looks unsafe, unclear, or off, no matter how busy the day is.
  • Daily huddles address safety fresh every morning, because as one superintendent put it, somebody woke up today to a new world, and the conversation has to happen again.

Turning This Into Daily Practice

None of this requires a complicated program. It requires a superintendent who shows up to every orientation personally, who cannot delegate safety any more than they could delegate their own doctor visits, and who treats a clean, safe, organized site as the non-negotiable baseline before anything else gets built.

It requires a team that has agreed, out loud, to watch out for each other, and a culture where speaking up is expected rather than awkward. When that culture exists and something still happens outside anyone’s control, that is a different conversation. But when the culture does not exist, the responsibility sits squarely with leadership.

Building People Who Build This

None of this happens by accident, and it does not happen without training. Superintendents who run real orientations, lead daily safety huddles, and build a team culture of speaking up are not born knowing how, they are trained into it on purpose.

If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow. Protecting people is not separate from protecting production, it is the whole foundation production stands on.

The Challenge

So here is the challenge worth carrying onto your own project this week: if you don’t feel the weight of every life on that job when you walk onto it, you don’t get it yet. As Jason often puts it, “the culture of any organization is shaped by the worst behavior the leader is willing to tolerate.” Decide today which behavior you are no longer willing to tolerate, and decide to watch out for the person next to you the way you would want them watching out for you. On we go.

FAQ

Why does Jason call zero tolerance a form of respect rather than punishment?

Zero tolerance means addressing unsafe behavior immediately so nobody gets hurt, and the goal is always getting people home safe to their families, not disciplining them for its own sake. Treating it as respect keeps the focus on protecting people rather than punishing them.

Who is really responsible for safety culture on a construction project?

The superintendent owns it. If the culture does not exist, meaning safety meetings, orientations, and daily follow-through are not happening, that responsibility sits with leadership. If the culture genuinely exists and something still happens outside anyone’s control, that is a separate conversation.

What does “keep your brain on” actually mean in practice?

It means recognizing that every person will have a moment of fatigue or distraction at some point, and that moment is normal, not a character flaw. The real safeguard is a team culture where the person next to you is watching closely enough to catch that moment and speak up.

How does a real safety culture show up day to day on a jobsite?

It shows up in daily huddles that address safety fresh every morning, leadership personally participating in orientations instead of delegating them, and a team that uses a clear stop, call, wait habit the moment something looks unsafe. It also shows up in workers feeling safe to speak up without fear of being seen as difficult.

Why does one story about a single unsafe moment matter for an entire project’s culture?

Because culture is built or broken in exactly those small moments. Hundreds of people can walk past one unsafe act without saying anything, and that silence, more than the unsafe act itself, is what allows a culture of complacency to take hold.

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.

Posted in All

What Matters Most!

Read 11 min

The Green Light Bulb Problem: Why Small Distractions Sink Big Construction Projects

The Bulb That Brought Down a Plane

On a dark December night, a jumbo jet circled the Florida Everglades because one green light on the instrument panel failed to illuminate. Every other system on that aircraft was working perfectly. The landing gear had actually lowered the way it was supposed to.

The crew just could not confirm it, because a twenty-cent bulb had burned out. So they circled. They investigated. They focused so hard on that one small failure that nobody noticed the plane was slowly descending into the swamp below.The aircraft crashed, killing more than a hundred people. Nothing major broke that night. One tiny thing did, and the crew let it steal their attention from everything that mattered more.

The Real Pain in the Field

Construction projects crash the same way. Not with a bang, most of the time, but with a slow, quiet drift that nobody clocks until the schedule is three weeks gone.

Walk any jobsite on a Tuesday afternoon and you will find a superintendent chasing an RFI that should have been a five-minute email. A project manager buried in a change order dispute that has nothing to do with tomorrow’s install. A foreman re-explaining a layout question for the third time because nobody closed the loop the first time.

Each of those things feels urgent in the moment, and each one pulls the whole team’s attention. While everyone is staring at the light bulb, the real work, keeping zones leveled, keeping trades flowing, keeping the plan honest, quietly falls apart in the background.

The Failure Pattern: Whoever Screams Loudest Wins

Here is the failure pattern, and it shows up on almost every project at some point: the team starts running the job reactively instead of running a system. Whatever feels loudest in the moment wins the day. A missing submittal becomes the entire morning. A frustrated trade partner becomes the entire afternoon. Nobody is doing anything wrong in these moments; they are responding to real problems.

But when the loudest problem always wins, the team loses the capacity to look ahead, to protect the plan, and to keep the project moving in the direction it actually needs to go. Busyness starts to look like productivity, and it is not the same thing. A reactive team tends to show the same handful of symptoms, worth naming plainly:

  • A five-minute RFI turns into a half-day chase because nobody triaged it before it consumed the whole team.
  • Today’s plan gets reshuffled to fight yesterday’s fire, and the zone that was supposed to move forward tomorrow never gets touched.
  • Paperwork and change order disputes eat the hours that should have gone to walking the project and catching next week’s roadblocks early.

This Isn’t a People Problem

It is important to be clear here: this is not a story about careless foremen or supers who cannot prioritize. Most people in the field are doing their best with the tools they were handed. If a team spends its whole day chasing one burned-out bulb, that is not a character problem, that is a system problem. Nobody gave them a personal organization system to run their day with intention, and nobody built a production system that made roadblocks visible before they turned into emergencies. The system failed them; they did not fail the system. Respect for people means building something that lets good people do good work without getting hijacked by whatever is loudest in the moment.

A Day Lost to One Light Fixture

Picture a superintendent on a mid-rise job who spends an entire day chasing down one RFI response about a light fixture spec. It genuinely needed an answer. But while that superintendent had the whole team’s attention locked on one detail, the zones behind schedule kept slipping. The electrical crew stacked on top of the drywall crew because nobody was watching the handoff, and by Friday the weekly plan looked nothing like what was promised on Monday. Nothing about that day was lazy. It was a team with no system for triage, reacting to whatever screamed loudest while the real plan burned quietly in the background.

Why It Matters More Than the Schedule

This matters far beyond the schedule. Rework climbs because zones were never leveled the way they should have been. Safety risk climbs because a frazzled, reactive team makes worse decisions under pressure than a calm one. Quality slips because nobody had the bandwidth to check the work. And underneath all of it, people pay with their own lives: overtime creeps in, weekends disappear, and superintendents miss their kids’ games chasing problems a stable system would have caught weeks earlier. Protecting flow on a jobsite is not just a production strategy, it is how you protect the marriages, the health, and the family time of everyone on that team.

The Fix: Building a System That Looks Ahead

The fix is not “try harder” or “pay closer attention.” The fix is building a system that keeps the team’s eyes on what actually matters, so a burned-out bulb never gets to hijack the whole flight. This is where the Integrated Production Control System, IPCS, earns its keep. IPCS links the First Planner System, the Takt Production System, and the Last Planner System into one continuous handoff.

First Planner designs the system before boots ever hit the deck. Takt sets the rhythm that levels zones and paces the trade train. Last Planner runs the short-interval commitments that keep the week honest. When all three are working together, the team has a structure that is always looking ahead, instead of a team that only ever reacts to whatever broke last.

Roadblocks vs. Constraints

Inside that system, one distinction matters more than almost any other: the difference between a roadblock and a constraint. A roadblock is a solvable blocker, a missing layout, an unanswered RFI, late material, and it needs to be removed fast so it does not sit there and rot.

A constraint is a limiting condition you plan around, a code requirement, a fixed lead time, a real capacity limit. Teams that confuse the two waste enormous energy either fighting something they cannot change or ignoring something they absolutely could have fixed in ten minutes.

Getting this classification right, and getting it right quickly, is a big part of what keeps a team from staring at one light bulb while the plane keeps descending. A few quick signals tend to show up when a team has lost that clarity, and it is worth checking your own project against them honestly:

  • The team can tell you exactly what fire they fought yesterday, but not what zone should be finishing this week.
  • Meetings are spent re-litigating the same roadblock instead of removing it and moving on.
  • Nobody can say, without looking it up, whether this week’s plan actually matches the Takt rhythm the project committed to.

Turning Insight Into Daily Habits

None of that means the team is failing. It means the system is not yet giving them the visibility to separate the loud from the important.

That is exactly what a real personal organization system solves at the individual level, and what a real meeting architecture solves at the team level. When a superintendent runs a morning routine that reviews the schedule, walks the project with intention, and flags roadblocks before they become emergencies, that superintendent is not managing chaos anymore, they are controlling the environment the chaos would otherwise live in.

When meetings exist to remove roadblocks and confirm readiness rather than just talk about problems, the team stops rewarding whoever yells the loudest and starts rewarding whoever protects the plan the best.

It’s Not Just a Jobsite Problem

There is a version of this same problem that shows up outside the jobsite too. A person can get so fixated on one small stressor at work, one health symptom they keep putting off, one strained conversation they keep avoiding, that they lose sight of their overall health, their marriage, their faith, their family.

The lesson is the same whether you are flying a plane, running a Takt plan, or running your own life: the things that seem urgent are not always the things that matter most, and a person who cannot tell the difference is flying blind toward a swamp they cannot see.

Building the People Who Build This

None of this happens by accident, and it does not happen without training. Building superintendents, project managers, and foremen who can tell a roadblock from a constraint, who run a real personal organization system, and who trust an IPCS built to keep them looking ahead, is a capability that has to be built on purpose.

If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow. That is the whole point of building people who build things, because a trained, balanced team is the only thing standing between a stable project and a slow, quiet crash nobody sees coming until it is too late.

The Challenge

So here is the challenge, the same one worth asking of any team on any project: what is the burned-out green light bulb your team is staring at right now, and what is it costing you while your attention is locked there?

Are you protecting the roadblocks that need to be removed, or are you circling the same problem while the real plan slips out from under you? W. Edwards Deming put it plainly: “A bad system will beat a good person every time.” Build the system. Protect the flow. Watch the whole instrument panel, not just the one light that is out. On we go.

FAQ

What is the difference between a roadblock and a constraint in construction?

A roadblock is a solvable blocker that should be removed quickly, things like a missing layout, an unanswered RFI, or late material. A constraint is a limiting condition you plan around instead, like a code requirement or a fixed lead time. Teams that mix the two up waste time either fighting something they cannot change or letting something fixable sit there and turn into a real problem.

Why does a construction team lose sight of the schedule chasing small issues?

It usually is not carelessness. Without a system that separates what is loud from what actually matters, whatever feels most urgent in the moment naturally grabs everyone’s attention, even when a bigger, quieter problem is unfolding underneath it. That is a system gap, not a people gap.

What is IPCS and how does it help prevent this kind of distraction?

IPCS, the Integrated Production Control System, links the First Planner System, the Takt Production System, and the Last Planner System together so the project always has a plan for what is next. Instead of reacting to whatever broke last, the team has structure that keeps its attention on protecting flow and removing roadblocks before they turn into emergencies.

How does staying distracted by small problems affect a construction team’s families?

When a team spends its energy on the loudest problem instead of the real plan, overtime and last-minute chaos tend to follow. That steals time and stability from people’s lives outside the jobsite. Protecting flow on a project is one of the most direct ways to protect the health and family time of the people building it.

What is a personal organization system, and why does it matter here?

It is a structured daily routine, reviewing the schedule, walking the project with intention, flagging roadblocks early, that keeps a superintendent or project manager in control of their day instead of reacting to whatever comes up. It is one of the clearest tools for making sure a team’s attention stays on what matters most instead of getting hijacked by one small, burned-out bulb.

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.

Posted in All

Project KPI Tracker

Read 11 min

The Project KPI Tracker: Why What Gets Seen Gets Done

What gets measured gets managed. What gets seen gets done.

Here is the deal. The best teams do not bury performance in a spreadsheet nobody opens. They put it on the wall. A single visual dashboard covering safety, people, quality, production, and cost turns abstract goals into a daily conversation. Red means act. Green means keep pushing. Trends tell you where you are headed before the numbers catch up. That last part matters more than most project teams realize, because a dashboard that only shows where you stand today is a snapshot. A dashboard that shows the trend is a warning system.

The Pain of Data That Nobody Looks At

Most projects already track everything on this dashboard. Safety incident rates exist in a report. Quality inspection pass rates exist in a spreadsheet. Schedule performance exists in scheduling software. Cost performance exists in a monthly report the project executive reviews. The data is not missing. What is missing is a place where that data lives visibly, continuously, in front of the people whose daily decisions actually move the numbers.

A metric that exists in a spreadsheet gets reviewed once a month, usually by someone several layers removed from the daily work that produces the number. By the time a declining trend surfaces in that monthly review, it has been declining for weeks, and the conversation about it happens well after the window for an easy correction has closed. The foreman who could have addressed a rising rework rate three weeks ago never saw the number, because the number lived in a report designed for an executive audience rather than a wall designed for a field team.

This is the quiet cost of reporting instead of displaying. The information exists, technically. It is accurate, technically. But it arrives too late and reaches the wrong audience to actually change behavior while the behavior is still changeable.

The Failure Pattern

The failure pattern is treating performance data as a reporting obligation rather than a daily management tool.

Reports are built for accountability after the fact. They tell an executive or an owner what happened last month, and they are structured to explain, justify, and summarize. That function is legitimate and necessary. But a report is inherently backward-looking, and a monthly cadence means the feedback loop between a behavior and its consequence is weeks long. A crew’s rework rate that started climbing in week one of a phase does not show up in a formal report until the phase is largely complete, at which point the opportunity to correct it within that phase has already passed.

A dashboard changes the cadence and the audience. It updates more frequently, it lives where the field team works, and it is designed to prompt action today rather than explain results after the fact. The same data, displayed differently, produces a completely different behavioral response. Nobody changes their approach because of a number in a report they will see in three weeks. People do change their approach because of a number on the wall they walk past every morning.

They Didn’t Fail the System

When a project’s quality or safety numbers decline gradually over a phase without anyone catching it early, the instinct is to ask why the team did not notice sooner. Why didn’t the foreman flag the rising re-inspection rate? Why didn’t the safety lead see the trend before it became a real problem?

The honest answer is usually that the trend was visible only in a system nobody was looking at daily. The foreman was managing the work in front of them, not cross-referencing a spreadsheet that updates monthly. The safety lead was reviewing incident reports as they came in, not tracking a rolling trend line that would have shown the direction of travel before any single incident occurred. Nobody failed to pay attention. The information was structured in a way that made early detection unlikely regardless of how attentive anyone was.

Put the same information on a wall, updated regularly, visible to the whole team every day, and the detection problem resolves itself. People do not need to remember to check a report. The report is in front of them, whether they intended to look at it or not.

What the Dashboard Actually Displays

The dashboard organizes performance into five categories, and the structure itself is part of what makes it work.

Safety metrics track lost time incident rate, total recordable incident rate, recordable incident rate, safety observations, safety training compliance, and PPE compliance, each against a specific goal with a trend line showing direction. People metrics track local workforce utilization, diversity in the workforce, project team utilization, and a pulse survey score, treating workforce health as something worth measuring with the same rigor as safety and cost. Quality metrics track inspection pass rate, re-inspection rate, open non-conformance reports, and close-out completion percentage. Production and schedule metrics track milestone progress, plan versus actual schedule performance, look-ahead plan percentage, and productivity in labor hours. Cost metrics track cost performance index, schedule performance index, forecast at completion, and contingency remaining.

Each metric carries a goal, last month’s actual, this month’s actual, and a trend line. That trend line is doing more work than either single number alone. A team hitting ninety-two percent on close-out completion this month, up from eighty-eight percent last month, is a team with positive momentum, even if ninety-two percent has not yet reached the goal. A team sitting at the goal but trending downward is a team about to miss it next month if nothing changes. The trend tells you where the number is going, and where a number is going matters more than where it happens to sit on any single day.

Why Trends Beat Snapshots

A single month can lie. A cost performance index of exactly 1.0 this month looks fine in isolation, but if last month was 1.15 and the month before that was 1.2, the team is looking at a declining trend that a snapshot alone would completely obscure. The direction of travel tells the truth that any single data point cannot.

This is why the dashboard’s design, showing last month, this month, and a trend line side by side for every metric, is not a cosmetic choice. It is the mechanism that turns data into a leading indicator instead of a lagging one. A leading indicator gives the team time to respond before a problem becomes a crisis. A lagging indicator only confirms, after the fact, that a crisis has already happened. Every team wants leading indicators. Very few teams build the display structure that actually produces them.

Why Visibility Builds Ownership

There is a behavioral principle underlying this entire practice that goes beyond the mechanics of data display. When everyone can see the score, everyone plays to win.

A crew that has no visibility into how their work contributes to the project’s overall quality or safety performance experiences their work as isolated tasks disconnected from a larger outcome. A crew that walks past a dashboard every day showing the project’s inspection pass rate, and understands that their work directly moves that number, experiences their work differently. They are not just installing material. They are contributing to a score the whole team is tracking together, and that shift from isolated task to shared outcome is what visibility actually produces.

This is the same principle behind the Circle of Trust and contractor grading. Performance that stays private, known only to the people directly responsible for reviewing it, produces isolated accountability. Performance that becomes visible to the whole team produces collective ownership. A trade partner who knows their grade is posted, or a crew that knows the project’s safety trend is on a wall they walk past daily, behaves differently than a team whose performance exists only in a report reviewed by people they rarely interact with.

Signals Your Project Needs a Visual Dashboard

Look for these patterns before deciding whether this practice would help your project:

  • Performance problems are being discovered during monthly reviews rather than caught early in the field
  • Different levels of the project team have access to different pieces of performance data, with no single shared view
  • Metrics exist in multiple disconnected spreadsheets and reports rather than one consolidated view
  • Field teams do not know how their daily work connects to overall project performance metrics
  • The team’s conversation about performance happens reactively, after a number has already declined, rather than proactively based on a visible trend

Each of these signals a visibility gap, and a visibility gap is exactly what a wall-mounted dashboard is designed to close.

Green Is Not the Goal

The instinct when building a dashboard like this is to treat green as the finish line, the state you reach and then relax. That instinct misses the actual purpose of the tool. The target is always the same: better than last month. A metric sitting at green with a flat or declining trend is a metric one bad week away from turning yellow. A metric sitting at yellow with a strong positive trend is a team that is clearly closing the gap and should be recognized for the direction they are moving, not just the number they currently show.

Momentum, not status, is what the dashboard is actually built to track. That reframing matters because a team fixated on hitting a static target will stop pushing the moment they cross the threshold. A team fixated on maintaining positive momentum keeps improving even after they have technically met the goal, because the measure of success was never the finish line. It was always the direction of travel.

Displaying Performance Instead of Reporting It

Stop reporting performance after the fact. Start displaying it in real time, and watch your team rise to meet it. This is the same discipline behind every visual management practice in Lean construction: the Circle of Trust, the situation room, quality-at-the-source floor markings, contractor grading. Every one of these tools works on the same principle. Make performance visible to the people who can act on it, at a cadence fast enough to matter, and the behavior changes without requiring anyone to force it. If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow. Jason Schroeder and the LeanTakt team build visual dashboards like this into every project because the discipline of displaying performance, rather than merely reporting it, is one of the highest-leverage changes a leadership team can make.

Put the Score on the Wall

Here is your challenge. Pick the five or six metrics that matter most on your project right now, across safety, people, quality, production, and cost. Build a simple version of this dashboard, even a whiteboard update weekly, and put it somewhere the whole team walks past every day. Do not wait for a polished digital version. Start with what you can build this week.

Taiichi Ohno taught that visibility is the foundation every improvement depends on, because a team cannot fix what it cannot see. Put your project’s performance where everyone can see it, every day, and watch how quickly the team starts managing toward the trend instead of waiting for the monthly report to tell them what already happened.

On we go.

FAQ

How often should a project dashboard like this be updated?
Monthly is the minimum useful cadence for capturing trend direction, but weekly updates on the metrics that change most quickly, such as safety observations or schedule performance, give the team a faster feedback loop. The right cadence depends on how quickly each specific metric can meaningfully change and how much lead time the team needs to respond before a declining trend becomes a serious problem.

Who should be responsible for maintaining and updating the dashboard?
A single owner, often a project engineer or project controls lead, should own the data collection and update process to ensure consistency and accuracy. Shared ownership across multiple people tends to produce gaps and inconsistent updates, the same failure pattern that affects unmanaged storage or unmaintained fencing. One accountable owner keeps the system reliable.

What should a team do when a metric shows a declining trend?
Treat a declining trend as an early warning rather than waiting for the metric to cross into a red or failing threshold. The whole value of trend-based tracking is catching problems while they are still small and correctable. A team that waits until a metric is already failing before discussing it has lost the main advantage a visual dashboard provides over a monthly report.

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.

Posted in All

The VDC War Room

Read 12 min

The VR Room: Rehearsing the Jobsite Before Anyone Sets Foot On It

We are bringing the jobsite into the training room.

Here is the deal. Most construction training happens after a crew is already on site, learning the layout, the hazards, and the sequence of work in real time while the schedule is running. That approach has always carried a cost. Mistakes discovered in the field are mistakes that have already consumed time, material, or worse, created a safety exposure. The VR Room changes when that learning happens. Instead of waiting until crews are in the field to catch problems, teams can rehearse layouts, tasks, and workflows in a fully visualized environment before a single tool is picked up. They walk the space, interact with tools and scenarios, and build confidence before the work ever starts.

The Pain of Learning in Real Time

Walk any active jobsite during the first week of a new phase and you will see it. A crew encountering a layout for the first time while trying to execute the work at the same time. A new hire learning where the hazards are by nearly encountering one. A trade partner discovering a coordination conflict with another trade because neither team walked the sequence together before both showed up expecting the same space.

None of that is a failure of the individuals involved. It is what happens when the only place to learn a jobsite is the jobsite itself, under the pressure of an active schedule, with real consequences attached to every mistake. A new crew member cannot fully understand a complex mechanical room layout from a drawing set alone. A safety scenario described in a toolbox talk is not the same as encountering the actual spatial relationship between a hazard and a walking path. The gap between reading about a space and standing in it is where uncertainty, hesitation, and preventable error live.

This gap costs more than most projects recognize, because it is distributed across every new task, every new hire, and every unfamiliar sequence. It shows up as slower ramp-up time, more questions during execution, and safety incidents that trace back to someone encountering a hazard for the first time in the moment they needed to already understand it.

The Failure Pattern

The failure pattern is treating the jobsite as the only place training can happen, and treating training itself as something that happens before deployment in a classroom disconnected from the actual physical reality of the work.

Classroom training covers rules, procedures, and general safety principles, and it does that well. What it cannot do is give someone a spatial understanding of the actual space they are about to work in. A classroom cannot simulate the exact dimensions of a mechanical room, the actual sightlines around a specific piece of equipment, or the precise sequence in which two trades will need to occupy the same zone. That gap between general training and site-specific readiness gets filled, by default, in the field, during the first days of actual work.

Projects that accept this as normal are accepting a preventable cost. The technology to close that gap, to give a crew a spatial, interactive rehearsal of the actual work before they arrive, has existed for years in other industries. Aviation has used simulation for decades because the cost of learning in the actual environment is catastrophically high. Construction has been slower to adopt the same logic, in part because the industry has normalized learning on the job as simply how the work gets done.

They Didn’t Fail the System

When a new crew member struggles in their first days on an unfamiliar layout, or a coordination conflict surfaces between trades who never walked the sequence together, the instinct is to look at training quality or communication discipline. Better onboarding. Better pre-task briefings. More detailed coordination meetings.

Those improvements have value, but they are working within a system that never gave anyone a way to actually experience the space before entering it. A pre-task briefing describes the sequence verbally or on a drawing. It does not let the crew walk it. A safety orientation lists hazards. It does not let a new hire encounter the spatial reality of where those hazards sit relative to the tasks they will be performing. The gap is not a discipline problem. It is an infrastructure problem, and until a project has a tool that closes the gap between description and experience, the field will keep serving as the first rehearsal space by default.

What the VR Room Actually Provides

The VR Room is built around six components that together create a genuine rehearsal environment rather than a passive training video.

The VR headset provides immersive jobsite visualization, placing the trainee inside a three-dimensional representation of the actual space rather than asking them to interpret a two-dimensional drawing. Hand controllers allow direct interaction with tools, spaces, and scenarios, so the experience is not observation but participation. The trainee is not watching a walkthrough. They are moving through the space, reaching for equipment, and encountering the sequence of a task the way they would encounter it in the field.

Dual monitors give observers the ability to coach, review, and guide in real time. A supervisor or trainer watching the same scenario from outside the headset can see exactly what the trainee sees, correct a decision in the moment, and reinforce a lesson while the trainee is still inside the experience. That immediate coaching loop is difficult to replicate in field training, where the coach and the trainee are often managing the actual work at the same time as the teaching moment.

The mobile workstation makes the system portable for classroom or field use, which means the rehearsal capability is not locked into a fixed training center. It can move to where the crews are, which matters on a multi-site organization or a project where pulling an entire crew off to a distant training facility is not practical. The open safe zone provides a clear area for physical movement and practice, giving the trainee room to actually walk and interact rather than standing in one place operating controls. And the digital scenarios are the content layer, the specific layouts, tasks, and workflows built into the system that let a team rehearse the exact conditions they are about to encounter, rather than a generic training module unrelated to their specific project.

Why Rehearsal Beats Description Every Time

There is a meaningful difference between being told about a space and experiencing it, and that difference is exactly what the VR Room is designed to close.

A design review conducted around a drawing set requires everyone in the room to individually translate two-dimensional information into a mental three-dimensional model. Different people do that translation with different accuracy, which is part of why coordination conflicts surface in the field that nobody caught during the design review. A design review conducted with the team walking the same virtual space together removes that translation step entirely. Everyone is looking at the same spatial reality, from the same reference points, and conflicts that would have been invisible on paper become immediately obvious when someone tries to walk through a doorway that a piece of equipment is blocking, or reaches for a device that another trade’s rough-in has displaced.

Safety simulation carries the same advantage. A hazard described in a toolbox talk is an abstraction. A hazard encountered in a realistic virtual rehearsal, where the consequence of a wrong decision is immediate and visible without any actual physical risk, teaches a lesson that sticks in a way a verbal warning rarely does. The trainee is not just told that a fall hazard exists near a specific opening. They experience the spatial relationship between their own position and that hazard, in a scenario built specifically to reinforce the caution that a real jobsite would demand.

Pre-task planning benefits the same way. A crew that rehearses a complex or unfamiliar task in the VR Room before performing it in the field arrives at the actual work with a mental model already built. They know where they are going, what the sequence looks like, and where the coordination points with other trades occur. That familiarity translates directly into faster execution, fewer questions during the work, and fewer decisions made under time pressure without adequate preparation.

Signals Your Project Would Benefit From Rehearsal Training

Look for these patterns on your current project before deciding whether virtual rehearsal deserves investment:

  • New crew members consistently need extended orientation time before becoming productive in a complex or unfamiliar space
  • Coordination conflicts between trades are being discovered in the field rather than during design review
  • Safety incidents or near misses trace back to someone encountering a hazard for the first time in the moment they needed to already understand it
  • Design reviews conducted purely from drawings are missing spatial conflicts that only become obvious once construction begins
  • Complex mechanical, electrical, or plumbing spaces require significant field learning time before trades can work efficiently

Each of these signals a gap between description and experience that a rehearsal tool is specifically designed to close.

Building Rehearsal Into the Project Rhythm

The VR Room works best when it is integrated into the project’s existing preparation rhythm rather than treated as a separate initiative disconnected from daily planning. Design review sessions can incorporate a virtual walkthrough of the specific space under review, surfacing spatial conflicts before construction documents are finalized. New hire onboarding can include a rehearsal of the specific area they will be assigned to before their first day on that task. Safety training can move beyond generic modules to project-specific scenarios that reflect the actual hazards on the actual jobsite. Pre-task planning meetings can use the mobile unit to walk a crew through an upcoming complex task, surfacing coordination questions and sequence uncertainty in the safe zone rather than in the field.

The common thread across every one of those applications is preparation. Design review, safety training, coordination, and pre-task planning are all fundamentally about building understanding before execution. The VR Room simply gives that preparation a spatial, interactive form that description alone cannot provide. If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow. Jason Schroeder and the LeanTakt team see rehearsal tools like this as a direct extension of make ready planning, closing the gap between design intent and field readiness before the work ever begins.

Rehearse It Before You Build It

Here is your challenge. Identify one upcoming task or space on your project that is complex, unfamiliar, or has a history of coordination conflict. Before your crew executes it in the field, find a way to rehearse it, whether through virtual tools, a physical mockup, or a detailed team walkthrough. Build the mental model before the real consequences are on the table.

Taiichi Ohno taught that the goal of any system is to make problems visible as early as possible, before they compound into something expensive. The VR Room takes that principle and applies it to the moment before a crew ever steps onto the jobsite. Train. Practice. Build safely. Get it right in the virtual world first, so the real one flows the way it was designed to.

On we go.

FAQ

How is VR training different from traditional safety orientation or toolbox talks?
Traditional orientation and toolbox talks describe hazards and procedures verbally or through printed material, which requires the trainee to mentally translate that information into an understanding of the actual physical space. VR training places the trainee inside a spatial representation of the actual jobsite, letting them encounter hazards, tools, and sequences directly. That direct experience builds understanding faster and retains better than description alone.

Can the VR Room be used for design review with the full project team, not just field training?
Yes, and this is one of its strongest applications. A design team, superintendent, and trade partners can walk the same virtual space together during design review, surfacing spatial conflicts, such as equipment blocking a doorway or a device location conflicting with casework, before construction documents are finalized. Catching those conflicts during design review is far less costly than catching them in the field after material has already been installed.

Is the investment in VR training equipment justified for a single project, or is it better suited to an organization running multiple projects?
The mobile workstation design makes the system portable, which supports use across multiple projects for organizations with recurring project types or repeated space configurations, such as hospital builds or standardized commercial layouts. A single project with a highly complex or high-risk sequence can still justify the investment if the cost of field-discovered errors or safety incidents in that sequence would exceed the training investment.

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.

Posted in All

Why Do Owners Lose Millions Because Of Bad Planning?

Read 8 min

Why Owners Lose Millions Because of Bad Planning

Here’s the deal. Owners lose millions on construction projects for a reason that has nothing to do with contractors, weather, or bad luck. They lose millions because they force their own general contractors into systems designed to fail, and then act surprised when the project comes in late and over budget.

I love owners. I want to be clear about that before I say the rest of this. But you play stupid games, you win stupid prizes, and a huge number of owners are setting up their own projects to lose before a single trade ever shows up.

The Stupid Games Owners Actually Play

Here is what this looks like in practice. An owner selects a design, bid, build contract structure that gives the project team no real chance to plan together before construction starts. They set up an adversarial relationship from day one instead of a collaborative one. They hire an owner’s rep whose main job seems to be beating up the contractor rather than helping the project succeed. They force CPM contract language onto the general contractor, then monitor and narrow that schedule down until it becomes genuinely unrealistic, all in the name of preventing the contractor from taking advantage of them. And on top of all of that, they hire a GC that does not actually know what they are doing in the first place.

It is your building and your money, and you can absolutely choose to spend it however you want. But every one of those choices is a stupid game, and every one of them produces the exact stupid prize you would expect. Owners who set their projects up this way are never going to get their projects finished on time, no matter how much pressure they apply or how tightly they try to control the contract.

What Owners Who Actually Win Do Differently

Now compare that to owners who consistently get their projects delivered well. They hire reliable general contractors who genuinely know what they are doing. They make sure that GC is trained on Lean implementation practices, not just familiar with the terminology. And they actively set up the system and environment for that GC to succeed, rather than assuming success will happen despite the environment they created.

That difference is not luck, and it is not a coincidence of which owners happen to get good contractors. It is a direct result of education and the deliberate use of the right systems. Owners who understand this stop treating their contract as a weapon to control a contractor they distrust, and start treating it as a framework for genuine collaboration toward a shared outcome.

The System Levers That Actually Matter

There is real systems thinking behind why this works, and it is worth understanding the mechanics rather than just the outcome. Donella Meadows explored this in her book Thinking in Systems, and Peter Senge covers related ground in The Fifth Discipline. The core idea is that within any system, there are specific levers you can pull that determine whether the whole thing functions well or badly.

For a construction jobsite, a handful of these levers have to be in place. The owner needs a genuine mindset focused on people, process, and quality, not just cost and schedule pressure. The stakeholders and the company itself need that same mindset, along with real education on what it actually requires. The project needs the right overall system and structure, not a contract format chosen out of habit or fear. And the project needs the right rules and the right goal, clearly defined and aligned with each other, rather than rules that quietly work against the stated goal.

Watch for these signs an owner has pulled the wrong levers before the project even starts:

  • A contract structure, like design bid build, that gives the project team no real opportunity to plan together before construction begins
  • An owner’s rep whose primary function appears to be pressuring the contractor rather than supporting project success
  • A CPM schedule that has been progressively narrowed until it is no longer realistically achievable

Any one of these levers set wrong creates real drag on a project. Set several of them wrong at once, and the project is fighting its own owner before it fights anything else.

The Boxer Nobody Would Actually Bet On

Here is the image that makes this land. Imagine paying someone to be your boxer and fight on your behalf. Now imagine starving that boxer, denying them water, smashing their knee before the match, and tying their hands behind their back, and then telling them to go out there and win.

That is exactly what a lot of owners do to their own general contractors. They select a contract structure that prevents real planning. They set up an adversarial relationship instead of a collaborative one. They hire an owner’s rep whose job is to make the contractor’s life harder rather than easier. They squeeze the schedule until it cannot realistically be hit. And then they expect the project to finish on time and under budget anyway. No boxer wins under those conditions, and no project does either.

Why This Actually Costs Owners the Most

None of this hurts the general contractor more than it hurts the owner, even though it might feel that way in the middle of a tense contract negotiation. An owner who sets their own project up this way absorbs the schedule delays, the cost overruns, and the adversarial change order battles that follow directly from the system they chose to create.

The owners who avoid all of that are not doing anything mysterious. They are pulling the right system levers from the start. They pick a delivery method that allows real collaborative planning. They hire a GC who is genuinely trained in Lean practices, not one who simply uses the vocabulary. They treat the owner’s rep as a partner in project success rather than an enforcer looking to catch the contractor doing something wrong. And they set a schedule that reflects reality rather than a number designed purely to protect against being taken advantage of.

What This Means If You Are an Owner Reading This

If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help owners and general contractors build the right system from the start, including the delivery method, the mindset, and the Lean training that actually determine whether a project succeeds. Getting these levers right before contracts are signed is worth far more than trying to fix an adversarial relationship after it has already cost months of schedule.

So here is the challenge. If you are an owner evaluating your next project, look honestly at the levers described here before you sign anything. Does your delivery method actually allow real collaborative planning? Is your owner’s rep set up to support success or to police the contractor? Is your schedule realistic, or has it been narrowed purely to protect against a fear of being taken advantage of? Every one of those answers predicts your outcome long before construction ever starts.

Jason Schroeder said it plainly: “You play stupid games, you win stupid prizes.” Choose the system levers that actually set your project up to win, and you will not need to play games with your own contractor to protect your investment.

On we go.

FAQ

Why does design bid build specifically create planning problems for owners?
Because that delivery method typically finalizes design before selecting a contractor, which removes the opportunity for the general contractor and trade partners to collaborate on planning, sequencing, and constructability during design. Without that early collaborative window, the project team inherits a design they had no input into, and problems that could have been solved cheaply during planning surface expensively during construction instead.

How does narrowing a CPM schedule actually hurt the owner who insists on it?
An overly narrowed schedule looks protective on paper, since it appears to prevent the contractor from padding time, but it typically becomes unrealistic to actually achieve. That mismatch between the contractual schedule and the physically achievable one produces the same crash landing and schedule failures that hurt every project running an unrealistic CPM plan, and the owner absorbs those consequences directly through delays and disputes.

What does it actually look like for an owner’s rep to support project success rather than police the contractor?
A supportive owner’s rep focuses on removing obstacles, facilitating clear communication between the owner and the project team, and helping resolve problems collaboratively as they arise. A policing owner’s rep focuses primarily on catching contract violations and applying pressure, which tends to push the contractor into defensive documentation and adversarial behavior rather than genuine problem solving, ultimately slowing the project down for everyone involved.

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.

Posted in All

Why Do Construction Projects Fall Even With Experienced Teams?

Read 8 min

Why Construction Projects Fail Even With Experienced Teams

Here’s the deal. I have watched genuinely talented, experienced project teams fall three months behind schedule, not because they lacked skill or effort, but because nobody on the team had a word for the actual problem slowing them down. You can staff a project with A-plus people and still get C-minus results if the system underneath them cannot see its own constraints.

Let me tell you the story that proves it.

A Half-Billion-Dollar Lab, Three Months Behind

I visited a four hundred eighty million dollar research laboratory project in the St. Louis area, all mild reinforced concrete structure, decks, columns, and core walls. The team was three months behind schedule and wanted to know how to fix it.

Looking at their sequence with a structural engineering colleague, the problem became obvious fast. Their placements were too large. Columns were running on a three day cycle, walls on a nine day cycle, and decks on a twelve to fourteen day cycle. Those cycles did not share a common rhythm, so even when the column and wall crews tried to help each other out, everyone was working out of sync with everyone else. The batch sizes themselves were the constraint.

When that was pointed out, the initial response was a familiar list of reasons it could not change. Budget concerns about additional finishers. Concerns that the construction joints were not designed for smaller placements. Uncertainty about what the structural engineer would say. All understandable concerns to raise, and also exactly the kind of thing that keeps a real constraint sitting unaddressed instead of getting solved.

What Happened When They Actually Solved It

Months later, at a Lean Community of Practice event in Phoenix, that same team ran up to share what happened next. They had gone back to the structural engineer, reused some rebar splices, adjusted the construction joint locations, and spent an additional twenty to twenty two thousand dollars on placement changes. In return, they got two full weeks back on the concrete schedule. The project went on to finish on time, and the relationship with that team stayed strong for the rest of the job.

Twenty two thousand dollars and a conversation with a structural engineer recovered two weeks on a project that had already been sliding for months. That is the kind of return you only get once a real constraint has actually been identified and named, instead of being treated as an unavoidable fact of the job.

Why the Word Constraint Has Been Doing Us a Disservice

Here is where I think our industry has genuinely hurt itself. The Lean community borrowed the word constraint from Eliyahu Goldratt’s theory of constraints, developed originally for manufacturing, and applied it to construction without adjusting for a critical difference between the two.

In line manufacturing, the product moves along a fixed line. In construction, the product stays put and the train of trades moves through the building instead. That difference matters, because it means construction has two genuinely different categories of problem that got flattened into one overused word.

Constraints are system design problems: the wrong Takt time, misshaped zones, the wrong number of zones, an improper sequence. These affect the train tracks themselves, meaning the zones and the path the trades travel through. Roadblocks are different. They are temporary, removable obstacles sitting in the way of otherwise normal work, like weather, an area not ready, or an unanswered RFI. Lumping both under the single word constraint is exactly why so many teams think a constraint is just bad luck or an external nuisance, rather than something built into the design of their own plan that can actually be corrected.

Watch for these signs your team is confusing a system constraint with a temporary roadblock:

  • A recurring schedule problem being treated as bad luck rather than investigated as a design issue
  • Nobody able to name whether the plan has the right number of zones or the right Takt time
  • Batch sizes or cycle times across trades that were never checked against each other for compatibility

The Real Reason A-Plus Teams Produce C-Minus Results

Here is the pattern underneath every version of this story I have seen. Projects fail with genuinely experienced teams because those teams are working inside a C-minus system, not because they lack talent.

They are usually running CPM, which has no mechanism for surfacing constraints in the first place. They do not have a shared word to identify what a constraint actually is, separate from a roadblock. They have not built a Takt plan, which is the tool that actually teaches a team how to optimize zone sizes, sequence, and cycle time. And without Lean thinking, including the theory of constraints applied correctly, there is no framework guiding anyone toward the fix at all.

If you reach the end of your pull plan without calculating your zone sizes, checking your ideal sequence, and confirming the right Takt time, you simply do not know whether you have a trade bottleneck or a zone bottleneck. You could staff that project with a demigod straight out of a Disney movie and it still would not finish on time, because the limiting factor was never identified, let alone optimized. Talent cannot compensate for a system that cannot see its own bottleneck.

The Framework That Actually Works

There is a real, teachable order to fixing this, and it consistently produces results when followed in sequence. Remove overburden first, meaning excess work in progress stacked beyond what the system can actually absorb. Once overburden comes down, unevenness becomes visible, which is your actual bottleneck showing itself clearly for the first time. Optimize that bottleneck specifically. Then remove waste at the bottleneck once it has been optimized.

That order matters. Trying to remove waste before the bottleneck has been identified wastes effort on the wrong part of the system. Trying to see unevenness while overburden still buries it means the real constraint stays hidden behind noise. Followed in the correct sequence, this framework is genuinely one of the most impactful tools available, and most teams have simply never been taught it.

What This Means for Your Own Project

None of this is really about one lab project in St. Louis. It is about recognizing that a schedule slipping despite a genuinely strong team is rarely a motivation problem or a talent problem. It is almost always a visibility problem, a system that cannot see its own constraint clearly enough to fix it.

If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your teams build the Takt planning and Lean vocabulary needed to actually see constraints, separate them from ordinary roadblocks, and optimize them the way that lab project eventually did. A twenty thousand dollar conversation that buys back two weeks of schedule only happens when someone knows to go looking for it.

So here is the challenge. Pull your own current schedule and check whether your zone sizes, sequence, and Takt time were actually calculated at the end of your pull plan, or whether they were assumed. If a schedule keeps slipping despite a genuinely strong team, stop looking for more effort or more hours, and start looking for the constraint nobody has named yet.

Jason Schroeder said it plainly: “Projects are failing because you have A-plus people in a C-minus system.” Fix the system, and the talent you already have will finally be able to show what it can actually do.

On we go.

FAQ

What is the actual difference between a constraint and a roadblock in construction?
A constraint is a system design problem, such as the wrong Takt time, poorly shaped zones, the wrong number of zones, or an improper sequence, and it affects the underlying structure of the plan itself. A roadblock is a temporary, removable obstacle sitting in the path of otherwise normal work, like weather, an unanswered RFI, or an area that is not yet ready. Confusing the two leads teams to treat fixable system problems as unavoidable bad luck.

Why did such a small additional cost recover so much schedule time on the lab project?
Because the fix addressed the actual root constraint, mismatched batch sizes and cycle times across trades, rather than trying to push through the symptom with more labor or overtime. Once the construction joints and rebar splices were adjusted to support smaller, better synchronized placements, the trades could flow together instead of working against each other’s rhythm, which is why a relatively modest investment produced a disproportionately large schedule recovery.

Why does the sequence of removing overburden before addressing waste matter so much?
Because excess work in progress, or overburden, buries the actual bottleneck under noise, making it impossible to see clearly. Removing overburden first reveals the unevenness that marks the real constraint. Trying to eliminate waste before that constraint is visible usually means effort gets spent on the wrong part of the system, since the true limiting factor has not actually been identified yet.

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.

Posted in All

What’s The Difference Between A Good Superintendent & A Great Superintendent?

Read 9 min

Good Superintendent vs Great Superintendent: The Real Difference

Here’s the deal. A good superintendent gets things done. A great superintendent gets things done the Lean way. That distinction sounds small until you watch what it actually produces over the life of a project, and it is the exact line I use when deciding who gets promoted.

Getting things done, on its own, is not actually rare in this industry. Plenty of superintendents can push a project across the finish line through sheer will, personal relationships, and enough hours to make almost anything happen. That is good. It is not great, and the difference matters more than most companies realize when they hand out promotions.

Getting It Done Their Own Way

A good superintendent has a method, and it usually works, at least well enough to finish. It typically lives entirely in their own head. They know the sequence, they know which trades need pushing and when, and they know how to solve problems as they come up. The project gets built.

The limitation is not effort or intelligence. It is that the whole system depends on one person’s memory, relationships, and personal style. Nothing about it is visible to anyone else, nothing about it is repeatable by someone else, and nothing about it necessarily respects the people executing the work along the way. It gets the job done. It does not build anything that outlasts that individual superintendent’s presence on the project.

Getting It Done the Lean Way

A great superintendent produces the same finished building, but through an entirely different process, and the difference shows up everywhere you look on the site.

Respect for people sits underneath everything else. The site is beautiful, clean, safe, and organized, not as decoration but as a direct reflection of how much the superintendent values the people working there every day. Work happens one thing at a time, genuinely flowing together, because the sequence has been well orchestrated rather than improvised under pressure. The plan itself lives on visual systems out where everyone can see it, not locked inside the superintendent’s head where only they can access it. Quality stays the actual focus, not an afterthought squeezed in after speed. Logistics run with real superiority, meaning materials, equipment, and information arrive where they are needed instead of causing daily scrambles. And the superintendent is always learning, treating their own development as an ongoing responsibility rather than something that stopped the day they earned the title.

Watch for these signs you are looking at the good version rather than the great version, even on a project that appears to be finishing on schedule:

  • The schedule and sequence exist mainly in the superintendent’s head rather than on a visible board or plan
  • Cleanliness and organization fluctuate heavily depending on how busy or stressed the superintendent currently is
  • Problem solving depends almost entirely on the superintendent’s personal relationships rather than a repeatable system

Any one of these can still produce a finished project. None of them produce a system that holds up without that specific person standing in the middle of it, and none of them make it any easier for the next superintendent to learn from what actually happened on that job.

Why Promotion Criteria Have to Reflect This

I want to be direct about something I hold firmly. I would never promote a superintendent who did not know how to train people, did not understand Lean systems, and could not keep a jobsite clean. Not because those are nice extras. Because those three things are the actual job.

I would not pay a nickel for an hour of work from a superintendent running a dirty jobsite who does not know Lean and does not know how to train people, no matter how fast that particular project happens to be moving. Training and building people is the main job of a superintendent, not a side responsibility squeezed in around the real work. A superintendent who cannot do that is missing the actual core of the role, regardless of how capable they are at pushing a schedule through sheer force.

That is a hard line, and I hold it on purpose, because promotion criteria built around who can get things done through personal grit alone will keep producing good superintendents forever and will never produce great ones. Great superintendents get made by promoting people specifically for the Lean capabilities that make their work repeatable, visible, and respectful of the people doing it.

This is where a lot of organizations quietly sabotage their own bench strength. They promote the person who fought hardest to finish the last project, without ever checking whether that person left behind a trained team or a system anyone else could pick up. Six months later, a new project starts, and the organization is right back to depending entirely on one individual’s personal grit again, because that is the only quality the promotion process actually rewarded.

What the Best of the Best Actually Do

The very best superintendents go one step further than running a clean, well organized, Lean site. They can scale systems, meaning what works on one project can be taught and replicated on the next one, not reinvented from scratch each time. They build humans, meaning the people who work under them come out of the project more capable than when they started, not just more tired. And they genuinely control the jobsite, meaning the environment, the rhythm, and the standards reflect deliberate leadership rather than whatever chaos happened to show up that day.

That combination, scaling systems, building people, and controlling the environment, is what actually separates the great superintendents from everyone else, and it is a completely different skill set than simply being good at getting a project finished. A superintendent operating at that level is not just running a good project. They are quietly training their own eventual replacement, and the organization’s next project, whether they realize it or not.

Why This Distinction Deserves Real Attention

None of this is really about superintendent titles or org charts. It is about what kind of legacy a superintendent leaves behind on every project and every person they work with.

A good superintendent leaves behind a finished building and a set of relationships that depended entirely on them personally. A great superintendent leaves behind a finished building, a team of people who are measurably better at their craft than when the project started, and a system that the next superintendent can actually learn from and build on. One of those outcomes compounds across a career and an organization. The other one resets to zero every time that superintendent moves to a new project.

If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field leaders make the shift from good to great, building the Lean capabilities, training instincts, and visual systems that separate the two. That shift is exactly what turns individual superintendent success into an organization that keeps getting stronger project after project.

So here is the challenge. Look at how your own organization currently evaluates and promotes superintendents. Is the criteria built around who gets projects finished, however they manage to do it? Or is it built around who runs a clean site, trains their people, and makes their plan visible to everyone around them? If it is the former, that is exactly where to start rewriting the standard.

Jason Schroeder said it plainly: “A good superintendent gets things done their own way. A great superintendent gets it done the Lean way.” Promote for the second one, and you build an organization that keeps getting better instead of one that keeps starting over.

On we go.

FAQ

Can a good superintendent become a great one, or is it mostly a matter of natural style?
It is absolutely learnable, and it typically comes down to deliberate training in Lean systems, visual planning, and how to actually develop the people working under them. Most superintendents who only know how to get things done their own way have simply never been taught the Lean alternative, not that they are incapable of it. Genuine investment in that training is usually what makes the difference.

Why does jobsite cleanliness matter so much in evaluating a superintendent’s actual quality?
Because cleanliness is a direct, visible reflection of respect for the people working there and of how much control the superintendent actually has over the environment. A superintendent who cannot maintain a clean, organized site is often also struggling with the underlying systems, standards, and consistency that a great superintendent maintains everywhere else, so it functions as a reliable leading indicator of deeper issues.

Why training people is considered the main job of a superintendent rather than a side responsibility?
Because a superintendent’s impact extends well beyond the single project they are currently running. Every crew member and future leader who passes through their supervision either grows in capability or does not, and that outcome compounds across an entire career and organization. A superintendent who finishes projects but never develops anyone leaves nothing behind once they move on, while one who trains consistently builds an organization’s long term capability with every 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.

Posted in All