October 2026 - Page 14 of 14 - Elevate Constructionist

AI Slop or a Tool for Better Work?

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

Read 9 min

Why AI Generated Images Are Not “Slop” When Paired With Real Expertise

Here’s the deal. AI generated visuals get dismissed constantly as low effort filler, and I genuinely understand why that reputation exists in a lot of places online. Used the way I actually use it, to illustrate real construction and Lean concepts I have genuinely lived through, it is something completely different, and I want to explain exactly why.

Why Confidentiality Used to Limit What I Could Actually Share

Some of the best ideas I encounter come from projects covered under a genuine confidentiality agreement, which means I cannot share the real photos or specific details directly. Before AI became a genuinely useful tool for this, that meant a lot of real, valuable lessons simply stayed locked away, unable to help anyone beyond the specific project where they happened.

Now I can take an actual photo, extract the underlying concept it illustrates, and have AI recreate that concept as a new, original image, one that teaches the exact same principle without ever violating the confidentiality agreement or revealing anything genuinely protected. That is not cutting corners. It is finding a genuinely ethical way to share a lesson that would otherwise never reach anyone at all.

This matters more than it might first appear. Some of the most advanced, genuinely impressive implementations of Lean and Takt thinking I have encountered exist specifically inside organizations that cannot let any of it be photographed or discussed publicly. Without a way to responsibly recreate those lessons, that knowledge would simply stay locked behind a confidentiality agreement forever, benefiting nobody outside that one project.

Why Recreating International Examples Helps People Actually Learn

A related problem shows up whenever I share real examples from Japan. People often dismiss them immediately, assuming the lesson only applies there and has nothing to do with their own project here. Recreating the same underlying concept as an original illustration, rather than relying on the original photo alone, often helps people actually engage with the idea honestly, rather than mentally filing it away as something foreign and irrelevant before they have genuinely considered it.

Stripping away the specific location or context, while keeping the actual principle fully intact, tends to force a more honest evaluation of the idea itself. People end up judging the concept on its own merits rather than dismissing it based on an assumption about where it came from.

I have also used this to illustrate real things I did earlier in my career, moments I never happened to photograph at the time, but remember clearly enough to describe accurately. Turning an accurate memory into a genuine visual teaching tool has given me more real content to actually teach with than I have ever had available before.

Think about how much genuinely valuable experience exists in the industry purely as memory, never documented visually because nobody happened to have a camera out at the right moment. That knowledge used to simply disappear over time. Now it can actually become a real teaching resource, as long as the person describing it genuinely knows what they experienced and checks the result carefully against that real memory.

Here are the specific situations where this approach has genuinely proven valuable.

Recreating a confidential project detail as an original image that teaches the same lesson without revealing anything protected.
Turning an international example into a more universally relatable illustration, so people engage with the actual concept rather than dismissing it as foreign.
Visualizing a real past experience that was never photographed at the time, based on an accurate firsthand description of what actually happened.

Why the Difference Comes Down to Genuine Quality Control

None of this works without real expertise sitting behind it. Every image I generate this way gets checked personally against my own firsthand knowledge. I have actually done these things, actually seen them happen, and know directly that what is being illustrated is genuinely possible and accurate. That review process is exactly what separates a genuinely useful teaching tool from the kind of low effort, unreviewed content that earns AI generated work its poor reputation in the first place.

That distinction is genuinely the whole point. Anyone without real domain knowledge can generate an image that looks technically polished but contains details that are subtly or obviously wrong. Someone who has actually spent years in the field can catch those errors immediately, which is exactly why expertise, not the tool itself, is what determines whether the final result genuinely teaches something true.

Watch for these signs AI generated content is actually being used responsibly, with real expertise providing genuine quality control.

The person generating the image has genuine, firsthand experience with the concept being illustrated.
Every image gets reviewed carefully before being shared, rather than published exactly as first generated.
The underlying concept traces back to something real and verifiable, rather than an invented or speculative scenario.

Why This Has Genuinely Accelerated My Own Work

Because of this approach, I have been able to write books at a pace I never thought was possible, research more thoroughly, and pull together material from across a much wider range of real sources than I could have managed working entirely alone. The volume of genuinely useful teaching material I can now produce has grown significantly, and the quality has not suffered, because real expertise still sits behind every single piece before it ever gets shared.

I genuinely believe the volume and the quality are connected rather than in tension with each other. Producing more material faster only works well when the underlying review process stays just as rigorous as it would be for a single, slowly produced piece of work. Skip that review, and speed simply amplifies whatever mistakes slip through, which is exactly the trap worth avoiding.

Why I Think This Technology Deserves a Fair Chance

New tools often face real skepticism before people fully understand how to use them well, and that skepticism tends to fade once the genuine value becomes clear through actual results rather than theoretical debate. I would rather keep using AI thoughtfully, with real expertise and genuine review behind every piece of content it helps me create, than dismiss the whole approach because of how poorly it gets used elsewhere.

That skepticism is not unreasonable either. Plenty of AI generated content genuinely deserves the criticism it gets, precisely because it skips the review process entirely. The goal is not defending every use of the technology indiscriminately. It is making the case that thoughtful, expertise driven use is a genuinely different thing from the low effort version people are rightly frustrated by.

If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your teams think through how to use AI responsibly in your own training and documentation, pairing it with real, firsthand expertise rather than treating it as a shortcut around genuine knowledge.

So here is the challenge. If you are using AI to create training content, checklists, or documentation of your own, ask honestly whether genuine expertise is actually reviewing what comes out the other end. That single habit is what determines whether the result is a genuinely useful teaching tool or exactly the kind of unreviewed content people are right to be skeptical of.

Jason Schroeder said it plainly: “I QC every image. I’ve done it, I’ve seen it, I know it’s possible.” That standard, not the tool itself, is what actually determines whether AI generated content is worth sharing.

On we go.

FAQ

Why does using AI to recreate a confidential project detail avoid violating a confidentiality agreement?

Because the recreation illustrates the underlying concept or lesson rather than reproducing the actual protected photo, document, or specific project detail itself. That distinction lets a genuinely valuable lesson reach a wider audience without exposing anything a client or partner genuinely expected to remain confidential.

Why might recreating an international example help people engage with a lesson more than the original photo would?

Because people sometimes mentally dismiss an example as culturally specific or irrelevant to their own situation before genuinely considering whether the underlying principle actually applies. A recreated, more universally relatable illustration can help someone engage with the actual concept honestly, rather than filing it away as something foreign that does not apply to their own work.

What specifically separates responsible use of AI generated content from the kind of “AI slop” people criticize?

Genuine firsthand expertise reviewing every piece of content before it gets shared, rather than publishing whatever AI produces without real scrutiny. Content grounded in something the creator has actually experienced and verified, checked carefully rather than accepted automatically, is fundamentally different from content generated and shared with no genuine review behind it.

Why does the article compare skepticism toward AI to historical skepticism toward earlier technologies?

To illustrate that genuine unfamiliarity with a new tool often produces real skepticism that fades once people see how it can actually be used well, through real examples rather than abstract argument. The comparison is not meant to dismiss legitimate concerns about the technology, but to suggest that thoughtful, expertise driven use tends to demonstrate real value more effectively than theoretical debate about whether the tool itself is good or bad.

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.

Accountability vs. Count-On-Ability

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

Read 8 min

It Is Not Accountability, It Is Count-On-Ability

Here’s the deal. I have been sitting with the word accountability for a while now, and I think the way most of us in the United States use it has drifted away from what it should actually mean. A small shift in how I think about that single word has changed how I approach holding anyone to a real standard.

What I Learned in Japan About Discipline

Traveling to Japan on a real Lean study trip with Paul Akers, I heard him make a point that stuck with me. Discipline is not actually a useful concept in Lean thinking. Expecting a human being to simply be disciplined through raw willpower alone is not a realistic standard to hold anyone to. Real Lean thinking instead focuses on good systems and visual tools that actually help people succeed, rather than expecting internal willpower to carry the entire weight on its own.

I also heard something directly from the director of the cleaning crew responsible for one of Japan’s famously fast bullet train turnarounds. When it comes to holding someone accountable, from a leadership standpoint, it really comes down to clarity, training, and support. If you want someone to do something well, you are clear with them about what that actually looks like, you provide real training, and then you support them in carrying it out.

That crew is famous for turning around an entire train car in a matter of minutes, to an extraordinarily high standard, over and over, consistently. Nobody achieves that level of performance through fear of a lecture. It comes from a team that has been given clarity about the standard, real training in exactly how to meet it, and consistent support that makes hitting it repeatable rather than a lucky exception.

Why the Common Version of Accountability Bothers Me

I love this country, and I am not criticizing it here. But when people in the United States say they are going to hold someone accountable, it usually means something closer to a stern lecture, a sharp confrontation, or some version of visibly expressing frustration at someone. Every time I hear that phrase used that way now, after hearing how that Japanese leader described it, it stops sitting right with me.

Jocko Willink writes about what leadership actually requires too, and the more I sit with all of this together, the more convinced I am that the common American version of accountability has drifted pretty far from what the word should actually mean.

Watch for these signs “accountability” has quietly become a euphemism for confrontation rather than support in your own organization.

The phrase “I’m going to hold them accountable” consistently followed by a lecture, a reprimand, or visible frustration rather than any real support.
No clarity or training actually provided before someone is expected to meet a standard they were never set up to reach.
Accountability treated as something that only happens after a failure, rather than something built in from the very start.

The Real Insight: Count-On-Ability

Here is the reframe that changed things for me. At its root, accountability is really about count-on-ability. Can I actually count on this person to do what they have committed to, or what belongs to their role. That is the real question underneath the word, whether most people actually use it that way or not.

Once you see it that way, holding someone accountable stops meaning confronting them after a failure. It means holding them count-on-able, meaning supporting their ability to actually be someone you can count on. And supporting that ability comes down to the exact same three things. Provide real clarity about what is actually expected. Provide training so they are actually equipped to meet that expectation. Provide real support throughout, so they are not left to figure it out entirely alone.

Notice how completely the responsibility shifts once you frame it this way. The common version of accountability puts the entire weight on the individual after something has already gone wrong. Count-on-ability puts real weight on the leader beforehand, asking whether they actually did their part to make success possible in the first place.

Why This Distinction Actually Matters in Practice

If holding someone accountable means throwing a hard hat down and delivering a sharp lecture, that approach might make the person delivering it feel better in the moment, and I doubt it produces the result anyone actually wants. If holding someone count-on-able means backing them up with clarity, training, and real support so they can actually fulfill their part of the agreement, that is something I can stand behind completely.

I think the confrontational version persists mainly because it feels like doing something in the moment, a visible, immediate reaction to a real problem. Count-on-ability requires more patience and more upfront investment, which makes it far less satisfying emotionally in the short term, even though it produces dramatically better results over time.

Watch for these signs a leader is practicing count-on-ability rather than the more common, confrontational version of accountability.

Clear expectations set before work begins, rather than only clarified after something has already gone wrong.
Real, ongoing training treated as a part of holding someone to a standard, not a separate, optional activity.
Visible support and backup offered proactively, rather than criticism delivered only once a commitment has already been missed.

Why This Small Shift in Language Helps

I know this might sound like I am simply playing with words here, and in a real sense, I am. But that small shift changed how I personally think about holding anyone, including myself, to a real standard. It moved the whole concept away from confrontation and squarely toward support, which is exactly where I believe it should have been the entire time.

I have started applying this to myself too, which is honestly the harder half of it. Before getting frustrated that I could not count on myself to follow through on something, I now ask whether I actually gave myself the same clarity, training, and support I would want to give anyone else. Usually the honest answer is no, and that is a far more useful place to start than simply being disappointed in myself after the fact.

If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your teams build count-on-ability into your own leadership approach, providing the clarity, training, and support that actually make someone worth counting on, rather than defaulting to confrontation once something has already gone wrong.

So here is the challenge. The next time you catch yourself about to hold someone accountable, pause and ask whether you have actually given them clarity, real training, and real support first. If any of those three is missing, that gap, not the person you are about to confront, is where the real problem is actually sitting.

Jason Schroeder said it plainly: “It’s not accountability. It’s count-on-ability.” Support someone’s ability to be counted on, and the confrontation you used to think you needed rarely becomes necessary at all.

On we go.

FAQ

Why isn’t discipline a useful concept in Lean thinking?

Because expecting a person to succeed purely through internal willpower places the entire burden on an individual’s self-control, rather than building systems and support that make success achievable in the first place. Lean thinking instead focuses on designing the environment and the process so that success does not depend entirely on one person’s personal discipline holding up under pressure.

What is the actual difference between “holding someone accountable” and “holding someone count-on-able”?

Holding someone accountable in its common usage typically means confronting them after a failure has already happened, often through criticism or a sharp conversation. Holding someone count-on-able means proactively supporting their ability to succeed through clarity, training, and support, which shifts the entire focus from reacting to failure toward actively preventing it.

Why does this reframe connect directly to clarity, training, and support specifically?

Because those three elements represent what a leader can actually control and provide before expecting someone to meet a real standard. Clarity ensures the expectation is understood, training ensures the person is actually equipped to meet it, and support ensures they are not left to figure out the rest entirely on their own, all of which build count-on-ability rather than assuming it will simply appear on its own.

Does reframing accountability this way mean a leader should never address a failure directly?

No, I am not arguing against addressing real failures. My point is that accountability starts well before any failure occurs, through clarity, training, and support provided up front. When a real gap does happen despite that preparation, addressing it is still necessary, but I suggest checking honestly whether the person was actually set up to succeed in the first place before assuming the failure reflects only their own shortcoming.

If you want to learn more we have:

Discover Jason’s Expertise:

What Does “External Email Only” Mean?

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

Read 9 min

Why We Only Use Email for External Communication

Here’s the deal. I have spent years on a mission to eliminate email from how our own organization actually communicates internally, and the rule we have landed on is simple to state, even though it takes real discipline to actually follow. Email is for external communication only, and even that category should stay narrow.

Why I Developed Such a Strong Reaction to Waste

Paul Akers writes in Two Second Lean about learning the eight forms of waste well enough to recognize them instantly, everywhere, once you understand them. I prefer his own ordering of that list over some of the more common acronyms people use, and once those eight wastes are memorized, you start noticing them constantly in your own daily work.

I want to be honest that this can become a real problem if it goes unchecked. Once you start seeing waste everywhere, it becomes tempting to react to it with more intensity than is actually healthy. I have had to be careful about that myself. The way I motivate my own brain to actually change a habit is developing a real, visceral dislike for the waste itself, the same reaction most people would have to discovering a pest infestation somewhere in their home. That reaction works for me personally, and I recognize it runs a little hot compared to how most people would describe the same frustration.

I share that honestly because I do not think everyone needs to feel this intensely about it to benefit from the underlying point. A calmer, more measured version of the same realization, simply noticing clearly how much time a bad habit actually costs, tends to work just as well for most people without the same emotional charge behind it.

Email became exactly that kind of target for me. Back-to-back meetings and constant email checking bother me at that same intensity, because I have come to see them as a direct drain on the actual value a leader should be creating.

Why Email Fails as an Internal Communication Tool

Email is slow, often taking roughly four times longer than a direct conversation or a quick message through a real-time tool. It is prone to miscommunication, since tone and nuance rarely survive translation into a written message the way people intend them to. And from a legal standpoint, it is often worse than people assume. In-house legal counsel frequently dislikes email specifically because poorly worded messages create a permanent, discoverable record of exactly the kind of casual misstatement that causes real problems later.

People often assume the opposite, that keeping everything in email protects a company legally by creating a paper trail. In practice, a large volume of casual, unfiltered email often creates more legal exposure than it prevents, since every message becomes a permanent record regardless of how carefully it was actually worded in the moment.

Watch for these signs email has quietly become the default in your own organization for things it was never actually well suited to handle.

Internal team members spending significant portions of their day answering email rather than being present with the actual work.
Critical decisions sitting in a queue, batched and delayed, rather than resolved through a quick real-time conversation.
Leaders physically at their desks managing an inbox instead of out in the field where leadership actually happens.

Why “External Only” Does Not Mean What People Assume

Here is the clarification that matters most. External does not mean anyone outside your own office, which some people hear as permission to email everyone they do not sit directly next to. It means a small, carefully selected list of situations where email is actually the right tool.

For anything internal, your own team, your own trades on your own project site, even other departments inside your own organization, default entirely to faster, real-time tools instead. Project management platforms, team messaging tools, radio, or simply a real conversation. There is no good reason to route internal communication through email when faster, more direct options already exist.

That default has to be absolute to actually work. The moment one internal exception gets made, a quick update here, a reminder there, the habit starts creeping back in, and before long email has quietly reclaimed territory it should never have had in the first place.

External use belongs to a narrow, specific category instead.

A brand-new potential client or a new vendor and trade partner your organization has not yet established a faster communication channel with.
Correspondence with another party’s legal counsel, where a documented, formal written record is actually appropriate and expected.
Any situation where you lack proximity or a faster communication channel, and legal counsel specifically confirms that a documented email is the correct approach for that exact circumstance.

That list should stay short. It is not a loophole back into heavy email use. It is a deliberate, narrow exception to an otherwise firm default.

I want to be direct about why this narrowness matters so much. The moment “external” quietly expands to include anyone slightly outside a person’s immediate daily circle, the entire discipline collapses back into exactly the habit it was meant to replace. Keeping the list short requires actively resisting that drift, not just defining it clearly once and assuming it will hold on its own.

A Practical Technique Worth Adopting

Paul Akers reportedly uses an auto-reply on his own email specifically redirecting people toward faster communication channels, letting correspondents know that another method will get them a response several times faster. That single habit keeps even his external email volume low, since he actively pivots nearly everyone toward quicker, more direct communication whenever possible.

The lesson underneath that habit is worth repeating. Even in the narrow category of situations where email applies, the goal is still moving people toward faster communication whenever a reasonable alternative exists, rather than treating the external label itself as a reason to stop looking for a better option.

Building This Discipline Into Your Own Organization

None of this requires eliminating email entirely overnight. It requires being honest about which communications belong there, and building real habits and tools that make faster, more direct communication the actual default for everything else.

If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your teams build this same external-only discipline, moving internal communication onto faster, more direct tools while keeping email reserved for the narrow situations where it belongs.

So here is the challenge. Track your own email volume for one full week and sort every message into internal or external. If the internal pile is larger than the external one, that gap is exactly where your own organization can reclaim real time currently being lost to a tool that was never actually built for that purpose.

Jason Schroeder said it plainly: “External does not mean I get to email everybody outside my office. It means a very small, very selective list.” Keep that list narrow, and watch how much time comes back to the rest of your day.

On we go.

FAQ

Why is email a poor fit for internal team communication specifically?

Because internal communication generally benefits from speed and real-time back-and-forth, which email structurally cannot provide as efficiently as a direct conversation, a radio call, or a real-time messaging tool. Email’s batching and queuing nature, along with its higher risk of tone-related miscommunication, makes it a weaker choice specifically for the fast, frequent coordination an internal team actually needs.

Why would legal counsel actually prefer less email rather than more, given that documentation often matters legally?

Because a poorly worded or hastily written email can become a permanent, discoverable record of a casual misstatement that causes real legal exposure later, which is different from a deliberate, carefully considered written communication. Legal counsel often prefers documentation created intentionally and carefully for situations that require it, rather than a large volume of informal email traffic that increases the risk of an unintended, damaging statement.

What are the specific situations where email remains the right communication tool?

Situations involving a new potential client, a new vendor or trade partner without an established faster channel yet, or correspondence with another party’s legal counsel where a formal, documented written record is actually appropriate. I treat this as a deliberately narrow category, not a broad justification for using email whenever the recipient happens to be outside one’s own immediate team.

Why might a company want to actively redirect external contacts toward faster communication channels rather than simply accepting email traffic as it comes?

Because consistently redirecting people toward quicker channels, like a direct message or a real-time tool, reduces overall email volume over time while still maintaining responsiveness. That approach protects a person’s time and attention from the inherent slowness of email without requiring them to abandon external communication altogether, since most external contacts are often willing to switch to a faster method once it is actually offered to them.

If you want to learn more we have:

Discover Jason’s Expertise:

What Killing Roaches Taught Me About Construction

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

Read 10 min

What Fighting a Pest Infestation With AI Taught Me About Running a Project

Here’s the deal. I recently spent several months working with AI to systematically eliminate a cockroach infestation at my own house, and by the end of it, I realized I had essentially relearned every core Lean principle I already teach, just through a completely different problem. I want to walk through exactly what that process taught me, because the parallels to running a real construction project are almost too clean to be a coincidence.

How the Infestation Actually Started

A water line broke at our house, which led to a full remodel of that section, and shortly afterward, we brought in some larger used refrigerators to fit our family’s needs. Slowly, we realized we had an infestation. In hindsight, the infestation almost certainly arrived with one of those used appliances, since the moment we finally removed that specific fridge, the problem disappeared for good. The common wisdom around this particular pest is bleak. Once you have them, people say you are essentially stuck living with them forever. I refused to accept that, and I decided to fight it systematically, with AI as my actual strategic partner throughout.

Lesson One: Never Fight the Enemy Everywhere

The first real lesson was refusing to spray or treat every single location at once. Real infestations concentrate around specific hiding spots, and AI kept redirecting my attention toward identifying those specific locations rather than treating the whole house indiscriminately.

This maps directly onto how a real project should be run. You do not solve every single problem on a project simultaneously. You identify the actual constraint limiting flow and focus your energy there specifically, rather than scattering effort evenly across everything that looks even slightly wrong.

Lesson Two: Intelligence Wins

Sticky traps were never actually about killing anything directly. They were reconnaissance, telling me precisely where the real activity was concentrated each night, so I knew exactly where to focus treatment the following day.

That is exactly the same instinct behind going to the Gemba, the actual place where real work happens, rather than leading purely from KPIs, dashboards, or a comfortable office removed from the real site. Intelligence comes from direct observation, not from secondhand data alone.

Lesson Three: Logistics Wins

Here is the part that surprised me. Poison was not actually the biggest factor in solving this. Removing food and water sources consistently, having a home cleaned thoroughly every single day during the worst of it, and sealing every physical entry point I could find mattered far more than any single treatment applied.

Military history teaches the same lesson repeatedly. Most conflicts are decided by which side can no longer eat, communicate, move, or resupply, not simply by direct confrontation. Construction is identical. Projects fail because logistics fail. This is exactly why I no longer think of it as a simple site utilization plan, the term I grew up using early in my career. It is a logistics plan, and real logistical superiority is what actually wins a project.

Lesson Four: Do Not Chase Individual Soldiers, Destroy the Base

Every individual pest represented a soldier. The actual hiding and breeding locations were the real factories behind the problem. The moment I stopped chasing individual sightings and focused entirely on destroying those underlying locations, real progress finally accelerated.

Construction runs on the exact same principle. Do not fight every individual RFI, every late delivery, every isolated mistake as its own separate battle. Fix the actual production system generating these symptoms in the first place, and trace every recurring problem back to its root cause.

Watch for these signs a team is fighting scattered symptoms rather than addressing the actual root cause behind them.

Constant reactive effort spent on individual problems that keep recurring in slightly different forms.
No clear identification of the one or two locations or conditions actually generating most of the trouble.
Energy spread evenly across every visible issue rather than concentrated on the source.

Lesson Five: Momentum Is Fragile

This might be the single biggest lesson of the whole process. More than once, seeing even a small setback made me want to panic and escalate treatment everywhere at once. Each time, that impulse would have actually disrupted a strategy that was already quietly working.

Project teams do exactly this constantly. Things start improving, someone panics at the first sign of a hiccup, the entire plan gets changed, and all the accumulated momentum disappears. Sometimes real leadership simply means holding the line and trusting a system that is already working, even when progress feels uncertain in the moment.

I experienced this directly years ago with an early client, the very first time we implemented Lean at real, meaningful scale. Partway through, I started to panic, convinced something was not working. Someone on that team told me plainly to hold course and trust the systems we had already put in place. It took roughly eight months of patience before it clearly started working. W. Edwards Deming made a related point in his own writing, that quality transformation is not instant pudding. You cannot implement Lean and expect everything to look perfect the following month.

Lesson Six: The Footprint Shrinks Before the Numbers Do

Real recovery follows a specific, predictable order. Chaos becomes organized first. Only afterward do the actual underlying numbers start improving. Misreading that order, expecting numbers to improve before the surrounding chaos has settled, is exactly what causes people to believe an effort has failed right when it is actually working.

Lesson Seven: The Last Stretch Feels Disproportionately Harder

I spent far more energy, attention, and discipline eliminating the final handful of stragglers than I did addressing the first hundred. Construction recovery efforts feel exactly the same way. The finish line is consistently, emotionally harder to reach than the starting point, even though the remaining work is objectively smaller.

Lesson Eight: Internal Disagreement Can Undo Real Progress

At one point, my wife and I disagreed about removing a specific appliance I suspected was still harboring the problem. Looking back, I am not proud of how that disagreement played out, but the underlying lesson matters regardless. A team that is not united on a key decision risks losing ground it had already fought hard to gain. Internal dissension between the people responsible for a project, say a superintendent and a project manager not aligned, can quietly undo progress just as effectively as any external problem can.

Lesson Nine: The System Beats Heroics

Discipline and a system mattered far more than any single burst of heroic effort on my part. I am honestly not certain I would have succeeded without consistent AI coaching specifically pulling me back from my own instinct to panic and overreact. That coaching, more than any single treatment applied, is what actually won this.

Watch for these signs a team is relying on heroic individual effort rather than a disciplined system.

Progress that depends heavily on one person’s personal intensity or willpower rather than a repeatable process.
A pattern of overreacting to small setbacks by abandoning an approach that was actually still working.
No one specifically coaching the team to stay calm and trust the plan already in motion.

Lesson Ten: The Real Goal Was Never to Win Every Battle

Here is the lesson that matters most. The actual goal was never eliminating every single pest directly. It was creating an environment where they could not survive in the first place. That is exactly how I have always approached running a real Lean project. I am never trying to attack a specific person. I am trying to build an environment where bad behavior and poor systems simply cannot take hold to begin with. Real victory never came from fighting harder. It came from making the environment increasingly hostile to failure and increasingly favorable to success.

Applying These Lessons to Your Own Project

None of this requires an unusual problem to learn from. The same principles apply directly to any recurring issue on a real project, identify the actual root cause, gather real intelligence at the source, protect your logistics, hold the line when momentum feels fragile, and build a system rather than relying on individual heroics.

If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your teams build exactly this kind of systemic discipline, addressing root causes and protecting real momentum, rather than fighting the same recurring symptoms over and over without ever resolving what is actually causing them.

So here is the challenge. Identify one recurring problem on your own project that keeps resurfacing in slightly different forms. Ask honestly whether your team has actually found its real root cause, or whether you have simply been treating each new occurrence as its own isolated battle.

Edwards Deming said it plainly: improvement is not instant pudding. Hold the line, trust the system you have actually built, and give it the real time it needs to work.

On we go.

FAQ

Why compare a home pest infestation to running a construction project?

Because both situations reward the same underlying discipline, identifying a root cause rather than treating scattered symptoms, gathering real intelligence at the actual source of the problem, and maintaining a consistent system rather than reacting emotionally to every small setback. The specific problem differs entirely, but the pattern for solving it effectively turns out to be remarkably similar.

Why does panicking at a small setback tend to make a recovery effort worse rather than better?

Because overreacting often means abandoning or disrupting a strategy that was already working quietly in the background, simply because visible progress has not yet caught up with the real underlying improvement happening beneath the surface. That premature change frequently resets momentum that had already been building, extending the overall recovery rather than shortening it.

What does “the footprint shrinks before the numbers do” mean?

It means real recovery typically brings order and organization to a chaotic situation before the actual underlying metrics show visible improvement. Expecting numbers to improve immediately, before that underlying organization has taken hold, can lead someone to wrongly conclude an effort has failed exactly when it is actually beginning to succeed.

Why was the real goal never eliminating every individual problem directly?

Because sustainable success comes from building an environment where problems cannot take root in the first place, rather than fighting an endless, exhausting series of individual battles against symptoms as they appear. That same principle applies directly to Lean leadership, where the goal is building systems that prevent bad outcomes rather than personally attacking every individual mistake as it happens.

If you want to learn more we have:

Discover Jason’s Expertise:

Data, Visibility, and the Limits of KPIs

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

Read 9 min

Brain Wiring: Why Continuous Learning Should Be a Condition of Employment

Here’s the deal. I have noticed something genuinely dramatic happening to my own understanding over the past year, and it came from an unexpected source, the sheer discipline of writing books faster than I ever thought possible. That process has taught me something worth sharing directly with anyone serious about this industry.

How I Am Actually Writing Books This Fast

People sometimes ask how I am producing so many books so quickly. The honest answer starts with raw material. Between podcast transcripts, video transcripts, articles, training content, and graphics, I have somewhere around six to seven thousand real pieces of content already sitting in text form, built up over years of actually doing this work.

That was not always the case. My very first book took roughly twelve to fourteen years from the initial outline to actual publication, much of it originally dictated by voice during a long drive, then edited and refined over and over. I even scrapped an entire earlier version of a different book after a collaborator started taking credit for it, and honestly, that early draft was not very good anyway. The version that eventually replaced it turned out to be one of my strongest, earning a genuinely high rating from real readers.

Going from one book roughly every year, to two books a year, to a book every three months, and now to a genuine book a week did not happen because the underlying work got easier. It happened because the accumulated archive of real content, combined with a genuinely disciplined process, finally let that existing depth of knowledge move from my head onto the page at a pace that actually matches how fast I am learning new things.

Why AI Collaboration Changes the Math, When Done Right

Of the roughly two dozen books I have written, about half came entirely from my own thinking and organization, with no AI collaboration at all. The rest were built through a real, deliberate process with AI, and I want to walk through exactly how that works, because the process itself matters as much as the tool.

Here is the actual sequence I follow when building a chapter with AI assistance.

Build a real outline first, load relevant transcripts as background material, and clearly explain the actual goal for that section.
Ask for a draft, listen to it critically, and give direct feedback, sometimes across several rounds, until it genuinely holds up.
Cross check any new idea that emerges against the rest of my existing material before treating it as something worth keeping.

Here is something genuinely useful I discovered along the way. Working inside a closed project that only references my own loaded material produces writing that is technically accurate and, honestly, a little flat. Working instead inside an open conversation that blends my own material with broader outside knowledge and commentary produces something noticeably richer. Think of the difference between plain bacon and eggs served with nothing else, versus a properly seasoned dish with real depth built in. Both are technically the same core ingredients. One tastes like an actual meal.

I only discovered this by actually testing both approaches on the same book and comparing the results honestly, rather than assuming one method was obviously correct in advance. That willingness to test an assumption against real output, rather than simply trusting a guess about which setup should work better, is itself a small example of the same discipline this whole post is actually about.

What I Have Personally Learned Through This Process

Here is the part that genuinely surprised me. I spent roughly ten years collecting logistics concepts, studying real experts in that space, and learning directly in Japan, and I still discovered real gaps in my own understanding while actually drafting the book. Concepts like Eliyahu Goldratt’s drum buffer rope method, or the specific differences between production Kanban, replenishment Kanban, and pull Kanban, only became genuinely clear to me once I had to actually explain them well enough for a real chapter to hold together.

That pattern has repeated constantly. I am learning somewhere between a dozen and sixty genuinely new concepts every single week, simply through the discipline of having to draft this material clearly enough for someone else to actually understand it. I recently walked through a massive manufacturing warehouse, uninvited to share an opinion, and quietly spotted a dozen or more real problems with how the plant was organized and how work was actually flowing through it. I said nothing, since nobody asked. I noticed everything, because I am genuinely sharper than I was even a year ago.

Why This Should Change How Every Role Approaches Learning

This is exactly why I believe continuous, role specific learning deserves to be treated as a genuine requirement, not an optional bonus. You cannot lead a logistics operation, run a prefabrication effort, or manage a project team well without actually reading, studying, and training in the specific material your role demands.

Here is roughly how I would build that discipline into any organization I ran.

Logistics staff genuinely re-reading their core reference material at least once a quarter, using audio if that fits their schedule better.
Project engineers revisiting the relevant training material on a consistent six month cycle, treated as a real job responsibility.
A genuine, ongoing book club running at the company or jobsite level, focused specifically on the material each role actually needs.

Why I Deliberately Make This Material Easy to Access

I want to share something practical here too. I intentionally do not restrict the digital rights on the books I publish, meaning people can download them freely and feed them into their own AI tools for summaries or audio conversion. I hold the actual intellectual property, and I would rather see this material spread and genuinely used than protect it so tightly that fewer people actually benefit from it.

Why This Deserves to Be Treated as Seriously as Any Professional Requirement

Pilots retrain constantly. Doctors retrain constantly. Every genuine professional field treats ongoing learning as a real requirement, not a nice extra. Construction deserves the exact same standard. Given how much outdated or simply incorrect information still circulates across this industry, I genuinely believe we cannot afford to treat continuous learning as optional any longer.

If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your teams build a genuine, role specific brain wiring habit, real reading, real retraining, and real reinforcement, rather than treating initial onboarding as the only training anyone ever receives.

So here is the challenge. Pick the single most relevant piece of training material for your own specific role, and commit to revisiting it on a real, recurring schedule, not just once when you started. Track honestly how much sharper your own diagnostic instincts feel after a genuine quarter of doing that consistently.

Jason Schroeder said it plainly: “We’ve all got to start doing this brain wiring thing.” Make continuous, role specific learning a genuine habit, and watch how much more you start noticing that used to slip right past you.

On we go.

FAQ

Why does the article distinguish between writing with AI inside a closed project versus an open conversation?

Because a closed project that only references a person’s own loaded material tends to produce technically accurate but somewhat flat writing, while an open conversation blending personal material with broader outside knowledge tends to produce something richer and more engaging. That distinction matters for anyone using AI tools to draft content, since the specific setup chosen genuinely affects the quality of what comes out.

Why did drafting a book actually reveal gaps in the author’s own understanding, despite years of prior study?

Because explaining a concept clearly enough for someone else to genuinely understand it requires a deeper level of mastery than simply being familiar with the idea personally. The discipline of writing forced a level of precision that surfaced real gaps, like fully understanding drum buffer rope or the different types of Kanban, that years of general familiarity had not fully closed on their own.

Why does the article recommend different reading schedules for different roles, like quarterly for logistics staff versus every six months for project engineers?

Because different roles carry different levels of complexity and different rates of change in the relevant material, so a single universal schedule would not genuinely fit every position well. Matching the reading cadence to how quickly a role’s core material actually needs reinforcement keeps the practice genuinely useful rather than becoming a generic requirement disconnected from actual need.

Why does the author choose not to restrict digital rights on the books he publishes?

Because the priority is genuinely spreading useful knowledge across the industry rather than protecting the material as tightly as possible. Allowing people to download and repurpose the content, including feeding it into their own AI tools for summaries or audio versions, reflects a belief that wider use of accurate information matters more than maximizing control over how it gets consumed.

If you want to learn more we have:

Discover Jason’s Expertise:

Takt Is Taking Off Across the Construction Industry

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

Read 9 min

Takt Is Taking Off Across This Industry, and Here Is the Proof

Here’s the deal. I want to share something exciting, and I want to be honest that I probably only see about one millionth of what is actually happening across this industry right now. If the progress visible to me looks this strong from that small a window, the real scope of what is actually happening is almost certainly much larger.

Short answer: Takt is spreading fast. Companies are taking Takt fully in-house, merging it with the Last Planner System on their own, and running one-day Takt times on hyperscale data centers, and even CPM software companies are building Takt interfaces into their products.

Three Real Examples Worth Sharing

The first pattern I see constantly is a company that originally worked with us on Takt implementation and has since taken the whole operation over internally, running their entire scheduling function and every one of their projects through what we call the integrated production control system. This specific pattern repeats itself over and over across different companies.

That pattern is the best possible outcome for any consulting relationship. It means a company did not just implement something temporarily with outside help. It built real internal capability that no longer depends on anyone outside the organization to sustain it, which is exactly the goal behind teaching a system rather than simply running it for someone indefinitely.

The second example impressed me. A company that adopted Takt a while back, independently merged it with the Last Planner System on their own, and now runs every single project on Takt, with real visuals and rhythm across the board. They read every one of our books, adopted our templates fully, and completed our entire free Takt production system course, training their whole team through it. Eventually they came to me directly and asked whether their people could go through a formal certification process. I said absolutely, and once I actually looked at their project results, I was blown away. Their numbers were remarkable enough that I turned screenshots from their presentation directly into teaching images, something I only do when results are worth showcasing that way.

Here is what stood out most clearly about how thoroughly that second company committed to doing this right.

Every single project running on Takt, with visual rhythm, rather than one pilot project treated as an isolated experiment.
Full completion of the free training course across their entire team, rather than a handful of individuals learning it informally.
Results strong enough to request formal certification proactively, rather than needing to be convinced the investment was worthwhile.

The Data Center Example That Blew Me Away

The third example involves a company hired by Meta to work inside one of these fast-tracked, hyperscale data center projects. They are prefabricating every segment into properly leveled components, running an actual one-day Takt time, and training every single person involved directly on Takt principles. We are actively helping them build orientation materials, and essentially every Lean principle I talk about regularly is being implemented directly on their site.

They are delivering at the most accelerated pace of any comparable project I am aware of, and they have taken this well beyond the basics, implementing Kanban and Andon systems as part of a complete, integrated approach. I took photos during a visit, and even working under a confidentiality agreement, I was able to use AI to recreate a representative example that illustrates the concept clearly without sharing anything actually protected.

Finding a way to still share the underlying lesson while respecting a confidentiality agreement matters here too. It means the industry as a whole gets to learn from what is working, without any single company having to expose its own competitive advantage in the process.

Here is what made this particular implementation stand out as advanced rather than simply competent.

Every project segment prefabricated and leveled before it ever reaches the actual site.
A one-day Takt time achieved consistently across a project of real scale and complexity.
Full Kanban and Andon systems layered on top of the core Takt structure, rather than Takt alone standing on its own.

Why the Skeptics Do Not Bother Me

I occasionally get pushback when I share stories like this, people asking directly whether any of it is real. I understand the skepticism, and it does not bother me. I keep receiving photo after photo, from company after company, showing beautiful kitting for crews, top-of-the-line prefabrication, and real Takt implementations executed at a level that consistently impresses me. The evidence keeps arriving faster than the doubt does.

Healthy skepticism is not a bad thing in this industry, given how many methods get oversold with little to show for it. The difference here is that the proof keeps showing up unprompted, from companies with no reason to exaggerate their own results to me directly, which is a different kind of evidence than a polished case study built for marketing purposes.

Why This Represents Real, Measurable Momentum

Just a couple of years ago, I was not sure Takt was catching on as quickly as I hoped. That has changed dramatically. Takt is now taking real ground away from CPM specifically, to the point where even CPM software companies are starting to build Takt interfaces directly into their own products. People across this industry are increasingly understanding something simple and powerful. Once you have real buffers and trade flow working together, you have essentially everything you need for a project to actually succeed.

That shift matters because software companies tend to follow demand rather than create it. A CPM provider investing real development time into a Takt interface is responding to what its own customers are actively asking for, which tells you something meaningful about how mainstream this conversation has become across the industry, well beyond the companies I happen to work with directly.

Why Sharing This Matters, Even in a Short Update

None of this requires an elaborate deep dive to be worth sharing. Sometimes a brief update on real industry momentum matters more than another detailed technical breakdown, simply because it shows people this approach is not theoretical anymore. It is working, at scale, across companies of very different sizes and specialties.

That range matters too. These examples span a company internalizing what it originally learned from outside help, a company that built on that foundation entirely on its own, and a company applying the same principles inside one of the most demanding, fast-paced construction environments that exists right now. Adaptability across that range is exactly what separates a real, durable methodology from a passing trend.

If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your organization become the next example of this momentum, rather than watching from the sidelines while competitors move further ahead with real Takt implementation.

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

So here is the challenge. Look honestly at where your own organization currently stands relative to the companies described here. If you are still treating Takt as an experiment rather than the operating standard across every project, that gap is exactly where the rest of this industry is now quickly leaving room to move ahead.

Bottom line: When you have buffers and trade flow, you have everything you need. More of this industry is finally proving that statement true, one impressive project at a time.

On we go.

FAQ

Why is a company independently merging Takt with the Last Planner System such a strong example?

Because doing that integration without direct outside guidance shows internal mastery of both systems, rather than surface-level adoption of either one. A company capable of combining them effectively on its own, and then completing formal training and certification on top of that, demonstrates a depth of understanding well beyond simply following a template.

Why is achieving a one-day Takt time on a large, complex project considered such a significant accomplishment?

Because a shorter Takt time generally reflects tighter coordination, more thorough prefabrication, and disciplined execution across every trade involved. Achieving that pace consistently on a project of real scale, rather than on a small or simple job, demonstrates that the underlying system supporting it is mature rather than newly implemented.

Why does it matter that even CPM software companies are building Takt interfaces into their own products?

Because it signals that Takt adoption has moved beyond individual companies experimenting with the method and into mainstream industry demand. Software companies generally build features in response to what customers are actually asking for, so CPM providers adding Takt functionality suggests real, widespread interest rather than a niche trend limited to a small group of early adopters.

Why isn’t skepticism about these Takt success stories a concern?

Because the evidence itself (repeated photos and real project results shared voluntarily by multiple different companies) is more persuasive over time than any direct argument could be. Rather than trying to convince skeptics through explanation, I let the accumulating volume of independent, real-world examples be the more convincing form of proof.

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.

Words Alone Don’t Work: Make Communication Visual

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

Read 9 min

Words Alone Will Never Cut It

Here’s the deal. I have spent years believing I was communicating clearly simply because I said something out loud. I have finally accepted something uncomfortable. Verbal instructions on their own are not reliable, no matter how clearly I think I explained them, and building real systems around that fact has changed how much actually gets done.

Why I Finally Stopped Trusting My Own Words

Verbal instructions get confused constantly. They get lost with a spouse, with kids, with coworkers, with direct reports. If something is not written down somewhere real, it might as well not have happened at all. I used to get frustrated telling my wife Kate that I had told someone to do something, only to have her ask a simple, maddening question. Did you write it down?

She was never saying I had done something wrong on purpose. She was making a much bigger point. Verbal communication by itself simply does not reliably work, for anyone, in any relationship, professional or personal.

That reframing mattered to me more than I initially expected. It stopped being about who was at fault when something got missed, and started being about whether the actual communication method being used was ever going to reliably work in the first place. Once I stopped taking it personally, it became a lot easier to actually fix.

Why I Resisted Lists for So Long

I used to believe that making lists for people, rather than communicating things verbally and personally, was somehow disrespectful. I have completely abandoned that belief. Once I started writing things down as real lists, everything on those lists got done, on time, exactly the way I expected. I also started using AI to help translate my own instructions into clear, understandable language before sharing them, and that consistently produces better results too.

The bigger shift was moving away from simply telling someone something and instead placing it directly onto a shared system, a project board, a Kanban board, a task management tool. In our own office, we run an actual physical board with stickies, and we huddle around it daily. Nearly everything placed there gets done. That pattern has proven itself so consistently that I cannot argue with it anymore.

Watch for these signs verbal-only communication is quietly failing your own team, even when everyone involved is trying their best.

The same instruction repeated multiple times to the same person, with the task still not getting done.
Tasks discussed clearly in conversation that somehow never make it onto any tracked list or board.
A pattern of assuming something happened simply because it was said out loud once.

The Deeper Lesson: Where Information Actually Lives Matters

Here is where this got more sophisticated for me. I was recently talking with Kate about someone talented we wanted to help succeed, who was struggling specifically with following standard work. My first response was, we do have standard work, it is right there on the board. Kate pushed back with a sharper question. Is it somewhere this specific person actually looks?

That distinction mattered more than I initially wanted to admit. A shared team board tracks big-picture tasks well, but an individual might be working primarily from their own personal task list in a completely different tool, never actually looking at that shared board day to day. Having information exist somewhere visible is not the same as having it exist somewhere a specific person will actually see it.

My honest first reaction was resistance, something like, I should not have to personally make sure this lives in every single place a person happens to look. Kate’s response reframed the whole question for me. I could keep being technically right about what should not be my responsibility, or I could actually get the outcome I wanted. Framed that way, the choice was obvious, and once I actually did the extra work of placing information exactly where that person would see it, it got done.

That small exchange captures something worth remembering well beyond this one situation. Being technically correct about whose job something should be rarely produces the actual result you want. Doing the slightly inconvenient extra step, meeting someone in the exact place they actually work from, tends to produce it almost every time.

Watch for these signs information technically exists somewhere but has not actually reached the specific person who needs to act on it.

Standard work or instructions posted on a shared team board that a specific individual rarely if ever actually checks.
A task considered communicated because it exists somewhere in the system, without confirming the responsible person’s own personal list actually reflects it.
Repeated frustration that something “was right there” while the person responsible for it never saw it in the place they actually work from.

What This Means for a Bootcamp Too

This same realization even changed how we run our own training. We completely revamped our participant guide materials after recent bootcamps specifically because I recognized that even in a room full of people actively listening, spoken words alone are not enough to make sure everyone understands and retains what is being taught. Written, visual materials have to carry real weight alongside whatever gets said out loud.

Why This Is Not an Argument Against Speaking at All

I want to be precise here, because I do not actually believe verbal communication is worthless. General Patton had a real doctrine worth remembering directly, that every order must be both written and verbal. Words add flavor, emphasis, and additional context on top of a written or visual plan, and that combination is powerful. What does not work is relying on words alone, with no written or visual system underneath them, and expecting that alone to reliably get the message across.

Why This Matters More as an Organization Grows

As our own organization has grown, I cannot afford to stay unclear anymore. There are simply too many people and too little time to rely on the hope that everyone remembered a conversation correctly. Building real clarity into written and visual systems benefits me every bit as much as it benefits anyone else on the team, which is exactly why I finally stopped fighting it.

A smaller team can sometimes get away with relying on memory and goodwill for a while, simply because everyone is close enough to catch a missed instruction before it causes real damage. That margin disappears quickly as a team grows, which is exactly why building written and visual systems tends to matter more, not less, the bigger an organization actually gets.

If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your teams build the written and visual systems that actually make instructions stick, rather than relying on verbal communication alone and hoping it holds.

So here is the challenge. Pick one instruction you have given verbally in the last week that still has not gotten done. Write it down, put it directly on whatever system the responsible person actually uses day to day, and see how differently it lands compared to simply saying it out loud again.

Jason Schroeder said it plainly: “Words alone will never cut it.” Pair them with something written and visual, placed exactly where the right person will actually see it, and watch what finally gets done.

On we go.

FAQ

Why are verbal instructions unreliable even when someone clearly heard and understood them?

Because hearing and understanding an instruction in the moment does not guarantee it gets remembered or prioritized later, especially once someone moves on to other tasks and competing demands on their attention. A written or visual record removes the dependence on memory entirely, which is why it tends to produce far more consistent follow-through than verbal communication alone.

What is the actual difference between information being “on the board” and information reaching the person who needs it?

A shared team board typically tracks larger tasks visible to the whole group, while an individual often manages their own day-to-day work through a separate personal list or tool. Information existing on the shared board does not guarantee that specific individual actually looks at it regularly, which is why confirming it also lives in that person’s own personal workflow matters just as much as posting it somewhere visible in general.

Why bring up General Patton’s doctrine that every order must be both written and verbal?

Because it captures the actual balance I am arguing for, not eliminating verbal communication entirely, but never relying on it alone without a written or visual record backing it up. Verbal communication adds real value as emphasis and context, while the written or visual version provides the reliable record that verbal communication alone cannot guarantee.

Why did revamping written training materials matter even for an in-person bootcamp where people are actively listening?

Because active listening in the moment does not guarantee retention once the session ends, especially across a room full of people absorbing a large amount of new information at once. Strong written and visual materials give participants something reliable to return to afterward, reinforcing what was said out loud rather than depending on memory alone to carry the material forward.

If you want to learn more we have:

Discover Jason’s Expertise:

The Smart PM Who Knows Everything and Gets Nothing Done

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

Read 8 min

The Smart Project Engineer Who Knows Everything and Enables Nobody

Here’s the deal. Before I say anything critical here, I want to be completely clear about something. Superintendents are nothing without a great project manager and project engineer behind them. This entire industry runs on that partnership, and I mean that sincerely. What I want to talk about is a specific persona I have run into more than once, and it is worth naming directly because it quietly undermines the very people it seems to help the most.

The Persona Worth Recognizing

You have probably met this person. Sharp, picks up systems fast, knows the drawings and the project inside and out after surprisingly little time on site. People notice immediately how smart they are. At the same time, this same person tends to be a little scattered, moving quickly from one thing to the next, becoming the go-to source of answers for everyone around them.

Here is exactly what happens next. This person defaults to running around answering questions constantly, becoming the central source of knowledge for the whole team. That sounds helpful on the surface. In practice, it quietly stops helping anyone, because that knowledge lives entirely inside one busy, disorganized person instead of somewhere the whole team can actually access it.

Why This Actually Hurts People

I experienced this firsthand recently with a talented project engineer. We had pre-planned a specific task together well in advance, confirmed it directly with him, and when the moment came, it simply was not ready. A group of us stood there waiting, and I got to feel something I had not felt in a long time, the exact frustration a trade partner feels when they are told something is coming and then have to stand around losing real time and real money while it does not arrive.

It was not a pleasant feeling, and I want to be honest that in the moment, I did not handle it particularly well myself. I got frustrated, more focused on simply wanting the task done than on being patient with what was actually happening. Looking back, that reaction was not my best leadership either, and I recognize that fully. But the underlying pattern itself deserves real attention regardless of how I personally reacted to it.

I share that honestly because it is worth remembering that even leaders who understand these principles still slip into impatience sometimes when they are the one standing there waiting. The goal is not pretending frustration never happens. It is noticing it, naming it honestly, and correcting course rather than letting that frustration harden into a pattern of its own.

Here is the sharpest way I can put the actual problem. Instead of getting information from someone, people end up waiting for information from them instead. I do not care how much someone knows if that knowledge is not actually accessible to the people who need it, when they need it. Knowing everything about a project and being able to recite it in a performance review is not the same thing as making that same information usable by everyone else.

Watch for these signs someone has quietly become a knowledge bottleneck rather than an enabler on your own team.

Trade partners or crews regularly waiting on one specific person for information that should have been documented and visible in advance.
The same individual constantly being the one everyone turns to, with no backup system or shared documentation behind them.
Intelligence and system knowledge paired with no personal organization system or visual tracking to support it.

Why This Persona Feels So Good to the Person Living It

There is a real reason this pattern is so seductive for the person caught inside it. Human beings are generally motivated by a handful of core needs, including significance, certainty, connection, and variety, and being the person everyone depends on for answers satisfies several of those at once. That is exactly why this habit can feel rewarding even while it quietly damages the team around it. Being needed constantly feels good. It does not automatically mean it is actually good leadership.

Why “Problems Are Opportunities” Only Applies Sometimes

There is a common saying that problems are opportunities, and there is an important nuance worth adding to it. A problem is an opportunity only if it does not actually impact the work. Once a problem reaches the field and disrupts real people trying to do their jobs, it is simply a problem, full stop. This exact behavioral pattern, a smart but disorganized central source of information, is a real problem the moment it starts leaving trade partners and crews waiting.

What This Culture Actually Teaches Younger Professionals

Here is what concerns me most about letting this pattern go unaddressed. If younger, up-and-coming professionals watch this behavior get rewarded, being praised purely for individual brilliance while organization and accessibility get ignored, that is exactly the model they will learn to imitate. Nobody benefits from a culture where one person’s individual brilliance becomes the entire system. The goal is a culture where everyone can succeed, built on real organization and visibility, not one where a single standout personality has to personally carry all the answers.

Watch for these signs a team has built accessible, organized systems rather than depending on one person’s individual knowledge.

Information documented visually somewhere the whole team can reference directly, without needing to track down one specific individual.
A real personal organization system behind even the most naturally quick-thinking, sharp team members.
New team members able to find answers independently, rather than defaulting to whoever happens to know the most in the moment.

What I Actually Want From Smart People

I love working with smart people. Being a bit unkempt, being scattered, being quick and energetic, none of that is a real problem on its own. What I want to see corrected is the habit of being the sole, disorganized source of knowledge for everyone else, because that habit does not actually enable a team. It mostly creates personal significance for the individual holding all the answers, even when that is never the intention behind it.

The fix is not becoming less smart or less energetic. It is building visual systems and a real personal organization method so that knowledge stops living exclusively inside one person’s head and starts living somewhere the whole team can access it.

Building This Into Your Own Team

None of this requires suppressing anyone’s talent or intelligence. It requires pairing that talent with real organization, so brilliance actually enables a team instead of quietly becoming a bottleneck everyone else has to wait on.

If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your teams build personal organization and visual systems around even your most naturally gifted people, so their knowledge reaches everyone who needs it, rather than staying locked inside one busy, well-intentioned individual.

So here is the challenge. Look at your own team and identify whoever tends to become the default source of answers for everyone else. Ask honestly whether that knowledge is actually documented and accessible, or whether people are waiting on that one person more often than they should have to.

Jason Schroeder said it plainly: “Instead of getting information from you, they’re waiting for information from you.” Build the systems that close that gap, and intelligence finally gets to help the whole team instead of just impressing it.

On we go.

FAQ

Why is being smart not the same as actually being helpful to a team?

Because knowledge only helps a team when it is actually accessible to the people who need it, when they need it. Someone can know a project inside and out and still fail to help the team effectively if that knowledge stays locked inside their own head, with no documentation or visual system letting others access it independently.

Why revise the common saying that “problems are opportunities”?

Because that saying only holds true when a problem is caught and resolved before it actually reaches and disrupts real work. Once a problem impacts the field, delaying trade partners or crews who are waiting, it is simply a problem, not an opportunity, and treating it otherwise risks minimizing real, costly disruption.

Why might this “central knowledge” pattern feel rewarding to the person exhibiting it, even when it hurts the team?

Because being the person everyone depends on for answers satisfies human needs like significance and connection, making the pattern feel good even while it creates real bottlenecks for everyone else. Recognizing that emotional reward is often the first step toward actually changing the underlying behavior.

What is the actual fix for someone caught in this pattern?

Building visual systems and a real personal organization method, so that knowledge becomes accessible to the whole team rather than staying dependent on one individual. The goal is not suppressing someone’s intelligence or energy, but pairing that talent with organization so it can actually reach and help everyone who needs it.

If you want to learn more we have:

Discover Jason’s Expertise:

The Governing Principles of Lean

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

Read 9 min

The Three Governing Principles That Resolve Every Lean Conflict

Here’s the deal. Somewhere in every Lean journey, you hit a moment where two real Lean principles seem to pull in opposite directions. Someone says, I want to eliminate this waste, but getting rid of it costs money. Someone else says, I see an improvement here, but at what point does chasing it become wasting time instead? Those moments are not a sign Lean is broken. They are a sign you need a tiebreaker, and there are three governing principles that consistently resolve these conflicts.

I want to be honest that I have not tested this exhaustively enough to claim it is complete, and this framework may keep developing as I encounter more edge cases. What I can say confidently is that these three have held up consistently every time I have actually applied them.

The First Governing Principle: Theory of Constraints

When two Lean principles conflict, the first question worth asking is simple. Is this actually your bottleneck? Theory of constraints is one of the biggest governing principles across all of Lean, and it works by asking which option actually addresses the real limiting factor in this specific situation, rather than which one sounds more theoretically correct in general.

Here is a real example. Our own CFO recently faced a conflict between one-piece flow, which would take more time, and batching a task, which would be more convenient but potentially risk quality on something legally sensitive that could not afford a mistake. The real question was not which principle sounds more Lean in the abstract. It was which one actually addressed her bottleneck. Since quality was clearly her most limiting factor in that specific situation, the correct move was choosing the larger batch, even though that technically violated one-piece flow, because it protected the thing that actually mattered most in that moment.

Notice what actually happened in that conversation. Nobody argued about which principle was more theoretically correct. The entire decision came down to one direct question, asked and answered honestly, about where the real risk actually sat. That is the whole value of leading with constraints first: it replaces a debate about ideology with a concrete diagnosis.

Watch for these signs theory of constraints should be the deciding factor in your own conflicting Lean decision.

One option clearly addresses a limiting factor, while the other option simply follows a general Lean rule without regard to what is actually constraining the situation.
A real, tangible cost, financial, legal, or safety-related, tied directly to getting the decision wrong in this specific instance.
Two Lean principles pulling in different directions where only one of them actually touches the real bottleneck at hand.

The Second Governing Principle: Respect for People

This one requires less explanation, though it deserves just as much weight as the other two. When two Lean principles conflict, ask directly which option best respects the human beings actually involved. That question alone tends to cut through a surprising amount of theoretical debate quickly, because it grounds the decision in something concrete rather than an abstract rule.

The Third Governing Principle: Quality

Here is where this framework got interesting for me recently. A colleague identified a real opportunity to improve the build kits we send out for our own training bootcamps, and it ran into a different Lean principle, the general guidance to only use thoroughly tested software and hardware rather than experimenting with something new. That created a conflict worth resolving properly.

The resolution came down to asking what our actual product is. Since our business depends on delivering a quality bootcamp experience, investing real, careful attention into getting those kits right was not wasted effort or unnecessary nerding out. It was directly serving the actual product we sell. Quality can never be good enough when quality itself is the entire reason people show up in the first place.

That decision led directly to a clever solution, organizing every kit so its contents are perfectly arranged inside their storage bins. That single change does more than one thing at once. It showcases Lean thinking directly to the people using it, and it creates a remarkable experience that makes people want to come back and tell others. Quality and respect for people were not actually competing in that decision. They were the same decision, viewed from two different angles.

That outcome is worth paying attention to, because it means these three governing principles do not always compete against each other in practice. Applied honestly to the same situation, they often converge on the exact same answer, which is a reassuring sign that the decision being made is actually the right one.

Watch for these signs quality should be the deciding factor when two Lean principles seem to conflict.

The improvement in question touches the actual core product or service your organization exists to deliver.
Client or customer experience is directly affected by whichever option you choose.
Investing real effort here would strengthen the very reason people choose to work with you in the first place.

Why Having Three Governing Principles Actually Simplifies Things

None of this requires memorizing dozens of individual Lean rules and hoping they never contradict each other. It requires holding these three governing principles above everything else, and running any conflict through them directly. Is this the actual bottleneck? Does this respect the people involved? Does this protect or strengthen real quality? Whichever principle answers most directly to the specific situation in front of you tends to be the one worth following.

This is also why the framework stays useful even as new, more specific Lean rules get added over time. Individual rules can multiply endlessly, and new situations will always surface conflicts nobody anticipated in advance. Three governing principles held consistently above all of them give a team a stable way to reason through whatever comes up next, without needing an ever-growing rulebook to cover every possible case in advance.

Applying This Framework to Your Own Team

None of this replaces good judgment, and it is not meant to. It gives that judgment a structure to work through, rather than leaving every conflicting decision to gut feeling or whoever argues most persuasively in the room.

If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your teams build decision-making discipline around these three governing principles, so conflicting Lean guidance stops feeling like a contradiction and starts feeling like a resolvable question.

So here is the challenge. The next time two Lean principles on your own project seem to pull against each other, run the decision through all three governing principles directly. Is this the actual bottleneck? Does this respect the people involved? Does this protect or strengthen real quality? More often than not, one of those three will answer the question clearly enough to move forward with real confidence.

Jason Schroeder said it plainly: “What would the theory of constraints say? What is best for our people? What is best from a quality standpoint?” Run every conflict through those three questions, and the path forward tends to become clear.

On we go.

FAQ

Why do Lean principles sometimes conflict with each other in the first place?

Because individual Lean principles, like one-piece flow or eliminating unnecessary spending, are each useful guidelines in general, but no single guideline accounts for every possible situation. Real projects and real businesses regularly encounter specific circumstances where two generally sound principles point in different directions, which is exactly why a higher-level framework is needed to resolve the tension.

Why does theory of constraints outrank a general Lean rule like one-piece flow when the two conflict?

Because theory of constraints asks which option actually addresses the real limiting factor in a specific situation, rather than which option follows a general rule correctly. A serious bottleneck, like a legal or quality risk, deserves more weight than a general preference for flow, since ignoring the real constraint causes far more damage than temporarily deviating from a standard rule.

How do you resolve the tension between quality and the Lean principle against unnecessary spending?

By asking what the organization’s actual product or core value proposition is. If quality is central to what a business delivers, investing real effort into improving it is not unnecessary spending; it is direct investment in the actual product itself. I treat this as a case where two principles only appear to conflict, since protecting quality in that specific business actually serves the deeper goal both principles are meant to support.

Can these three governing principles ever conflict with each other, and if so, how should that be resolved?

I have not fully worked through this scenario yet, and I will admit the framework may still be developing. In practice, working through all three questions honestly, addressing the real bottleneck, respecting the people involved, and protecting quality, tends to surface which concern is actually most urgent in a specific situation, even when more than one of the three principles applies at once.

If you want to learn more we have:

Discover Jason’s Expertise:

General Offerings

Company Offerings

Systems

Month: October 2026

AI Slop or a Tool for Better Work?

Accountability vs. Count-On-Ability

What Does “External Email Only” Mean?

What Killing Roaches Taught Me About Construction

Data, Visibility, and the Limits of KPIs

Takt Is Taking Off Across the Construction Industry

Takt Is Taking Off Across This Industry, and Here Is the Proof

Three Real Examples Worth Sharing

The Data Center Example That Blew Me Away

Why the Skeptics Do Not Bother Me

Why This Represents Real, Measurable Momentum

Why Sharing This Matters, Even in a Short Update

FAQ

Why is a company independently merging Takt with the Last Planner System such a strong example?

Why is achieving a one-day Takt time on a large, complex project considered such a significant accomplishment?

Why does it matter that even CPM software companies are building Takt interfaces into their own products?

Why isn’t skepticism about these Takt success stories a concern?

Words Alone Don’t Work: Make Communication Visual

The Smart PM Who Knows Everything and Gets Nothing Done

The Governing Principles of Lean

Subscribe Now

Our Office

Get In Touch

Company

Follow Us

General Offerings

Company Offerings

Systems

Takt Is Taking Off Across This Industry, and Here Is the Proof

Three Real Examples Worth Sharing

The Data Center Example That Blew Me Away

Why the Skeptics Do Not Bother Me

Why This Represents Real, Measurable Momentum

Why Sharing This Matters, Even in a Short Update

FAQ

Why is a company independently merging Takt with the Last Planner System such a strong example?

Why is achieving a one-day Takt time on a large, complex project considered such a significant accomplishment?

Why does it matter that even CPM software companies are building Takt interfaces into their own products?

Why isn’t skepticism about these Takt success stories a concern?

SUBSCRIBE NOW !

Subscribe to our newsletters and stay updated!