October 2026 - Page 13 of 14 - Elevate Constructionist

Massive and Small Problems on the Job Site.

Posted on October 2, 2026October 2, 2026 by Team Jason Schroeder

Read 8 min

Massive and Small Problems, and Why the Order You Solve Them In Matters

Here’s the deal. During a recent field walk, I watched a genuinely strong team handle big, massive roadblocks really well, while quietly letting the small ones slip through unaddressed. That observation, paired with a deeper conversation I had afterward about how waste actually gets eliminated, revealed something worth sharing directly.

Why Small Problems Get Left Behind

I generally recommend visual boards on the wall showing zone maps and logistics plans, where trade partners place red magnets directly on the board to flag real problems. Those magnets go up before the meeting even starts, specifically so the meeting itself is not wasted on the motion of physically posting each issue. Once the meeting begins, the team works through the board magnet by magnet, spending real time actually removing roadblocks rather than just discussing them.

Some magnets represent genuinely small issues, a stack of plywood sitting in someone’s way, for example. A foreman can simply agree to handle it on the spot, and the magnet comes right off. Other magnets represent something far more serious, an RFI with a hard deadline that could genuinely stop work in two days if left unresolved. That kind of issue needs real escalation, reaching the project engineer, the project manager, and the designers directly, and it either stays on the board or gets transferred into a dedicated roadblock log for ongoing tracking.

What I noticed on this particular project was a team focused almost entirely on that roadblock log, the bigger items. I had to ask directly, how are the smaller issues actually being coordinated? The honest answer was that they were not being coordinated at all. Small problems were simply left out in the field for individual workers to notice, walk around, and figure out on their own time, wasting real effort simply because nobody addressed them in the meeting itself.

We genuinely need three distinct levels of roadblock tracking working together.

Magnet level roadblocks, small enough to resolve on the spot during the meeting itself, with the magnet coming down immediately once handled.
Roadblock log level items, serious enough to need ongoing tracking across multiple meetings until fully resolved.
Escalated items significant enough to require attention at a genuine owner, architect, and contractor meeting, reaching well beyond the immediate project team.

We cannot ever only cover the big items, and we cannot ever only cover the small ones either. Everything needs a real place on the board, attacked visually every single day. Done consistently, that list should never grow large enough to become genuinely unmanageable.

Why a Narrow Focus on Waste Alone Can Backfire

I was talking recently with someone from a production department who described their entire focus as eliminating waste. That reminded me of a pit crew analogy I use constantly. If a pit crew looks idle while a car is out on the track, someone focused purely on spotting waste might conclude that crew is doing nothing and should be eliminated, or kept busy with something else in the meantime. Then the car actually pulls in for service, and if that same crew is now distracted doing something else entirely, it takes too long to get the car back out, and the race gets lost because of it.

This is exactly the trap of looking at any single concept in isolation. You cannot build your entire approach around waste alone, or around theory of constraints alone, or around work in progress alone, or around big problems versus small ones. Everything genuinely connects as one single system, and how you categorize a problem should never get in the way of your actual ability to solve it.

Why Overburden, Unevenness, and Waste Form a Genuine Sequence

Here is something genuinely remarkable I want to share. Removing overburden first, unevenness second, and waste third is not simply a priority ranking. It is an actual procedural sequence, where each step genuinely enables the next one to happen.

Addressing overburden means reducing work in progress until the actual workload sits genuinely within people’s real capacity. This also does something else important, it lets real problems finally become visible that excess work in progress was previously hiding.
Once that visibility exists, unevenness becomes genuinely identifiable, specifically the stops and restarts that typically happen right at a real bottleneck. This is exactly where Eliyahu Goldratt’s theory of constraints thinking becomes useful, helping pinpoint precisely where that bottleneck actually sits.
Once the actual bottleneck location is clear, you can finally go to work eliminating waste specifically at that bottleneck, using the eight, or sometimes nine, wastes framework to guide exactly where to focus.

Notice how beautifully these three steps build on each other rather than functioning as three separate, unrelated priorities. Reducing work in progress reveals the bottleneck. Identifying the bottleneck tells you precisely where to eliminate waste. None of these steps makes full sense without the one that came before it.

Skipping straight to waste elimination without doing this groundwork first tends to scatter effort across the entire project, removing small inefficiencies everywhere while the one constraint actually limiting overall output stays completely untouched. The sequence exists precisely to prevent that kind of unfocused, well intentioned effort.

What I Would Actually Do Running a Project

If I were running a project with this in mind, I would write down every problem touching overburden, unevenness, or waste as it surfaces. I would align work in progress first, until it is genuinely manageable. Only then would I map out where the bottlenecks causing unevenness actually sit. From there, I would subordinate everything else to that bottleneck specifically, working to increase its capacity or remove waste directly at that one critical point.

Why Both Lessons Point to the Same Underlying Truth

Covering only big roadblocks while ignoring small ones is a form of the exact same myopia as chasing waste without first understanding capacity and bottlenecks. In both cases, a narrow focus on one category, scale, or concept quietly hides real problems sitting just outside that narrow view.

Building This Integrated Thinking Into Your Own Project

None of this requires choosing between tracking big problems and small ones, or between eliminating waste and understanding theory of constraints. It requires holding all of it together as one connected system, addressing capacity first, locating the real bottleneck second, and eliminating waste specifically where it actually matters third.

If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your teams build genuinely integrated problem solving, covering every scale of roadblock and following the real sequence that actually makes waste elimination effective, rather than tackling each concept in isolation.

So here is the challenge. Look at your own current roadblock board and ask honestly whether small problems are genuinely being addressed alongside the big ones, or quietly left for individual workers to sort out on their own. Then ask whether your team is reducing work in progress before hunting for waste, or jumping straight to waste elimination without first locating the real bottleneck underneath it.

Jason Schroeder said it plainly: “Remove overburden first, unevenness second, and then waste third.” Follow that real sequence, and cover every scale of problem at once, and watch how much more effectively your team actually solves what is genuinely in front of it.

On we go.

FAQ

Why does the article warn against a project team focusing only on the roadblock log and ignoring smaller, magnet level problems?

Because smaller problems, left unaddressed in a formal meeting, do not disappear, they simply get pushed onto individual workers who have to notice, navigate around, and resolve them on their own time instead. Tracking only the bigger items creates a false sense of thorough problem solving while real, smaller inefficiencies continue accumulating unaddressed in the field.

Why might someone mistakenly identify an idle pit crew as waste worth eliminating?

Because a narrow focus on visible busyness, without understanding the crew’s actual purpose, makes genuine readiness look identical to unnecessary idleness from the outside. The crew’s real value only becomes visible the moment a car actually needs service, which a surface level search for waste completely misses if it judges activity only by what is happening right now rather than what the role is actually there to provide.

Why does reducing work in progress specifically help reveal where a real bottleneck is located?

Because excess work in progress tends to mask genuine capacity problems, spreading effort so thin across many tasks that no single constraint stands out clearly. Once work in progress is reduced to a genuinely manageable level, stops and restarts become visible exactly where they are actually happening, typically right at the real bottleneck limiting the entire system.

If you want to learn more we have:

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

Discover Jason’s Expertise:

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

The Waiting You Pay For and the Waiting You Don’t.

Posted on October 2, 2026October 23, 2026 by Team Jason Schroeder

Read 9 min

The Waiting You Pay For, and the Waiting You Do Not

Here’s the deal. There are two kinds of waiting on a construction project that look remarkably similar from a distance and carry completely different real costs. Learning to tell them apart changes how you should actually respond when you see a zone sitting idle or a worker not fully occupied.

What Triggers the Expensive Kind of Waiting

The waiting you pay for usually starts with someone in authority insisting on something that sounds reasonable on the surface. I want every worker busy. I want extra crews. I want overtime. I want every single zone being worked on at all times. That demand is exactly what creates the expensive version of waiting.

Waiting, in this context, means people standing around for information, for a roadblock to clear, for materials that have not arrived. It means treasure hunts, searching for something that should have been staged properly. It means busywork invented simply to look occupied, or someone doing planning work that belonged to a project engineer instead.

A colleague once came back from a real Last Planner training with a useful way to frame this. It is either workers waiting on work, or work waiting on workers. Workers tend to wait constantly in construction, which is different from manufacturing, and one of those two situations is considerably worse than the other.

Why Niklas Modig’s Framework Is Missing a Third Category

Niklas Modig writes about resource efficiency and flow efficiency, and his work is excellent. Because he is not writing specifically about construction, he never fully pulls apart both extremes and explains the real middle ground between them. There is actually a third concept worth naming directly, work efficiency, sitting as its own distinct failure mode alongside resource efficiency.

Here is how these three differ from each other.

Resource efficiency optimizes each individual piece of equipment or each individual trade on its own, which can quietly sub-optimize the overall project and hurt flow.
Work efficiency means keeping every single zone worked on constantly, so each area looks efficient within itself, which also ends up hurting overall workflow.
Flow efficiency sits in the middle, matching the actual pace and capability of your resources with the demand of the client, balancing supply and demand rather than optimizing either extreme in isolation.

A trade that wants the entire building to themselves, free to stage however they like because it feels maximally efficient for them individually, is actually detrimental to overall production. Insisting that every single zone must be worked on and every person must stay busy at all times is just as false, and it hurts people in the process.

Why Adding More Workers Does Not Automatically Create More Speed

When everyone tries to work at full efficiency inside every zone simultaneously, aggregated across an entire project, you get real trade stacking and trade burdening. You end up throwing large numbers of people at work that may not even be ready for them yet.

Here is something I say constantly in trainings and conferences. You could add ten additional trained people to every single crew on a site and not go any faster, if the areas are not ready, if the overall system is not in rhythm, and if the materials or information required simply are not there yet. More labor thrown at an unready system does not create speed. It mostly creates cost.

If you are operating inside a real Takt production system, some zones will always, at any given moment, not be actively worked on. Some people will not be at one hundred percent capacity at every moment either. That is completely normal. The moment an owner notices this and demands that something be done about it without understanding why, that is exactly the moment a project tips into the expensive version of waiting.

Telling the Two Kinds of Waiting Apart

The waiting you pay for looks like this. Work is not made ready, and in response, additional crews get brought in, trades get stacked or burdened, extra workers show up, overtime gets authorized, and the whole team shifts into rushing, pushing, and panicking. That version of waiting is expensive.

The waiting you do not pay for looks completely different. A zone might sit waiting briefly for a crew because of a small natural gap, or because trades are moving at slightly different paces. A crew might even get intentionally reduced in size to match the pace of everyone else around them. Nobody is working at full individual efficiency in this scenario, and nobody is actually paying for it either, because the overall production plan still finishes at the soonest reasonable point, without panic, without additional overtime costs, without wasted treasure hunts, and without idle labor nobody can put to use.

Watch for these specific signs you are experiencing the expensive version of waiting rather than the harmless kind.

Extra crews or additional labor brought in specifically because a zone sat briefly idle, rather than because the actual schedule required it.
Overtime, time and a half, or double time costs appearing directly in response to pressure to keep every zone constantly occupied.
A visible shift into rushing, pushing, or panicking triggered by an owner or executive noticing an empty zone without understanding why it is temporarily empty.

What I Am Not Actually Saying Here

I want to be clear about something. I am not saying work everyone at full resource efficiency, since that creates real gaps elsewhere in the schedule. I am also not saying focus purely on work efficiency, keeping every zone occupied at all times. What I am actually recommending is a balanced plan between those two extremes, landing on real flow efficiency.

If every trade simply does whatever is best for itself individually, that is sub-optimization, and it is harmful. If an owner insists there should never be an empty zone, demands overtime, and does not care about trade stacking or trade burdening, that is equally harmful. The intelligent, educated approach keeps everyone moving in real flow, optimized for the shortest overall throughput time and the highest quality, while still respecting the people doing the work. That balance is the only way to actually win.

Building This Understanding Into Your Own Project

None of this requires choosing one extreme over the other. It requires understanding that some amount of idle time, in a zone or in an individual worker, is normal and healthy inside a well-run Takt system, and resisting the instinct to throw expensive resources at something that does not actually need fixing.

If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your teams distinguish between the waiting worth paying to eliminate and the waiting that simply reflects a healthy, well balanced production system.

So here is the challenge. The next time you notice an idle zone or an underutilized worker, pause before reacting. Ask honestly whether that gap reflects a real roadblock worth addressing, or a normal, healthy rhythm you would actually be paying real money to eliminate unnecessarily.

Jason Schroeder said it plainly: “Lean is about finishing a project or a phase at the shortest duration, highest level of quality, that takes care of our people, at the lowest overall total project cost.” Learn to tell these two kinds of waiting apart, and you protect every single part of that definition at once.

On we go.

FAQ

Why is Niklas Modig’s resource efficiency and flow efficiency framework missing something important for construction?

Because Modig’s work was not written specifically about construction, and it only fully explains one extreme, resource efficiency, alongside the balanced middle ground of flow efficiency. I argue that construction needs a third category named directly, work efficiency, to describe the opposite extreme of insisting every zone stay constantly occupied, which causes its own distinct set of problems.

Why would adding ten extra trained workers to every crew on a site not necessarily make the project move faster?

Because speed in a Takt system depends on zones being ready, the overall system being in rhythm, and materials and information actually being available when needed, not simply on how many people are physically present. Extra labor thrown at an unready system adds real cost without addressing the actual constraint slowing the project down.

What is the practical difference between a zone sitting idle due to “waiting you pay for” versus “waiting you don’t pay for”?

The expensive version involves a reactive response, extra crews, overtime, trade stacking, rushing and panicking, triggered by the idle zone itself. The non-expensive version involves a zone or worker not at full utilization simply because trades move at slightly different paces, with the overall schedule still finishing at the soonest reasonable point without any of those extra costs being incurred.

Why shouldn’t an owner react negatively to seeing an empty zone or an idle worker?

Because some amount of idle time is a completely normal, expected feature of a well-functioning Takt production system, not necessarily a sign of inefficiency worth correcting. An owner who pushes a team to eliminate all idle time without understanding this risks triggering the expensive form of waiting, since that pressure typically gets answered with extra crews, overtime, and rushed decision-making rather than improvement.

If you want to learn more we have:

Discover Jason’s Expertise:

Work Planning For Superintendents: How To Create Flow In The Field?

Posted on October 2, 2026October 21, 2026 by Team Jason Schroeder

Read 9 min

Busyness Is Not Production, Busyness Is Waste

Here’s the deal. When it comes to work planning for superintendents, the job is not to keep everyone busy. It is to keep the actual work flowing. Those two things sound similar and are opposite in practice, and understanding the difference changes almost everything about how work should actually get packaged and sequenced in the field.

Short answer: A superintendent’s job is to keep the work flowing, not to keep everyone busy. Break the project into phases, break each phase into zones leveled by work density rather than equal size, flow trades through them in sequence with leveled crews, and watch for trade stacking, trade burdening and the handoffs between zones.

Why Keeping People Busy Is Not the Same as Keeping Them Productive

A superintendent who believes their job is keeping everyone busy will constantly move people around, shift crews here and there, and fill gaps with activity. The problem is that most of that activity is waste, even though it looks like productive motion from a distance.

Here is exactly what that looks like in practice.

Moving someone from one task to another simply to keep them occupied, with no connection to the actual flow of work.
Having a crew wait at a hoist and then sending them somewhere else temporarily in the meantime, rather than solving the actual constraint causing the wait.
Reworking something that should have been done correctly the first time, which counts as activity but represents lost time and effort.

Busy, busy, busy. Waste, waste, waste. That is the honest reality behind a lot of what passes for hard work on a construction site. The actual job of a superintendent is keeping everything flowing, not simply keeping everyone visibly in motion.

This distinction matters because visible busyness is easy to measure, and real flow is harder to see at a glance. A superintendent walking a site can notice immediately whether people look busy. Noticing whether the actual work is flowing well requires a completely different kind of attention, one focused on whether zones are closing out cleanly and trades are moving through in sequence, not just whether everyone appears occupied.

The Simple Framework That Actually Creates Flow

Break the project into phases first. A phase is a geographical area with a real start and finish, containing its own unique zones and its own unique trades running through it. Site work, foundations, structure, rough-in, finishes, exterior work, the roof, elevators, and stairs are all phases worth thinking of this way.

Once phases are defined, break each one into zones. Even doing this imperfectly puts a project far ahead of not doing it at all. A client in New Mexico recently told me exactly what changed once they adopted this approach. They started planning, building, and finishing one zone completely, then closing it down before moving on, rather than spreading effort across the entire site trying to finish a long list of partially completed work everywhere at once.

Why Smaller Zones Move Faster

Using a real Takt time calculator, the rule of thumb is simple. Make zones as small as they can be while still leaving enough spatial room to actually work and fit your trade partners comfortably. Smaller zones move faster. That principle holds up consistently in practice.

Why Leveling by Work Density Matters More Than Equal Size

Here is where a lot of teams, myself included at an earlier point, get this wrong. I used to recommend a simple rule of thumb, something like equal ten-foot increments across the board. That approach misses something important.

Picture a building zoned purely by equal square footage, where one particular zone happens to contain an elevator bank and a cluster of bathrooms: denser, more complex work than the zones around it. Equal sizing in that case produces an easy zone, another easy zone, then a hard zone, then easy again, creating a predictable bottleneck exactly where the dense work sits.

The same problem shows up in civil work. Divide a water line into equal segments, say a flat one hundred eighty linear feet each, and ignore that one particular stretch has a cluster of utility services crossing through it. You get easy, easy, hard, easy, and the project bogs down right at that dense segment regardless of how evenly the linear footage was actually divided.

The real fix is leveling zones, stations, or prefabricated sections by work density, not by equal physical size. That might mean one zone ends up at two hundred linear feet while another needs two hundred eighty, simply because the actual work inside each one is not evenly distributed.

Flowing Trades and Leveling Crews

Once phases and zones are properly leveled, flow your trades through them in sequence, trade one, two, three, four, five, moving beautifully through each zone in turn. Level the crew sizes and durations too. If crew one takes two days, crew two takes ten days, and crew three takes two days, that mismatch is obvious. Crew two’s work needs to be broken down into smaller two-day segments so every trade moves through the sequence at the same consistent rhythm.

What to Actively Avoid as Trades Move Through the Sequence

Two specific problems deserve direct attention as trades flow through your zones.

Trade stacking, where too many trades end up working unsafely and unnaturally crowded into the same area at the same time.
Trade burdening, asking a single trade to be spread across more areas simultaneously than is possible for them to cover well.
Unmonitored handoffs, the critical moments when one trade moves from one zone into the next, which deserve active tracking throughout your production plan rather than being left to happen automatically.

That is the entire framework for work packaging and creating real flow, described in the simplest language possible. None of it requires specialized software or an advanced degree in scheduling theory, just discipline in applying each step consistently.

Why This Matters Most on the Largest, Most Complex Projects

One of the most common requests we receive involves data center projects, helping build a proposal, creating a schedule from scratch, recovering and rebuilding a struggling schedule, or helping a data center contractor actually run their project well. On mega projects like these, getting phases and zones right, especially alongside advanced work packaging, matters enormously. Once that leveling is done correctly, the entire project starts to flow beautifully. The job of a superintendent, at any scale, is exactly that. Flow beautifully.

Building This Framework Into Your Own Project

None of this requires complicated software or an elaborate new system. It requires breaking your project into phases and zones, leveling them by actual work density rather than equal size, flowing your trades through them in sequence, and watching closely for trade stacking, trade burdening, and the handoffs between zones.

If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your teams build exactly this kind of leveled, flowing work packaging, whether that means a standard project or a complex mega project like a data center.

Want your team trained on this? See our Last Planner® System and Takt training.

So here is the challenge. Look at your own current zone breakdown and ask honestly whether it was leveled by actual work density or simply by equal size. If you find one zone that is clearly denser than the others around it, that is exactly where your next bottleneck is quietly waiting to happen.

Bottom line: Busyness is not production. Busyness is waste. Stop measuring success by how busy everyone looks, and start measuring it by how well the work actually flows.

On we go.

FAQ

Why is keeping workers busy potentially harmful rather than simply neutral?

Because activity that looks productive, like moving crews around or having them temporarily handle something else while waiting, often represents waste rather than real progress toward finishing the actual work. Mistaking visible busyness for real production can mask the fact that the underlying flow of work is actually stalled or poorly organized.

Why does leveling zones by equal size sometimes create worse outcomes than leveling by work density?

Because equal physical size does not guarantee an equal amount of actual work, and a zone containing denser elements, like an elevator bank or a cluster of utility services, will naturally take longer regardless of how it compares in size to the zones around it. Leveling by work density prevents a predictable bottleneck from forming at whichever zone happens to contain more complex work than its neighbors.

What is the practical difference between trade stacking and trade burdening?

Trade stacking means too many trades are crowded unsafely into the same physical area at the same time, creating safety and coordination problems. Trade burdening means a single trade is being asked to cover more areas simultaneously than it can realistically manage well, spreading that trade too thin across the project.

Why should you monitor handoffs between zones as trades move through a production plan?

Because the moment one trade finishes in a zone and another trade begins is precisely where delays and miscommunication tend to accumulate if nobody is actively tracking it. Watching these critical handoffs closely helps catch a stall or a miscommunication early, before it has the chance to disrupt the broader flow moving through the rest of the project.

If you want to learn more we have:

-Takt Virtual Training: (Takt Virtual Training)
-Check out our YouTube channel for more info: (Elevate Construction on YouTube)
-Listen to the Elevate Construction podcast: (Elevate Construction Podcast)
-Check out our training programs and certifications: (Training Programs and Certifications)
-The Takt Book: (The Takt Book on Amazon)

Discover Jason’s Expertise:

Meet Jason Schroeder, the driving force behind Elevate Construction. As the company’s Founder and COO, 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.

Ideas That Tear the System Down.

Posted on October 1, 2026October 1, 2026 by Team Jason Schroeder

Read 9 min

Ideas Are Not the Same Thing as Tearing the System Down

Here’s the deal. There are two genuinely different things every organization has to manage. The system itself, and the improvement of that system. Confusing those two is one of the most damaging mistakes a team can make, because it leads people to believe they are improving something when they are actually quietly tearing it apart.

Why You Cannot Improve Your Way Into a System

You cannot effectively or quickly improve yourself into having a genuine system in the first place. I have never seen that actually work. Toyota took somewhere between twenty and sixty years, genuine experts can argue about the exact number, to develop what eventually became the Toyota production system. If you want to spend decades slowly evolving your own system from scratch through trial and error, that is a real option. I simply do not recommend it.

There is a saying I genuinely love. We can learn from wisdom or from sad experience. I would always rather learn from the accumulated wisdom of people who already figured something out than from the slow, repeated pain of making the same mistakes myself. That is exactly why I sought out the best training available, learned directly from people who already knew what they were doing, read real books, and put together a complete system before ever stepping onto my first project as a superintendent.

Why the Integrated Production Control System Exists

That early effort eventually became what we call the integrated production control system, built from the First Planner System, the Takt production system, and the Last Planner System. I want to be genuinely clear that the Last Planner System is not my own creation, and I never want to imply otherwise. Takt steering and control, on the other hand, is something I did actually develop myself. Distilling all of this down into something clear and usable, then actually implementing it, is what let that first project succeed.

Once a real system like that exists, you finally have something worth improving. Continuous improvement is the house that rests upon the foundation of standards, of stability. You genuinely cannot improve something that does not exist yet, and you cannot tear down an existing system in the name of trying to improve it either.

Why Our Own Bootcamp Proves the Point

Here is a concrete example from our own Super PM Bootcamp. We have a standard outline, a standard preparation process, standard presentation templates, standard visuals, standard checklists, standard order forms. That level of consistency is exactly what makes genuine improvement so easy to actually implement. Because everything is stable, a single real improvement can be identified clearly and applied cleanly.

What we never do is decide to skip the bootcamp entirely, skip presenting the material, skip the visuals, or skip the music that sets the tone. None of that is improvement. That is tearing down the system, and it does not lead to continuous improvement at all. It leads straight back into chaos.

What a Genuine System Actually Requires

The integrated production control system depends on a long list of real, non-negotiable components working together. A genuinely balanced team, with every individual carrying their own personal organization system. A real plan and schedule, built on genuinely Lean contracts, supported by a working risk analysis and removal process. A functioning supply chain management system for both information and materials, real prefabrication, and a genuinely strong logistics system behind it all.

It also depends on actually winning over the workforce, maintaining a genuinely clean, safe, and organized culture, running a real onboarding system, and training people consistently. It requires a daily correction system built around quality at the source, real contractor grading, genuine team balance grading, and zero tolerance actually implemented rather than simply written down somewhere.

Watch for these signs an organization still has real gaps in this foundation rather than a genuine system to actually build improvement on top of.

Core components like contractor grading or team balance tracking existing on paper but never actually practiced consistently.
Zero tolerance policies that technically exist but get quietly waived whenever enforcing them feels inconvenient in the moment.
A supply chain, logistics, or onboarding process that varies significantly from one project to the next rather than following a consistent standard.

Why Loosening These Standards Is Never Actually an Improvement

I hear teams, often working comfortably removed from the actual field, rationalize weakening these exact standards constantly. We will not do contractor grading every week, we will stretch it to every three months instead. We will not require everyone to attend the morning worker huddle. We will only bother with standard visuals after the pre-construction meeting when it feels truly necessary. We will relax our focus on cleanliness and quality a little. We will ease up on safety standards just slightly.

None of those are improvements. Every single one is tearing down the system.

Each example shares the same underlying pattern. A real standard gets reframed as merely inconvenient, and the reduction gets described using the language of flexibility rather than the language of removal. That framing is exactly what makes this trap so easy to fall into, since nobody sets out deliberately to dismantle a working system. It simply happens one reasonable sounding exception at a time.

Watch for these specific rationalizations that sound reasonable in the moment but are actually quietly dismantling a real, functioning system.

Reducing the frequency of a genuine accountability practice, like contractor grading, simply because maintaining it weekly feels inconvenient.
Making attendance at a core practice like the morning worker huddle optional rather than genuinely universal.
Treating cleanliness, quality, or safety standards as flexible, situational preferences rather than fixed, non-negotiable requirements.

Why Proximity to the Field Protects a Real System

A genuinely Lean company stays close to the field. A company that is not genuinely Lean drifts away from it. You cannot tear down these specific standards and still expect to win, no matter how reasonable the individual justification sounds in the room where that decision actually gets made. Ideas for genuine improvement are valuable. Rationalizing the quiet removal of a real standard is something else entirely, and confusing the two is exactly how a working system slowly comes apart.

Building Real Stability Before You Chase Improvement

None of this means avoiding change or treating a system as permanently fixed. It means building genuine stability first, and holding that foundation firmly even while you continue looking for real, legitimate ways to improve on top of it.

If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your organization build this exact kind of stable, complete system first, so that every improvement you make afterward actually builds something stronger, rather than quietly chipping away at a foundation that was never genuinely solid to begin with.

So here is the challenge. Look at your own organization’s recent decisions and ask honestly whether each one actually strengthened your existing system, or whether it simply loosened a standard because holding it felt inconvenient in the moment. That distinction alone will tell you whether you are genuinely improving or quietly tearing something down.

Jason Schroeder said it plainly: “Continuous improvement is the house that rests upon the foundation of standards, of stability.” Protect that foundation first, and genuine improvement has something real to stand on.

On we go.

FAQ

Why does the article argue that an organization cannot quickly “improve itself into” having a genuine system?

Because a real system, like the Toyota production system, typically takes decades of deliberate development to mature, and shortcuts rarely produce the same depth of stability. Learning from the accumulated wisdom and training of people who already built a working system, rather than trying to evolve one from scratch through trial and error, is presented as a far faster and more reliable path.

What is the actual difference between improving a system and tearing it down?

Genuine improvement strengthens an existing, stable standard, making it more effective while keeping its core function intact. Tearing the system down means weakening, skipping, or making optional a core component of that standard, often justified with language that sounds like flexibility or pragmatism, while actually removing something the system genuinely depends on to function.

Why does the article list so many specific components as “non-negotiable” parts of a real system?

Because each component, from personal organization systems to contractor grading to zero tolerance enforcement, plays a specific role in supporting the overall system’s stability. Treating any one of them as optional or situational creates a gap that weakens the entire structure, even if the rest of the system still appears to be functioning normally on the surface.

Why does proximity to the field matter so much to whether a system stays genuinely stable?

Because decisions to loosen or skip a core standard tend to get made and rationalized more easily by people removed from the actual consequences of that decision, happening far from where the real work is being done. Staying genuinely close to the field keeps leadership accountable to the real, visible impact of weakening a standard, rather than approving that weakening from a comfortable distance where the consequences are never fully seen.

If you want to learn more we have:

Discover Jason’s Expertise:

Standard Sizes: Why Everything Fits in Construction Logistics.

Posted on October 1, 2026October 23, 2026 by Team Jason Schroeder

Read 9 min

The Myth That Vendors Will Not Fit Into Standard Sizes

Here’s the deal. I keep hearing the same excuse from general contractors. Vendors will not ship it that way. They will not box it that way. They will not transport materials into the specific prefabrication sizes a Takt plan actually needs. I think that excuse is nonsense, and the entire global shipping industry proves it.

Why Standard Sizes Have Always Existed for Real Reasons

Standard unit sizes show up constantly throughout history, often traced back through surprising historical chains. One well-known story, worth treating as popular legend rather than verified fact, involves NASA rocket components that had to travel by rail to reach launch facilities, constrained by the width of railway tunnels. Those tunnels were originally sized around standard railroad boxcars, which were sized around standard rail gauge, which traced back through old wagon ruts from pioneer era roads, reportedly inherited all the way from Roman era cart dimensions, based on the spacing needed for two horses pulling a cart side by side.

I cannot personally verify every link in that chain, and I would encourage anyone curious to look into it further themselves. Whether every detail holds up to scrutiny or not, the underlying point is real and important. Standard sizes exist because an enormous, interconnected system depends on them fitting together consistently, often for reasons that trace back further than anyone involved in a single decision would ever realize.

That is exactly why dismissing a standard as arbitrary or unnecessary deserves real skepticism before accepting it at face value. A size, a format, or a delivery rhythm that looks inconvenient in the moment often exists because dozens of other systems downstream already depend on it staying consistent.

Why Shipping Containers Prove This Beyond Any Doubt

Here is the example that matters most directly. Standard shipping container sizes are a real, deliberate achievement, built specifically to work seamlessly with cranes, trucks, railways, tie-downs, and international shipping all at once. Before that standardization existed, every shipment risked becoming its own unique logistical puzzle. Once it existed, the entire global supply chain gained a shared, universal unit that everyone involved could simply build around.

Vendors do not argue about fitting metal panels, engines, or tires into that standard container size. Nobody treats it as an unreasonable request. It is simply the common, accepted standard the entire industry already operates around, without resistance and without constant negotiation.

That acceptance did not happen automatically either. It took real, deliberate industry wide agreement to establish those standard dimensions in the first place, decades ago. Once established and clearly communicated, though, resistance essentially disappeared, because everyone involved understood exactly what to build around from that point forward.

Watch for these real world examples proving that standardized units already work seamlessly across massive, complex industries without the resistance construction often assumes.

International shipping containers fitting cranes, trucks, and rail systems worldwide without constant renegotiation of size.
Standard rail gauge allowing railcars from different manufacturers and countries to run on the same tracks without incident.
Entire global supply chains built around a shared, universal unit that nobody treats as optional or negotiable.

Why the Same Resistance Myth Does Not Hold Up in Construction

So when a general contractor insists that vendors simply will not conform to a specific Takt time rhythm, a zone based delivery schedule, or a defined prefabrication unit size, the honest question is, what exactly are you talking about. The entire international logistics order already runs on standardization, and it only works because everyone involved accepts and builds around those standards rather than treating every delivery as a unique negotiation.

The actual myth here is not that trade partners or vendors refuse to work within a system. The real issue is a lack of management and a lack of leadership. Everyone across the broader logistics value stream is already fully accustomed to operating inside standardized systems in every other part of their business. Construction simply has not consistently asked for the same discipline, and then mistakenly concludes the industry itself is the obstacle.

The same vendor shipping a prefabricated unit to your jobsite may also be shipping standard containers to a port the very same week, built around dimensions everyone involved accepted without hesitation. The capability to work within a standard clearly already exists. What is often missing is a construction team willing to define one clearly and hold to it consistently.

Watch for these signs a lack of standardization on your own project is actually a leadership gap rather than a vendor limitation.

No consistent, pre-communicated standard for delivery sizes, zones, or timing shared with vendors before a project actually begins.
Deliveries treated as individually negotiated events rather than built around a shared, expected standard from the start.
Problems with delivery size or timing blamed on vendor behavior rather than traced back to whether the standard was ever clearly set in the first place.

Why the Real Fix Starts With Us, Not Our Vendors

The honest reason we do not get what we want, in the format we want it, delivered the way we actually need it, is that we do not standardize it and expect it up front. We do not pre-plan for it. That is not a criticism meant to embarrass anyone. It is simply an accurate diagnosis of where the real gap actually sits.

This reframing matters because it changes where a team looks for the actual fix. Blaming a vendor for not meeting an undefined expectation leads nowhere productive, since there was never a clear standard to actually meet in the first place. Defining that standard clearly, early, and consistently gives a vendor something real to build around, exactly the same way the shipping industry gave every port and carrier a real standard to design around decades ago.

If we want to improve how our jobsites run, we have to stop catching and correcting mistakes reactively once materials have already arrived in the wrong size or format. We have to start demanding real accuracy and precision up front instead, asking for exactly what we need, in the right sizes, built around the right standards, delivered according to the actual Takt time our project requires, in the format our site is prepared to receive.

Building Real Standardization Into Your Own Supply Chain

None of this requires reinventing how global logistics already works. It requires applying that same discipline, clear, communicated, expected standards, directly to your own project’s delivery requirements, rather than assuming vendors are uniquely incapable of meeting them.

If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your teams build standardized delivery expectations directly into your supply chain, rather than treating every vendor conversation as a fresh negotiation that somehow always ends the same disappointing way.

So here is the challenge. The next time you hear that a vendor simply will not deliver materials in the size or format your project actually needs, ask honestly whether that standard was ever clearly communicated and expected from the very beginning. More often than not, that gap in leadership, not vendor resistance, is where the real problem actually started.

Jason Schroeder said it plainly: “The myth that vendors won’t fall into a system is false. It’s a lack of leadership.” Set the real standard clearly, expect it consistently, and watch how quickly that supposed resistance disappears.

On we go.

FAQ

Why treat the story about NASA rocket components and horse cart width as popular legend rather than confirmed fact?

Because the specific historical chain connecting ancient cart widths to modern rocket component sizing is widely circulated but difficult to verify in full detail, and treating it as entertaining folklore rather than established history is the more accurate way to present it. The underlying point about standardization tracing back through surprising historical chains remains valid regardless of whether every specific link in that particular story holds up to scrutiny.

Why do standard shipping container sizes matter so much for construction deliveries?

Because they demonstrate, at a massive global scale, that complex industries can and do operate successfully around shared, universal standards without constant resistance or negotiation. If an entire worldwide shipping industry can standardize successfully, the claim that construction vendors specifically cannot adapt to a defined delivery standard becomes much harder to justify.

What is the actual root cause behind vendors seeming to resist standardized delivery requirements?

A lack of clear, consistently communicated standards set by the project team itself, rather than resistance from vendors. Vendors across the broader logistics industry already operate successfully within standardized systems elsewhere, which suggests the real gap is a failure to clearly define and expect those standards within construction specifically.

What practical change should teams make to fix this pattern?

Shifting from reactively catching and correcting delivery problems after materials arrive in the wrong size or format, toward proactively defining and communicating exact delivery standards before a project begins. That shift requires asking vendors clearly for what is actually needed, in the right sizes and formats, aligned with the project’s real Takt time, rather than discovering a mismatch only after delivery has already happened.

If you want to learn more we have:

Discover Jason’s Expertise:

The Engines of the Train: Pace Setters in Construction Flow

Posted on October 1, 2026October 21, 2026 by Team Jason Schroeder

Read 9 min

Why Your Bottleneck Trade Is Rarely Where You Expect It to Be

Here’s the deal. Driving through the Cajon Pass in Southern California recently, watching real freight trains move through the mountains, I noticed something that challenged an assumption I had carried for years without ever questioning it. The engine is not always at the front of the train. Sometimes it sits in the middle. Sometimes it sits at the back entirely. That small observation turned into a useful extension of how I think about Takt planning.

Short answer: The trade setting the pace for your train of trades isn’t always first in the sequence. Like a freight train’s engine, it can sit in the middle. Find that pace-setting trade, protect it with buffers, and put your improvement effort there, not on the wagons.

Why the Engine’s Position Challenges a Common Assumption

Most of us picture a train the way cartoons show it, one engine pulling everything from the very front. Real freight trains do not always work that way. Engines get positioned wherever they actually need to be to move the full length of the train effectively, sometimes distributed through the middle or placed toward the back, depending on the weight and length of what is actually being hauled.

That observation connects directly to drum buffer rope, the theory of constraints concept built around a bottleneck setting the real pace for everything around it. In the classic version of that idea, a group of hikers deals with the exact same problem. The slowest hiker, the pace setter, does not always get to conveniently stand at the front of the line. Sometimes that person is stuck in the middle, and the whole system has to account for that reality rather than wishing it were otherwise.

Both examples make the same underlying point in a different setting. The thing actually setting the pace does not arrange itself according to what would be most convenient to plan around. It sits wherever real conditions actually put it, and a planner who assumes otherwise is planning against reality rather than working with it.

Why Your Actual Pace Setter May Not Be First in Your Sequence

Here is the extension worth sitting with. In a real train of trades moving through a project, your actual bottleneck, the trade setting the pace for everything else, is not guaranteed to be the first trade in your sequence. It might sit squarely in the middle of your train, just like a real locomotive sometimes does.

Watch for these signs your actual bottleneck trade is positioned somewhere other than the convenient front of your sequence.

A later trade in the sequence consistently determining how fast the entire train of trades can actually move, regardless of how quickly earlier trades finish their own work.
Buffers built only at the front of a sequence, while the pace-setting trade sits further back, unprotected from upstream disruption.
Assumptions about sequence order based on convention or habit, rather than an honest assessment of which trade actually represents the real limiting factor.

Why This Matters for Where You Actually Place Your Effort

Here is the practical insight that matters most. If you want an entire train, or an entire train of trades, to move faster or slower, you do not focus your attention on the wagons. You focus entirely on the engine itself. Does it actually need to accelerate? Does it have the capacity to do so? Does it have the fuel, meaning the real resources, it actually needs? Is it staying in pace with any other pace setters you are managing? That last one is particularly relevant once you are running multiple trains through a complex, multi-train Takt plan.

Applied directly to a real jobsite, this means resisting the instinct to pour extra attention into trades that are not actually your bottleneck, simply because they happen to be easier to influence or more visible in the moment. Real improvement in overall pace comes specifically from investing in whichever trade is setting that pace, wherever it happens to sit in your sequence.

This runs against a common instinct. When a project feels behind, the natural reaction is often to push every trade harder at once, hoping the combined pressure produces a faster overall result. It rarely does. Pushing a trade that was never the actual constraint simply produces wasted effort and frustration, while the real bottleneck continues setting the same pace it always was.

Questions Worth Asking About Your Actual Engine

Once you have identified which trade functions as your real engine, a specific set of questions becomes far more useful than general schedule pressure applied evenly across everyone.

Does this trade actually have the crew capacity needed to move at the pace the rest of the project requires?
Does this trade have the materials, equipment, and information, the fuel, it needs to avoid unnecessary delay?
Is this trade staying synchronized with any other pace-setting trade running elsewhere in a multi-train plan, rather than drifting out of alignment with it?

None of those questions make sense applied to a wagon. They only make sense applied directly to the actual engine, which is exactly why correctly identifying your real bottleneck matters so much before you ever decide where to focus real improvement effort.

Why Real-World Observation Keeps Teaching Me New Things

I cannot stop noticing these kinds of parallels once I start looking for them. A real train passing through a mountain pass taught me something about Takt planning I had not fully articulated before, simply because I took a moment to actually look closely at something most people would drive right past without a second thought. That habit, pausing to examine something ordinary and ask what it might teach you, tends to produce exactly this kind of useful insight more often than people expect.

I would encourage anyone trying to master this kind of thinking to practice the same habit deliberately. Pick something ordinary you encounter constantly, traffic flow, a grocery store checkout line, a shipping dock, and ask honestly what it might reveal about pace, bottlenecks, and sequencing. The specific example matters far less than the discipline of actually looking closely enough to notice something real.

Building This Awareness Into Your Own Takt Plan

None of this requires abandoning the drum buffer rope framework you already use. It requires being honest about where your actual pace-setting trade sits within your sequence, rather than assuming it will conveniently appear at the front simply because that would be easier to plan around.

If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your teams correctly identify where your bottleneck actually sits within a train of trades, and focus real improvement effort there specifically, rather than spreading attention evenly across trades that were never actually the real constraint.

Want your team trained on this? See our Last Planner® System and Takt training.

So here is the challenge. Look at your own current train of trades and ask honestly which specific trade is actually setting the real pace for the rest of the sequence. If that trade is not positioned at the front, check whether your buffers and your improvement effort are actually protecting and strengthening it, or whether they are still built around an assumption about where the pace setter should be rather than where it is.

Bottom line: If we want to go faster, we do it at the engine, not the wagons. Find your actual engine wherever it sits, and put your real effort there.

On we go.

FAQ

Why can a bottleneck trade be positioned in the middle of a sequence rather than at the beginning?

Because the actual limiting factor in any sequence depends on real conditions like crew capacity, material availability, and the complexity of the specific work involved, not on where convention suggests it should sit. Just as a real train’s engine gets positioned based on the actual weight and length of the cars behind it, a bottleneck trade sits wherever real conditions place it, regardless of where it would be most convenient to plan around.

Why shouldn’t you focus improvement effort on trades that are not the actual bottleneck?

Because speeding up a trade that is not limiting the overall pace does not change how fast the entire sequence can actually move, since the true bottleneck still caps the pace regardless of how much faster the other trades become. Effort spent there is effort not spent on the trade that would actually produce a real improvement in overall project pace.

What practical questions should a team ask once it has identified its actual bottleneck trade?

Whether that trade has the crew capacity to move at the pace the project requires, whether it has the materials, equipment, and information it needs to avoid unnecessary delay, and whether it remains synchronized with any other pace-setting trade running elsewhere in a multi-train plan. These questions target the real constraint directly, rather than applying generic schedule pressure evenly across every trade in the sequence.

Why can an ordinary observation, like watching a train in a mountain pass, be a source of useful insight?

Because pausing to actually examine something familiar closely, rather than accepting a common assumption without question, often reveals a pattern that applies well beyond the original observation itself. I treat this habit of curious observation as a practical skill worth developing, since useful analogies and insights frequently come from paying real attention to ordinary things most people overlook.

If you want to learn more we have:

Discover Jason’s Expertise:

Mastering Construction Flow: Lessons from Elevating Construction Logistics.

Posted on October 1, 2026October 1, 2026 by Team Jason Schroeder

Read 8 min

Lead Time Is the Enemy, and Other Logistics Concepts Worth Stealing

Here’s the deal. I recently finished writing an entire book on construction logistics, pulling together an outline I had genuinely been collecting for ten to fifteen years, and researching concepts from military history, maritime operations, and manufacturing to fill in the gaps. A handful of these concepts genuinely changed how I think about running a jobsite, and I want to walk through the ones that matter most.

Why the Berlin Airlift Belongs in a Construction Logistics Book

The book opens with the story of the Berlin Airlift, an entire city supplied continuously from the sky during a real historical crisis. I do not think a logistical achievement of that scale has ever been genuinely replicated since. Reading through exactly how that operation actually worked made something click for me. Logistics is not a supporting function sitting quietly in the background of a project. Done well, it is genuinely one of the most impressive disciplines a team can master.

Why You Should See Only the End of the Tail

The military has a real concept worth borrowing directly, the logistics tail. What you actually receive and see on a jobsite is only the very end of a much larger chain that has to be managed carefully long before materials ever arrive. Treating that visible end point as the whole picture misses almost everything that actually determines whether logistics succeed or fail.

Why Toyota Spends Ninety Percent of Its Time Away From the Factory Floor

Here is a genuinely striking real example. Toyota reportedly spends roughly ninety percent of its time working directly with vendors and logistics, and only about ten percent of its time inside the actual factory. That ratio exists specifically to prevent mistakes, waste, misaligned behavior, trash, and incorrect materials from ever reaching the factory floor in the first place, rather than catching and correcting those problems once they have already arrived.

That is a genuinely different mindset than how most construction logistics actually operate. Most of our attention goes toward managing problems once they are already on site. The real opportunity sits upstream, preventing them from ever showing up there at all.

Why Lead Time Deserves to Be Treated as an Enemy

One chapter in the book carries a title I genuinely love. Lead time is the enemy. Too many teams simply accept a given lead time as a fixed fact and plan passively around it. The better approach is actively investigating and engineering a genuinely shorter, better lead time for your supply chain, rather than treating whatever a vendor initially quotes as something beyond your control.

Practical Concepts Worth Implementing Directly

A handful of specific ideas from manufacturing and military logistics translate directly onto a real jobsite.

Strive for five, meaning a worker should be able to access whatever they genuinely need within five seconds and five steps of where they are actually working.
The breakout queue, where materials get inspected, de-trashed, and properly kitted before they are ever allowed onto the jobsite itself.
Marshalling yards, genuine staging areas where resources are fully prepared and queued so they can be dispatched quickly the moment they are actually needed at the point of work.

A related concept worth borrowing from supply chain and distribution design is the hub, spoke, and feeder route model, the same structure familiar from distribution centers and retail logistics. Applying that same structure to a genuinely large or complex project gives logistics a real system for supplying work across multiple zones efficiently, rather than treating every delivery as its own isolated event.

What I Would Do Differently if I Ran These Jobs Again

Here is my honest reflection after working through all of this. If I could go back and run these projects again, I would spend significantly more time on genuine respect for people and significantly more time on logistics specifically. Too often, the default pattern on a real jobsite looks something like this. A crew arrives misaligned with a poor attitude, and the plan is to let them start anyway and address it through accountability later. Bad materials show up, and the plan is to install them anyway and sort out the reorder afterward. Trash gets hauled directly into the building, and the plan is to deal with it eventually.

None of that is actually acceptable. The real challenge is making sure everything, materials, equipment, and people, is genuinely queued up and ready before it ever enters the site at all, rather than entering first and getting corrected afterward.

Watch for these signs your own project is correcting problems after they enter the site rather than screening them out beforehand.

Crews allowed to begin work despite a known misalignment, with the plan to address it through a conversation later rather than before they start.
Materials installed despite a known defect, with reordering treated as an acceptable fallback rather than something to prevent entirely.
Trash or debris regularly entering a building during construction, with cleanup treated as routine rather than as something to stop at the source.

Traditional Japanese architecture includes a genuinely interesting real concept worth borrowing here too, built around an entry point specifically designed to determine whether whatever is arriving should actually be allowed through. I want to be clear that the point here is never about people. Our people are never the enemy. But misaligned behavior, poor mindsets, defective materials, waste, and vehicles that are not meeting your actual standard absolutely deserve to be screened out at that same kind of entry point, before they are ever allowed onto your site at all. Never let a problem walk through the gate and then chase it around the jobsite afterward trying to fix it. Stop it at the entrance instead.

Why This Book Covers So Much More Than These Highlights

Beyond these specific concepts, the book moves through Gemba and continuous improvement, standing up a genuine supply chain, real material management, how ordering loops back into your overall logistics plan, a complete logistics checklist, the actual role of a dedicated logistician on a jobsite, and deeper concepts around lead time, critical inventory, and dead stock. Every one of these deserves real attention on its own.

Building This Discipline Into Your Own Project

None of this requires rebuilding your entire logistics approach overnight. It requires picking one of these concepts, the breakout queue, a genuine marshalling yard, or simply asking whether your own lead times have ever actually been challenged, and applying it deliberately to see what changes.

If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your teams build genuine logistics discipline directly into your project, screening problems out before they ever reach the site rather than managing them reactively once they have already arrived.

So here is the challenge. Pick one recurring problem on your own project that currently gets fixed after it reaches the jobsite, a materials issue, a crew alignment problem, debris entering the building. Ask honestly what it would take to screen that specific problem out at the gate instead, before it ever becomes something your team has to chase down and correct later.

Jason Schroeder said it plainly: “Lead time is the enemy.” Stop accepting it passively, and start actively engineering something better.

On we go.

FAQ

Why does the article describe what arrives on a jobsite as only “the end of the tail”?

Because the visible delivery of materials represents the final, smallest piece of a much larger logistics chain that had to function correctly long before anything actually arrived. Focusing only on that visible end point misses the upstream decisions, routing, timing, and coordination, that actually determine whether logistics succeed or create real problems later.

Why does Toyota reportedly spend so much more time with vendors and logistics than inside its own factory?

Because preventing a problem before it ever reaches the production floor is significantly more effective than catching and correcting it afterward. Investing heavily in vendor relationships and logistics coordination upstream is what allows a company to avoid introducing waste, misalignment, and defective materials into the actual production environment in the first place.

What is the practical difference between accepting a lead time and treating it as “the enemy”?

Accepting a lead time means planning passively around whatever a vendor initially quotes, treating that number as a fixed constraint. Treating lead time as the enemy means actively investigating why that lead time exists and working to engineer something genuinely shorter, rather than assuming the original quote represents the best possible outcome available.

Why does the article emphasize screening materials and behavior “at the gate” rather than correcting problems once they are already on site?

Because correcting a problem after it has already entered the project, whether that is a misaligned crew, defective materials, or debris brought into a building, costs significantly more time and effort than preventing it from entering in the first place. Screening at the entry point treats prevention as the actual goal, rather than treating correction after the fact as an acceptable default approach.

If you want to learn more we have:

Discover Jason’s Expertise:

Pre-Construction Planning For Superintendents: What To Look For?

Posted on October 1, 2026October 23, 2026 by Team Jason Schroeder

Read 8 min

What a Superintendent Should Actually Do During Pre-Construction

Here’s the deal. Too many superintendents get brought into pre-construction and then simply parked at an empty desk with a set of drawings and a vague instruction to get familiar with the project. That is not useful, it does not fit how a field-focused person actually works best, and it wastes one of the highest-leverage windows available on the entire project.

Why This Time Deserves Real Extra Effort

I am generally not an advocate for working weekends or constant overtime. Pre-construction is the one exception worth making. If there is ever a moment to put in extra hours and real additional effort, it is here, before the job actually starts, specifically so the field phase itself runs smoothly and you can go home on time once real construction begins.

An hour spent in pre-construction is worth a week spent recovering from a problem in the field. A day spent here is worth a month later. That ratio alone should settle any debate about where the real effort belongs.

Think about what that ratio actually means in practice. A superintendent who spends an extra evening working through a logistics plan or a zone map during pre-construction is effectively buying back an entire week of chaos later, the kind that shows up as rework, miscommunication, and crews standing around waiting on something that should have already been resolved.

What Actually Belongs in This Time, Step by Step

None of this means sitting bored behind a desk staring at drawings. There is a specific, structured sequence worth following instead.

Start by building the macro-level Takt plan, including a real logistics plan and zone maps. Begin long lead procurement immediately. Start actively supporting your designers rather than waiting passively for finished documents. Run real-time constructability reviews and budget analysis as the design develops, rather than after it is locked. Look closely at the land itself and the utilities serving it, identifying any make ready work, like shoring, that will be required before work can actually begin.

Here are the specific planning deliverables that should come out of this detailed phase.

A real plan and schedule, built alongside zone maps and logistics maps rather than treated as separate afterthoughts.
A deliberately designed project trailer and a clear plan for how the project team itself will actually be organized and broken out.
A risk and opportunity register, tracking long lead procurement and supply chain items specifically.

From there, review the site make ready requirements directly, read the actual soils report rather than skimming a summary, and map out the first ninety days in detail, both the ninety days leading up to notice to proceed and the ninety days immediately following it.

The Question Worth Asking Constantly Throughout

Keep returning to one useful question throughout this entire process. What could stop construction in six months? That question alone tends to surface real risks long before they would otherwise become visible, giving you time to actually address them.

A practical extension of that question is researching every authority having jurisdiction requirement that could hold up the project later. Do you need two paved roads and active fire hydrants in place before you can go vertical. Do you need a vertical standpipe installed for the fire sprinkler system before building above the third floor. These specific requirements vary significantly by jurisdiction, and AI tools can help you research them thoroughly and quickly, well ahead of when they would otherwise surface as a real problem.

Watch for these specific categories of jurisdiction requirements worth researching proactively during pre-construction rather than discovering them later.

Infrastructure requirements, like paved roads or active fire hydrants, that must exist before certain construction activities can legally proceed.
Fire and life safety system requirements, like standpipes, that must be installed before building beyond a specific height or floor count.
Any other authority having jurisdiction requirement specific to your exact location and project type that could otherwise halt work unexpectedly.

There is no such thing as too much research during this phase. Every hour spent here protects real time later. The teams that treat jurisdiction research as a box to check quickly, rather than investigation worth real time, are consistently the ones who discover a serious constraint only once it has already cost them weeks on the schedule.

Why I Increased My Own Recommendation on Fresh Eyes Meetings

I used to recommend one to three fresh eyes meetings before a project starts, where an outside perspective tears the plan apart specifically to find every flaw worth catching early. I have since increased that recommendation significantly. On our own next project, I told our team directly that I want eight separate fresh eyes meetings, continually tearing the plan apart until it is right before we ever break ground.

That increase was not arbitrary. Each additional round tends to surface issues the previous ones missed, and the cost of catching a problem during one more meeting is nothing compared to the cost of discovering it once real construction is already underway.

I understand the instinct to treat eight meetings as excessive before you have actually tried it. In practice, the eighth meeting rarely feels redundant. It tends to catch something the first seven missed, which is exactly why the number keeps climbing rather than settling back down once teams actually experience the difference.

Why You Do Not Have to Do This Entirely Alone

If you are working through this process on your own, a resource like Elevating Pre-Construction Planning walks through this exact sequence visually, step by step, and the First Planner System audiobook covers the same material for anyone who learns better by listening during a commute. If you would rather bring in real support, a dedicated planning team can work alongside you directly, whether that means staffing a single position or bringing in a full team to handle the work with you and reduce risk across the entire project.

Building This Structure Into Your Own Pre-Construction Process

None of this requires guessing at what to do with your time during pre-construction. It requires following this same sequence deliberately, protecting time for it, and treating it with the seriousness its real leverage actually deserves.

If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your superintendents build exactly this kind of structured pre-construction process, rather than being handed a set of drawings and left to figure out where to start on their own.

So here is the challenge. Before your next project reaches pre-construction, map out which of these specific steps your current process already covers well, and which ones tend to get skipped or rushed. Whichever step consistently gets the least attention is exactly where your next field-level problem is most likely already forming.

Jason Schroeder said it plainly: “An hour in precon is worth a week in the field. A day in precon is worth a month in the field.” Protect that time deliberately, and the field phase becomes easier because of it.

On we go.

FAQ

Why put in extra effort specifically during pre-construction rather than throughout the entire project?

Because problems caught and solved during pre-construction are dramatically cheaper and easier to fix than the same problems discovered once real construction is already underway. I see this as an extremely high-leverage trade, where an hour invested early saves far more time later, which is why I treat this specific phase as the exception to generally avoiding overtime.

What is the actual purpose of mapping out the first ninety days before and after notice to proceed?

Because the early weeks of a project are where momentum either builds correctly or starts falling behind immediately, and detailed planning for that specific window helps ensure the project starts strong rather than scrambling to catch up from the very beginning. Covering both the ninety days before and after notice to proceed ensures preparation work and early execution are planned together rather than treated as separate phases.

Why research authority having jurisdiction requirements so far in advance?

Because requirements like needing paved roads, active fire hydrants, or specific fire safety systems in place before certain construction activities can proceed vary significantly by location and can halt work if discovered too late. Researching these requirements thoroughly during pre-construction gives a team real time to plan around them, rather than discovering a hard stop once construction is already underway.

Why did the recommended number of fresh eyes meetings increase so significantly, from one to three up to eight?

Because each additional round of outside review tends to surface issues the previous rounds missed, and the cost of running one more meeting is minimal compared to the cost of a problem discovered once construction has already started. The increase reflects a growing recognition that more thorough review during pre-construction consistently pays for itself many times over.

If you want to learn more we have:

Discover Jason’s Expertise:

Do We Really Know Who Our Customer Is?

Posted on October 1, 2026October 23, 2026 by Team Jason Schroeder

Read 8 min

We Do Not Know Who Our Customer Actually Is

Here’s the deal. There is a line I keep coming back to. People will admire your depth until it is time to swim in it. They will praise your wisdom until it holds them accountable. They will love your light until it exposes their shadows. I am nowhere close to fully living that out myself, but being around wise people has taught me that real clarity tends to make some people uncomfortable, especially when it asks them to look honestly at something they have been getting wrong.

That discomfort is exactly what I expect this next point to create, and I believe it anyway. Feel free to disagree, but hear me out before you decide.

The Customer We Have Completely Misidentified

In construction, we do not know who our customer actually is. We assume it is the public. We assume it is the building owner who signed the contract and paid the bill. It is not. As general contractors and project delivery teams, our actual customer, overwhelmingly and without real competition, is the trade partner. The foreman. The worker. That is who we actually serve.

Failing to understand that has cost this industry more than we can calculate. Because we assume the owner is the only real customer, we pull schedules through impossibly tight constraints at the direct expense of trades and workers, and we deliver at the last possible moment, sometimes at the expense of real human safety, simply because we never stopped to ask who was actually bearing the cost of that decision.

That misidentification is not a minor error either. It shapes nearly every downstream decision on a project, who gets squeezed when a schedule slips, whose comfort gets sacrificed first when budgets tighten, and whose concerns get heard when something goes wrong. Getting this one assumption wrong quietly distorts almost everything that follows from it.

What Actually Changes Once You Get This Right

Once you internalize who your real customer is, a whole series of obvious conclusions follow immediately. You should be making sure trades have full kit before they ever start work. You should be treating them with real respect, not simply tolerance. You should have decent bathrooms and lunch areas, not an afterthought bolted onto the edge of the site. You should think twice before defaulting straight to a cure notice the moment something goes wrong, and consider talking to the trade partner directly first. You should be vetting trade partners more carefully during selection, checking for fit rather than simply picking the lowest bid. You should be a good neighbor to the people actually building your project, not simply a client writing checks to them.

None of these conclusions are complicated once the underlying assumption actually changes. The reason they so often go unaddressed is not a lack of ideas. It is that the wrong customer was identified from the very start, which meant none of these obvious steps ever seemed necessary in the first place.

Watch for these specific behavioral shifts that show up once an organization treats trades as its actual customer.

Full kit provided proactively for every crew, rather than assembled reactively once a problem already surfaces.
A default instinct to communicate directly with a struggling trade partner before escalating straight to a formal cure notice.
Real investment in facilities, bathrooms, lunch areas, and comfort, treated as a real priority rather than a minimal legal requirement.

Why the Owner Still Ultimately Benefits From This

If you are not ready to fully accept that trades are literally your customer, I understand, and I would still ask you to accept at minimum that they are your first customer, with the building owner as your second. That distinction alone changes everything, because you cannot treat your first customer poorly and reasonably expect your second customer to receive anything better as a result.

Think of it the way any well-run business thinks about an internal supply chain. A company that treats its own manufacturing team poorly does not somehow produce a better product for the customer at the end of that chain. The same logic applies directly here. Trades are the internal chain producing the actual result an owner eventually receives.

How you treat the workforce is how they treat the building, and how they treat the building is ultimately how they treat your actual paying client. Neglecting trades in favor of protecting the owner relationship does not actually protect that relationship at all. It quietly undermines the very outcome the owner is paying for in the first place.

Owners rarely see this connection directly, since they are not present for the daily treatment of the trades actually building their project. They only ever experience the final result, the quality, the schedule, the overall experience of working with your company. That result is shaped entirely upstream, by decisions about how the actual customer, the trades doing the work, was treated along the way.

Watch for these signs an organization has quietly built its entire operating model around the owner alone, with trades treated as an afterthought.

Contract terms and schedule commitments negotiated entirely around the owner’s preferences, with no real consideration for whether trades can deliver on them.
Cure notices and adversarial correspondence used as a default first response rather than conversation.
Trade partner facilities, communication, and treatment consistently deprioritized relative to whatever protects the owner relationship most directly.

Why This Realization Is Uncomfortable, and Worth Sitting With Anyway

This is exactly the kind of insight that tends to put people off once it actually holds them accountable to something they have been doing wrong for years. Nobody enjoys realizing that an entire industry practice, one they may have personally defended, was built on a mistaken assumption about who actually deserved to be treated as the customer. I believe it anyway, because the cost of continuing to get this wrong is simply too high to ignore.

I would rather say this clearly and have some people disagree with me than stay quiet about something I believe is actually hurting real people every single day. That is worth more to me than being universally comfortable to listen to.

If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your organization rebuild its practices around trades and workers as the customer they actually are, rather than continuing to operate as though the building owner is the only relationship that matters. That shift touches contracts, staffing, onboarding, and daily leadership decisions alike, not just one isolated policy.

So here is the challenge. Look honestly at your own organization’s actual priorities, where real investment goes, how disputes get handled, and whose comfort gets protected first. If the honest answer consistently points toward the owner alone, that gap is exactly where your real customer has been quietly overlooked all along.

Jason Schroeder said it plainly: “We don’t know who our customer is.” Figure that out honestly, and nearly everything else about how you run a project starts to look different.

On we go.

FAQ

Why are trade partners, not building owners, a general contractor’s actual customer?

Because trades and workers are the people actually executing the work a general contractor delivers, and treating them as a secondary concern behind the owner relationship tends to produce worse outcomes for everyone involved, including the owner. Serving trades well is what ultimately produces the quality and reliability an owner is actually paying for.

How does neglecting trade partners eventually hurt the relationship with a building owner?

Because the quality of a finished project reflects how well the people building it were actually supported and treated throughout the process. A workforce treated as an afterthought tends to produce work that reflects that treatment, which ultimately affects the outcome the owner receives, even though the owner may never directly witness how trades were treated along the way.

Why rethink the default use of a cure notice when a trade partner struggles?

Because a cure notice functions as an adversarial, formal escalation, and defaulting to it immediately skips over conversation that might resolve the underlying issue more effectively and with less damage to the relationship. Treating trades as a customer means extending the same good-faith communication a business would extend to any other valued customer before escalating to something more formal.

What is the practical difference between treating trades as “a” customer versus “the first” customer?

Treating trades as simply one customer among several can still allow an organization to prioritize the owner relationship whenever the two seem to conflict. Treating trades specifically as the first customer establishes a clear priority order, meaning their treatment and support come first, with the understanding that doing so well is exactly what protects and strengthens the relationship with the owner as the second customer.

If you want to learn more we have:

Discover Jason’s Expertise:

General Offerings

Company Offerings

Systems

Busyness Is Not Production, Busyness Is Waste

Why Keeping People Busy Is Not the Same as Keeping Them Productive

The Simple Framework That Actually Creates Flow

Why Smaller Zones Move Faster

Why Leveling by Work Density Matters More Than Equal Size

Flowing Trades and Leveling Crews

What to Actively Avoid as Trades Move Through the Sequence

Why This Matters Most on the Largest, Most Complex Projects

Building This Framework Into Your Own Project

FAQ

Why is keeping workers busy potentially harmful rather than simply neutral?

Why does leveling zones by equal size sometimes create worse outcomes than leveling by work density?

What is the practical difference between trade stacking and trade burdening?

Why should you monitor handoffs between zones as trades move through a production plan?

Why Your Bottleneck Trade Is Rarely Where You Expect It to Be

Why the Engine’s Position Challenges a Common Assumption

Why Your Actual Pace Setter May Not Be First in Your Sequence

Why This Matters for Where You Actually Place Your Effort

Questions Worth Asking About Your Actual Engine

Why Real-World Observation Keeps Teaching Me New Things

Building This Awareness Into Your Own Takt Plan

FAQ

Why can a bottleneck trade be positioned in the middle of a sequence rather than at the beginning?

Why shouldn’t you focus improvement effort on trades that are not the actual bottleneck?

What practical questions should a team ask once it has identified its actual bottleneck trade?

Why can an ordinary observation, like watching a train in a mountain pass, be a source of useful insight?

SUBSCRIBE NOW !

Subscribe to our newsletters and stay updated!