Elevate Construction official logo
Contact us

Month: September 2026

Labor Productivity: How Superintendents Control Costs Through Flow?

Posted on by Team Jason Schroeder
Read 8 min

How Superintendents Actually Control Labor Cost Through Flow

Here’s the deal. The typical approach to controlling labor productivity cost focuses on production units tracked daily, allocated time per linear foot or square foot, and digging deep into cost codes. All of that financial tracking has its place. None of it is actually the real lever that controls cost. The real lever is readiness.

The Sign I Am Putting on the Wall

I have shifted my own thinking enough on this that I am putting a sign directly on the conference room wall at our next project. It says, I will not tomorrow panic. I will not tomorrow absorb variation. I will not tomorrow respond to non-safety emergencies. Whatever you need from me, get it from me today. We are not starting tomorrow until we are ready to finish it today.

Planning the day before is the actual key to everything. Not motivation. Not pushing harder. Planning, done completely, the day before work begins.

The Only Question That Actually Matters

For every single crew, the real question is simple. Do they have full kit? Materials, tools, equipment, people, permissions, layout, space, and everything else they genuinely need to complete their work. That question, asked honestly and answered completely, controls cost more directly than any financial tracking system ever will.

If you genuinely want better cost control for labor productivity, here is what that actually requires in practice. The space has to be clear. The layout has to be ready. It has to be crystal clear exactly what the crew is installing, through an installation work package, a checklist, or a visual work board feature that leaves no ambiguity. Materials need to be pre-kitted the day before, staged specifically for that area so the crew can walk in and start immediately. Expectations need to be genuinely clear, communicated through a real morning worker huddle. Materials need to have already been inspected. And the path needs to be genuinely roadblock free.

Watch for these signs a crew’s readiness has not actually been verified, regardless of what the schedule says:

  • Materials staged generally on site but not specifically pre-kitted for the exact area a crew will work in tomorrow
  • Installation expectations communicated verbally in passing rather than through a clear visual work package
  • A crew arriving at their zone and discovering the space is not actually clear or ready

Think of it the way you would think about assembling a piece of furniture that ships with everything included and clear instructions. That is genuinely what every crew’s readiness should be built around.

Nobody opens that kind of box and finds half the hardware missing or a single confusing diagram standing in for real instructions. Everything is accounted for before the box ever leaves the warehouse. A crew arriving at their zone should have that exact same experience, everything they need already accounted for, nothing left for them to discover was missing only after they have already started.

Why the Daily Question Has to Change

Most jobsites default to a version of, hey, are you doing good, hurry up, hurry up. That is a reactive question, and it treats speed as the thing worth checking on. The actual question that controls cost is different. Do you have full kit for the next day? That single shift, from checking on speed to verifying readiness, is where genuine cost control on labor productivity actually happens.

Asking about speed puts pressure on the crew to move faster inside whatever conditions they were handed, ready or not. Asking about readiness puts the responsibility on leadership to make sure those conditions were actually set up correctly in advance. Only one of those questions can genuinely be answered by the people responsible for planning, and it is not the one about speed.

A Concrete Example Worth Remembering

Here is where I have pushed this thinking further than most people take it. Picture a typical approach to safety logistics. A team realizes they need fire extinguishers, so they scramble to bring in a safety kit. That is reactive, and reactive is expensive.

The better question is why the fire extinguisher stands are not already waiting there before the building even needs them. Why is the safety kit not already staged and waiting? Why is the cool down station not already positioned next to the building before anyone asks for it? Why is all of the necessary signage not already packaged and ready to go? Full kit applies to logistics just as much as it applies to installation materials. If you genuinely want self-performing trades to make money, every single crew needs to be logistically ready, completely, the day before they actually start.

Why This Actually Controls Cost Better Than Financial Tracking Alone

None of this means production units, cost codes, and daily tracking are worthless. They tell you what already happened. Readiness is what determines what happens next. A crew with genuine full kit works efficiently because nothing is standing in their way. A crew without it burns labor hours hunting for materials, waiting on layout, or improvising around a roadblock nobody removed in advance, and no amount of after the fact cost code analysis recovers that lost time.

Think about what a cost report actually shows you in that second scenario. It shows a productivity number that came in low, sometimes long after the day is already over. It does not show you the missing pre-kit that caused it, or the layout conflict that ate an hour before anyone even noticed. Readiness checks catch that gap while it can still be fixed. A cost report only ever documents it after the money is already gone.

Controlling labor cost through flow means the cost control actually happens the day before, in the planning and staging, rather than the day of, through pressure and monitoring. By the time a crew is standing in their zone, the real cost control opportunity has already passed, for better or worse, based on how completely that readiness question was answered the previous day.

This applies just as directly whether you are self-performing the work or enabling a trade partner to do it. The specific labor may sit outside your own payroll in one case and inside it in the other, but the underlying lever is identical either way. Readiness the day before determines productivity the day of, regardless of whose crew is actually standing in the zone.

Building This Discipline Into Your Own Project

If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your teams build the genuine full kit verification process described here, checking every crew’s readiness completely the day before, rather than relying on financial tracking alone to catch cost problems after they have already happened.

So here is the challenge. Tomorrow, before your crews start, walk through the full kit question for every single one. Space clear. Layout ready. Materials pre-kitted. Expectations communicated. Roadblocks removed. If any answer comes back uncertain, that gap is exactly where tomorrow’s labor cost overrun is quietly forming right now, while there is still time to fix it.

Jason Schroeder said it plainly: “It’s not are you doing good, hurry up. It’s do you have full kit for the next day?” Ask that question completely, every single day, and watch what happens to your actual labor cost.

On we go.

FAQ

Why does the article argue that readiness controls labor cost more effectively than financial tracking?

Because production units, cost codes, and daily tracking report on what already happened, while readiness determines what actually happens the next day before it occurs. A crew with genuine full kit works efficiently by default, while a crew missing materials, layout, or clear instructions loses labor hours that no amount of after the fact cost analysis can recover.

What does “full kit” specifically include beyond just having the right materials on site?

Full kit covers materials, tools, equipment, people, permissions, layout, and space, all verified and ready specifically for the exact area a crew will work in. It also includes clear installation expectations communicated through a real work package or visual board, materials that have already been inspected, and a path genuinely free of roadblocks before the crew ever arrives.

Why does the article use fire extinguishers and safety kits as an example of proactive versus reactive logistics?

Because it illustrates how easily an organization defaults to reacting to a need in the moment rather than staging it in advance. Waiting until a fire extinguisher is needed to bring one in reflects the same reactive pattern that shows up with installation materials, while staging it, along with safety kits, cool down stations, and signage, before it is needed reflects genuine full kit thinking applied to logistics rather than just materials.

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 47 Things Before Work Starts

Posted on by Team Jason Schroeder
Read 9 min

The 47 Things: Why Before-Phase Planning Matters More Than the Phase Itself

Here’s the deal. Working through how to keep everyone genuinely on track on our own Aviator project, I landed on something that changed how I think about project delivery entirely. The preparation that happens before any activity starts is more important than actually standing there supervising the work once it begins.

Poorly run project delivery teams hand a trade a contract, tell them to go ahead and start, and then spend their time walking around watching. Genuinely great project delivery team leaders understand something different. There are roughly forty seven distinct things that have to happen, done well and done on time, before any single work package can actually begin.

Visualizing Where the Real Work Actually Sits

Here is the exercise that made this concept click for me. Take a construction schedule and isolate every first activity, every independent wagon, everything with a work package that has to be prepared in advance. Line those starting activities up on a diagonal, running from the top left down to the bottom right of your production plan. Now look at what sits in front of each one of those starting points, further to the left on the timeline. That is where you find roughly forty seven preparation activities that genuinely have to happen before that work package can begin.

Do this across an entire project and you end up staring at an enormous page covered in stickies. Each one represents a real piece of preparation work, and each one requires a genuine level of effort to complete. Here is where it gets difficult. Every human on your project delivery team only has a certain amount of capacity to actually do that preparation work, and that capacity has to account for PTO, doctor’s appointments, ordinary distractions, and everything else that eats into a normal week.

Why Projects Actually Fall Behind

Once you see it laid out this way, the real problem in construction becomes obvious. We are not starting these preparation activities soon enough. They need to move further to the left on the timeline, meaning they need to begin earlier, and most project teams simply are not doing that.

Watch for these signs your project is not moving preparation activities far enough ahead of when they are actually needed:

  • Work packages arriving at their start date with prep activities still incomplete or barely underway.
  • No visible tracking of preparation work separate from the visible construction schedule itself.
  • Project delivery team members consistently overloaded right before a phase begins, rather than steadily working ahead of it.

Why the Back Third of Almost Every Project Suffers

Here is where this connects directly to something worth understanding about the human brain. At roughly the two thirds point of a typical project, CPM schedules already start hurting teams structurally, since that is usually where borrowed schedule slack finally runs out. On top of that structural problem sits a genuinely human one. The human brain is de-incentivized to do pre-planning and incentivized instead to fight fires. Firefighting feels urgent and rewarding in the moment. Quiet, unglamorous preparation work does not carry that same emotional pull, even though it matters just as much, if not more.

So exactly when a project needs more disciplined pre-planning, people naturally do less of it, because their attention gets pulled toward whatever fire is burning loudest right now. The final third of a project ends up suffering directly because of that missing before-phase planning, compounding on top of whatever schedule pressure was already building.

What We Actually Built to Fix This

On the Aviator project, I broke this preparation work into distinct categories. Supply chain. Contracting. Training. Pull plan preparation. Work packaging. Then I built a series of gates a project delivery team has to pass through, in sequence, before moving forward.

The first gate is the pre-mobilization meeting, and I want to personally be present in that meeting. The next gate sits before the pull plan itself, where I check that the team has genuinely completed all the necessary preparation activities leading up to it. Another gate sits before the pre-construction meeting for each trade. Moving from left to right across the project, each gate has its own checklist, and the exact count is not fixed at forty seven for every single situation. Sometimes it is thirty five. Sometimes closer to fifty. What matters is capturing every genuine preparation activity and looping it into the relevant gate, rather than letting any of it slip through unnoticed.

When I walk into a pre-mobilization meeting, I can check directly with the project delivery team. Are these specific things actually done? If yes, we move forward, and the next set of items becomes their active to-do list. When we reach the pre-construction meeting gate, I check the same way. Are these things ready? The gates move the team forward deliberately, one verified step at a time, rather than assuming preparation happened simply because the calendar says it should have.

Making This Genuinely Trackable, Not Just Theoretical

None of this works as an idea alone. It needs a real system behind it. We built templated checklists for every gate inside a project management tool, in our case ClickUp, so a team member entering a new phase has an actual template to work from rather than a vague understanding of what needs to happen.

Between gates, team members plan their own work using Fibonacci numbers through a Scrum style approach, which helps genuinely manage their available capacity rather than simply hoping everything fits. Our Takt software carries the same gates and timelines built directly into the production plan, so the entire system, software and checklist templates together, keeps everyone moving forward deliberately instead of discovering a gap only once it becomes urgent.

Why This Deserves Real Attention From Project Management Software Broadly

The honest takeaway here goes beyond one project. Most project management software tracks the visible scheduled activities well. Very little of it genuinely tracks the forty seven things sitting in front of each one, the real preparation work that determines whether that visible activity can actually start on time. We need project delivery systems built specifically to track and manage that preparation work, while genuinely accounting for the real human capacity available to complete it.

If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your teams build exactly this kind of gate based preparation system, tracking the real work sitting ahead of every activity rather than only watching the schedule once work has already started.

So here is the challenge. Pick one upcoming phase on your current project and count the actual preparation activities sitting in front of it. Do not stop until you have genuinely captured all of them, however many that turns out to be. Then check honestly whether each one has already been started, or whether it is still sitting further to the right on the timeline than it should be.

Jason Schroeder said it plainly: “Before-phase planning is more important than actually the phase.” Build your systems around that truth, and the back third of your project stops absorbing the consequences of what never got prepared early enough.

On we go.

FAQ

Why does the exact number of preparation activities vary between thirty five and fifty rather than always being forty seven?

Because the real number of preparation activities depends on the specific work package, trade, and phase involved, and no single count applies universally across every situation. The number forty seven functions as a useful shorthand for the concept, a genuinely large volume of prerequisite work sitting ahead of any visible schedule activity, rather than a precise figure meant to apply identically everywhere.

Why does the human brain resist proactive pre-planning even when it clearly matters?

Because firefighting an active, visible problem feels urgent and rewarding in the moment, while quiet preparation work for something that has not gone wrong yet does not carry that same emotional pull. That mismatch means people naturally drift toward reactive work under pressure, even during the exact stretch of a project where disciplined pre-planning matters most.

How do gates actually prevent a project from falling behind on preparation work?

Gates create a specific checkpoint before a team can move forward into the next phase, forcing an honest verification that the required preparation activities are genuinely complete rather than assumed to be done. That verification catches gaps while there is still time to close them, instead of discovering a missing piece of preparation only once the phase it supports has already begun.

Why does human capacity need to be factored into a preparation tracking system rather than just listing the tasks themselves?

Because a list of preparation tasks alone does not account for the real, limited time each team member actually has available once PTO, appointments, and normal distractions are factored in. A system that ignores capacity can produce a checklist that looks complete on paper while quietly overloading the people responsible for actually completing it, which defeats the purpose of tracking preparation in the first 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

Lazy and Entitled Behavior Does Not Get to Use Lean Principles

Posted on by Team Jason Schroeder
Read 9 min

Lazy and Entitled Behavior Does Not Get to Hide Behind Good Principles

Here’s the deal. I teach principles like we do not start until we are ready to finish, real buffers, taking care of people, and team balance because they genuinely respect the people doing the work. I have also watched these exact principles get twisted into excuses for laziness and entitlement, and I want to name that pattern directly, because it damages the very people these principles were built to protect.

When “Ready to Finish” Gets Weaponized

Here is a real example. I once worked with someone for six to eight months on preparation for a delivery, and they simply did not do the necessary preparation on time. I do not think that was pure laziness or entitlement, honestly. It may have just been a genuine disconnect in how their brain tracked the timeline. But when the actual delivery date arrived and I pushed to get things moving, the response was, Jason, you said we do not start until we are ready to finish.

No. That principle was never meant to protect someone who had six to eight months and simply did not use that time well. Being genuinely particular and disciplined about readiness is exactly the right instinct before a deadline, while there is still time to prepare properly. It becomes something entirely different when it gets pulled out after the fact, as a shield for having not done the work in the first place. That is not disciplined readiness. That is an excuse dressed up in the language of discipline.

I want to be fair here too. Not everyone who invokes a principle this way is being deliberately manipulative. Sometimes it genuinely is a disconnect, someone who did not track the timeline well and reaches for the nearest available justification once confronted. The intent matters less than the pattern, though, because either way, the actual deadline still needs to be met, and the team still needs an honest accounting of what happened rather than a principle used to avoid that conversation.

When “Taking Care of People” Gets Twisted Into Entitlement

Here is another version of the same problem. Taking care of people and respecting people gets stretched, by some, into an excuse for excessive unearned time off, chronic lateness, or calling in sick when someone is not actually sick. None of that is what taking care of people ever meant.

Taking care of people and respect for people was never a license to avoid hard work. It means we work hard specifically because we respect the foremen and workers who are genuinely putting in real effort in the field every single day. Twisting that principle into cover for entitled behavior does the opposite of respecting the people around you. It puts more weight on everyone else who is actually showing up and doing their part.

Watch for these signs a genuinely good principle is being misused as cover for poor performance:

  • A discipline focused principle invoked only after a deadline has already been missed, rather than during the preparation that was supposed to precede it.
  • A people-focused principle used to justify chronic absence or reduced effort rather than genuine care during real hard work.
  • Team balance treated as permission to reduce hours meaningfully below what the actual workload requires.

When Team Balance Becomes an Excuse Instead of a Genuine Standard

I have also watched team balance, a concept genuinely built to protect people from being overburdened, get reinterpreted into something like a right to banker’s hours, treating a normal, genuinely demanding workweek as somehow excessive. That misreads the entire point. Team balance exists to protect people from being asked to give more than the system can reasonably sustain. It was never meant to shrink genuine effort down to a fraction of what the actual work requires.

Principles for Hardworking People, Not an Escape Hatch

I once worked alongside a genuinely great colleague who used to joke that if he ever started his own construction company, he would call it Get Stuff Done Construction. I loved that name immediately, because it captures exactly what these principles are actually built for.

Stop, call, resolve. Taking care of people. Team balance. Respect for people. Stability and standardization. Stopping to get something right. Building in a real buffer at the end. We do not start until we are ready to finish. None of these are my personal invention. They are genuine Lean principles, and every single one of them exists specifically for hardworking people. They are not an excuse for someone to behave poorly or coast on someone else’s effort.

I genuinely resent watching this happen in practice. A buffer built in specifically so a crew can teach each other, improve each other’s skills, organize a zone properly, and finish an area with real quality gets misused instead as an excuse to disappear from the site entirely. Respect for people gets twisted into justification for irresponsible personal behavior that has nothing to do with genuine wellbeing. Team balance gets used as cover to abandon real responsibilities rather than protect against genuine overburden. None of that is what these principles were ever meant to support.

Each of those misuses shares the same underlying move. Take a principle built to protect people doing real work, and quietly redirect it to protect someone avoiding that work instead. The words stay the same. The actual meaning gets hollowed out entirely, and everyone else on the team ends up carrying the difference.

Lean Works for Get Stuff Done Construction

These principles exist so that hardworking people can do genuinely good work while being respected and taken care of along the way. They were never built to accommodate people unwilling to put in real effort. I will not support or advocate for behavior that treats hard work as optional while still expecting the benefits that hard work actually earns.

I hold a real, unapologetic standard here. Living without a genuine sense of purpose or mission, coasting through work while expecting the same respect owed to someone genuinely giving their effort, is not something I am willing to quietly accept. We are not building a culture around self-indulgence for its own sake. We are building a culture around genuinely giving value and adding real effort, and every principle I teach exists specifically to support people doing exactly that.

Building This Distinction Into Your Own Team

None of this requires abandoning care for people or genuine flexibility. It requires being precise about what these principles actually protect, and refusing to let them be reinterpreted into cover for behavior they were never meant to excuse.

If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your teams hold this exact distinction clearly, genuinely taking care of hardworking people while refusing to let entitled behavior hide behind principles built for something else entirely.

So here is the challenge. The next time someone invokes one of these principles to explain why they did not deliver, or why genuine effort was skipped, ask directly whether the principle is actually being honored or simply being used as cover after the fact. That question tends to reveal the difference immediately.

Jason Schroeder said it plainly: “Lazy and entitled behaving people do not get to latch onto my principles.” These principles exist for people genuinely putting in the work, and that distinction is worth holding firmly.

On we go.

FAQ

How can you tell the difference between genuinely holding a standard and using it as an excuse after the fact?

Look at the timing. Holding a genuine standard, like insisting on real readiness before starting, happens during the preparation window, while there is still time to actually do the work well. Using the same language as an excuse typically shows up only after a deadline has already been missed, invoked specifically to avoid accountability for time that was not used properly.

Why does the article insist that taking care of people never meant working less hard?

Because the actual purpose of taking care of people is protecting them from being overburdened or disrespected while doing genuinely demanding work, not eliminating the demanding work itself. Twisting that principle into justification for reduced effort or chronic absence shifts more burden onto teammates who are still showing up and working hard, which is the opposite of the respect the principle was meant to encourage.

What is the actual purpose of team balance, and how does it get misused?

Team balance exists to ensure a team is not asked to take on more than it can reasonably sustain, protecting against burnout and overwork. It gets misused when it is reinterpreted as justification for significantly reducing hours or effort below what the actual workload genuinely requires, treating a normal demanding workweek as excessive rather than addressing genuine overburden when it exists.

Why does the article distinguish between hardworking people and entitled behavior so sharply?

Because the principles being described, buffers, team balance, respect for people, and disciplined readiness, only function as intended when the people applying them are genuinely putting in real effort. Applied to someone unwilling to do the underlying work, these same principles get hollowed out into excuses, which damages trust and unfairly shifts additional burden onto teammates who are genuinely contributing.

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

Meeting Time Limits Are Stupid

Posted on by Team Jason Schroeder
Read 9 min

Lazy and Entitled Behavior Does Not Get to Hide Behind Good Principles

Here’s the deal. I teach principles like we do not start until we are ready to finish, real buffers, taking care of people, and team balance because they genuinely respect the people doing the work. I have also watched these exact principles get twisted into excuses for laziness and entitlement, and I want to name that pattern directly, because it damages the very people these principles were built to protect.

When “Ready to Finish” Gets Weaponized

Here is a real example. I once worked with someone for six to eight months on preparation for a delivery, and they simply did not do the necessary preparation on time. I do not think that was pure laziness or entitlement, honestly. It may have just been a genuine disconnect in how their brain tracked the timeline. But when the actual delivery date arrived and I pushed to get things moving, the response was, Jason, you said we do not start until we are ready to finish.

No. That principle was never meant to protect someone who had six to eight months and simply did not use that time well. Being genuinely particular and disciplined about readiness is exactly the right instinct before a deadline, while there is still time to prepare properly. It becomes something entirely different when it gets pulled out after the fact, as a shield for having not done the work in the first place. That is not disciplined readiness. That is an excuse dressed up in the language of discipline.

I want to be fair here too. Not everyone who invokes a principle this way is being deliberately manipulative. Sometimes it genuinely is a disconnect, someone who did not track the timeline well and reaches for the nearest available justification once confronted. The intent matters less than the pattern, though, because either way, the actual deadline still needs to be met, and the team still needs an honest accounting of what happened rather than a principle used to avoid that conversation.

When “Taking Care of People” Gets Twisted Into Entitlement

Here is another version of the same problem. Taking care of people and respecting people gets stretched, by some, into an excuse for excessive unearned time off, chronic lateness, or calling in sick when someone is not actually sick. None of that is what taking care of people ever meant.

Taking care of people and respect for people was never a license to avoid hard work. It means we work hard specifically because we respect the foremen and workers who are genuinely putting in real effort in the field every single day. Twisting that principle into cover for entitled behavior does the opposite of respecting the people around you. It puts more weight on everyone else who is actually showing up and doing their part.

Watch for these signs a genuinely good principle is being misused as cover for poor performance:

  • A discipline focused principle invoked only after a deadline has already been missed, rather than during the preparation that was supposed to precede it.
  • A people-focused principle used to justify chronic absence or reduced effort rather than genuine care during real hard work.
  • Team balance treated as permission to reduce hours meaningfully below what the actual workload requires.

When Team Balance Becomes an Excuse Instead of a Genuine Standard

I have also watched team balance, a concept genuinely built to protect people from being overburdened, get reinterpreted into something like a right to banker’s hours, treating a normal, genuinely demanding workweek as somehow excessive. That misreads the entire point. Team balance exists to protect people from being asked to give more than the system can reasonably sustain. It was never meant to shrink genuine effort down to a fraction of what the actual work requires.

Principles for Hardworking People, Not an Escape Hatch

I once worked alongside a genuinely great colleague who used to joke that if he ever started his own construction company, he would call it Get Stuff Done Construction. I loved that name immediately, because it captures exactly what these principles are actually built for.

Stop, call, resolve. Taking care of people. Team balance. Respect for people. Stability and standardization. Stopping to get something right. Building in a real buffer at the end. We do not start until we are ready to finish. None of these are my personal invention. They are genuine Lean principles, and every single one of them exists specifically for hardworking people. They are not an excuse for someone to behave poorly or coast on someone else’s effort.

I genuinely resent watching this happen in practice. A buffer built in specifically so a crew can teach each other, improve each other’s skills, organize a zone properly, and finish an area with real quality gets misused instead as an excuse to disappear from the site entirely. Respect for people gets twisted into justification for irresponsible personal behavior that has nothing to do with genuine wellbeing. Team balance gets used as cover to abandon real responsibilities rather than protect against genuine overburden. None of that is what these principles were ever meant to support.

Each of those misuses shares the same underlying move. Take a principle built to protect people doing real work, and quietly redirect it to protect someone avoiding that work instead. The words stay the same. The actual meaning gets hollowed out entirely, and everyone else on the team ends up carrying the difference.

Lean Works for Get Stuff Done Construction

These principles exist so that hardworking people can do genuinely good work while being respected and taken care of along the way. They were never built to accommodate people unwilling to put in real effort. I will not support or advocate for behavior that treats hard work as optional while still expecting the benefits that hard work actually earns.

I hold a real, unapologetic standard here. Living without a genuine sense of purpose or mission, coasting through work while expecting the same respect owed to someone genuinely giving their effort, is not something I am willing to quietly accept. We are not building a culture around self-indulgence for its own sake. We are building a culture around genuinely giving value and adding real effort, and every principle I teach exists specifically to support people doing exactly that.

Building This Distinction Into Your Own Team

None of this requires abandoning care for people or genuine flexibility. It requires being precise about what these principles actually protect, and refusing to let them be reinterpreted into cover for behavior they were never meant to excuse.

If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your teams hold this exact distinction clearly, genuinely taking care of hardworking people while refusing to let entitled behavior hide behind principles built for something else entirely.

So here is the challenge. The next time someone invokes one of these principles to explain why they did not deliver, or why genuine effort was skipped, ask directly whether the principle is actually being honored or simply being used as cover after the fact. That question tends to reveal the difference immediately.

Jason Schroeder said it plainly: “Lazy and entitled behaving people do not get to latch onto my principles.” These principles exist for people genuinely putting in the work, and that distinction is worth holding firmly.

On we go.

FAQ

How can you tell the difference between genuinely holding a standard and using it as an excuse after the fact?

Look at the timing. Holding a genuine standard, like insisting on real readiness before starting, happens during the preparation window, while there is still time to actually do the work well. Using the same language as an excuse typically shows up only after a deadline has already been missed, invoked specifically to avoid accountability for time that was not used properly.

Why does the article insist that taking care of people never meant working less hard?

Because the actual purpose of taking care of people is protecting them from being overburdened or disrespected while doing genuinely demanding work, not eliminating the demanding work itself. Twisting that principle into justification for reduced effort or chronic absence shifts more burden onto teammates who are still showing up and working hard, which is the opposite of the respect the principle was meant to encourage.

What is the actual purpose of team balance, and how does it get misused?

Team balance exists to ensure a team is not asked to take on more than it can reasonably sustain, protecting against burnout and overwork. It gets misused when it is reinterpreted as justification for significantly reducing hours or effort below what the actual workload genuinely requires, treating a normal demanding workweek as excessive rather than addressing genuine overburden when it exists.

Why does the article distinguish between hardworking people and entitled behavior so sharply?

Because the principles being described, buffers, team balance, respect for people, and disciplined readiness, only function as intended when the people applying them are genuinely putting in real effort. Applied to someone unwilling to do the underlying work, these same principles get hollowed out into excuses, which damages trust and unfairly shifts additional burden onto teammates who are genuinely contributing.

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

If Lean Makes You Feel Justified, You Likely Didn’t Understand

Posted on by Team Jason Schroeder
Read 9 min

If Lean Makes You Feel Justified, You Probably Did Not Understand It

Here’s the deal. I want to say this with real humility, because I genuinely do not know everything, and I respect anyone who disagrees with what follows. But here is something I have noticed repeatedly, and it is worth saying plainly. When someone studies Lean, visits Japan, or reads deeply into Takt planning and comes back feeling like it confirms everything they already believed, that is usually a sign they missed the actual point.

What a Real Study Trip Should Actually Teach You

Traveling to Japan with Paul Akers was genuinely one of the most important experiences of my life. What I saw there was remarkable enough that I came home and wrote an entire six book series trying to catalog it clearly for the construction industry, covering respect for people, nature, and resources, stability and standardization, one piece process flow, flowing together on Takt time and pull, total participation and visual systems, and quality with continuous improvement. Those books have genuinely resonated, to the point where an order for five hundred copies of just the stability and standardization book came in recently.

The trip taught me something true. It also revealed a pattern in how other people process the exact same kind of experience, and that pattern is worth examining honestly.

The Trap of Confirming What You Already Believed

I want to be careful here, because this observation can sound judgmental, and I genuinely do not mean it that way. People come back from a genuine Lean study experience and sometimes latch onto the strangest possible interpretations. Someone might miss the emphasis on cleanliness entirely and instead fixate obsessively on optimizing one narrow detail before ever actually implementing anything, insisting that is how the Japanese really do it.

Here is one I have heard often. Someone hears that Japanese companies make decisions slowly, and comes back convinced that leadership should deliberately slow down its own decision making, treating chronic indecision as somehow culturally validated. That is not what the principle actually means. It means building genuine consensus before bringing a decision into the room, not sitting in the room agonizing endlessly once it is there. Ohno’s own teaching on this is direct. First say yes, then figure it out, and stick with something until it is genuinely completed. Japanese car companies are not bottlenecked by decision fatigue or endless consensus building. They move with real speed once a direction is set.

Watch for these signs a Lean concept has been quietly bent to justify a pre-existing habit rather than genuinely understood:

  • A single narrow piece of Lean, like pull or cleanliness, obsessed over while the surrounding framework gets ignored entirely.
  • A principle interpreted in whatever direction happens to validate a behavior someone was already inclined toward.
  • Confidence that a concept has been fully grasped without ever checking it against the whole system it came from.

Why This Happens So Easily

Here is the honest mechanism behind this pattern. The human brain is genuinely skilled at retroactively justifying beliefs it already holds. If someone already struggles with indecision, a vague reference to slow Japanese decision making becomes exactly the confirmation their brain was looking for. If someone already wants to perfect something endlessly before shipping it, a misread concept about care and precision becomes permission to keep delaying. Ohno’s actual teaching runs the opposite direction. First establish it, and then perfect it later.

Without genuine field experience, real practice, and real money already invested in actually doing the work, a study trip or a deep dive into the material can accidentally magnify exactly what someone already wanted to believe, rather than correcting it. That is how genuinely well intentioned people end up wildly misinterpreting something they encountered directly.

This is not a criticism reserved for other people either. I try to hold myself to the same standard, since the same mental shortcut applies to anyone processing a new experience through an existing lens, myself included. The honest fix is not confidence that you avoided the trap. It is a habit of checking your own conclusions against the full framework every time, rather than assuming a comfortable interpretation is automatically the correct one.

The Specialist Trap

Here is a version of this trap that shows up constantly. Someone whose personal specialty is pull planning goes to Japan, comes back talking exclusively about pull, pull, pull, and barely mentions Takt, even though Takt is genuinely one of the very first things actually taught there. That person is not lying. They are seeing the whole system through the lens of the one piece they already loved before they arrived, and mistaking their own specialty for the complete picture.

The correct sequence matters here too. You first remove overburden, then address unevenness, then eliminate waste, in that order. Someone fixated on a single tool, whichever one happens to be their personal passion, is not actually seeing the whole picture, no matter how genuinely skilled they are at that one specific piece.

The Real Test Worth Applying

If you study Lean and immediately feel justified in whatever you were already doing, that feeling itself is the warning sign, not the confirmation. The real question worth asking is whether what you are doing actually respects people, and whether it genuinely fits within the full framework, rather than one convenient slice of it pulled out to support a conclusion you had already reached.

Here is a way to think about Lean that clarifies this. If Lean had a genuine mission statement, it would be to elevate humanity. If it had a stated purpose, every Lean system would be described as a seeing system, one that lets us see the inherent value of the people involved and the systems affecting them clearly. Its core values run through respect, stability, flow, Takt and pull, total participation and visual systems, and quality with continuous improvement. None of those values exist to make anyone feel comfortable with a habit they already had. They exist specifically to challenge and improve it.

Why This Matters Beyond a Single Study Trip

If Lean never feels hard, if it never feels contrary to something you already assumed, if it stops feeling fundamentally about people and starts feeling like justification for a shortcut you wanted to take anyway, that is exactly the moment to stop and dig deeper rather than move forward confidently.

If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your teams genuinely test their understanding of Lean and Takt against the full framework, rather than letting a single comfortable interpretation quietly stand in for the whole system.

So here is the challenge. Think honestly about a Lean or Takt concept you have applied recently, and ask whether it genuinely challenged something you were already doing, or whether it simply gave you permission to keep doing it. If the answer is the second one, that is exactly where real understanding still has room to grow.

Taiichi Ohno said it plainly: “First establish it, then perfect it later.” Get the whole system in place honestly first, before deciding you have already mastered it.

On we go.

FAQ

Why does the article suggest that feeling justified after learning Lean is actually a warning sign?

Because genuine Lean principles are usually more demanding than comfortable, challenging existing habits rather than confirming them. If a person walks away from studying Lean feeling entirely validated in whatever they were already doing, that often means they absorbed only the piece of the framework that happened to align with their existing beliefs, rather than genuinely engaging with the whole system.

Why does the article single out the misinterpretation of “slow decision making” as an example?

Because it illustrates how easily a real principle can get twisted into permission for an existing weakness. The actual idea is building consensus before bringing a decision into a room, which enables fast, decisive action once a direction is set. Misreading it as literal slow deliberation in the room itself turns a principle about speed and alignment into an excuse for chronic indecision.

Why does specializing narrowly in one Lean tool, like pull planning, create a distorted understanding of the whole system?

Because a person’s existing passion or specialty naturally shapes what they notice and remember from a broader learning experience, even when that specialty is only one part of a much larger framework. Focusing exclusively on pull while overlooking Takt, which is typically taught earlier and just as fundamentally, produces a genuinely skewed picture of the system, even though the person’s expertise in their specific area may be completely genuine.

What is the actual test the article proposes for checking whether someone has genuinely understood a Lean concept?

Ask whether the interpretation actually respects people and fits within the complete framework, rather than checking whether it simply feels comfortable or validating. A genuine understanding of Lean tends to challenge existing habits and require real change, while a distorted interpretation tends to conveniently justify whatever someone was already inclined to do.

If you want to learn more we have:

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

Discover Jason’s Expertise:

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

Posted in All

You Gotta Have Time for Quality

Posted on by Team Jason Schroeder
Read 9 min

You Have to Have Time for Quality

Here’s the deal. Quality is not primarily a skill problem in most organizations. It is a time problem. You can have genuinely capable people who know exactly what quality work looks like, and still fail to deliver it consistently, because nobody actually carved out the time required to do it right.

Why Quality Matters at a National Level

  1. Edwards Deming taught quality principles directly to Japanese manufacturers, and that emphasis is widely credited as a major driver behind the rise of Japanese, and later Korean and Chinese, manufacturing output and economic growth. Quality genuinely built GDP. In the United States, that same focus has quietly declined across much of manufacturing, even as newer growth areas like data centers get most of the attention. We cannot let that broader manufacturing quality focus keep slipping simply because a newer growth story is capturing everyone’s interest.

The Real Reason Quality Suffers

Here is the honest root cause behind most quality failures. We live inside a culture of push, push, push, rush, rush, rush, panic. Nobody set out to produce a lower quality product on purpose. The actual work simply never got the time it genuinely needed, because everything downstream of planning was compressed by that same rushing culture.

There is a distinction worth being precise about here. Driving hard and being genuinely aggressive during planning and pre-construction is a good thing. Overcommitting to preparation, front loading the difficult thinking before work begins, protecting time specifically so the field never has to rush later, all of that is exactly the right instinct. Pushing during actual execution in the field is the opposite. Starting too soon, over-committing to an unrealistic pace once real work is underway, and falling into what amounts to a commitment fallacy, believing haste will somehow make up for insufficient preparation, are all genuinely damaging. I try to be as aggressive as possible during planning specifically so that I never have to push once we are actually building.

What Genuinely Having Time for Quality Requires

Having time for quality is not a vague aspiration. It requires specific, deliberate structure. Real buffers built into individual activities. Real buffers built into Takt wagons. Real buffers at the end of phases. Real buffers at the overall project level. And a genuine willingness to stop, pull the andon, and pause long enough to inspect and verify that work is actually done the way it needs to be done, rather than pushing forward on the assumption that it probably is.

Watch for these signs your organization has stopped genuinely protecting time for quality:

  • Buffers treated as padding to be quietly absorbed rather than genuine protection for quality checks.
  • Inspections rushed or skipped under schedule pressure rather than treated as non-negotiable.
  • Planning compressed to free up more time for execution, rather than protected as the phase where real rigor belongs.

The Spiral That Starts with a Lack of Quality

Here is something I have noticed directly from real experience, and it explains why quality failures compound rather than staying contained. Excessive work in progress, meaning overproduction beyond what the system can actually absorb, usually starts with financial panic. That panic itself frequently traces back to a lack of quality in the first place, since customers simply buy less from a company whose product or work has started to disappoint them.

Once that financial pressure hits, the instinctive response is to overproduce to compensate, which increases work in progress, generates more waste, and accelerates the exact spiral described in earlier discussions about cutting expenses and focusing purely on efficiency. A lack of quality upsets customers directly, and it also pulls leadership attention away from genuine improvement and toward damage control, distracted trying to patch symptoms instead of addressing the actual root cause. That distraction alone damages a brand, on top of whatever the original quality failure already cost.

Notice how many separate points of damage trace back to that same single root cause. Fewer sales. Fewer people employed as revenue contracts. A production system straining under excess work in progress. Leadership distracted fighting symptoms instead of building. None of those are independent problems requiring independent fixes. They are downstream consequences of one upstream failure, which is exactly why protecting quality at the source is so much more effective than trying to manage each symptom separately as it appears.

Why Brand Damage from Quality Failures Rarely Fully Recovers

Here is the part that deserves real attention, because it explains why this issue matters so much more than a single missed deadline or a single unhappy customer. Damage to a brand’s reputation for quality tends to be extraordinarily difficult to reverse, even long after the underlying problem has genuinely been fixed.

Think about Kia as an example. The brand has genuinely improved its reliability and build quality significantly over the years. Ask most people what comes to mind first when they hear the name, and a lingering association with lower quality often still surfaces, well after that reputation stopped being an accurate reflection of the current product. That lag is exactly the risk every organization takes when it lets quality slip, even temporarily. The improvement can happen. The reputational damage frequently outlasts it by years.

Construction carries this same risk, even though the mechanism looks slightly different. A general contractor whose name becomes associated with rushed, low quality work does not simply lose the next bid on price alone. Owners and trade partners remember that reputation long after any single project team has genuinely improved its practices, which means protecting quality from the start is far cheaper than trying to out-market a damaged reputation later.

Why This Comes Back to Time, Every Single Time

All of this, the spiral, the brand damage, the customer frustration, traces back to the same root cause. Not enough time was carved out to actually do the work right the first time. Getting out of a rush, push, and panic culture requires a genuine willingness to stop, to protect real buffers, and to accept that pausing to get something right costs less in the long run than rushing forward and discovering the cost later, once a customer, or an entire market, has already noticed.

Building Real Time for Quality into Your Own Project

None of this happens automatically. It requires deliberately protecting planning time up front, building genuine buffers into every level of a schedule, and creating a culture where stopping to verify quality is treated as strength rather than as a delay to apologize for.

If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your teams build the buffer structure and planning discipline that genuinely protects time for quality, rather than treating quality as something squeezed in only when the schedule happens to allow it.

So here is the challenge. Look at your own current project and identify one place where a buffer meant to protect quality has quietly become a source used to make up lost time instead. Restoring that protection, even in just one place, is exactly where genuine quality starts to hold again.

Jason Schroeder said it plainly: “You’ve got to have time for quality.” Protect that time deliberately, because the alternative costs far more than the time itself ever would have.

On we go.

FAQ

Why is aggressive planning considered good while aggressive pushing during execution is considered harmful?

Aggressive planning front loads the difficult thinking, research, and preparation before real work begins, specifically so that execution can proceed smoothly without needing to rush later. Aggressive pushing during execution instead tries to compensate for insufficient preparation with speed and pressure in the moment, which tends to sacrifice quality and increase the very problems that preparation was supposed to prevent.

How does excessive work in progress actually trace back to a lack of quality?

A lack of quality tends to reduce sales, which creates financial pressure. That pressure often triggers overproduction as an attempt to compensate, which increases work in progress beyond what the system can actually absorb efficiently, generating more waste and accelerating the same financial pressure that caused it in the first place, creating a self reinforcing spiral.

Why does brand damage from a quality failure tend to last longer than the actual quality problem itself?

Because customer perception often lags well behind actual improvement, meaning a brand can genuinely fix an underlying quality issue while public perception continues to reflect the old reputation for years afterward. That lag means the reputational cost of a quality failure frequently outlasts the practical cost of the failure itself, which is why protecting quality proactively matters more than most organizations initially assume.

What are the specific places a project should build in buffers to protect time for quality?

Buffers belong at multiple levels simultaneously: within individual activities, within Takt wagons, at the end of project phases, and at the overall project level. Treating these buffers as protected time for verification and inspection, rather than as flexible padding to be absorbed whenever schedule pressure increases, is what actually keeps genuine time for quality available when it is needed most.

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

Climb With Your Feet: People, Quality, Process

Posted on by Team Jason Schroeder
Read 9 min

Why the Real Priority Order Is People, Quality, Process, Not People, Process, Quality

Here’s the deal. I have been teaching people, process, and quality as the core Lean priority order for a long time, borrowed directly from what I learned studying Japanese manufacturing culture. I recently caught myself getting the order wrong, and correcting it matters enough that I want to walk through exactly why.

Catching My Own Mistake

The framing I originally used was people first, process second, quality third. Sitting with that order honestly, I realized it does not actually reflect what matters most in practice. Process exists specifically to support quality. It is not equally important alongside it. If a team has to work a little less efficiently in the short term to protect a genuinely quality product, protecting that quality is worth the temporary inefficiency. Refining the process itself, once quality is genuinely secured, is exactly the kind of improvement work that comes later, once a team has clearly identified and is working on its actual bottleneck.

The correct order, in my view now, is people, quality, process. Take care of your people first. Deliver a genuinely quality product second. Refine the process behind it third, once the first two are solid.

Climbing With Your Feet

There is an image that captures this well, and it comes directly from rock climbing. Watch a genuinely skilled climber, the kind documented in the film Free Solo about an ascent of El Capitan, and you will notice something specific about their technique. Handwork matters, and footwork comes first. A climbing coach will tell you directly, climb with your feet, and make sure you have a genuine foothold before you commit any further weight to it.

Applied to how an organization actually builds itself, climbing with your feet means stabilizing your people practices first. That is exactly why books built around the idea of getting the right people in place before deciding what to do next, first who, then what, put the priorities in the correct order. Build a sustainable, scalable system starting with your people, and everything built on top of that foundation actually holds.

Two Footholds Before You Climb Any Further

Here is how that translates into a genuine operating sequence. The first foothold is people, taking real care of the humans doing the work. The second foothold is quality, meaning a genuinely frictionless product that people actually want to buy or work with. Only once both of those footholds are secure should a team start climbing with process and its ability to scale.

Watch for these signs an organization has skipped a foothold and is climbing on an unstable base:

  • Cost cutting or efficiency initiatives introduced before quality has genuinely been secured.
  • Process refinement discussed constantly while genuine care for the people doing the work gets treated as secondary.
  • A company’s public messaging about quality that does not match what customers or employees actually experience.

Why This Matters More Than a Slogan

There is a story I recall hearing about Steve Jobs observing that Japanese companies do not mention quality in their commercials, because quality is simply assumed, a given, built into the culture through the influence W. Edwards Deming had on Japanese manufacturing. Quality is not a marketing message there. It is the baseline expectation.

That distinction matters more than it might seem at first. A company that has to advertise its own quality is often signaling, whether it means to or not, that quality is not simply assumed by its own customers. The strongest possible position is one where quality never needs to be the pitch, because it has already been proven consistently enough that customers take it for granted.

That contrast becomes obvious the moment you look at how differently two real companies have handled this same principle.

What Happens When a Company Claims Quality Without Living It

I recently came across reporting suggesting that a well known fast food chain has faced real quality erosion after prioritizing cost cutting and efficiency over its own stated food standards, reportedly including a shift from fresh, whole leaf lettuce to a cheaper shredded version, smaller or lighter portions on certain menu items, thinner patties, and rising prices alongside declining value. The reporting also mentioned slower drive through times, inconsistent food preparation, and customer frustration tied to newer automated ordering technology.

I want to be honest that I have not independently verified every specific detail of that reporting myself, and I would encourage anyone interested to check the current facts directly rather than relying solely on my secondhand summary here. What I can say confidently is the underlying pattern, whether or not every detail above is precisely accurate in this particular case, is exactly what happens when a company’s actual practice drifts away from a quality message it still puts on its own signage. You cannot claim to produce a quality product and genuinely care about people while quietly cutting corners on both. Eventually the gap between the message and the reality becomes visible to everyone.

What Happens When a Company Actually Lives It

Compare that against a company whose slogan is built directly on a real operating practice rather than aspiration alone. One well known burger chain’s tagline about quality you can taste comes from a strict rule to use only fresh, never frozen ingredients. They keep only about two days of stock on hand for their products, and if it is not used within that window, it genuinely gets discarded rather than pushed out to customers past its freshness. I have seen this practice firsthand, and it reflects a company actually climbing with its feet, protecting quality even when it costs more to do so.

Why You Cannot Skip Straight to Process

None of this works if a team tries to jump straight to process optimization before genuinely securing the first two footholds. Focusing on cost cutting or efficiency prematurely, before people and quality are genuinely stable, is exactly how an organization loses its way, even while its marketing continues to say all the right things.

The theory of constraints reinforces this same order. Identify the actual bottleneck, and focus your energy there first, rather than optimizing a process broadly before you know where the real constraint sits. Refining process before quality is secured is optimizing in the wrong place, no matter how efficient it looks on paper in the short term.

Applying This to Your Own Organization

None of this requires a dramatic overhaul to start applying. It requires reordering the questions your team asks before making a decision. Is this genuinely good for our people. Will this deliver a frictionless, genuinely quality product. Only after both of those are answered honestly does the question of process efficiency belong in the conversation.

If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your teams build genuine stability around people and quality first, so process improvement actually strengthens a solid foundation instead of quietly papering over cracks in it.

So here is the challenge. Look at your own organization’s recent decisions and ask honestly which foothold, people or quality, got skipped in favor of a process or cost efficiency improvement made too early. That gap is exactly where your own climb has become unstable, whether or not it has become visible to your customers yet.

Jason Schroeder said it plainly: “We climb with our feet.” Secure your people and your quality first, and the process you build on top of that foundation will actually hold.

On we go.

FAQ

Why does process rank third rather than second in this corrected priority order?

Because process exists specifically to support and protect quality, rather than standing as an equally weighted priority alongside it. A team can tolerate some short term inefficiency in service of protecting genuine quality, but sacrificing quality in service of a more efficient process undermines the actual purpose process is supposed to serve in the first place.

How does the theory of constraints connect to prioritizing quality before process refinement?

The theory of constraints argues that improving anything other than the actual bottleneck rarely improves overall system performance. Refining process broadly before quality is genuinely secured risks optimizing parts of the system that were never the real constraint, while the genuine priority, protecting a quality product for the people who depend on it, goes unaddressed.

Why does the article compare two specific fast food companies to illustrate this principle?

Because the contrast between a company whose quality messaging has reportedly drifted from its actual practice and one whose slogan is built directly on a verifiable operating rule makes the underlying principle concrete rather than abstract. The specific claims about any individual company should be verified independently, but the broader pattern, that customers eventually notice when practice does not match messaging, holds regardless of the exact details in any single case.

What does “climbing with your feet” actually mean when applied to a real organization?

It means stabilizing genuine care for people and a real commitment to quality as the foundation before pursuing process efficiency or scaling. The metaphor comes directly from rock climbing, where a climber secures a solid foothold with their feet before committing further weight, rather than reaching upward with their hands before the foundation beneath them is actually stable.

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

More Detail Isn’t Always Better

Posted on by Team Jason Schroeder
Read 9 min

Why Wanting More Detail in Your Schedule Is Usually an Escape

Here’s the deal. A company we support, genuinely committed to Takt and Lean, has one superintendent who has fought the transition every step of the way. Grumpy, closed off, resistant to Takt, resistant to pull planning, resistant to nearly all of it. I actually think that resistance is fine, even healthy, as long as the rest of the team is genuinely on board and moving forward, which in this case they are. What is worth examining is the specific reason he gave for rejecting it, because that reason reveals something important about how a lot of superintendents think about scheduling.

Why He Rejected the Takt Schedule

His stated complaint was simple. I do not like the Takt schedule. I just need the detail. On the surface that sounds like a reasonable preference. It is not accurate, and here is why.

A properly built Takt plan actually contains more detail and more logic than a traditional CPM schedule, just presented far more simply. The real issue was not a lack of detail at all. It was an inability to adjust from a time by deliverable mental model, the format CPM has trained an entire generation of builders to think in, over to a time by location format, which is structurally different and genuinely better, but does require a real mental shift to use comfortably.

Detail Is an Escape

Here is the core idea worth sitting with. Wanting more detail is often an escape. It is an excuse. It is, at its root, an insecurity, and understanding why changes how you should respond the next time someone demands more detail before they will trust a plan.

There is a well known saying, if I had more time, I would have written a shorter letter. I genuinely love that line, because it captures something true about sophistication. Writing something simple, clear, and elegant actually requires more skill than writing something long and dense, not less. The same principle applies directly to scheduling. Genuine sophistication in planning means being able to express a schedule in time by location format at a high level, with the real detail inherent in how the plan is packaged, rather than needing every granular item spelled out visually before anyone can trust it.

Detail Belongs on a Rolling Wave, Not All at Once

There is a second piece to this worth understanding clearly. Detail is supposed to increase as you actually approach a specific phase. That is what pull planning and detailed work packaging are for, adding real, trade informed detail in a rolling wave as each phase gets closer, rather than demanding exhaustive detail for the entire project up front.

People who insist on heavy detail early, without trade input, are usually doing something different than genuine planning. They are letting their own anxiety run unchecked, relying on detail that has not actually been verified as accurate, simply because generating it makes them feel less worried in the moment.

Watch for these signs that a request for more detail is really an anxiety response rather than genuine planning discipline:

  • Detail requested far in advance of the phase it actually applies to, with no trade partner input yet available.
  • Detail so granular that the rest of the team can no longer actually read or use the plan.
  • Detail treated as proof a schedule is correct, without any real verification that it is achievable.

Why More Detail Does Not Actually Solve Anything

Here is the honest problem with piling on detail early. Even once you have it, so what. Having more detail does not mean the plan is right. It does not mean it can actually happen. It just means somebody got the anxiety out of their own head, and that relief does not help anyone else, because the rest of the team usually cannot even parse a schedule buried in that much granularity.

It gets worse from there. Even if that excessive detail happened to be accurate, it still would not matter, because trades have not actually bought into it yet. A schedule only becomes real once it has been verified as genuinely achievable by the people executing it, and no amount of detail generated in isolation, without trade input, can substitute for that verification.

There are really three separate failure points stacked on top of each other here, and each one alone is enough to undermine the value of that extra detail. It might not be accurate. Even if accurate, the rest of the team often cannot read a schedule buried in that much granularity. And even if both accurate and readable, it still has not been verified as achievable by the trades who would actually have to execute it. Detail solves none of those three problems on its own.

Why the Most Detail Obsessed Supers Are Often the Weakest

I want to say something direct here, based on real experience. Some of the least effective superintendents I have worked with were the ones constantly demanding more and more detail. That pattern usually traces back to a specific gap, not a character flaw.

It looks like this. I do not know how to orchestrate this at a high level in rolling waves. I do not know how to coordinate effectively. I do not know how to work collaboratively with trade partners to build genuine buy-in. I do not have a real system installed. So instead, detail gets piled on top of detail, over and over, because generating detail feels productive even when it is not actually solving the underlying gap. Detail becomes the escape hatch for a missing skill set, not evidence of genuine competence.

Where Detail Actually Belongs

None of this means detail itself is bad. If you genuinely need more detail, put it where it actually belongs. Detail it out visually. Detail it in drawings. Detail it on your logistics maps. Those are the places granular information genuinely helps, because they are built to hold that level of specificity without burying the overall plan.

What you should not do is dump a mountain of unverified, trade uninformed detail directly into the schedule itself, because that does not make the schedule more accurate. It just makes it harder for anyone else to actually read and trust.

Building Genuine Confidence Instead of Chasing Detail

None of this is really about one grumpy superintendent. It is about recognizing a pattern that shows up across this industry constantly, mistaking volume of detail for genuine planning competence.

If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your teams build the real skills that make a high level, time by location plan genuinely trustworthy, rolling wave detailing, collaborative trade buy-in, and real coordination discipline, so nobody on your team needs to escape into unnecessary detail to feel secure about a schedule.

So here is the challenge. The next time someone on your team insists a plan needs more detail before they will trust it, ask a direct follow-up question. Is this detail actually verified with trade input, or is it simply detail for its own sake? That single question tends to reveal whether the request is genuine planning discipline or an anxiety response dressed up as one.

Jason Schroeder said it plainly: “Detail does not mean that it’s right, and it does not mean that it can happen.” Build genuine confidence in your plan instead of chasing detail as a substitute for it.

On we go.

FAQ

Does a Takt plan in time by location format actually contain less detail than a traditional CPM schedule?

No, and this is a common misconception. A well built Takt plan, particularly using dedicated software, typically contains more logic and more genuine detail than a traditional CPM schedule. The difference is that Takt presents that detail at a higher, more readable level, rather than spreading it across an activity list most people cannot mentally parse once it grows past a few hundred items.

Why should detail increase in a rolling wave rather than being fully specified at the start of a project?

Because detail specified too early, before the relevant trade partners have had a chance to provide real input, is essentially an unverified guess, regardless of how granular it looks. Adding detail through pull planning as each phase actually approaches ensures that detail reflects genuine trade input and real conditions, rather than one person’s early assumptions about how the work will actually unfold.

Why does the article connect excessive early detail to insecurity rather than diligence?

Because detail generated without trade input or verification does not actually make a plan more accurate, it simply relieves the discomfort of uncertainty for the person creating it. When that detail cannot be used or trusted by the rest of the team, and has not been confirmed as achievable, it functions more as a coping mechanism for anxiety about the unknown than a genuine planning tool.

If detail does not belong directly in the schedule, where should it actually go?

Detail belongs in supporting documents built to hold it well, such as detailed drawings, visual work packages, and logistics maps. These formats are designed to carry granular information without burying the overall plan, which is exactly what happens when that same level of detail gets forced directly into a schedule meant to communicate flow and sequence at a readable level.

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

Data, Risk, and Authority

Posted on by Team Jason Schroeder
Read 9 min

Data, Risk, and Authority: How to Actually Resolve a Disagreement in Pre-Construction

Here’s the deal. Somebody recently described a real situation to me. A superintendent had gone through a fresh eyes review during pre-construction, the kind of session where an outside team looks at a plan with genuinely fresh perspective before construction starts. The review team came across as forceful and dismissive of his ideas, wanted things done a different way, and the whole experience left him nervous rather than genuinely collaborative. His question was simple and fair. How much authority should the fresh eyes team actually have over the superintendent when they disagree?

That question deserves a real answer, not a vague appeal to teamwork. Here is the actual hierarchy I use.

If We Have Data, Use the Data

There is a line I genuinely love, even though I recognize it can sound a little sharp if said the wrong way. If we have data, let’s go with data. If all we have is opinions, let’s go with mine. Said with the right tone, that is not an authoritarian power move. It is an honest statement about what should actually break a tie, and data comes first, before anyone’s personal preference, mine included.

In practice, that means when two people disagree during pre-construction, the first move is never simply picking whoever argues more forcefully. It is asking whether a historical reference class exists, whether a real what-if scenario can be modeled, or whether actual research can settle the question. If the data exists, let it decide, regardless of whose idea it happens to support.

This step alone resolves more disagreements than people expect, precisely because it changes what the conversation is actually about. Instead of two people defending their own instincts, the room shifts toward jointly investigating what the evidence actually shows, which tends to defuse the personal tension that makes disagreements feel adversarial in the first place.

If It Is Genuinely Risky, Take the Safer Path

When no clear data exists to settle a disagreement, the next question is risk. If one option carries genuine potential to put the business, the company, or actual people at real risk, that risk should decide the outcome, again regardless of personal preference. A safer option beats a slightly more convenient one every time real risk is on the table.

Watch for these signs a disagreement is actually being resolved by force of personality rather than this hierarchy:

  • A decision made simply because one person pushed harder or louder in the room.
  • No attempt to check historical data or model a what-if scenario before settling an argument.
  • Risk to the business or to people treated as a secondary concern rather than a genuine deciding factor.

Past Data and Risk, Default to the Superintendent and PM

Once you have genuinely checked for data and ruled out significant risk, and a real disagreement still remains, my honest default leans toward letting the superintendent and project manager make the call. That is not because their opinion outranks everyone else’s by default. It is because somebody has to make the decision, and the people accountable for actually running the project are a reasonable default when the choice is otherwise a genuine toss-up.

Notice that this is explicitly a default, not a rule applied automatically in every case. The next distinction below explains exactly when that default should shift toward the broader team instead, which is where this hierarchy actually gets interesting rather than simply restating a standard chain of command.

The What Versus the How

Here is a distinction that changes how this actually plays out in practice, and it comes up constantly in my own thinking. What we are doing on a project is fundamentally a company leadership decision. How we are doing it, the actual means and methods, belongs mainly to the people with boots on the ground, the trade partners actually executing the work.

That distinction matters directly for the fresh eyes scenario that started this whole conversation. If a disagreement is genuinely about means and methods, with no real data available and no significant risk difference between the two approaches, meaning it is close to a coin flip either way, my instinct leans toward letting the team closest to that decision make the call themselves, rather than the superintendent or PM overriding it by default.

Why Letting the Team Decide Actually Matters

That preference is not just about being nice or building consensus for its own sake. It connects directly to a real leadership principle worth taking seriously. Jocko Willink’s laws of combat, built around the extreme ownership framework, make a specific point. If a team made the plan themselves, they genuinely own it, and they can be held properly accountable for how it plays out.

That accountability only holds up if the team actually had real input into the decision in the first place. Override a team’s means and methods call by default, even when data and risk genuinely do not favor either side, and you quietly remove their ownership over the outcome. Then, when something does not go perfectly, holding them fully accountable for a decision they never truly made becomes much harder to justify.

Applying This Back to the Fresh Eyes Scenario

Go back to the original situation. A superintendent felt steamrolled during a fresh eyes review, not genuinely collaborated with. Run that disagreement through this hierarchy honestly, and the fix becomes clear. Start by asking whether real data actually existed to settle whatever the disagreement was about. If it did, that should have decided the outcome regardless of who felt strongly about it. If no data existed, ask whether real risk was genuinely at stake. If it was not, and the disagreement was really about means and methods with the two options roughly equivalent, the superintendent’s team, the people who would actually own executing the plan, deserved real weight in that decision, not a forceful override from reviewers who would not be the ones held accountable for how it went.

A fresh eyes review is genuinely valuable when it surfaces real data or real risk nobody had considered yet. It becomes counterproductive the moment it turns into simply overriding the field team’s judgment on a genuine toss-up decision, because that erodes the very ownership that makes accountability meaningful later.

Building This Hierarchy Into Your Own Team

None of this requires a formal policy document to implement. It requires a shared, genuinely understood order of operations that everyone in a room actually applies consistently, rather than defaulting to whoever argues the loudest or holds the most senior title.

If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your teams build genuine decision making discipline around data, risk, and authority, so pre-construction reviews and fresh eyes sessions actually build ownership instead of quietly eroding it.

So here is the challenge. The next time a genuine disagreement comes up in pre-construction or during a fresh eyes review, walk through this hierarchy out loud with the room. Is there real data? Is there real risk? And if neither settles it, is this a means and methods question that genuinely belongs to the people who will own executing it? That simple sequence turns a personality contest into an actual decision process everyone can respect afterward.

Jason Schroeder said it plainly: “If we have data, let’s go with data. If all we have is opinions, let’s go with mine.” Said with the right intent, that is not arrogance. It is a genuine commitment to letting evidence, not force of personality, decide.

On we go.

FAQ

Why should data outrank even a senior leader’s strong opinion when resolving a disagreement?

Because personal conviction, no matter how confident, is not the same thing as verified evidence, and a historical reference class or a modeled what-if scenario reflects reality more reliably than anyone’s gut feeling, regardless of their seniority. Prioritizing data over opinion protects a project from decisions driven by whoever argues most forcefully rather than what actually tends to work.

What is the actual difference between a “what” decision and a “how” decision?

A “what” decision covers the overall direction or goal a project is working toward, which generally belongs to company leadership. A “how” decision covers the specific means and methods used to accomplish that goal, which generally belongs to the people actually doing the work, since they carry the practical knowledge and the eventual accountability for how well that method performs.

Why does letting a team make its own means and methods decision matter for accountability later?

Because genuine accountability depends on genuine ownership, and a team that never actually got to make a real decision cannot fairly be held fully responsible for how that decision turned out. Letting the team closest to the work make a genuine toss-up call preserves their ownership over the outcome, which is exactly what makes holding them accountable later fair and meaningful.

When does a fresh eyes review in pre-construction become counterproductive?

It becomes counterproductive when it shifts from genuinely surfacing new data or risk the original team had not considered into simply overriding the field team’s judgment on a decision that was really a toss-up. A fresh eyes review adds real value when it changes the actual inputs to a decision. It causes harm when it just replaces one opinion with another more forceful one.

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