Why a Construction Company Shouldn’t Have a Corporate Office.

Posted on September 30, 2026September 30, 2026 by Team Jason Schroeder

Read 9 min

Why a Beautiful Corporate Office Is One of the Biggest Hindrances to Lean

Here’s the deal. I recently learned that a construction company in Japan we are visiting later this year offered to walk us through its fabrication facilities and shop floor. There was no mention of a corporate office anywhere in the conversation. That detail stopped me cold, because it revealed something most companies in this industry never actually question. Why would a construction company have a beautiful corporate office at all.

Why Would a Construction Company Not Simply Manufacture Everything It Can

Once that question hit me, it kept unfolding into more questions worth actually asking out loud. Why would a construction company not fabricate its own job site office components, custom gang boxes, and tools for its carpenters and laborers directly. Why would it not prefabricate its own assemblies in house, or use its yard as a genuine marshaling area and queuing space for logistics. Why would it not build actual mock-ups of end user spaces and exterior skin assemblies somewhere teams can walk through them before they ever reach the field.

Every one of those questions points toward the same conclusion. A construction company’s physical space should be built around producing and supporting real work, not around housing people comfortably at desks.

None of that requires abandoning administrative functions entirely. It requires asking, honestly, whether each square foot of a company’s physical footprint is actually earning its place by supporting the field, or whether it exists simply because that is how corporate space has always been built in this industry.

Here are just a few of the specific things worth asking your own organization why it is not already doing.

Fabricating custom tools, gang boxes, and job site components directly rather than purchasing everything ready made.
Building physical mock-ups of end user spaces and exterior assemblies before that work ever reaches a real building.
Using yard and shop space as an actual marshaling and queuing area for field logistics.

Why an Office Itself Works Against Lean Thinking

Here is the deeper problem underneath all of this. An office puts people into a false, unrealistic environment, disconnected from other human beings and from where real decisions actually need to be made. It removes leaders from proximity to the work and from what Lean practitioners call the Gemba, the actual physical place where value gets created. Away from that, a leader stops solving real problems and stops doing the actual job of stabilizing systems and working shoulder to shoulder with people. That disconnection is exactly why Toyota keeps its own leaders physically out on the line rather than behind a desk.

Even much of what fills a typical office day, endless meetings and constant email, can quietly become a kind of escapism from the harder, more valuable work leadership is actually supposed to be doing. It feels productive in the moment, since a full calendar and an empty inbox both look like real accomplishment, even when neither one actually moved a real project forward that day.

The Real Insight: Beautiful Buildings Actively Block Visual Management

Here is the piece that genuinely surprised me once I thought it through fully. A beautiful corporate office is not simply disconnected from the field. It actively works against the specific tools Lean depends on to function at all.

Think about what a genuinely beautiful office actually prioritizes. Pristine wall space. Exposed concrete left untouched. Clean, uncluttered aesthetics that a visitor would find impressive. Every one of those priorities directly competes with what a real Lean environment actually needs covering those same walls. Metrics. Screens. Project maps. Pre-construction documents ready for review. Huddle boards. Kanban boards. Genuine visual signals. Standard work posted where anyone can see it. Value stream maps built and updated constantly rather than filed away somewhere.

Watch for these signs your own office space is quietly prioritizing appearance over the visual management Lean genuinely requires.

Walls kept intentionally clear and uncluttered rather than covered in active metrics, boards, and standard work.
No huddle boards, Kanban boards, or project visuals anywhere a visitor or employee would actually see them.
A workspace that would photograph beautifully for a company brochure but tells you almost nothing about how the actual work is going.

That is genuinely the biggest anti-Lean decision a construction company can make without realizing it. Choosing beauty over function at the level of the physical space itself.

It is worth being honest about why this happens so often, even in companies that genuinely believe in Lean principles on paper. Nobody sets out deliberately to sabotage visual management. A beautiful space simply gets built first, often by people focused purely on architecture and impression, and only afterward does anyone realize that the walls meant to look impressive leave nowhere left for the boards and metrics that actually run the business.

What I Would Actually Build Instead

If I ran a construction company with multiple active projects, here is specifically what I would want the physical space to look like. Offices that manufacture and produce key logistical items directly for the field. Real marshaling areas supporting field logistics. Open workspace for pre-construction teams built around collaboration rather than separation. Massive training areas, genuine dojos for developing people. Highly visual situation rooms or command centers where anyone can see exactly where every project actually stands.

And even in the parts of the business that do need something resembling a traditional office, I would still want interactive screens, standing and sitting desks, and whiteboard paint covering the walls, used constantly for real value stream mapping and genuine problem solving, not decoration waiting to be admired.

That last detail matters more than it sounds. Whiteboard paint only earns its place on a wall if leadership is actually willing to mark it up daily, in front of their own team, rather than leaving it pristine because a marked up wall feels less polished than a blank one.

Why This Matters More Than It Might Seem

None of this is meant as criticism of any specific company, and I genuinely understand the normal instinct behind wanting a polished, professional looking headquarters. But if your organization has invested heavily in a beautiful corporate office, that investment itself is a meaningful signal. It suggests a classical business management mindset still sitting underneath the surface, one that will keep working against genuine Lean practice until the physical space itself actually changes to match the philosophy you are trying to build.

If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your organization rethink its physical space around genuine flow and visual management, rather than assuming a polished office and real Lean practice can comfortably coexist without one eventually undermining the other.

So here is the challenge. Walk through your own company’s office space and count how many walls are genuinely covered in active metrics, huddle boards, and visual management tools, versus how many are being kept clean and uncluttered for the sake of appearance. That ratio alone will tell you more about your organization’s real relationship with Lean than almost anything else you could measure.

Jason Schroeder said it plainly: “You will never be lean until you fix the space.” Start there, and see how much of the rest of the system starts to follow.

On we go.

FAQ

What does the term “Gemba” actually mean, and why does it matter for leadership?

Gemba refers to the actual physical place where real work happens and real value gets created, the jobsite itself rather than an office somewhere removed from it. Lean thinking places enormous importance on leaders spending genuine time at the Gemba, since that proximity is what actually lets them see real problems, stabilize real systems, and lead shoulder to shoulder rather than manage from a distance through reports and secondhand updates.

Why does the article treat a beautiful office as worse for Lean than simply a neutral, comfortable workspace?

Because a genuinely beautiful office actively prioritizes clean, uncluttered walls and pristine aesthetics, which directly conflicts with the visual management tools Lean depends on, metrics, huddle boards, Kanban boards, and standard work posted where everyone can see them. A merely neutral space might simply lack those tools by default, while a deliberately beautiful one tends to actively resist adding them in order to preserve its polished appearance.

Is the article arguing that construction companies should never have any office space at all?

Not entirely. It argues that whatever office space exists should be built around function rather than appearance, filled with interactive screens, whiteboard paint used constantly for real work, and open layouts that support collaboration rather than separation. The core argument is against beauty and comfort as the guiding design priority, not against having any indoor workspace whatsoever.

Why does the article suggest that meetings and email can become a form of escapism for leadership?

Because time spent in meetings or managing an inbox can feel productive without actually requiring a leader to engage directly with real problems happening in the field. The article argues that genuine leadership requires physical presence and direct engagement with the actual work, and that office-based activities can sometimes substitute for that harder, more valuable engagement without anyone noticing the difference in the moment.

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.

Strive for Perfection.

Posted on September 30, 2026September 30, 2026 by Team Jason Schroeder

Read 8 min

Strive for Perfection: Why Real Improvement Is Fractal, Not Linear

Here’s the deal. I used to think striving for perfection was genuinely futile, a wasteful pursuit chasing diminishing returns the closer you got to it. I was wrong, and understanding why has completely changed how I think about improvement, both in business and in my own life.

Why “Diminishing Returns” Was the Wrong Mental Model

The common assumption is that once you get close to excellent, further improvement barely matters anymore, so why keep pushing. Visit a genuinely advanced Lean manufacturing facility, the kind Toyota and Honda have spent decades building, and that assumption falls apart immediately. Those organizations are so deeply standardized and so thoroughly Lean that they perceive an entire level of possible improvement most people cannot even comprehend yet, simply because they have never actually gotten close enough to see it.

That is genuinely the key insight. You cannot see where the next level of improvement actually leads until you take the next real, actionable step toward it. Read a book like Elevating Construction Logistics, a genuinely substantial six hundred fifty page work, and it is easy to assume there is no realistic way to implement all of it. Implement even a small piece of it, though, and the next available step becomes visible in a way it simply was not before.

The mindset that opens up is worth emphasizing on its own. It is not really about the specific page count or the specific technique implemented first. It is about what happens to someone’s own thinking once they have genuinely tried even one small piece of a much larger system and watched it work. That experience, more than any individual improvement itself, is what makes the next step feel possible rather than theoretical.

The Nautilus Shell

Here is the image that finally made this click for me. Picture a tiny creature living at the very center of a nautilus shell, moving through one compartment at a time. Each compartment feels complete on its own, genuinely satisfying to have reached. Then the creature moves forward into the next one, and that next chamber is not simply a little bigger. It is exponentially larger, following the same underlying pattern at a dramatically larger scale. Move forward again, and the next chamber repeats that same fractal expansion, again and again, each one larger than the last in the same consistent proportion.

Real improvement works exactly like that. It does not shrink as you approach some theoretical ceiling. It keeps opening into a larger version of the same pattern, over and over, for as long as you keep moving forward.

Watch for these signs a person or organization has mistakenly concluded that improvement has run its course.

A team that describes its current results as the absolute best they could ever be, with no further room imagined beyond that.
Genuine plateau in one area of a business while stability and standardization quietly succeed everywhere else.
A sense that reaching a solid, functioning system marks the finish line rather than the entrance to an entirely new level.

Proof From My Own Life

This pattern has shown up directly outside of work too. As soon as I finished renovating a base area of my own house, an entirely new set of improvement opportunities I had genuinely been walking past for years suddenly became visible. After my mother passed away, my dad asked me to take over payments on her car, a genuinely nice Honda. Taking real care of that vehicle led me almost immediately into an entire cascade of new ideas, small accessories worth adding for trips to the lake, a better system for cleaning it consistently, even a smarter standard for exactly where we park it. And within that same excitement, I found myself thinking directly about our own morning huddle process at work, wondering whether we could standardize and improve it the exact same way.

None of that would have occurred to me before actually finishing the smaller project that came right before it. The pattern was identical to what happens in a business, just playing out at home instead, one completed step quietly revealing an entire set of possibilities that genuinely did not exist from where I was standing before.

Why This Matters at the Level of an Entire Business

I have watched this exact pattern play out building our own company too. I started in a shed, genuinely unsure how to even set up my own email account. From there, real training, then a next step, then another, learning podcasting, learning social media, eventually hiring our first employee, something I could never have imagined from where I started. Now we are looking at acquiring a building in Phoenix specifically to begin fabricating products for our clients directly. Every single one of those steps opened onto a scale of possibility that was genuinely invisible from the step before it.

Watch for these signs the fractal pattern is actually unfolding inside your own project or organization right now.

A newly stabilized jobsite revealing an entirely new category of possible improvement, like advanced logistics kitting or dedicated queuing areas, that was not even on the radar before.
Each new level of improvement feeling meaningfully larger or more exciting than the one immediately before it, rather than smaller or less significant.
A genuine sense of surprise at discovering something that was apparently always possible, simply never visible until now.

Why Clients Sometimes Stall Right Before the Best Part

I see this pattern play out with clients constantly. A jobsite finally becomes genuinely clean, safe, and organized. Rework numbers start dropping. The company becomes consistently profitable. A real training facility gets built. Standard work finally exists everywhere it should. And right at that exact moment, some organizations quietly stall, mistaking that hard won stability for a finish line rather than what it actually is, the entrance into an entirely new chamber of the shell.

That is exactly the wrong moment to ease off. It is the moment to double down, triple down, and treat continuous, never ending improvement as simply part of how the work gets done, rather than a phase that eventually concludes once things finally look stable.

Taking Your Own Next Step

None of this requires seeing the entire path in advance. It requires taking the next real, actionable step from wherever you currently stand, trusting that the next chamber will become visible only once you have genuinely reached the one you are standing in right now.

If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your teams take that next concrete step, whether that means finally stabilizing a chaotic jobsite or pushing an already strong operation into logistics and improvements most competitors have not even considered yet.

So here is the challenge. Look at whatever part of your own project or business currently feels finished, genuinely stable, and hard to improve any further. Take one small, real step past that point this week, and pay close attention to whatever becomes newly visible once you do.

Jason Schroeder said it plainly: “You’re never going to see where you can go next until you take the next actionable step.” Take that step, and trust that the next chamber really is exponentially bigger than the one you are standing in right now.

On we go.

FAQ

Why does the article compare continuous improvement to a nautilus shell rather than a straight path?

Because improvement does not shrink as it approaches some theoretical limit, it keeps expanding into a larger version of the same underlying pattern, the same way each chamber of a nautilus shell grows exponentially larger than the one before it. That fractal quality is what makes improvement feel genuinely endless rather than a process that eventually runs out of meaningful next steps.

Why can’t someone simply plan out every future improvement in advance instead of taking things one step at a time?

Because the next genuine opportunity for improvement typically only becomes visible once the current step has actually been completed, not before. Trying to see the whole path in advance tends to produce guesses rather than real insight, since the actual next chamber only reveals itself once you have genuinely reached the one you are currently standing in.

Why do some organizations stall right after achieving genuine stability and strong results?

Because they mistake that hard won stability for a finish line rather than recognizing it as the entrance into an entirely new level of possible improvement. That misunderstanding causes them to ease off exactly when the next major opportunity, often bigger and more exciting than anything achieved so far, is actually within reach.

Does this fractal pattern of improvement apply outside of a business or construction context?

Yes, and the article uses personal examples, a home renovation and caring for a family vehicle, to illustrate that the same pattern shows up in ordinary daily life. Completing one small improvement regularly reveals an entirely new set of possibilities that were not visible beforehand, suggesting the underlying principle applies far beyond any single professional context.

If you want to learn more we have:

Discover Jason’s Expertise:

New Constraints Reveal System Bottlenecks.

Posted on September 30, 2026September 30, 2026 by Team Jason Schroeder

Read 9 min

If You Are Not Finding a New Constraint, You Have Not Optimized the Last One

Here’s the deal. I recently had a realization that genuinely excited me, and it came from the most unexpected place, running out of knee pads at one of our own training bootcamps. That small, almost silly problem turned out to reveal something important about how real continuous improvement actually works.

A Problem We Had Never Had Before

At a recent bootcamp, class sizes had grown, and I had made real improvements to how our physical training models were built, specifically by pre-cutting sections so teams could spend far more of their time on genuine logistics planning rather than basic fabrication. The session ran smoothly. Then my dad, who was helping run the event, pointed out that people were missing knee pads and tools. We simply did not have enough to go around, something that had never happened at any previous bootcamp.

At first, that felt like a straightforward equipment shortage. Looking closer, it was actually proof of something much bigger.

I had spent years slowly refining these bootcamps without ever hitting a genuine supply problem like this one. The fact that it showed up now, right after a real improvement to how teams built their models, was not a coincidence. It was a direct signal that something underneath the surface had genuinely changed.

Why Standardization Is What Makes Improvement Possible

We have standardized nearly everything about how these bootcamps run. Standard presentation files. Standard outlines. Standard work for setup and teardown. Standard processes for nearly every piece of the event. That level of standardization is exactly what has let us make so many improvements, sometimes in real time during a single event, and sometimes as major overhauls between one bootcamp and the next, that it genuinely becomes hard to keep track of them all.

The teams at this particular bootcamp were so well prepared, the content so clear, and the supplies so easy to use, that they moved through the model building process noticeably faster than ever before, spending more of their actual time together as a team rather than struggling with the mechanics of assembly. That speed is exactly what created the sudden tool shortage. Not because we planned poorly, but because we had genuinely gotten faster.

The Law of Bottlenecks

This is where it clicked for me. Every system has a limiting factor, a genuine bottleneck, and once you find and optimize it, another one will show up in its place. That principle, closely tied to Eliyahu Goldratt’s work on the theory of constraints and explored further by researchers like Niklas Modig, means something specific and genuinely useful. If you are not finding a new bottleneck after resolving the last one, that is not actually a sign of success. It usually means the original bottleneck was never fully optimized in the first place.

Running out of tools proved two things simultaneously. First, our original constraint, the model building and pre-planning process itself, really had been genuinely optimized, since teams were now moving through it noticeably faster than before. Second, a brand new constraint had emerged in its place, our actual physical tool supply, and now I had a clear, specific target to solve before the next event.

Watch for these signs a previous bottleneck was never actually optimized, even if it looks resolved on paper.

The same recurring complaint keeps showing up in a slightly different form, rather than genuinely disappearing.
No measurable improvement in speed or output after the supposed fix was implemented.
No new limiting factor ever emerges, months after a change was made, suggesting nothing actually shifted underneath it.

Why a New Constraint Is Actually Good News

I solved the immediate tool shortage quickly, getting extra supplies delivered before the next event and making sure we had more than enough going forward. The more important realization was recognizing that discovering this new constraint was genuine proof of progress, not a setback. I now have a clear next target to optimize, and once that gets solved, I fully expect a third constraint to reveal itself at the following bootcamp. Finding out exactly what that turns out to be is honestly one of the more exciting parts of running this training.

That mindset shift matters more than the specific fix itself. Plenty of leaders would have looked at a tool shortage and simply ordered more tools, closing the loop without ever asking what that shortage actually revealed about the rest of the system. Treating it instead as data about where the next real constraint lives is what keeps this whole cycle moving forward rather than stalling out after the first visible win.

Watch for these signs your own continuous improvement process is actually working the way it should.

A newly discovered limiting factor that is genuinely different from the one you just solved, rather than a repeat of the same underlying issue.
Teams or processes measurably faster or more effective than before, even if that speed reveals a new gap elsewhere.
A growing willingness to treat each new constraint as a signal of real progress rather than a frustrating setback.

Why We Have Barely Scratched the Surface

Even after training thousands of people through these bootcamps, I genuinely believe we have barely scratched the surface of what this training can become. The audio system. The headsets. The floor layout. The music. The level of automation behind the scenes. The specific Lean examples we use to teach each concept. Every one of those is a place a future constraint is likely still waiting to be discovered and optimized.

My goal is for this to become the best training available anywhere in the world, the kind where people look at it and genuinely cannot imagine how it could be topped. And even once we reach that point, I expect it will still only be the beginning, because that level of standardization tends to open up an entirely new world of improvements nobody could have anticipated from where we currently stand.

Applying This Same Discipline to Your Own Project

None of this only applies to running a training bootcamp. The exact same law of bottlenecks applies to a construction schedule, a pre-construction process, or any recurring system your team runs repeatedly. Solve one constraint, and if nothing new ever surfaces afterward, that silence is worth investigating rather than celebrating.

A Takt plan works exactly the same way. Optimize the first bottleneck holding a phase back, and a genuinely faster, better coordinated crew will almost always run straight into whatever the next limiting factor happens to be, whether that is material staging, a specific trade’s capacity, or a piece of equipment shared across too many zones. Expecting that next constraint, rather than being surprised by it, is what separates a team that keeps improving from one that quietly stalls after its first success.

If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your teams build the genuine standardization that makes this kind of continuous, compounding improvement possible, rather than settling for a single fix and assuming the work is finished.

So here is the challenge. Think about the last constraint your team genuinely solved. Has a new one shown up since then. If the honest answer is no, that silence deserves a second look, because it may mean the original fix never actually took hold the way everyone assumed it had.

Jason Schroeder said it plainly: “If you’re not finding a new bottleneck, you haven’t actually optimized the first one.” Keep looking for the next constraint, and treat finding it as the genuine sign of progress it actually is.

On we go.

FAQ

Why does discovering a new constraint count as evidence that the previous one was actually solved?

Because a genuinely optimized system moves faster or performs better than before, and that improved performance naturally exposes whatever limiting factor comes next in line. If no new constraint ever appears after a supposed fix, it often means the underlying process never actually sped up or improved in a way that could reveal the next bottleneck.

Why does standardization enable more improvement rather than locking a process in place?

Because a standardized process gives everyone a shared, documented starting point, which makes it possible to identify exactly what changed when something improves or breaks down. Without that shared baseline, it becomes far harder to isolate which specific change actually caused an improvement, which slows down the entire cycle of finding and solving the next constraint.

What should a team do when a newly discovered constraint feels like a step backward rather than progress?

Recognize that the constraint itself is evidence the previous fix genuinely worked, since a truly unresolved system would keep producing the same old problem rather than revealing a new one. Reframing a new constraint as a sign of real progress, rather than a frustrating setback, is what keeps a team motivated to continue the cycle of improvement rather than treating each new problem as a failure.

Why is it significant that a team can trace a tool shortage directly back to a genuine process improvement?

Because it demonstrates the constraint moved location within the system rather than disappearing entirely, which is exactly what the law of bottlenecks predicts. Tracing that connection clearly, from a specific improvement to a specific new limitation, shows the team is genuinely diagnosing its own system correctly rather than guessing at unrelated fixes.

If you want to learn more we have:

Discover Jason’s Expertise:

How Bureaucracy Destroys Leadership

Posted on September 30, 2026September 30, 2026 by Team Jason Schroeder

Read 8 min

Why Bureaucracy Is Always a Leadership Capacity Problem

Here’s the deal. Bureaucracy does not appear randomly inside an organization. It shows up as the direct, predictable result of a distracted leader who no longer has the time or capacity to actually stabilize systems and work shoulder to shoulder with their own people.

A Real Pattern Worth Recognizing

I have recently been working around a genuinely high level executive who is spread far too thin, without enough real support, and simply not able to stay on top of everything the role actually requires. I do not fault this person individually, and honestly, faulting the individual is not even the right Lean framing to begin with. There is a real system failure surrounding this person specifically because they are so busy and, at the same time, still trying to control too much directly. That combination produces exactly what you would expect. Heavy bureaucracy. Excessive rules. Genuine stagnation. Constant panic and worry. A toxic undercurrent running through the whole organization.

Why Distraction Directly Produces Bureaucracy

Here is the honest mechanism behind this. If you cannot maintain genuine stability because you are simply too distracted to build it, bureaucracy is what naturally fills that gap instead. Think about any organization where a single small mistake sends everyone into a genuine panic, or where so many rules pile up that nobody can actually innovate or move anything forward without permission from three different directions. That paralysis is not a coincidence. It is what happens when centralized control tries to compensate for a lack of real, distributed stability.

History offers a useful, if uncomfortable, example of this dynamic in action, entirely separate from any moral judgment about the cause being fought for. Rigid, overly centralized military command structures have repeatedly shown the same failure pattern, where decisions take far too long, everyone becomes afraid to act without explicit approval, and the layers of required sign off eventually paralyze the organization from actually responding to what is happening in real time. Bureaucracy produces exactly that kind of paralysis, regardless of the setting it shows up in.

A construction project shows the same dynamic on a smaller scale. A superintendent who cannot make a routine field decision without three layers of approval is operating under exactly the same paralysis, just measured in days lost on a schedule rather than territory lost on a map. The scale is different. The underlying failure is identical.

Watch for these signs your own organization has slipped into this exact pattern of distraction driven bureaucracy.

A single small mistake triggering a disproportionate, organization wide reaction rather than a calm, contained response.
Rules and approval layers accumulating faster than anyone can actually track or justify.
Decisions that used to happen quickly now taking months to move through the organization.

What Deming Actually Meant by Leadership

Edwards Deming wrote and spoke about leadership constantly, and one of his central points was deceptively simple. What organizations genuinely need is leadership. On its own, that statement sounds almost too vague to act on. Sit with it longer, and the real meaning becomes clear. Get rid of the slogans hanging on the wall that nobody actually lives by. Get rid of the distant, disconnected corporate office culture that keeps leadership physically and emotionally removed from the actual work. Get out, and actually provide real leadership, stabilizing systems and processes while training and working shoulder to shoulder with your own people.

That is genuinely the job. A leader’s core responsibility is to stabilize systems and processes and to work directly alongside the people doing the work, not to manage from a distance and hope stability simply emerges on its own.

Notice how differently that reads from a typical leadership job description, which often emphasizes oversight, reporting, and decision authority. Deming’s version puts the leader physically in the work, building stability directly rather than monitoring it from a report generated by someone else. That distinction alone explains why so many organizations with plenty of oversight still end up drowning in bureaucracy.

Why “Too Busy” Is Never a Sustainable Excuse

When a leader says, I am too busy, I am too spread thin, treating their own overextension as something happening to them rather than something within their control to fix, they lose the capacity to create real stability or train anyone properly. Bureaucracy is what naturally fills that vacuum instead. And bureaucracy never moves an organization forward. It stagnates it, gradually pulling the whole culture back toward classical business management thinking, losing sight of the organization’s actual purpose, and eventually starting to genuinely hurt the people caught inside it.

Watch for these signs a leader has actually regained the real capacity needed to stabilize their organization, rather than continuing to hide behind bureaucratic layers.

Genuine time blocked consistently for direct, in-person engagement with the team, not just scheduled around whatever is left over.
Decisions made close to where the actual work happens, rather than routed through several unnecessary layers of approval.
A visible reduction in rules and process specifically because trust and stability have genuinely replaced the need for them.

The Real Fix Starts With Two Honest Questions

Turning this around starts with two direct questions. Do you genuinely have the right people in the right seats. And does your leadership actually have the real capacity needed to get out of their own ivory castles and go lead boots on the ground, rather than managing everything remotely through policy and process. That second question matters more than most organizations want to admit, because building real capacity often means removing something from a leader’s plate, not simply asking them to try harder while carrying the exact same load.

That is often the hardest step in practice, because it usually requires someone above that leader to make a genuine decision, reassigning a responsibility, adding real support, or restructuring a role entirely, rather than simply telling an already overwhelmed person to manage their time better.

Why This Deserves Genuine Leadership Attention

If your organization has become genuinely bureaucratic, that outcome means your leaders either cannot be where they actually need to be, or will not be, because staying behind a desk managing through policy is the easier, second best option compared to the harder, far more effective work of leading shoulder to shoulder in the field.

If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your organization address the real capacity problem underneath bureaucratic stagnation, rather than adding yet another layer of process on top of a leadership gap that process alone will never actually fix.

So here is the challenge. Look honestly at your own leadership team’s calendars and ask how much time is genuinely spent shoulder to shoulder with the people doing the actual work, versus time spent managing from a distance through rules, reports, and approvals. If that ratio has quietly tipped toward distance, that is exactly where your organization’s bureaucracy is actually coming from.

Edwards Deming said it plainly: “What we need is leadership.” Get your leaders out of their offices and back into genuine, shoulder to shoulder engagement, and the bureaucracy that distraction created starts to genuinely dissolve.

On we go.

FAQ

Why does the article treat bureaucracy as a symptom rather than a cause of organizational dysfunction?

Because bureaucracy tends to emerge specifically when leaders lack the time or capacity to build genuine stability directly, and rules and approval layers fill that gap as a substitute for real, distributed trust and engagement. Treating bureaucracy as the root problem leads to adding more process, while treating it as a symptom points toward the actual fix, restoring leadership capacity for direct, shoulder to shoulder engagement.

What does it actually mean for a leader to get out of their “ivory castle”?

It means physically and consistently engaging with the team and the actual work, rather than managing primarily through policies, reports, and approvals issued from a distance. A leader who stays removed from the day to day work tends to rely on rules to maintain control, since they no longer have direct, personal visibility into what is genuinely happening on the ground.

Why does the article insist that “too busy” is not a sustainable excuse for a leader?

Because framing overextension as something happening to a leader, rather than something within their control to address, removes any real path toward fixing it. The article argues that genuine leadership capacity often requires deliberately removing something from a leader’s plate, rather than simply asking an already overloaded person to somehow find more time.

If you want to learn more we have:

Discover Jason’s Expertise:

Toxic Project Managers and Leadership Lessons.

Posted on September 30, 2026September 30, 2026 by Team Jason Schroeder

Read 8 min

What a Toxic Project Manager Actually Costs a Team

Here’s the deal. Early in my career, I worked under genuinely excellent superintendents at Hensel Phelps, a company I still love deeply. On two different projects, though, the project managers I reported to were toxic in a very specific, classical business management kind of way, and the damage that caused went well beyond a bad personality. I want to be direct about what that experience actually taught me, without dwelling on any individual, because the lesson matters more than the person.

Understaffed, Overworked, and Left to Figure It Out

On one of those projects, the job was genuinely understaffed. The general superintendent was pulled in multiple directions at once and often not closely engaged with what was actually happening day to day. That left an enormous amount of coordination work falling onto the field engineers, office engineers, and project engineers on site, myself included, well beyond what any of us should reasonably have been carrying alone.

I remember being exhausted, genuinely worn down from the sheer volume of work stacked onto too few people. During an actual lunch break, I put my head down on my desk to close my eyes for a few minutes. I was called into an office and reprimanded directly for it. When I pointed out that this had happened during a legitimate lunch break, the response I got back was dismissive, essentially suggesting that construction simply did not have lunch breaks in the first place. That moment, not Hensel Phelps itself, was what made me decide to leave that specific team.

Sit with that exchange for a second. The actual problem on that project was never a field engineer resting his eyes for a few minutes during a break he had genuinely earned. The actual problem was a staffing and workload situation severe enough that reaching that point of exhaustion had become possible in the first place. Punishing the symptom while ignoring the cause is exactly the kind of leadership failure that quietly drives good people out of an otherwise strong company.

What a Project Manager’s Job Actually Is

Looking back on that experience now, especially after working directly with a number of genuine industry experts to write a book specifically about what construction project management should actually look like, I see clearly what was missing. A project manager’s real job is to build the team, connect with people directly and personally, and take responsibility rather than default to blame. It means building a genuine system that prevents a field engineer from ever becoming so depleted that closing their eyes during an actual break becomes necessary just to keep functioning.

Watch for these signs a project is running on classical business management thinking rather than genuine team leadership.

A jobsite consistently understaffed relative to the actual volume of coordination work required.
Exhaustion among field engineers or office staff treated as a normal cost of doing business rather than a genuine warning sign.
Leadership more focused on personal recognition or outside pursuits than on actually engaging with the project day to day.

Why This Pattern Deserves to Be Named Directly

I do not enjoy being critical like this, and I want to be clear that everything here reflects my own experience and my own opinion, not an accusation of any specific wrongdoing. But the pattern itself is worth naming plainly, because it shows up far too often across this industry. Condescending leadership. A tendency to blame the team rather than build it. A classical business management mindset that quietly prioritizes appearances and personal significance over the actual, unglamorous work of supporting the people on a project.

That pattern rarely announces itself directly. It shows up instead in small decisions made repeatedly over months, a staffing request denied, a coaching conversation skipped, a moment of genuine struggle met with correction instead of support. None of those individual moments looks dramatic on its own. Stacked together, they add up to exactly the kind of environment that eventually pushes a genuinely capable person out the door.

I would not give a nickel for a project manager operating that way, no matter how polished they might look from the outside.

The Contrast That Actually Changed My Career

Compare that to the very first project manager and superintendent I ever worked under. They were genuinely kind, supportive, and invested in me as a person, going out of their way to offer real personal coaching and help me grow. That contrast is what ultimately shaped how I think about leadership today. The difference between those two experiences was not talent or credentials. It was whether the person leading actually saw building the team as the job, rather than something that happened to be in the way of it.

Both of those leaders were operating inside the exact same industry, often under similarly demanding schedules and real budget pressure. The circumstances were not what separated them. Their actual priorities were, and that is genuinely good news, because it means this is a choice available to any leader willing to make it, regardless of how difficult a given project happens to be.

Watch for these signs a leader is genuinely investing in building their team rather than simply managing it.

Real, personal coaching offered proactively, not only when a problem has already surfaced.
Staffing levels that reflect an honest assessment of actual coordination workload, not an assumption that people will simply absorb the gap.
A leader who is present and engaged with the day to day project, not primarily focused on external recognition elsewhere.

Why This Still Matters for Every Project Manager Today

Eventually, I found my way back to Hensel Phelps, once I had genuinely gotten away from that specific toxic environment, and went on to build a career there that I am still deeply proud of. That experience left me with a permanent, clear standard for what a project manager’s role genuinely is, and what it never should be.

I share this not to relitigate old grievances, but because that early standard shaped nearly everything I have built since, the training programs, the books, the coaching work. Every one of them traces back, in some way, to a simple decision made early in my career never to lead a team the way I once watched a team get led.

If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your organization build genuine project management leadership, staffing decisions grounded in real workload, and a culture where building the team is treated as the actual job, rather than something that gets in the way of looking good elsewhere.

So here is the challenge. Look honestly at your own project’s staffing levels against the real coordination workload your field and office engineers are currently carrying. If exhaustion has quietly become normalized as simply how the job goes, that is exactly where genuine leadership needs to step back in.

Jason Schroeder said it plainly: “I wouldn’t give a nickel for a classical business management project manager.” Build your team instead, and the rest of the job gets genuinely easier for everyone carrying it.

On we go.

FAQ

Why does understaffing a project count as a leadership failure rather than simply a budget decision?

Because understaffing shifts an unreasonable coordination burden onto the people already on site, field engineers and office staff who then have to absorb work well beyond their actual role. Leadership is responsible for recognizing when workload has exceeded what a team can reasonably sustain and adjusting staffing accordingly, rather than treating chronic exhaustion as an acceptable cost of running a lean project.

Why does the article treat a reprimand over resting during a legitimate break as more than an isolated incident?

Because it reflects a broader mindset that treats basic human needs, rest, recovery, and legitimate break time, as somehow incompatible with construction work. That mindset tends to accompany the same classical business management thinking that prioritizes appearances and output over genuinely supporting the people doing the work, which is why a single incident like this often points to a much larger cultural problem.

What is the actual difference between managing a team and building one?

Managing a team typically focuses on directing tasks and monitoring output, while building a team involves genuine investment in people, coaching, real staffing decisions that account for actual workload, and personal engagement with how the team is actually doing. The article argues that building the team is the real job of a project manager, and that managing without building tends to produce exactly the exhaustion and disengagement described here.

Lorem If you want to learn more we have:

Discover Jason’s Expertise:

Faster Software Isn’t the Solution, Fix Flow.

Posted on September 30, 2026September 30, 2026 by Team Jason Schroeder

Read 8 min

If You Need Faster Update Software, You Have a Flow Problem

Here’s the deal. A software user recently asked for faster updates, better tracking of delays and impacts, and more robust reporting on why a schedule got hit. That request sounds reasonable on the surface, and it actually points to something worth taking seriously. If you need better software to track delays and impacts more quickly, that need is itself a downstream symptom. It does not address the real root cause, which is a lack of genuine upstream flow.

The Bodyguard Analogy

Here is an analogy I have found genuinely useful. Picture a major celebrity or public figure who needs real bodyguard protection, someone like a global pop star, a world class athlete, or a head of state. That kind of protection always works the same way, with security positioned both in front and behind.

In a Takt production system, the bodyguard out front is roadblock removal, paired with genuine preparation like pre-construction meetings and the broader trade partner preparation process. The bodyguard in the back is buffers. And the actual superstar being protected, the person all of that protection exists to serve, is trade flow itself. Ask how the front bodyguard keeps that flow safe, and the answer is roadblock removal and real advanced preparation. Ask how the back bodyguard protects it, and the answer is genuine buffers. It really is that simple.

Push the analogy a little further and it explains why so many teams end up asking for the wrong kind of help. Nobody protects a genuine superstar by building a better system to document what happened after an attacker already got through. The entire point of hiring real security is preventing that breach from happening in the first place. A construction schedule deserves exactly the same standard.

Why Faster Tracking Software Misses the Point

If we keep asking for software that shows delays and impacts faster and faster, we should instead ask the question Taiichi Ohno would ask. Why do we have the impacts in the first place? Instead of building better systems to mask and manage waste after it has already happened, the actual goal should be removing that waste before it ever occurs.

Here is where I want to be direct, because this deserves real clarity rather than a soft version of the point.

If you are not fanatically finding five to ten roadblocks a day, writing them down, and actively attacking them to clear the way for trades, you do not have a genuine production system.
If you are not hosting a genuinely remarkable pre-construction meeting for every new trade at least three weeks before they start, ending with a real visual feature of work board, you do not have a well run jobsite.
If you are not aligning your supply chain and monitoring it weekly, you do not have a well run jobsite either.
If you are not pull planning and triggering the plan for a phase of work, defined correctly as an actual geographical zone rather than simply a duration, three to four months before that phase starts, you are not genuinely doing your job as a planner.

None of that requires new software to accomplish. It requires genuine discipline in the field, applied consistently, well before a delay ever has the chance to actually happen.

Notice that every single item on that list happens well before a schedule ever shows a delay. Roadblocks get caught days or weeks in advance. Pre-construction meetings happen weeks before a trade even mobilizes. Supply chain issues surface during a weekly check rather than at delivery. Pull planning happens months ahead of a phase. By the time a delay would normally show up in a report, disciplined teams have often already prevented it.

Why the Office Itself Might Be Part of the Problem

Here is a thought that has been sitting with me, and I want to share it directly. No construction company should have a genuinely nice, comfortable office. Not the operations team. Not even the finance department. A comfortable office is simply not the natural environment for people who work for a construction company.

What I actually want to see instead is a real manufacturing facility, a genuinely organized yard, open spaces where teams simulate buildings and rooms using foam and mockups, dedicated pre-planning rooms, and dynamic, open control rooms that function like a genuine situation room for one project or several at once. I want project leadership physically positioned in front of the actual work rather than tucked away in a comfortable office. Even the finance group should be embedded in open, visual, dynamic space, close enough to the work to help get trades paid and genuinely enable the project team, rather than isolated somewhere comfortable and disconnected.

Watch for these signs a company’s physical workspace is quietly working against genuine flow rather than supporting it.

Leadership and support functions physically separated from the field, with little visual connection to actual project work.
A polished, comfortable office environment that would look at home in almost any industry, rather than one built specifically around construction flow.
No dedicated space where teams can physically simulate, plan, and visualize upcoming work before it reaches the field.

I am not impressed walking into a construction company and seeing a beautiful office. I want to walk into a massive, organized manufacturing facility, a genuinely well run yard, and open, visual spaces built specifically to create optimized flow for the field, spaces where everyone in the building can actually see that flow happening in real time.

A beautiful office signals that comfort and appearance took priority somewhere along the way. A genuinely well organized yard and manufacturing space signals the opposite, that every square foot of the company’s physical footprint got built around actually supporting the work, rather than impressing a visitor who happens to walk through the front door.

Why This Matters More Than Any Reporting Feature

The honest bottom line is this. We should not want better software, nicer offices, or more detailed paperwork simply to track the wrong things happening in the wrong places more efficiently. We should be out in the field, in real physical spaces, actively preventing flow problems from ever occurring in the first place.

If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your teams build the genuine upstream discipline, roadblock removal, real pre-construction meetings, weekly supply chain alignment, and properly timed pull planning, that actually prevents delays rather than simply tracking them faster once they happen.

So here is the challenge. Before requesting a new reporting feature or a faster way to log the next delay, ask honestly whether your team is genuinely finding and clearing five to ten roadblocks a day, running real pre-construction meetings three weeks out, and pull planning a full three to four months ahead of each phase. If any of those are missing, that gap, not your software, is where your next delay is actually coming from.

Taiichi Ohno’s guiding question applies here as directly as anywhere. “Why do we have the impacts in the first place?” Answer that honestly, and the need for faster delay tracking tends to shrink on its own.

On we go.

FAQ

Why does wanting faster delay tracking software actually indicate a deeper problem?

Because a genuine need to track delays and impacts more quickly means delays are happening often enough to require that level of tracking in the first place. Addressing the root cause, preventing those delays through roadblock removal, real preparation, and disciplined planning, reduces the need for sophisticated tracking far more effectively than any reporting feature ever could.

What is the practical meaning of the bodyguard analogy for trade flow?

It illustrates that trade flow needs protection from both directions to stay genuinely safe. Roadblock removal and thorough advance preparation protect flow from problems approaching ahead of it, while real buffers protect flow from disruptions that could otherwise hit it from behind. Both pieces working together are what actually keep flow moving smoothly through a project.

Why does the article insist a construction phase should be defined by geographic zone rather than duration?

Because defining a phase purely by a length of time, rather than the actual physical zones it covers, disconnects planning from the real, physical work that has to happen there. Planning around an actual geographical zone with its own defined boundaries keeps preparation, like pull planning, genuinely tied to the specific conditions and requirements of that space, rather than an arbitrary block of time on a calendar.

If you want to learn more we have:

Discover Jason’s Expertise:

Designing Systems Around the Human Brain

Posted on September 30, 2026September 30, 2026 by Team Jason Schroeder

Read 9 min

Stop Expecting the Human Brain to Do What It Is Not Designed to Do

Here’s the deal. You cannot leave human beings unprompted and simply expect good habits, consistent safety, or reliable follow through to develop on their own. That is not a criticism of anyone’s character. It is simply an honest description of how the human brain actually works, and understanding it changes how seriously you take standard work, huddles, and visual systems.

Why the Brain Cannot Be Counted On by Default

Left to its own devices, the human brain defaults toward self preservation, not toward the disciplined behavior a jobsite genuinely needs. It wants to conserve energy rather than expend extra effort. It forgets details constantly, even important ones. It filters out information that feels inconvenient in the moment. It gets pulled toward whatever the surrounding social group happens to be doing, whether or not that direction is actually the right one.

None of that makes someone a bad worker or a bad person. It makes them human. I genuinely used to misread this myself. Before I understood how differently people can process time, attention, and focus, whether through something like time blindness or simply the ordinary limits of human attention, I assumed a person who kept showing up late or missing a detail must not care. In most cases, that assumption was wrong. The brain itself, not a lack of care, was the actual obstacle.

That shift in perspective changed how I approach a recurring problem on a jobsite. Instead of assuming the worst about someone’s intentions the third or fourth time something slips, the more useful question is whether the actual system around that person gave their brain a real chance to succeed. Usually, it did not.

Why Standard Work Is an Act of Respect, Not an Insult

Here is the real insight underneath all of this. You cannot truly respect somebody without also building stability and standardization around them. Those two things are not separate. They function together. Expecting someone to remember every detail, stay motivated to finish a task with no real reward attached, and resist the pull of distraction purely through willpower is not a high standard. It is an unfair standard, because it asks a person to fight their own biology every single day with nothing but personal discipline to rely on.

Genuine respect looks different. It looks like standard work. A standard environment. Standard visuals and labeling. A clear, repeated daily rhythm that does not depend on any one person remembering everything correctly from memory alone.

Watch for these signs a team is being asked to rely on willpower and memory instead of genuine structure.

Expectations communicated once, verbally, with no visual reminder or repeated reinforcement afterward.
Recurring mistakes blamed on carelessness rather than traced back to a missing checklist or unclear standard.
No daily rhythm reinforcing the same core expectations every single day.

Why Daily Repetition Is Not Redundant, It Is Necessary

This is exactly why a genuine morning worker huddle matters so much, and why skipping it causes real damage. If you do not run one, every single brain on your crew will naturally filter out whatever you were hoping they would remember. That is not a guess. It is the predictable, biological result of leaving expectations unreinforced.

No general contractor gets to complain that their people are not following direction if that direction was never actually repeated, visually reinforced, and made genuinely easy to find. Two minutes of training every single day. A clear, consistent answer to the question, what is our culture, and how do we do business here, repeated daily rather than explained once and assumed to stick.

Watch for these signs your team’s daily habits are actually holding because of real structure, not lucky circumstance.

A consistent daily huddle covering the same core expectations, reinforced rather than assumed.
Standard work documented visually, somewhere anyone can find it without needing to ask.
New behaviors introduced gradually, with genuine reinforcement, rather than announced once and expected to stick immediately.

Why This Does Not Excuse a Lack of Effort Either

None of this means removing personal responsibility from the equation entirely. Someone still has to decide to be a genuinely hard worker. Someone still has to choose to be fully invested, to put in real time, and to at least try. As long as a person is genuinely doing that, the responsibility shifts to fixing the system around them, rather than expecting their brain alone to compensate for a system that was never actually built to support them.

That distinction matters. It is not about lowering the bar or making excuses for poor effort. It is about recognizing that even the most genuinely committed person cannot out-willpower a system with no real structure behind it, day after day, indefinitely.

Think about how quickly even a highly motivated person burns out trying to hold an entire standard in their head alone, catching every detail purely through vigilance, with no checklist or visual system backing them up. That is an exhausting way to work, and it rarely lasts. A system that shares the load is what actually makes sustained excellence realistic over the full length of a project.

Why Standard Work Practices Like Six S Matter So Much

Paul Akers has written extensively about the value of standard work and small, continuous improvements, and that same discipline applies directly here. A genuine daily six S practice, covering everything from safety to sorting and cleanliness, works precisely because it does not depend on anyone remembering to do it well from pure motivation alone. It becomes part of the actual rhythm of the day, reinforced through repetition rather than willed into existence through personal discipline every single morning.

That is the entire underlying logic behind training elevating people and stability elevating systems. Training gives someone the knowledge. Stability, built through standard work and consistent daily structure, is what actually lets that knowledge hold up against the very real limits of human memory, focus, and energy.

Neither piece works well without the other. Training without stability produces people who know what to do but have no system reinforcing it once the training session ends. Stability without training produces a rigid structure nobody actually understands or believes in. Put them together, and the system starts carrying weight that used to rest entirely on individual willpower.

Building Real Structure Into Your Own Team

None of this requires assuming the worst about anyone’s character or effort. It requires building the kind of stability that respects what human beings genuinely are, rather than what we might wish they were capable of sustaining through willpower alone.

If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your teams build the standard work, daily huddles, and visual systems that make genuinely good habits sustainable, rather than expecting memory and motivation to carry that weight on their own.

So here is the challenge. Pick one expectation on your own project that currently depends entirely on people remembering it correctly, with no huddle, checklist, or visual reminder reinforcing it. Build that reinforcement in this week, and watch how much more consistently that expectation actually gets followed.

Jason Schroeder said it plainly: “Stop expecting the human brain to do what it’s not designed to do.” Build the structure instead, and watch how much more that same team is actually capable of.

On we go.

FAQ

Why does the article treat forgetting instructions or missing a detail as a systems problem rather than a personal failing?

Because the human brain naturally filters information, forgets details, and gravitates toward distraction regardless of someone’s genuine intentions or work ethic. Treating every lapse as a character issue misses the more useful question, which is whether the expectation was actually reinforced through a visual system or a repeated daily habit, rather than communicated once and assumed to stick.

Why does the article insist that standard work is an act of respect rather than a rigid, impersonal system?

Because expecting someone to rely purely on memory and willpower to meet every expectation, with no reinforcement or support, sets them up to fail against limits that are genuinely biological rather than a matter of character. Building real structure around people, through standard work and consistent daily habits, acknowledges what human beings are actually capable of sustaining, which the article treats as the more respectful approach.

Does building this kind of structure remove personal responsibility from workers?

No. The article is clear that someone still has to choose to work hard, stay invested, and genuinely try. What shifts is where the responsibility for consistency sits once that effort is present. Rather than expecting willpower alone to overcome a system with no real support behind it, the article argues leadership’s job is to build the structure that lets genuine effort actually succeed consistently.

Why does daily repetition matter more than a single thorough explanation of expectations?

Because a single explanation, no matter how thorough, still competes against the brain’s natural tendency to forget and filter out information over time. Repeating core expectations daily, through a consistent huddle or visual reminder, reinforces them before they have a chance to fade, which is why the article treats repetition as necessary rather than redundant.

If you want to learn more we have:

Discover Jason’s Expertise:

Training: The Component That Makes Every System Work

Posted on September 30, 2026September 30, 2026 by Team Jason Schroeder

Read 9 min

What Happens When You Do Not Have Real Training

Here’s the deal. Of everything I talk about across this entire system, training might be the single hardest one to overstate. Skip it, and every other component you have built, every system, every plan, every good intention, simply stops functioning the way it was designed to.

What Real Training Actually Covers

When I talk about training, I mean genuine individual professional development built around the whole builder, not just their technical role. That means covering the learning habit itself, a real personal organization system, the short term habits and the long term habits that define a genuine builder, a real planning method, a functioning meeting system, standing tactical orders, and the Lean way of thinking underneath all of it. The personal organization system is one of the most important pieces in that entire list, and team balance and health need to be taught too, even though that piece belongs more to a related system than to training itself.

Only once that foundation exists is someone actually ready to learn the specific Lean construction systems, the First Planner System, the Takt production system, and the Last Planner System, along with whatever role specific training their position actually requires.

The Real Formula for Scaling in This Industry

Companies scale successfully in construction by adopting a genuine operating system, thoroughly training everyone in that system, and then running field walks for eight to eighteen months, holding teams accountable the entire time. Real accountability means clarity, training, and support together, helping a team implement shoulder to shoulder rather than simply demanding results and walking away.

This formula works consistently, every time it gets genuinely applied. Skip even one of those three pieces, and a client experiences plenty of change without ever reaching the full results. Implement all three together, and the full results genuinely follow.

What the Research Says Happens Without It

The research behind How Big Things Get Done, by Bent Flyvbjerg and Dan Gardner, identifies training as one of the primary factors determining whether projects actually succeed. Skip it, and three specific things happen. Your team ends up going in different directions. Your systems end up substandard, regardless of how good they looked on paper. And people’s brains default straight to bad behavior, because that default is simply what happens without proper training to override it.

Rushing, pushing, and panicking happen because of ignorance. Keeping everything locked inside your own head happens because of ignorance. Toxic behavior happens because of ignorance. Not knowing how to genuinely partner with a team happens because of ignorance. Not knowing how to schedule properly happens because of ignorance. Even loving CPM happens because of ignorance.

Watch for these specific signs that missing training, not bad character, is the real root cause of dysfunction on your own project.

A team consistently working toward different, uncoordinated priorities with no shared plan actually driving them.
Leaders keeping critical information locked in their own heads rather than documented in a genuine system.
Recurring toxic behavior that seems to trace back to nobody ever being taught a genuinely better way.

Why Training Elevates People and Stability Improves the System

I love a saying that captures this well. Training elevates humans, and stability improves the system. There is a related insight worth sitting with too, one I only recently put into words clearly. A bad system will break a human every single time, but it takes a genuinely trained guardian to actually fix that system rather than simply be broken by it. The only way to become that kind of guardian is through real training. That means doubling down on training, and honestly, it means doing real work to undo some of the damage a formal education system leaves behind, one that in my own view teaches very little that is genuinely practical and does real harm to how people learn to interact with each other.

What real, practical education on a project site should teach is humility, genuine open mindedness, a willingness to follow direction first before challenging it, and the discipline to actually implement what is being taught rather than simply absorbing it passively.

Why “They Won’t Learn” Is a Genuinely Bad Excuse

I get genuinely tripped up by companies that assume superintendents and foremen simply will not learn, will not read a real book, and cannot handle training that runs longer than a few minutes because they will not pay attention. That framing coddles people who do not need to be coddled at all. These are smart, capable human beings. Nearly anyone with reasonable aptitude can learn genuinely remarkable things, and what actually determines whether they do comes down to the expectation leadership sets for them, not some inherent limit on what they are capable of.

Watch for these signs an organization is quietly underestimating its own foremen and superintendents rather than genuinely investing in them.

Training materials deliberately shortened out of an assumption that field leaders will not engage with real depth.
No expectation that foremen and superintendents read or study genuine industry material on their own.
A pattern of treating field leadership roles as positions to manage rather than people to develop.

Why the Default Human Instinct Actually Favors CPM

Without training, every behavior I typically push back against becomes the natural default, because it aligns with basic human instinct. People gravitate toward CPM specifically because our natural instincts lean toward fear, fighting, jealousy, hoarding resources, blaming and hurting others, taking rather than giving, overburdening people around us, and treating other human beings as interchangeable, usable resources rather than people. Every one of those instincts aligns naturally with the classical business management thinking CPM was built on.

Aligning with Takt instead requires leaning deliberately toward something better, and that shift genuinely does not happen without real training behind it. Skip training entirely, and you do not simply have a weaker version of the system. You genuinely have nothing at all.

Building Real Training Into Your Own Organization

None of this happens through a single seminar or a shortened video nobody actually engages with. It requires the full sequence, a genuine operating system, thorough training in it, and sustained field walks over many months, holding people accountable through real clarity, training, and support together.

If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your organization build exactly this kind of complete training foundation, rather than assuming your field leaders cannot handle genuine depth and shortening their development as a result.

So here is the challenge. Look honestly at your own training program and ask whether it treats your foremen and superintendents as capable of genuinely remarkable growth, or whether it has quietly been shortened and simplified based on an assumption that they will not engage with anything more. That assumption itself may be the single biggest thing standing between your current results and what your team is actually capable of.

Jason Schroeder said it plainly: “A bad system will break a human every time, but it’s the guardians that fix the system.” Train your people to become those guardians, and watch what they are actually capable of doing with a system worth their effort.

On we go.

FAQ

Why does the article insist that behaviors like rushing, panicking, and loving CPM trace back to ignorance rather than character?

Because those behaviors reflect the natural human default in the absence of better training, not a deliberate choice to behave poorly. People fall back on fear-driven, self-protective instincts when they have never been taught a genuinely better alternative, which is why the article treats these patterns as fixable through training rather than as fixed personality traits.

What is the actual difference between a company’s operating system and its training program?

The operating system is the overall framework a company runs on, its business systems, planning methods, and processes. Training is what actually equips people to understand and use that operating system correctly. A strong operating system without genuine training behind it tends to produce plenty of visible change without ever reaching full results, since people are following a system they do not fully understand.

Why does the article push back so strongly against shortening training for foremen and superintendents?

Because that practice is based on an unproven assumption that field leaders cannot handle genuine depth or sustained attention, which becomes a self-fulfilling limitation once training gets shortened to match it. The article argues that most people with reasonable aptitude can learn far more than they are typically given credit for, and that the real limiting factor is the expectation set for them rather than their actual capability.

What does the article mean by describing a well trained leader as a “guardian” of the system?

It means someone equipped through real training to recognize when a system itself is flawed and to actually fix it, rather than simply absorbing the damage a broken system causes and passing that damage along to others. Becoming that kind of guardian, according to the article, requires genuine training, since without it, people tend to default to blaming themselves or others rather than addressing the actual system at fault.

If you want to learn more we have:

Discover Jason’s Expertise:

Onboarding & Orientation: Your Workforce’s First Impression

Posted on September 30, 2026September 30, 2026 by Team Jason Schroeder

Read 9 min

What Happens When Onboarding and Orientation Is Missing

Here’s the deal. I like to walk through exactly what a new worker’s first day actually feels like when onboarding and orientation are missing or done poorly, because the story is more revealing than any checklist could ever be.

A First Day Worth Actually Imagining

Picture a new worker arriving on a project site with no signage anywhere, unable to even find the parking lot. Meanwhile, the trailer where office staff work has genuinely nice bathrooms, a comfortable lunch area, and real perks. The field worker gets none of that consideration. They rush to grab their tools, desperately search for a bathroom, and when they finally find one, there is no toilet paper waiting for them either. That is the very first impression of the project, before a single hour of actual work has happened.

From there, they try to find the trailer with no clear direction. A grumpy office admin barely points them toward somewhere to sit. Nobody tells them where to put their belongings, what is actually expected of them, or whether they are already in trouble. They wait nervously in a conference room, checking the time, not properly hydrated, increasingly anxious. Eventually a visibly disengaged project engineer walks in, starts an orientation video with no real connection to the person watching it, and leaves to go check email, treating the entire moment as an inconvenience rather than someone’s actual introduction to the company. That video may not even be in a language the worker genuinely understands.

Notice how many separate small failures stack on top of each other in that sequence. No signage. No facilities. No clear direction. No genuine human presence during orientation. No accommodation for language. Any single one of those failures alone might seem minor. Stacked together on someone’s very first morning, they add up to a genuinely miserable introduction to the company, one that took real effort not to notice and fix.

Once it ends, they get an orientation sticker and are told to go figure it out. They trip over things trying to locate their own crew, and when they finally find it, they get reprimanded for being late, despite the entire process itself being what delayed them in the first place. Nobody, anywhere, ever wants to work hard for a company after an experience like that.

Why This Reaction Is Completely Predictable

That worker now feels genuinely disrespected, unseen, and possibly even a little traumatized by how their first day actually went. They are already nervous simply being on a new site, and now they are expected to do demanding physical work, in whatever heat or cold the day brings, for people they do not yet trust in the slightest.

Ask yourself honestly what motivation that person now has to do the general contractor a genuine favor. None. Nobody, having just been treated that way, wakes up the next morning determined to go above and beyond for the company that put them through it. Whatever goodwill they might have arrived with that morning is already gone by the time they actually reach their crew.

Watch for these specific signs your own onboarding process is creating exactly this kind of first impression, whether or not anyone has said so directly.

No clear signage or directions guiding new workers to parking, restrooms, or the actual jobsite trailer.
Field workers given noticeably worse facilities than office staff working the same project.
New arrivals left waiting with no clear explanation of what is expected of them or where they belong.

Why Missing Onboarding Costs You Every Single Lean Component

If your onboarding and orientation system is genuinely weak, two things happen almost immediately. Workers will not actually understand the real safety requirements on the site, no matter how thorough the paperwork looked on paper. And you will end up with a genuinely upset workforce, one that will not just drift in different directions but may actively vandalize the site, graffiti the bathrooms, and leave the same physical mess described when a workforce is never won over in the first place. That is not random misbehavior. Human beings are reciprocal. They are like mirrors, and how they were treated on day one reflects directly in how they treat everything afterward.

Watch for these downstream consequences that trace directly back to a poor first day, even when they show up weeks or months later.

Quality problems appearing on crews who never felt genuinely welcomed or invested in from the start.
Total participation and improvement suggestions completely absent from a workforce that feels unseen.
Crews doing the visible minimum required, disengaged and mentally checked out for the rest of the project.

Here is the part that genuinely surprises people. You might assume that even with an alienated workforce, you still at least get the physical labor you are paying for. You do not. You lose the work of their heads and their hearts, certainly, but you also lose real effort from their hands, because disengaged people find countless small ways to give less than their genuine best without ever technically refusing to work.

That gap is expensive precisely because it is so hard to point to directly. Nobody writes a report saying morale caused this delay. It shows up instead as slightly slower pace, slightly more rework, slightly less willingness to speak up about a problem before it becomes serious, all quietly traceable back to a first day that told the workforce exactly how much they actually mattered.

Why This Single Moment Deserves So Much More Attention

A new worker’s first day is genuinely a captive audience moment, someone arriving ready to connect, ready to be shown they matter, before any resentment has had the chance to build. Waste that moment, and the consequences follow you through the entire remainder of the project, creating stress that genuinely wears on a career over time, not just a single bad week.

That stress compounds too. A superintendent managing a disengaged, resentful workforce spends real energy every single day fighting problems that a genuinely good first impression would have prevented from ever taking root. Over the life of a project, that difference adds up to a meaningfully harder job, carried entirely by leadership, for a problem that was actually solvable on day one.

If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your teams build a genuinely welcoming onboarding and orientation process, one that treats a worker’s first day with the same seriousness given to safety training itself, rather than treating it as an administrative box to check quickly.

So here is the challenge. Walk through your own onboarding process from the exact moment a new worker arrives at your gate, and be honest about every single step along the way. If you would not want your own child to experience that first day exactly as designed, that is precisely where the redesign needs to begin.

Jason Schroeder said it plainly: “They’re reciprocal. They’re like mirrors.” Give a new worker a genuinely good first day, and that reflection follows you for the rest of the project.

On we go.

FAQ

Why does the article treat a new worker’s first day as more important than it might initially seem?

Because a new worker arrives as a genuine captive audience, open to connection and ready to be shown they matter, before any frustration or distrust has had the chance to build. That window closes quickly once a poor first experience sets a different tone, which is why the article treats the first day as disproportionately important relative to how little attention it often receives.

Why does the article claim workers lose “the work of their hands” too, not just their heads and hearts?

Because genuinely disengaged workers rarely refuse outright to do their job, they simply find countless small, hard to detect ways to give less than their real effort. That erosion in physical productivity is harder to notice than an obvious refusal to work, which is exactly why it can quietly damage a project’s quality and schedule for months without an obvious single cause.

Why does the article connect poor onboarding directly to vandalism and site disrespect?

Because human behavior tends to mirror how people themselves were treated, and a worker who felt disrespected and unseen on their very first day is far more likely to treat the site itself with that same lack of respect. This reflects the same reciprocity principle that governs how a workforce treats a building overall, applied specifically to the earliest possible moment that relationship actually begins.

What is the practical difference between having an orientation process and having a genuinely good one?

A basic orientation process might legally cover required safety information without any real human connection behind it, such as an unengaged presenter or a video in a language the worker does not fully understand. A genuinely good process ensures the worker actually understands the material, feels welcomed rather than processed, and leaves the experience with real clarity about expectations and where they belong on the team.

If you want to learn more we have:

Discover Jason’s Expertise:

General Offerings

Company Offerings

Systems

Month: September 2026

Why a Construction Company Shouldn’t Have a Corporate Office.

Strive for Perfection.

New Constraints Reveal System Bottlenecks.

How Bureaucracy Destroys Leadership

Toxic Project Managers and Leadership Lessons.

Faster Software Isn’t the Solution, Fix Flow.

Designing Systems Around the Human Brain

Training: The Component That Makes Every System Work

Onboarding & Orientation: Your Workforce’s First Impression

Subscribe Now

Our Office

Get In Touch

Company

Follow Us

General Offerings

Company Offerings

Systems

SUBSCRIBE NOW !

Subscribe to our newsletters and stay updated!