IPD Explained: How Lean Teams Lead Differently

Posted on March 30, 2026March 30, 2026 by Jason Schroeder

Read 19 min

IPD Explained: How Lean Teams Do It Differently

There is a word that keeps coming up every time I research great businesses, great teams, and great construction projects. It does not matter whether I am reading W. Edwards Deming, studying how Google works, or digging through the research behind high-performing project delivery. The word is the same every time. Integration. And integrated project delivery IPD is the methodology that takes that word and builds an entire system around it.

The Pain of Building in Silos

Walk into most construction projects and you will see the same structural disease at work. The owner is in one corner. The designers are in another. The general contractor is running a separate meeting. The trades are waiting to be told what to do. Contracts are written to protect individual parties rather than to optimize the whole. When something goes wrong, lawyers get involved before solutions do. And the result is a project built on friction, mistrust, and wasted time.

That is not a people problem. The owners, designers, contractors, and trade partners on those projects are often talented and well-intentioned. But the system they are operating inside was designed to separate them, not integrate them. When the structure pushes people into silos, people in silos is exactly what you get.

The System Built the Silos

Here is what I want builders at every level to understand: the adversarial dynamic on most construction projects is not a personality trait. It is an organizational outcome. Design-bid-build delivery puts parties into contractual positions where their interests diverge. Everybody optimizes for their own scope, their own schedule, their own margin. And when those sub-optimized pieces try to come together in the field, they collide. The schedule slips. The budget bleeds. The team fractures. And everyone points at someone else.

The system failed them. They did not fail the system.

A Story That Made This Real for Me

When I was at DPR Construction, I had the chance to work on IPD-light projects environments that used IPD behaviors even without the full integrated form of agreement. The difference was immediately visible. The kickoff was not a handshake and a slide deck. It was a structured event where the whole team built shared goals together. Communication was transparent and open cost, schedule, decisions, everything. Trade partners were involved in constructability reviews before anyone had swung a hammer, because general contractors, no matter how talented, simply do not know what trades know about how something actually gets built.

Those projects did not feel like the typical industry experience. They felt like a team. And when problems surfaced and they always do people ran toward the problem together instead of scrambling to document who was responsible.

Why Integration Is the Job of the General Contractor

When we were writing the book Elevating Construction General Superintendents, we had to distill the general contractor’s job down to its essential functions. We landed on four. First, create a clean, safe, organized, stable, and standardized environment. Second, create rhythm through the Takt plan and ensure the train of trades is moving through the project together. Third, provide the finances and resources pay trade partners on time, not late, and make sure the material and information supply chains are queuing up to enable the work. And fourth the one that ties all the others together integration. Integrated communication, integrated meeting systems, integrated teaming, integrated participation, everything integrated.

That fourth function is the one most GCs under-deliver on. They run the environment, they manage the schedule, they handle the money. But they do not always do the hard work of integrating the people. And that gap is where projects fall apart.

The Five Components That Make IPD Work

The first is shared risk and reward. This is the structural heart of true IPD. When all parties owner, designer, contractor, and key trades share in both the upside and the downside, the incentive to sub-optimize disappears. Nobody can win by making someone else lose. The Integrated Form of Agreement, or IFOA, formalizes this structure. But even teams without a formal IFOA can adopt shared-risk thinking by making every decision through the lens of what is best for the whole project, not just one party.

The second is transparency primarily in cost, but really everywhere. Transparent cost data, transparent schedules, transparent decisions, transparent means and methods. When everyone can see the same picture, the motivations that drive bad behavior in traditional delivery are simply removed. People stop gaming the system because the system is visible. And when everybody knows the goal, the structure, and the rules, alignment happens naturally.

The third is early trade partner involvement. Here is a hard truth I want builders to sit with: general contractors do not know how to do real constructability reviews without trade input. We can coordinate. We can budget. We can schedule. But the trades are the experts in how their work actually gets built. Bringing them in early during design, not just during construction produces better details, more accurate durations, fewer surprises, and a team that has already built the project once in their heads before anyone touches the field.

Here are the signals that early trade partner involvement is working:

Constructability issues are caught in design, not during installation
Trade durations in the schedule are based on real crew capacity, not guesses
Trade foremen arrive at pre-construction meetings already prepared
Design details reflect how the work is actually built, not just how it looks on paper

The fourth is joint decision-making. This is where a lot of teams struggle because the instinct is to either centralize every decision or die by committee. The answer is a clear distinction between tactical and strategic decisions. Tactical decisions cleanliness, organization, safety, the non-negotiables of how the site operates are not up for debate. They are the core values of the project and they get enforced without committee. Strategic decisions sequencing, phasing, budget allocation, design trade-offs require consensus among the parties who share the risk. You build a coalition. You work through the group. And you move forward together.

The fifth is big room collaboration. Not separate offices. Not siloed meetings. Not teams that communicate by email when they could be working side by side. Co-location, even partial, changes the speed and quality of every decision. When the owner, designer, contractor, and key trades are working in proximity, with shared visual systems and real-time data, problems get solved in minutes instead of weeks. The big room is not just a physical space. It is the physical expression of the commitment to optimizing the whole.

Optimizing the Whole Is the Point

There is a concept I love from the theory of constraints. Imagine a pipe with a bottleneck in the middle. An improvement at the far end of the pipe means nothing as long as the bottleneck remains. The only improvement that matters is the one that addresses the actual constraint. In construction, most teams are making improvements to their own pipe sections while the project bottleneck stays unresolved. IPD fixes this by orienting the entire team toward the same bottleneck, the same constraint, the same goal. We optimize the whole, not the parts.

That shift in orientation is profound. It means a designer changes a detail not because it makes their work easier but because it makes the trade’s installation faster. It means a contractor absorbs a cost in one area because it removes a bigger constraint somewhere else. It means trade partners share information about their capacity because doing so helps the schedule flow. Total participation produces total optimization. And that is what IPD, at its best, is engineered to produce.

Why This Connects to the Mission

The mission at Elevate Construction is to build remarkable people and systems that build the world. IPD is the delivery methodology most aligned with that mission because it is the one that takes the integration of people seriously. It does not just talk about collaboration. It structures the contract, the environment, the meetings, and the relationships around it. When you work in a true IPD environment, you do not just build a better project. You build better builders. People who know how to work as a team, make decisions together, and optimize for something larger than themselves. If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow.

Integration is what it is going to take to build great projects. Not better individual performance. Integration.

A Challenge for Every Builder

The next time you feel the friction of a siloed project the owner going one direction, the design team another, the trades waiting and wondering ask yourself what one step toward integration looks like. It might be a co-location session. It might be a transparent cost meeting. It might be inviting a trade partner into a constructability conversation they were never included in before. Start there. Integration compounds.

As W. Edwards Deming said, “A bad system will beat a good person every time.” IPD is the system designed so that good people can finally win together.

On we go.

Frequently Asked Questions

What is the difference between IPD and traditional design-bid-build?

Design-bid-build separates the parties into contractual positions where their interests often conflict, producing adversarial dynamics and sub-optimization. IPD integrates them through shared risk, shared reward, and co-located decision-making so everyone optimizes for the whole project, not just their own scope.

Do you need a formal IFOA to get IPD benefits?

No. Many teams use IPD-light behaviors early trade involvement, transparent cost, co-location, and joint decision-making inside CM at risk or other contract structures. The mindset and the behaviors produce most of the benefit even without the formal agreement.

Why is early trade partner involvement so important?

Because general contractors, no matter how experienced, cannot do real constructability reviews without trade expertise. Trades know how their work actually gets built, and involving them during design eliminates expensive surprises in the field.

What does “optimizing the whole” mean in practice?

It means making every decision based on what is best for the project overall, not for any individual party. A designer improves a detail because it helps the trade, not because it makes their own work easier. The bottleneck gets fixed, not the easy parts downstream from it.

How does IPD connect to Lean and Takt?

IPD and Lean are natural complements. IPD creates the integrated team and the shared goals. Takt Planning and Last Planner give that team the production system to execute with rhythm, flow, and visibility. Together they cover the full lifecycle from pre-construction alignment through field delivery.

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.

On we go

How Long Does It Take To Become A Project Manager?

Posted on March 30, 2026March 30, 2026 by Jason Schroeder

Read 19 min

How Long Does It Take to Become a Construction Project Manager And What Actually Matters

Five to ten years. That is the honest answer to how long it takes to become a construction project manager. But here is what I want you to understand: the timeline is not the interesting part. The interesting part is what happens inside those years. Because I have seen people hit the PM title in four years and struggle badly, and I have seen people take eight years and become genuinely outstanding. The difference was never the calendar. It was what they learned, how they saw their role, and whether they built the five things that actually make a project manager effective.

The Pain That Stalls Most PMs Before They Even Start

I got a WhatsApp message from a superintendent not long ago. He said the project manager on his project was technically sharp great with computers, good with the details. But when the materials hit the site, the PM said, “I got them here. It’s yours to worry about now.” And then walked away.

I was genuinely sad when I heard that. Not because the PM was a bad person. But because he had completely misunderstood his job. He thought his role was to do things. Order materials. Process RFIs. Review submittals. And once he did the thing, his responsibility ended.

That framing produces projects that limp. Materials arrive damaged or staged in the wrong location. Nobody QCed them. Workers are tripping over them. The superintendent is managing consequences instead of building. And the PM wonders why everyone seems frustrated.

The Failure Pattern Is in the Misunderstood Role

The failure pattern for most developing project managers is not laziness or incompetence. It is a fundamental misidentification of what the job is. They believe the role is built around tasks RFIs, submittals, pay applications, supply chains. Those tools are real and they matter. But they are not the job. They are instruments in service of the actual job, which is enabling trade partners to be successful so the project can be successful so the client gets what they paid for.

A project manager who gets that right manages an entire process: buyout, executed contract, pre-mobilization meeting, pre-construction meeting, first in-place inspection, follow-up inspections, final inspections, payments, and supply chain all the way from plan to build to finish. The RFI is not the deliverable. A prepared trade partner with clear expectations, confirmed materials, and a quality plan is the deliverable. That shift in thinking changes everything.

A Story About What Good PM Leadership Looks Like

When I was project superintendent on the Bioscience Research Laboratory with DPR Construction, my project manager was Brian Young. He is a great example of what leadership maturity actually looks like in this role. He was supportive. He also held the line. He spoke up when something needed to be said. He did not put up with nonsense including from me. He walked the field. He helped me own issues rather than leaving me exposed. He was always strategically where he needed to be, and he was always building the team.

Brian never smothered me. He never went around me. But he also never disappeared. He had the rare ability to bring out the best in the people around him while still meeting the goals of the project. That is what leadership maturity looks like in practice. And I have watched people with that kind of maturity get promoted faster and perform better than anyone else in the room.

The Five Things That Actually Determine How Well You Perform

The technical mechanics of the PM role how to write an RFI, how to review a submittal, how to process a subcontractor pay application, how to use project management software you can learn most of that in eighteen months to four years. It is teachable and learnable and plenty of people come out of school and reach PM-level competence within four or five years on those tasks. But if they skip what I am about to describe, it will hurt them, and the project teams depending on them will feel it.

The first is a real understanding of construction operations. Not the version taught in some companies, where you learn to hold retainage, pay trade partners late, or rely on composite cleanup crews. That is not construction operations. That is extraction masquerading as management. I am talking about thoughtful, effective, actually good construction operations how work flows, how trade partners are prepared, how decisions in the office create or destroy capacity in the field. A PM who does not understand operations will be perpetually behind the people they are supposed to be enabling.

The second is communication. The project manager lives at the intersection of the owner, the design team, the superintendent, the trade partners, and the executive team. That intersection only produces good outcomes when the PM can communicate well not just clearly, but strategically. Two books I recommend to every PM developing this skill are How to Win Friends and Influence People by Dale Carnegie and Never Split the Difference by Chris Voss. One teaches you how to build allies and move people toward shared goals. The other teaches you how to negotiate for win-win outcomes rather than win-lose conflicts. Read both. Apply both. They will change how you show up.

The third is financial literacy. Not bookkeeping. Strategic financial thinking. A good PM understands the numbers not just to track them but to shape them to look at projections and play what I call the Monopoly game of construction finances. The goal is a win-win-win: the owner wins, the company wins, and the trade partners win. When a PM only manages the numbers reactively, cost overruns are discovered too late to do anything about them. When a PM manages them strategically, they create margin through preparation, sequencing, and smart relationships.

The fourth is leadership maturity. Here is what it is not: a PM and a superintendent constantly fighting, a PM who manages their entire work life through emails, a PM who is disrespectful to field leadership, or a PM who is emotionally reactive under pressure. Leadership maturity is the ability to work with a diverse group of people different personalities, different experience levels, different priorities while still holding to standards and meeting the goals of the project at the end of the day. Anyone can lose their composure. Anyone can decide they are done with a person or a problem. That is immature and it costs projects dearly. Leadership maturity means you stay in it, you hold the line with dignity, and you keep building the team regardless of the difficulty.

The fifth is risk management. Great PMs see what could go wrong before it does. They think in terms of readiness what does this trade partner need to be ready to execute, and does that thing exist yet? They identify constraints early, mitigate them systematically, and protect the team from surprises that were entirely preventable. Risk management is not a software function. It is a mental habit built over years of watching what happens when preparation is skipped.

Here are the signals that a PM is developing these five things well:

Trade partners leave pre-construction meetings with a clear installation work package
The superintendent and PM meet regularly and trust each other
Problems surface early in meetings rather than exploding in the field
Financial projections are updated proactively, not reactively
The PM walks the site and knows what is actually happening

The Path That Sets You Up for All of It

I never recommend going straight from college into a project engineer role. The fastest path to a great PM career runs through the field first. College, then field surveyor, foreman, or whatever entry point fits your background military, trade work, industry hire then field engineer. The field engineer role teaches you how construction actually gets built. It forces you to respect the people boots on the ground doing the work. And that respect, once built, stays with you for the rest of your career in a way that makes everything else work better. How long that field phase takes varies by person. But skipping it produces PMs who manage paper and miss the point.

Why All of This Connects to Something Bigger

When a project manager truly understands the role enabling people, preparing trades, building partnerships, leading with maturity the project becomes a different experience for everyone on it. Trade partners feel respected instead of managed. Superintendents feel supported instead of abandoned. Owners get what they paid for because the system was designed to deliver it. That is not accidental. That is what a well-developed project manager produces. If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow. The five to ten years is real. But more than the time, it is what you do with it. Build the five things. Go through the field. Learn from people like Brian Young who show you what leadership maturity actually looks like. The career you want is built one good decision at a time.

On we go.

Frequently Asked Questions

Is five to ten years really how long it takes to become a project manager?

Five to ten years reflects the time needed to develop real construction operations knowledge, communication skill, and leadership maturity not just technical PM tasks. You can process RFIs in eighteen months, but you cannot replace the judgment that comes from years of field-grounded experience.

Why is going through the field so important before becoming a PM?

The field teaches you how construction actually gets built and, more importantly, how to respect the people doing the building. PMs who skip this step tend to manage paper instead of enabling people, and that gap shows up on every project they run.

What is the real job of a project manager?

The job is to enable trade partners to be successful so the project can be successful so the client gets what they paid for. RFIs, submittals, and pay applications are tools in service of that goal not the goal itself.

What does leadership maturity look like for a PM?

It is the ability to work with diverse people, hold to standards, support the superintendent without smothering them, and stay constructive under pressure. It is the opposite of managing by email and avoiding hard conversations.

How does financial literacy differ from just tracking numbers?

Strategic financial literacy means shaping outcomes through proactive projection and relationship management creating win-win-win results for the owner, the company, and the trades. It is playing offense with the numbers, not just recording what already happened.

If you want to learn more we have:

Discover Jason’s Expertise:

On we go

What Lean Construction Is (And What It’s Not)

Posted on March 27, 2026March 27, 2026 by Jason Schroeder

Read 17 min

What Lean Construction Is And What It Is Not

I get fired up about this topic. Not in a bad way. In a this-matters-deeply-and-I-want-you-to-get-it-right way. Because Lean has changed how I see every jobsite, every team, and every project I have ever been a part of. And when it gets misrepresented when people use the word Lean to describe something it was never meant to be it sets back the very builders and trades who deserve the benefits most. So let’s clear the air.

What Lean Actually Is

Lean construction, at its core, is the willingness to learn and implement excellent practices for the purpose of benefiting people and humanity. That is the definition. Read it again slowly. It is not about efficiency for its own sake. It is not about squeezing more out of less. It is a commitment, a posture, a way of building that starts with people and ends with people.

Here is how I break it down. Lean is about respecting people, nature, and resources in a fundamental way. It is about stabilizing your project with cleanliness, organization, and safety. It is about creating standards so that work is predictable and repeatable. It is about working in one-piece, one-process, or one-progress flow meaning we do not start anything until we are ready to finish it with full kit. It is about flowing together, trades working shoulder to shoulder collaboratively, nobody going rogue, everybody following the system together and delivering a quality product. And it is about continuous improvement, the daily habit of asking how we can do this better and actually acting on the answer.

At Elevate Construction and LeanTakt, this is not a poster on the wall. It is how we build. Continuous improvement is woven into every training, every project, every system. And when teams commit to it fully, the results are not just better schedules and budgets. They are calmer projects, cleaner sites, fewer surprises, respected trade partners, and builders who are proud of what they built.

The Pain of Getting Lean Wrong

Here is the problem. Too many companies hear the word Lean and immediately think cost reduction. They walk into pre-construction thinking about labor counts. They sit in a Lean training looking for ways to do the same work with fewer people. And then they try to implement Lean from that mindset, and it fails. Every time. Without exception.

The people on the receiving end of that failure are not the executives who misapplied the concept. They are the foremen and workers who were told a better system was coming, who got their hopes up, who maybe even started to believe the project could run differently and then watched it collapse because the intention was never right. The system failed them again. Not because Lean doesn’t work. Because Lean was never truly implemented.

The System Failed Them

I want to say something here directly. When Lean is used as cover for cutting people or reducing staff, that is not a Lean failure. That is a leadership failure dressed up in Lean vocabulary. The people caught in that crossfire were not let down by a method. They were let down by leaders who grabbed a tool without ever understanding the philosophy behind it. The system failed them. They did not fail the system.

The companies that actually win with Lean are the ones that say something like this: we are going to do what is best for our people and our clients first, and as a natural result, we will do what is best for the business. That is the order. People and clients first. Business results follow. When you flip that sequence and lead with profits, Lean will cost you more than it ever saves you.

A Story From the Field

On one of my best projects, we implemented Lean to its fullest extent. We had morning worker huddles every single day. We taught the eight wastes. We gave out mission coins to workers who could recite them. We modeled improvements to foremen first and then to the whole crew. We gamified the recording of improvement videos and ended up with over 160 documented improvements still on YouTube today.

That did not happen because the company wanted to reduce headcount. It happened because the team believed in the people doing the work. Workers are brilliant. Given the right environment, the right clarity, and the right respect, they will improve anything you point them at. When you walk a clean, safe, organized site with a crew that is engaged and improving daily, you are seeing what Lean actually looks like. Not a spreadsheet. A culture.

What Lean Is Not

Let’s name it plainly because the industry is full of the misconceptions and the people paying the price are the ones doing the building.

Lean is not cutting people. It is not removing jobs. It is not replacing humans with software or eliminating the roles that field teams need. Anyone using Lean as a justification for workforce reduction has fundamentally misunderstood or deliberately misrepresented what Lean is. We do not have a labor shortage in this industry. We have a training problem. We have a respect-for-people problem. We have an unwillingness to invest in developing the people who are standing right in front of us waiting to be taught.

Lean is not bureaucracy. It is not added work. When Lean is implemented correctly, it reduces the cognitive load on every person on the project. It creates standards so people do not have to guess. It creates visual systems so people can see what is happening without having to be told. It removes the friction that makes the work harder, slower, and more frustrating than it needs to be.

Here are the things Lean is not, stated directly:

A quick-fix tool or a single software solution
A single method applied in isolation without a systems mindset
Classical management relabeled with Lean terminology to sell work
Rush, push, and panic dressed up in better vocabulary
Something compatible with CPM-only scheduling or throwaway culture

Lean is also not something you implement for the wrong reason and expect to survive. If the motivation behind your Lean effort is profit improvement or headcount reduction, walk away from it. Do not give it a bad name. The builders and trades who genuinely need what Lean offers deserve leaders who come to it honestly.

Why It Matters to Every Builder

Here is what is at stake. The construction industry has a massive opportunity to become what it was always capable of being: a profession that attracts talented people, develops them well, treats them with dignity, and produces remarkable work. That future is available. It is not theoretical. It is happening on projects right now where Lean is being implemented the right way, with the right intention, for the right reasons.

When Lean works, projects are calmer. Foremen are not firefighting every morning. Workers know what is expected and have what they need to deliver it. Families are protected because the people building the work are protected. That is not a side effect of Lean. That is the point of it. If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow. The proof test for Lean is simple: are your projects calmer? Is the site clean? Are the trades respected? Are outcomes predictable without heroics? If yes, you are building toward what Lean is meant to produce.

A Challenge for Every Builder

Before your next project kicks off, ask yourself what your real motivation is for implementing Lean. Not the answer you would give in a meeting. The honest one. Is it to bless the lives of the people on your project? Is it to create an environment where workers can win? Is it to protect families by protecting flow? If the answer is yes, you are ready. Lean will reward that commitment with results that no shortcut-seeking approach ever produces. As W. Edwards Deming said, “A bad system will beat a good person every time.” Lean is how you fix the system. Not the people. Never the people.

On we go.

Frequently Asked Questions

What is the simplest definition of Lean construction?

Lean construction is the willingness to learn and implement excellent practices for the purpose of benefiting people and humanity. It is built on respect for people, stability, one-piece flow, visual systems, and continuous improvement.

Why does Lean fail when companies use it to cut costs or reduce staff?

Because the foundational philosophy of Lean is respect for people. When the motivation is cost reduction or headcount reduction, that philosophy is absent from the start, and without it, the tools and methods have no foundation to stand on.

Is there really a labor shortage in construction?

Not in the way most people frame it. We have people. What we have is a training problem and a respect-for-people problem. When workers are developed, valued, and given a system that supports them, retention and performance both improve significantly.

How do I know if Lean is actually working on my project?

The proof test is practical: calmer projects, cleaner sites, fewer surprises, respected trade partners, and predictable outcomes without heroics. If your site is cleaner, your foremen are more prepared, and your crews know the plan, Lean is taking hold.

Can Lean work with CPM scheduling?

CPM as a standalone scheduling system is fundamentally incompatible with Lean because it does not show flow, trade sequencing, or zone-by-zone capacity. Lean-based scheduling systems like Takt and Last Planner are designed to make the plan visible, executable, and respectful of the people doing the work.

If you want to learn more we have:

Discover Jason’s Expertise:

On we go

Advanced Logistics Queuing

Posted on March 27, 2026March 27, 2026 by Jason Schroeder

Read 20 min

Why Logistics Kitting Is the Most Underused Productivity System in Construction

Walk onto most construction projects and within five minutes you’ll see it. Cardboard scattered across hallways. Materials piled near the stairwell that nobody ordered moved. A journeyman wandering two floors looking for a fitting that arrived three days ago but nobody knows where it went. The job is moving, but it’s grinding. And the crew doing the actual installing is burning time and energy on work that should have been solved before they ever picked up a tool.

That’s not a people problem. That’s a logistics problem. And it’s costing projects more than most teams realize.

What Most Projects Call Logistics

Here’s the honest picture on most job sites. A truck shows up. Someone calls the foreman. A couple of laborers get pulled off their work to help unload. The materials land in the nearest open space. The packaging stays on because no one has time to deal with it. The pallet gets broken down by whoever needs a piece first. And by the end of the day, what arrived as a complete delivery has been scattered across three floors, half of it still in cardboard, half of it missing from the count because nobody verified the delivery in the first place.

That pattern repeats every delivery day, on every project, until the site is a maze of material piles and packaging waste. Crews adapt by spending twenty minutes at the start of each task finding what they need. Leaders adapt by calling it normal. And the schedule absorbs the invisible hours as if they simply don’t exist.

They do exist. They show up as overtime, rework, and frustrated trades who feel like the project is working against them instead of for them. The system failed them. They didn’t fail the system.

A Different Way to See the Problem

Early in my career, I remember standing on a large federal project watching a crew stop installing mid-morning because the materials they needed for the next run were somewhere in the building but nobody could say exactly where. The foreman started walking. Twenty minutes later he came back with the wrong size. That’s a full-time tradesman fully loaded cost on the payrol burning half an hour on a logistics problem that a well-designed system could have solved the day before.

That moment crystallized something for me. The material delivery problem in construction is not a purchasing problem or a coordination problem in the traditional sense. It’s a system design problem. We have never intentionally designed how materials move from the truck to the hands of the worker. We just let it happen and then manage the chaos. That has to change.

What Advanced Logistics Queuing Actually Is

The concept is called advanced logistics queuing, and it treats the movement of materials from the delivery truck to the zone of install as a deliberate production system not an afterthought. The image at the top of this post maps it out clearly. Every element has a role and a location. Nothing is random.

It starts at the gate. Delivery trucks enter the project site and route directly past the project management trailer so that field engineers can perform materials inspections before anything moves. This is not a bureaucratic step. It’s a quality gate. Verifying materials at the point of entry checking counts, checking specs, identifying damage takes fifteen minutes and prevents three days of downstream problems. One project I worked on routed deliveries so they queued near the deck of the trailer, making it seamless for the office team to inspect before anything touched the yard. That one design decision eliminated weeks of RFI delays that used to come from wrong materials reaching the zone.

From there, materials move into the unpacking and kitting logistics area. This is where the real work happens outside the building. A yard forklift unloads the truck onto unpacking stations where the team removes all packaging, cardboard, and shipping materials. Debris removal dumpsters are staged in the yard for immediate disposal, compacting, and recycling. Nothing goes into the building wrapped in cardboard. Nothing carries packaging waste onto a finished floor. This is “nothing hits the floor” thinking applied to logistics the work area stays clean, and materials arrive in the condition they’ll be used, not the condition they were shipped in.

Here is where most projects stop and where great projects are just getting started.

Watch for these signals that logistics has not been designed on your project:

Crews are breaking down pallets in hallways and stairwells
Packaging and cardboard waste is accumulating inside the building
Foremen are making unscheduled trips to staging areas mid-task
Materials are staged by delivery date rather than by zone and crew need
Workers are searching for materials that are somewhere on site but unlocated

Kitting: Putting the Right Materials in the Right Place Before Work Starts

After unpacking, materials are sorted and loaded onto kitting pallets. Each pallet is built for a specific zone. Zone 1 gets exactly what Zone 1 needs for the Takt window. Zone 2 gets exactly what Zone 2 needs. Nothing extra goes into the zone. Nothing gets sent early just because it arrived. The pallet is built the way a kit gets built completely, intentionally, in advance.

This is Point-of-Use Storage and Kitting in practice. Jason Schroeder teaches this as a core Lean principle: eliminate walking, searching, and re-handling by delivering complete work packages to the place of install. When kitting works, the crew doesn’t become the supply chain. The supply chain has already done its job before the crew touches a tool.

Once the kitting pallets are staged, telehandlers deliver them directly to the work area. Visual indicators on the pallets or the zone board communicate readiness, so trades know exactly what has arrived and where it sits before they walk to the zone. There is no guessing, no hunting, no forty-five-minute material chase to start the morning.

The Water Spider Role

The people who operate this logistics system are called Water Spiders. This is a formal role, not an informal assignment. Water Spiders are logistics specialists whose entire job is to feed crews what they need, just in time, at the place of work. They shake out materials, manage the kitting area, coordinate delivery sequencing, and keep the zones supplied so the trade workers can focus entirely on installing.

The principle behind the Water Spider is simple and powerful. Value-adding workers should be adding value. Installers should be installing. When an electrician, pipefitter, or carpenter spends a meaningful portion of the day doing logistics work moving materials, breaking down deliveries, searching for parts the system is robbing the project of its most expensive resource. The Water Spider absorbs that burden and returns it to where it belongs: a specialized logistics role that costs far less than the value it protects.

This is how Lean projects eliminate material chaos and create real installation flow. The procurement feeds production. The supply chain is zoned. Just-in-time means the crew has exactly what they need at the place of work when they need it. When logistics flows, production flows. When logistics breaks down, everything breaks down not because the trades failed, but because the system failed to feed them.

Why This Connects to Dignity and Flow

There is a human dimension to all of this that gets lost in the logistics conversation. When a skilled tradesperson spends hours every day searching for materials, waiting for deliveries, or working around packaging waste, that is not just inefficiency. It is disrespect. It says the system doesn’t value their time. It says their craft matters less than the chaos that surrounds them. It burns people out quietly, day by day, until they either check out or leave the trade entirely.

Protecting logistics is protecting people. When the system delivers exactly what the zone needs, when the zone needs it, crews can perform at the level they were trained for. They can take pride in the installation. They can finish the zone completely before moving to the next one. They can go home at a reasonable hour because the day wasn’t eaten by supply chain problems. If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow. That work starts with designing the system right from the gate to the zone.

Build the System That Feeds Your Crews

Here is the challenge I want to leave you with. Look at your next project during preconstruction and ask one question: have we designed how materials will move from the delivery truck to the hands of the installer? Not “where is the laydown yard?” That’s a location decision. The design question is: how does a material get inspected, unpacked, kitted by zone, and delivered to the place of work without a tradesperson ever having to leave the zone to find it?

If you can answer that question clearly before the project mobilizes, your crews will feel the difference on day one. LeanTakt and Elevate Construction have seen what happens when logistics is treated as a production system rather than an afterthought. The zones stay clean. The crews stay in flow. The schedule holds. Taiichi Ohno, the father of the Toyota Production System, said it best: “All we are doing is looking at the timeline from the moment the customer gives us an order to the point when we collect the cash. And we are reducing that timeline by removing the non-value-added wastes.” In construction, logistics waste is one of the biggest wastes we have. And it’s one of the most fixable.

On we go.

Frequently Asked Questions

What is advanced logistics queuing in construction?

Advanced logistics queuing is a deliberate system for moving materials from the delivery truck through inspection, unpacking, kitting, and zone delivery without bringing packaging waste or unorganized material into the building. It treats material flow as a designed production process, not a random site activity.

What is kitting and why does it matter?

Kitting is the process of sorting and staging materials onto zone-specific pallets before they enter the building. Each zone receives exactly what it needs for its Takt window. Kitting eliminates searching, re-handling, and crew downtime caused by missing or misplaced materials at the point of install.

What is a Water Spider in Lean construction?

A Water Spider is a dedicated logistics support role whose job is to supply crews with what they need, just in time, at the place of work. The role exists so that value-adding trade workers stay installing rather than doing logistics tasks. It’s a structural advantage that protects production pace and crew focus.

How does logistics kitting support the Takt Production System?

Takt requires trades to move through zones on a steady rhythm. If materials aren’t ready in the zone when the trade arrives, the rhythm breaks. Kitting by zone ensures the supply chain matches the Takt plan, so each zone is fed in the right quantity at the right time and the train of trades stays moving.

Where do material inspections happen in this system?

Inspections happen at the delivery entry point, before materials reach the unpacking area. Routing trucks past the project management trailer gives field engineers the opportunity to verify counts, check specifications, and identify damage before anything moves deeper into the site preventing downstream quality and schedule problems.

If you want to learn more we have:

Discover Jason’s Expertise:

On we go

The Crew Preparation Huddle

Posted on March 27, 2026March 27, 2026 by Jason Schroeder

Read 20 min

What the Crew Preparation Huddle Actually Does And Why It Changes Everything

Here’s the deal: all that planning you did the pull plan, the look-ahead, the weekly work plan, the preconstruction meeting none of it matters if the person actually doing the work cannot see it. That’s the hard truth. And most job sites are built in a way that guarantees the worker never gets there.

Walk any large project and ask a journeyman what the plan is for today. Not what the foreman mentioned in the parking lot the actual plan, the sequence, the quality standard, the coordination handoff with the trade coming behind. Most of the time, the answer is a shrug. Not because the worker doesn’t care. Because the system was never designed to tell him.

The plan lives in someone’s laptop. The schedule is a 76-page PDF that no one in the field can read. The quality standard is in a binder in the trailer. The zone map is on a screen three floors above the work. The information exists. It’s just completely inaccessible to the person who needs it most. And that single failure cascades into rework, stacking trades, safety pressure, and exhausted crews pushing to the finish line every single week.

The Pattern That Created This Problem

Construction has been designed, for decades, as a top-down information system. Leadership creates the plan. Management communicates the plan. Workers execute the plan. And somewhere in that chain, the plan gets filtered, simplified, and eventually reduced to “just start over there and work your way down.”

The people closest to the work have the least access to the information about the work. And then we wonder why quality fails. Why coordination breaks down. Why the same problems repeat zone after zone, floor after floor. The system produced those outcomes, not the workers. A bad system will beat a good person every time. The workers showed up ready. The system wasn’t ready for them.

The System Failed Them

The workers on your projects are skilled professionals electricians, pipefitters, carpenters, ironworkers. People who have spent years mastering their craft. They show up every day ready to produce. The problem is the system keeps them in the dark. It filters, fragments, and delays the information they need, then holds them accountable for outcomes the system made impossible. The system failed them. They didn’t fail the system.

Early in my career, I was a field engineer at a project at Whole Foods world headquarters. Two rod-busting crews, same size, same experience, same tools and materials. One was always ahead. The other was always behind. I asked the foreman of the crew that was consistently ahead what was going on. He said, “Jason, look at that other foreman. What’s he doing?” The other foreman was tying rebar head down, working right alongside his crew. The foreman next to me said, “That’s the problem. He’s working his time bar. When he hits a roadblock, his crew hits a roadblock. I bring materials and information to my crew all day long. I get out ahead of them.” That stuck with me for my entire career. The foreman’s job is not to be the hardest worker in the crew. It’s to be the best preparer. And preparation only works when the information is right there visible, accessible, in the zone, before the work starts.

Why This Matters Beyond Productivity

When workers can’t see the plan, they guess. Guessing in construction leads to rework. Rework leads to schedule compression. Schedule compression leads to stacking trades. Stacking trades leads to safety incidents and exhausted crews. Every one of those outcomes has a human cost. Schedules compress and families lose evenings. Trades stack and workers cut corners under pressure.

This is not just a productivity issue. It’s a respect issue. A family issue. A dignity issue. If we are serious about protecting workers and protecting the families that depend on those workers coming home whole then getting the right information into the field, every single day, is the whole game. Flow over busyness. Clarity over chaos. The plan has to reach the crew.

What the Crew Preparation Huddle Is and How It Works

The Crew Preparation Huddle is a short, structured daily meeting where the crew gathers in the zone, around a visual crew board and prepares for the work together. Not a safety toolbox talk in a parking lot. Not a general announcement with no connection to the crew’s specific scope. An actual, practical, plan-the-day session that involves the people doing the work, built around information they can see and act on immediately.

The crew board is the anchor of the entire system. It moves with the crew. On the front sits the look-ahead plan, the weekly work plan, production visuals, and zone maps that crews can mark up with magnets or dry-erase markers. This is not information buried in a schedule it’s in the zone, readable by the workers who are about to do the work. On the back sit Installation Work Packages, crew prep meeting guides, feature-of-work expectations, and visual quality standards for how the work should be done. The quality checklist built in the preconstruction meeting three weeks ago? Right there. The visual standard for a proper installation? On the board that travels with the crew.

Watch for these signals that the Crew Preparation Huddle is missing or broken on your project:

Workers are unclear on today’s scope and sequence when the day starts
Quality failures are discovered after the work is complete, not before it begins
The same coordination breakdowns repeat week after week in different zones
Foremen are working alongside crews instead of planning ahead of them
Lean habits like 5S and waste identification feel like GC programs, not crew practices

The huddle agenda is deliberate from start to finish: shout-outs, safety training, a review of the last day or zone, a reflection and improvement session, day planning, a Lean training topic, stretch and flex, a walk of the work area, filling out the pre-task plan, and a 5S check with a look for the eight wastes. Each step serves a purpose. The review of yesterday builds a culture of continuous improvement. The Lean training topic even two minutes builds a crew that understands the system they’re working inside. The walk of the work area creates shared situational awareness before a single tool is picked up. In a Takt production system, this daily crew-level visibility is what keeps zones flowing on rhythm and handoffs clean.

What Total Participation Actually Looks Like

Jason Schroeder teaches that visual systems exist for one reason: total participation. Visual management is a core Lean principle a work environment that is self-explaining and self-improving because the right information is visible to everyone who needs it. The Crew Preparation Huddle is that principle made operational at the crew level. The board doesn’t just display information. It creates a daily ritual where the crew engages with the plan, improves the plan, and owns the plan.

Total participation in practice means leaders come to the board instead of workers going to the trailer. Problems get raised by the crew before they become roadblocks. Zones finish completely because handoff expectations are visible and understood by everyone. The plan gets better every day because the people doing the work are the ones improving it. Lean is impossible without standard work at the crew level and standard work is impossible without visibility. If workers cannot see the plan, reflect on it, and improve it, there is no total participation. There is only managed execution from a distance. As Jason teaches, everything visual so that we have total participation that’s not a nice-to-have. It is one of the six foundational pillars of Lean in construction.

Dignity, Respect, and the Reason All of This Matters

The Crew Preparation Huddle is ultimately about respect respect for the worker’s skill, judgment, and intelligence. Respect for the crew’s ability to improve a process when given the right tools and information. Respect for the families who depend on stable, predictable work.

When we design systems that bring the plan to the worker visually, accessibly, every morning we are not just improving production metrics. We are saying to every person on that crew: you deserve to know what we’re building today, and your opinion on how to build it better matters. If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow. That mission is simple: we’re building people who build things.

A Challenge for Builders

Here’s what I want you to do next week. Walk up to a journeyman on your project and ask: “What are you building today, and how does it connect to what the next trade needs from you?” If the answer is confident and clear, your system is working. If the answer is a shrug, you know exactly what to fix. Run the Crew Preparation Huddle consistently. Bring leaders to the board. Train the crew every day even for two minutes. Reflect, improve, and plan again tomorrow. Do that for thirty days and watch what happens to your project, your quality numbers, and the energy of your crews. W. Edwards Deming said it plainly: “A bad system will beat a good person every time.” The Crew Preparation Huddle is how you fix the system one crew, one zone, one day at a time.

On we go.

Frequently Asked Questions

What is the Crew Preparation Huddle, and how is it different from a safety meeting?

The Crew Preparation Huddle is a structured daily meeting where a crew gathers in their work zone to review yesterday, improve the process, plan the day, cover safety, walk the area, and look for waste. It is specific to that crew’s work package and zone not a general announcement. The purpose is preparation, not compliance.

What is on the crew board, and why does it move with the crew?

The front holds the look-ahead, weekly work plan, production visuals, and markable zone maps. The back holds Installation Work Packages, meeting guides, and visual quality standards. The board moves with the crew because the plan needs to be where the work is not in a trailer three floors away.

How does the Crew Preparation Huddle support Lean construction?

Lean requires visual systems for total participation, and the Crew Preparation Huddle makes that real at the crew level. Lean is impossible without standard work and visibility at the crew level. If workers cannot see, reflect on, and improve the plan, total participation doesn’t exist.

What role does the foreman play during and after the huddle?

The foreman facilitates the huddle, then spends the rest of the day planning and preparing work ahead of the crew not working alongside them. A foreman who gets ahead of the crew ensures they never stop. The huddle sets the crew up for a full, uninterrupted day of production.

What are the 8 wastes and why do crews look for them daily?

The 8 wastes in Lean construction are defects, overproduction, waiting, non-utilized talent, transportation, inventory, motion, and extra processing. Looking for them daily builds the habit of continuous improvement at the field level, turning workers into active problem-solvers not passive executors.

If you want to learn more we have:

Discover Jason’s Expertise:

On we go

Respect for People: The Foundation That Makes Lean Construction Work

Posted on March 27, 2026March 27, 2026 by Jason Schroeder

Read 16 min

Respect for People: The Foundation That Makes Lean Construction Work

Most construction companies say they value people. Walk the average jobsite for one day and you will see the truth. Not because the people are bad. Not because the leaders do not care. But because the system they inherited was designed around a different assumption entirely that people are costs to control, not capacities to develop. And until that assumption changes, every Lean tool you implement is building on sand.

The Pain That Lives on Every Jobsite

Here is the pattern that plays out on projects running under the old command-and-control mindset. Labor gets tracked obsessively as a cost rather than as a capacity. Workers get measured instead of the waste in the system getting measured. People are caught failing rather than being set up to succeed. Leadership shows up through pressure, criticism, and stress. And the results are predictable. Turnover is high. Quality suffers. Schedules slip. People disengage. The team stops bringing problems to the surface because the surface is not safe.

The painful part is that this is not a malicious system. Most of the leaders perpetuating it were trained inside it. They were told that tight control and high pressure are what drive results. Nobody ever stopped to ask what the workers were experiencing on the receiving end of that philosophy, or what it was doing to the quality of their thinking, their commitment, and their willingness to give the project their best.

The Failure Is in the System, Not the People

When turnover is high, the instinct is to ask what is wrong with the people leaving. When quality suffers, the instinct is to ask who made the mistake. When schedules slip, the instinct is to push harder. Every one of those instincts is pointing in the wrong direction. The correct question is always: what in the system made this outcome inevitable? The workers showed up to an environment built around catching them failing instead of helping them succeed. The foremen operated in a culture that punished problems instead of surfacing and solving them. The system failed them. They did not fail the system.

A Story That Changed How I See Leadership

I have been on jobsites where the morning worker huddle was the most respected fifteen minutes of the day. Where workers knew what was happening, knew the safety focus, knew the plan, and knew that if they had a problem, raising it would result in action not blame. On those projects, something remarkable happens. Workers start improving things without being asked. Foremen start surfacing roadblocks before they become crises. The team begins to function as one social group instead of a collection of separate subcultures waiting for the shift to end.

I have also been on jobsites where none of that was true. Where workers felt expendable, where feedback loops ran in one direction only, and where the only leading indicator anyone measured was labor cost per hour. On those sites, you could feel the tension from the parking lot. The system was telling people every single day that they did not matter, and those people responded exactly the way you would expect anyone to respond to that message.

The difference between those two experiences is not the workers. It is not even the schedule. It is whether respect for people is structural on that project, embedded in the environment, the meetings, the coaching, and the expectations or whether it is a laminated value statement on the trailer wall that nobody takes seriously.

What the Lean Mindset Actually Looks Like

The shift from command-and-control to Lean leadership is not about being softer or lowering expectations. It is about understanding what actually produces results. The Lean mindset develops capability instead of demanding output. It treats accountability as an act of care setting clear expectations, following through consistently, and doing it with dignity rather than humiliation. It guides instead of corrects, meaning the goal is to improve the process, not to shame the person. And critically, it fixes systems rather than blaming people, because in a healthy Lean environment, when something goes wrong, the first question is always what in the system allowed that to happen.

Here is what changes when this mindset takes hold on a project:

Trust between trades and leadership rises measurably
Stress levels drop because people are not hiding problems
Flow improves because roadblocks surface early when they can still be solved
Quality rises because workers bring their best thinking instead of just their hands

These are not soft outcomes. They are production outcomes. They show up in the schedule health, the punch list count, the safety record, and the morale of the team as they carry it across the finish line. Respect for people is not a values statement. It is a production strategy.

Why Tools Fail Without This Foundation

Takt Planning, Last Planner, and the Kanban Method are powerful systems. I believe in them deeply and have seen them transform projects. But here is something I want every builder reading this to understand clearly: those tools only work when the people within them feel respected. A Takt plan on a project where workers do not trust leadership becomes a schedule that trades quietly ignore. A Last Planner pull session on a project where foremen are afraid to surface constraints becomes a room full of optimistic commitments that nobody intends to keep. The tool is only as strong as the cultural foundation it sits on.

Lean tools require honest input, real commitment, and the willingness of every person on the project to surface what is actually happening in the field. None of that is possible in a command-and-control environment. You will not get people’s best thinking when they do not feel safe giving it. And without their thinking, you do not have continuous improvement. You have compliance and compliance produces mediocrity, not excellence.

Connecting to the Mission

At Elevate Construction, the phrase we come back to is this: we build remarkable people who build remarkable things. That is not a slogan about construction. It is a belief about the sequence. You build the person first. The person builds the project. When people are developed, respected, and given systems that support them, quality and flow are the natural consequence. Families are protected because the workers building the project are protected. Schedules hold because the teams running them are stable. Safety improves because people feel safe enough to stop and say something when something is wrong.

This is what the image at the top of this post is really saying. Clean environments, shoulder-to-shoulder coaching, systems designed for human success, an empowered and smiling workforce those are not perks. They are the foundation that everything else stands on. If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow.

A Challenge Before Your Next Project Meeting

Walk your project today and ask yourself the honest question. Not the version you would say in a leadership meeting. The real one: do the people on this site feel respected? Not just employed. Not just managed. Respected. Do they have clean facilities? Do they know the plan? Do they feel safe raising a problem? Does leadership show up shoulder to shoulder, or does it show up to inspect and correct?

When we put people before the product or the profit, the product and profit take care of themselves. That is not idealism. That is the most practical truth in construction. Build the foundation right, and everything you stack on top of it will hold.

On we go.

Frequently Asked Questions

What does “respect for people” actually mean on a construction site?

It means creating an environment where workers have clean facilities, clear plans, and a leadership team that develops capability rather than just demanding output. Respect is structural it shows up in how the site is run every single day.

How is accountability compatible with a respect-for-people culture?

Accountability in a Lean culture is an act of care, not punishment. It means setting clear expectations and addressing performance with dignity, because treating people as capable adults who deserve clarity is the most respectful thing a leader can do.

Why do Lean tools fail when the culture is command-and-control?

Because tools like Takt Planning and Last Planner depend on honest input from the field. When people do not feel safe surfacing problems, the tools become theater instead of production control.

What is the difference between guiding and correcting?

Guiding focuses on improving the process so the same mistake does not repeat. Correcting focuses on the individual who made it. The first produces learning and loyalty. The second produces defensiveness.

How do you know if respect for people is actually embedded in your project culture?

Watch the leading indicators: do foremen surface problems proactively, is the site clean, and does the team move together as one group? When those things are true, respect is structural not just a value on a poster.

If you want to learn more we have:

Discover Jason’s Expertise:

On we go

Estimating Deadlines

Posted on March 27, 2026March 27, 2026 by Jason Schroeder

Read 29 min

Are You Setting Realistic Deadlines or Just Telling People What They Want to Hear?

You’re in schematic design and the owner asks how long the project will take. Your instinct says 14 months based on similar projects. But you know they want to hear something faster. So you say 11 months. You tell yourself you’ll make it work. You’ll push harder. You’ll find efficiencies. You’ll figure it out. Then reality hits in construction. The project takes 13 months. The owner is furious because you missed your commitment. Your team is burned out because you spent months in crisis mode trying to achieve a deadline that was never realistic. And you wasted everyone’s time and money crash landing a project that could have flowed smoothly if you’d just told the truth upfront.

Here’s what actually happened. You lied. Not maliciously, but you lied. You committed to a deadline you knew you couldn’t hit because saying 14 months felt uncomfortable. And that lie guaranteed failure before the project even started. Contractors undercut budgets, team sizes, and durations by 15 to 20 percent routinely. We call it competitive pricing. We call it aggressive scheduling. But it’s lying to customers, then scrambling to get back the time we never had in the first place. And the scramble destroys people, quality, and profit while delivering projects late anyway because unrealistic deadlines create the very delays they’re meant to prevent.

The deeper problem is that humans are horrible at estimating time and deadlines. Studies show we can be four times off in early planning phases and two times off even in detailed design. We’re better at estimating effort than duration. But we keep using CPM schedules built on time guesses instead of Takt planning built on effort estimates and flow analysis. So we stay bad at deadlines while pretending we’re getting better. The solution is not trying harder to guess. It’s admitting we’re terrible at it and using systems that estimate what we can actually estimate, which is effort, not time.

The Real Pain: Deadlines Nobody Can Hit

Walk into any project struggling with schedule and you’ll see the pattern. Leadership committed to a deadline they knew was aggressive. They told themselves they’d make it work through efficiency and hustle. Then reality hit. The deadline was impossible. But they’d already committed to the owner. So instead of renegotiating, they pushed. They threw more people at the work. They extended hours. They crashed the schedule. And the project still finished late. But now it also finished over budget with burned-out people and quality problems because pushing doesn’t create time. It creates waste.

The pain compounds when teams realize the deadline was always unrealistic. The project executive guessed durations based on gut feel. Foundations three months. Superstructure four and a half. Finishes five. Closeout two. Total 14 and a half months. But we’ll fit it in 13 because that’s what the owner wants. No flow analysis. No Takt planning. No trade input. Just guessing based on similar projects and aggressive hoping. Then six weeks into construction someone does the actual analysis and discovers the project needs 15 months minimum just for procurement alone. But leadership already committed to 13. So the team suffers trying to achieve the impossible while leadership blames execution instead of admitting the deadline was broken from the start.

The worst part is the culture this creates. When missing deadlines becomes routine, deadlines lose meaning. People stop trusting commitments. They assume every deadline will slip so they don’t take them seriously. And leadership loses credibility because everyone knows the schedules are fiction. You can’t build a culture of discipline when deadlines are negotiable. Real discipline means refusing to commit to deadlines you can’t hit, then hitting the deadlines you do commit to 100 percent of the time. But most construction companies do the opposite. They commit to impossible deadlines, then normalize slippage. And that destroys trust with owners and teams.

The Failure Pattern: Guessing Time Instead of Estimating Effort

Here’s what teams keep doing wrong. They estimate time when they should estimate effort. Time estimation is terrible. Studies show we can be two to four times off depending on project phase. But effort estimation is much better. Within about 25 percent error, you can consistently estimate effort if you anchor it properly. So when you use CPM schedules built on time guesses, you’re optimizing for the thing humans are worst at. When you use Takt planning built on effort estimates and flow analysis, you’re optimizing for what we can actually predict. The tool determines whether you fail or succeed before you start.

They also create deadlines based on what people want to hear instead of what’s actually achievable. The owner wants 11 months. Your analysis says 14. But you commit to 11 anyway because saying 14 feels like losing the job. So you lie to get the work, then spend the entire project in crisis trying to make up time that never existed. This is not competitive. This is dishonest. And it guarantees failure. A realistic 14-month deadline that you hit on time with quality work builds more trust than an aggressive 11-month deadline you miss while delivering poor quality and burning people out.

The failure deepens when they don’t use intermediate milestones to track progress. They commit to a final completion date months or years away. Then they drift. No mini marches. No intermediate deadlines forcing accountability. Just a vague target in the distant future that everyone knows will slip. When you break projects into shorter milestones, completion dates you can actually see and commit to, you create accountability. You know immediately when you’re off track. You can course correct before the problem compounds. But when your only deadline is 18 months away, you drift for 12 months before realizing you’re six months behind. And by then recovery is impossible.

The System Failed You

Let’s be clear. When teams commit to unrealistic deadlines, it’s not because they’re dishonest or incompetent. It’s because the system rewards aggressive bidding over realistic planning. The contractor who says 11 months gets the job. The contractor who says 14 months loses to the competition. So everyone lies. Everyone underbids. Everyone commits to deadlines they can’t hit. And everyone scrambles through projects in permanent crisis mode pretending this is normal. The system created this by rewarding optimistic lies over realistic truth.

The system fails because it never taught people to estimate effort instead of time. We learned to build CPM schedules with duration guesses. Three months for foundations. Five months for finishes. Numbers pulled from gut feel and adjusted to fit what owners want to hear. But we never learned that humans are terrible at time estimation and much better at effort estimation. We never learned about Takt planning that estimates the effort for each work package, simulates flow, and produces schedules dramatically more accurate than CPM even in early design phases. So we keep using tools that guarantee failure while wondering why our deadlines are always wrong.

The system also fails because it treats deadline slippage as normal. When missing deadlines becomes routine, deadlines lose power. They become suggestions instead of commitments. And that destroys the culture of discipline required for real performance. Jim Collins teaches that a culture of discipline is about freedom in a framework, not about disciplining people. It’s about finding self-disciplined people who always fulfill commitments. But you can’t build that when deadlines are flexible. You need zero tolerance for missing deadlines, which means zero tolerance for committing to deadlines you can’t hit. The discipline is in the refusal to make unrealistic commitments, not in the heroics of trying to achieve them.

What Realistic Deadlines Look Like

Picture this. A contractor is asked for a completion date. His gut says October 31st feels aggressive but achievable. He offers that date. The owner pushes back. That deadline is too aggressive. We both know there’s almost no chance you hit October 31st, which makes it useless. Come back with a deadline you can 100 percent commit to hitting with perfect work, absolutely complete, absolutely on time, no matter what happens with weather and unexpected problems. The contractor reconsiders. March 31st at 5 PM. Now that’s a deadline. Can you 100 percent commit? Yes. No problem.

The owner clarifies: it’s not my deadline, it’s your deadline. The pace quickens. The team hits the deadline at 4:45 PM on March 31st with 15 minutes to spare. This is how deadlines work when they’re realistic commitments instead of aggressive wishes. The deadline was achievable. The commitment was 100 percent. And the team delivered because the deadline wasn’t fiction. It was truth.

The project also uses Takt planning instead of CPM guessing:

Estimate effort for each work package based on crew size, production rates, and historical data, not time guesses.
Simulate flow using Takt wagons and trains that show how work moves through the building in a repeatable rhythm.
Involve trades early so durations come from the people who’ll do the work, not from gut feel in a conference room.
Build intermediate milestones every few weeks so the team stays on mini marches with clear short-term targets they can actually see and commit to.

This produces schedules dramatically more accurate than CPM even in schematic design because it estimates what humans can estimate, which is effort and flow, not abstract time in a vacuum.

The team also builds a culture where missing deadlines is not an option. There are only two acceptable ways to miss a deadline. First, the person you committed to changes the deadline without you asking. Second, you’re truly incapacitated by something that happened to you or your loved ones and it would be inhumane to hold you to it. Otherwise, you hit your deadline. Period. And that means refusing to commit to deadlines you can’t hit. Self-disciplined people crave wide latitude to do their best work, but they refuse to accept impossible constraints that guarantee failure. If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow.

Why Realistic Deadlines Matter

Realistic deadlines enable flow. When you commit to achievable durations, you can plan work properly. Make-ready happens. Constraints get removed. Work flows. But when you commit to impossible durations, you skip planning and start pushing. You throw more people at the work. You extend hours. You crash the schedule. All of which creates more waste than it eliminates. Counterintuitively, realistic deadlines that feel slower produce faster results because they enable flow instead of forcing chaos.

Realistic deadlines also protect people. When you commit to 11 months knowing you need 14, you guarantee your team will burn out trying to achieve the impossible. They’ll sacrifice their families. They’ll work 80-hour weeks. They’ll grind through months of crisis. And they’ll still miss the deadline because it was never achievable. But they paid the price in their health, their relationships, and their well-being. Realistic deadlines mean people can succeed without destroying themselves. That’s not soft. That’s strategic. You can’t build a sustainable business on burning people out project after project.

Most importantly, realistic deadlines build trust. When you commit to 14 months and deliver in 14 months with perfect work, owners trust you. When you commit to 11 months, deliver in 13 months with quality problems and cost overruns, owners never trust you again. One realistic commitment kept builds more business than ten aggressive commitments missed. Trust is the foundation of repeat work and referrals. And you can’t build trust with lies, even optimistic ones.

How to Set Realistic Deadlines

Start by admitting you’re terrible at estimating time. Stop using CPM schedules built on duration guesses. Start using Takt planning built on effort estimates and flow simulation. Estimate the effort for each work package based on crew sizes and production rates. Build Takt wagons showing how work moves through the building. Simulate flow. Involve trades so durations come from people who’ll do the work. This produces schedules dramatically more accurate than CPM because it estimates effort, which humans can predict, instead of time, which we can’t.

Set intermediate milestones. Don’t just commit to a completion date 18 months away. Break the project into mini marches with milestones every few weeks. Substantial completion of this phase. Closeout of that area. Clear short-term targets the team can see and commit to. This creates accountability. You know immediately when you’re off track. You can course correct before problems compound. And you build momentum through small wins instead of drifting toward a distant deadline you’ll probably miss.

Build a culture of discipline where missing deadlines is not an option. Not by disciplining people who miss deadlines, but by refusing to commit to deadlines you can’t hit. Ask for proposed deadlines from your team. Navigate to realistic dates with zero tolerance for missing them. Make it clear that there are only two acceptable ways to miss: the person you committed to changes it, or you’re truly incapacitated and it would be inhumane to hold you. Otherwise, you hit your deadline 100 percent of the time with perfect work. That’s discipline. And it starts with realistic commitments, not aggressive wishes.

The Challenge

Here’s your assignment. Look at your current project commitments. Are they realistic or aggressive wishes? If you committed to durations you knew were optimistic, you set your team up to fail. Stop doing that. Go back to the owner. Show them the Takt plan. Explain that the realistic duration is longer than you originally said. Renegotiate now before you miss the deadline and destroy trust. Honesty upfront builds more credibility than lies that lead to slippage.

Start using Takt planning instead of CPM guessing. Estimate effort, not time. Simulate flow. Involve trades. Build schedules based on what humans can actually predict. And refuse to commit to deadlines you can’t hit. If the owner wants 11 months and you need 14, say 14. If they go with the competitor who says 11, let them. You’ll get the call when that competitor misses the deadline. And your reputation for realistic commitments that you actually keep will build a business that lasts.

Build intermediate milestones. Break your project into mini marches with clear short-term targets every few weeks. Create accountability. Track progress. Course correct immediately when you drift. Don’t wait until you’re six months behind to realize the deadline was fiction. Know immediately and fix it fast.

Stop lying to get work. Start telling the truth to build trust. Realistic deadlines that you hit build more business than aggressive deadlines you miss.

Jim Collins said deadlines stimulate progress, but only if they are commitments. To hit a deadline means achieving the objective with absolutely A-level work, absolutely complete, absolutely on time, absolutely without complaint.

On we go.

FAQ

How do you convince owners to accept realistic deadlines instead of aggressive ones?

Show them the data. Build a Takt plan that estimates effort and simulates flow. Make it visual so they can see exactly why the project needs the duration you’re proposing. Explain that realistic deadlines you hit build more trust than aggressive deadlines you miss. Most owners would rather have truth upfront than optimistic lies that lead to slippage and conflict later.

What if your competitor bids 11 months and you bid 14 months?

Let them have it. When they miss the deadline and deliver poor quality, the owner will remember you told the truth. Your reputation for realistic commitments builds long-term business even if you lose some short-term jobs. Trust is worth more than winning every bid with lies.

How do you estimate effort instead of time?

Use historical production rates, crew sizes, and work package analysis. In Takt planning, estimate how much effort each work package requires, then simulate how that flows through the building in a repeatable rhythm. This estimates what humans can predict, which is effort and flow, instead of abstract time durations we’re terrible at guessing.

What if your team committed to an unrealistic deadline already?

Renegotiate now. Go to the owner with a Takt plan showing the realistic duration. Explain that the original commitment was based on incomplete information. Ask to reset the deadline to something achievable. Some will say yes. Some won’t. But honesty now is better than slippage later that destroys trust completely.

How do you build a culture where missing deadlines is not acceptable?

Start by refusing to commit to deadlines you can’t hit. Make it clear that the only acceptable reasons to miss are if the person you committed to changes the deadline, or you’re truly incapacitated. Otherwise, you hit your commitment 100 percent of the time. This requires self-disciplined people who refuse impossible constraints instead of accepting them and failing heroically.

If you want to learn more we have:

Discover Jason’s Expertise:

Don’t Assume It’s a, “No!

Posted on March 27, 2026March 27, 2026 by Jason Schroeder

Read 31 min

Are You Leaving Good Decisions on the Table by Not Asking?

You know your project needs three more weeks. The duration you promised in schematic design was based on incomplete information and CPM guessing, not actual Takt planning with trade input. But you don’t ask the owner for more time because you assume they’ll say no. You know your team needs another field engineer to prevent the quality disasters piling up. But you don’t ask your company for the hire because budgets are tight and you assume they’ll reject it. You know a change order is warranted because the scope actually changed. But you don’t submit it because you assume the owner will fight it. So you eat the cost, extend your team’s hours, and watch people burn out while the project suffers. All because you assumed no without ever asking the question.

Here’s what you’re missing. Most people will say yes more than you think the first time you ask for something that’s actually needed. Studies show 80 percent approval rates for reasonable requests backed by data. Owners want their projects to succeed. Companies want their teams supported. People want to do the right thing. But they can’t say yes to requests you never make. You’re leaving good decisions on the table. Resources that would protect people. Time that would preserve quality. Budget that would prevent disasters. All available if you’d just ask. But you won’t ask because you’ve convinced yourself the answer is no before you tried.

The catch is the second yes. Most people will say yes the first time when you ask for what’s needed and show them the data. But when you come back asking again because you didn’t do your due diligence the first time, that’s when they get angry. When you tell an owner the project is 11 months in schematic design, then come back in CDs asking for 13 months because you finally did real planning, they feel manipulated. When you ask for budget, get it, then ask for more because your original estimate was sloppy, they lose trust. The first yes is easy if you’ve done your homework. The second yes is nearly impossible because it proves you didn’t.

The Real Pain: Needs That Go Unmet Because You Won’t Ask

Walk any struggling project and you’ll see the pattern. Superintendents who need help but won’t ask for it because they think asking proves weakness. Project managers who know the schedule is impossible but won’t go to the owner because they assume pushback means no. Teams that need training, resources, or support but never request them because the culture says figure it out yourself. And everyone suffers. Quality drops. Safety incidents increase. People burn out. Families pay the price. All because nobody asked for what was needed to prevent the disaster.

The pain compounds when you finally do ask but you ask wrong. You go to the owner without data. Just a request for more time or more money without showing them why. They say no because you didn’t make it visual. You didn’t show them what the is is. You just asked for more without proving you need it. Or worse, you ask after you already got a yes once. You told them 11 months. They planned around it. They made commitments. Then you come back asking for 13 months because you didn’t do Takt planning upfront and your original estimate was garbage. That second ask destroys trust even when the request is legitimate. Because it proves you didn’t do your homework the first time.

The worst part is the three types of yes you don’t recognize. Chris Voss teaches in Never Split the Difference that not all yeses are the same. There’s the counterfeit yes, where someone plans to say no but uses yes as an escape route or to get more information from you. There’s the confirmation yes, just simple affirmation with no promise of action. And there’s the commitment yes, the real deal that leads to action. Most people confuse these. They get a confirmation yes or even a counterfeit yes and think they have commitment. Then they’re shocked when nothing happens. You need commitment yes. But you won’t get it if you don’t know how to ask for it properly.

The Failure Pattern: Assuming No Without Ever Asking

Here’s what teams keep doing wrong. They assume no before they ask. They need resources. They need time. They need support. But they’ve internalized a culture that says don’t ask, just make it work. So they don’t ask. They grind. They extend hours. They burn people out. They accept quality failures. They watch projects struggle. All while the resources they need sit available, waiting for someone to request them with data that shows why they’re needed. But nobody asks. So nobody gets. And everyone suffers.

They also ask without doing their homework. When they finally do ask, they show up unprepared. No data. No visual schedule showing the constraint. No budget breakdown showing the cost. Just a request for more without proving why. And leadership or owners say no because the request looks like guessing or complaining, not legitimate need. If you’d done Takt planning in preconstruction instead of CPM estimating, you’d know the real duration. If you’d involved trades early, you’d have real pricing. If you’d made the constraint visual, you could show exactly why you need what you’re asking for. But you didn’t. So your ask looks like incompetence instead of legitimate need.

The failure deepens when they get a first yes then come back for a second. You told the owner 11 months. You got buy-in. They planned their financing, their occupancy, their commitments around that number. Then you come back asking for 13 months because you finally did real planning and discovered your original estimate was wrong. They’re furious. Not because 13 months is unreasonable. Because you wasted their first yes on bad information. You proved you didn’t do your due diligence. And now they can’t trust anything you say. The second yes is nearly impossible to get because it reveals the first yes was built on incompetence or dishonesty.

The System Failed You

Let’s be clear. When people don’t ask for what they need, it’s not because they’re weak or incompetent. It’s because the system taught them that asking is losing. The culture celebrates grinding through impossible situations instead of questioning whether the situation should be impossible in the first place. Heroes who work 80-hour weeks get praised while people who ask for support get labeled as complainers. So people stop asking. They internalize the message that real professionals figure it out themselves. And that message destroys people while leaving resources on the table that would have prevented the destruction.

The system fails because it doesn’t teach people how to ask effectively. Asking for what you need is not complaining. It’s leadership. But you have to ask right. Make it visual. Know what the is is. Show the data. Present the constraint on a schedule everyone can see. Break down the cost so leadership understands exactly what they’re approving. Use Takt planning in preconstruction so your first ask is based on real data from trades, not CPM guessing. When you ask with data, 80 percent of reasonable requests get approved. But when you ask without data, most get rejected because they look like guessing.

The system also fails because it doesn’t teach the difference between the three types of yes. Most people think yes means commitment. But Chris Voss shows that counterfeit yes and confirmation yes sound identical to commitment yes. The difference is follow-through. If someone says yes but takes no action, you got confirmation or counterfeit, not commitment. Real negotiation means getting to know first. What are the nos? What won’t work? What constraints exist? When you clarify the nos, the yes that emerges is more likely to be commitment because you’ve eliminated the counterfeit and confirmation options through clear communication about boundaries.

What Asking Right Looks Like

Picture this. A superintendent knows the project needs three more weeks. Instead of assuming no, he does his homework. He creates a Takt plan showing exactly where the constraint exists. He involves trades in validating the durations. He makes it visual so anyone looking at the plan can see why 11 months won’t work and 14 months will. Then he goes to the owner. He doesn’t ask for more time without context. He shows them the data. Here’s the constraint. Here’s what happens if we compress it. Here’s what we gain by addressing it properly. The owner looks at the visual plan, asks questions, and says yes. Because the request is backed by data, not guessing.

The team also understands the three types of yes:

Counterfeit yes happens when someone wants to escape the conversation or gather more information without committing. They say yes but plan to say no later.
Confirmation yes is simple affirmation with no promise of action. They’re agreeing you asked a question correctly, not committing to do something about it.
Commitment yes is the real deal. True agreement that leads to action. This is what you want, but you only get it by clarifying the nos first so the yes that emerges is genuine.

When you understand these distinctions, you ask better questions. You don’t start with yes. You start with no. What won’t work? What constraints exist? What boundaries matter? Then when you get to yes, it’s commitment because you’ve eliminated the counterfeit and confirmation options through clear communication.

Most importantly, they protect the first yes by doing their homework upfront. They don’t tell the owner 11 months based on CPM guessing in schematic design, then come back asking for 13 months in CDs when they finally do real planning. They do Takt planning in preconstruction. They involve trades. They validate durations. They know what the is is before they ask. So when they get the first yes, it’s based on real data. And they don’t need a second yes because they got it right the first time. If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow.

Why Asking Matters

Asking for what you need protects people. When you don’t ask for the field engineer your team needs, quality suffers. When you don’t ask for the realistic schedule, people burn out trying to achieve the impossible. When you don’t ask for warranted change orders, your company eats costs that destroy profit and force layoffs. Every time you leave a good decision on the table by not asking, people pay the price. Asking is not weakness. It’s leadership. It’s protecting the humans doing the work by getting them what they need to succeed.

Asking also builds trust when you do it right. When you ask with data, make everything visual, and show people what the is is, they respect the request even if they can’t approve it. They see you did your homework. They trust your judgment. And next time you ask, they listen because you’ve proven you don’t ask frivolously. But when you ask without data or come back for a second yes because you didn’t do your homework the first time, you destroy trust. People assume future requests are equally sloppy. The quality of your ask determines whether people trust you.

Most importantly, asking gets you what you need 80 percent of the time when you ask right. Studies show reasonable requests backed by data get approved at remarkably high rates. Owners want projects to succeed. Companies want teams supported. People want to do the right thing. But they can’t say yes to requests you never make. Stop assuming no. Start asking with data. And watch how often the answer is yes when you ask for what’s actually needed to protect people and deliver quality.

How to Ask for What You Need

Start by doing your homework before you ask. Don’t go to owners or leadership with requests based on guessing. Use Takt planning in preconstruction to know real durations. Involve trades in validating estimates. Make constraints visual so everyone can see exactly what you’re asking for and why. Know what the is is. When you show data, not opinions, 80 percent of reasonable requests get approved. When you show up unprepared, most get rejected because they look like complaining instead of legitimate need.

Understand the three types of yes. Counterfeit, confirmation, and commitment. Don’t start by pushing for yes. Start by clarifying the nos. What won’t work? What constraints exist? What boundaries matter? When you eliminate what doesn’t work, the yes that emerges is more likely commitment because you’ve built it on clear communication about reality. And watch for follow-through. If someone says yes but takes no action, you got confirmation or counterfeit, not commitment. Real commitment leads to action.

Protect the first yes by getting it right. Don’t tell owners 11 months in schematic design based on CPM guessing, then come back asking for 13 months in CDs. Do real planning upfront. Involve trades. Validate durations. Know the real number before you ask. When you get the first yes, make it count. Because the second yes is nearly impossible to get. It reveals you didn’t do your homework the first time. And that destroys trust even when the second request is legitimate.

Ask for what you need to protect people and deliver quality. More time. More resources. More support. Warranted change orders. Realistic schedules. Whatever’s needed to prevent burning people out or delivering poor quality. Stop assuming the answer is no. Start asking with data. And trust that 80 percent of the time, when you ask for what’s actually needed and show people why, the answer is yes.

The Challenge

Here’s your assignment. Identify what you need right now on your project to protect people and deliver quality. More time? More resources? Support? Training? A warranted change order? Write it down. Then do your homework. Create the visual schedule showing the constraint. Build the budget breakdown showing the cost. Make it factual so anyone looking can see what the is is. Then ask. Don’t assume no. Ask with data. And watch how often the answer is yes when you ask right.

Understand the three types of yes. Counterfeit. Confirmation. Commitment. Start by clarifying the nos instead of pushing for yes. What won’t work? What constraints exist? Build the yes on clear communication about reality. And watch for follow-through. If someone says yes but takes no action, you got confirmation or counterfeit. Push for commitment by making the ask specific and action-oriented.

Protect your first yes by doing your homework upfront. Use Takt planning in preconstruction. Involve trades. Validate durations. Know the real number before you ask. Don’t waste your first yes on bad data. Because the second yes is nearly impossible to get and destroys trust even when legitimate. Get it right the first time. And stop leaving good decisions on the table by not asking.

Most people will say yes more than you think the first time. But only if you ask with data and do your homework. Stop assuming no. Start asking right.

Chris Voss said there are three kinds of yeses: counterfeit, confirmation, and commitment. Only commitment leads to action. Get commitment by clarifying the nos first, then building the yes on reality.

On we go.

FAQ

How do you know if you got a commitment yes versus confirmation or counterfeit?

Watch for follow-through. Commitment yes leads to action. Someone approves your request and then schedules the resource, adjusts the timeline, or processes the change order. Confirmation yes is just affirmation with no action. Counterfeit yes means they’re planning to say no later or gathering information. If you get yes but nothing happens, you got confirmation or counterfeit. Push for commitment by making asks specific and action-oriented with clear next steps.

What if you already wasted your first yes and need a second?

Own it. Don’t make excuses. Show them exactly what you got wrong the first time and what you did to fix it. Present data that proves the second ask is legitimate, not more guessing. Acknowledge you should have done this homework upfront. Then ask if they’ll give you another chance despite the mistake. Some will. Some won’t. But honesty gives you better odds than pretending you didn’t mess up the first ask.

How do you ask for something when company culture says don’t ask, just grind?

Change the culture by being the example. Ask with data. Make it visual. Show what the is is. When your ask gets approved and the project improves, others notice. They see that asking with data works better than grinding through impossible situations. Culture changes when better methods produce better results. Be the proof that asking right is leadership, not weakness.

What’s the best way to make requests visual so people can see what the is is?

Use Takt plans that show constraints in the flow. Use budget breakdowns that show exactly where costs come from. Use graphs that show trend data proving the problem exists. Use photos that show the physical constraint. Make it impossible for someone to look at your request and not understand exactly what you’re asking for and why. Visual data eliminates debate about whether the need is real.

How do you do your homework in preconstruction to avoid needing a second yes?

Use Takt planning instead of CPM guessing. Involve trades in validating durations and costs. Build the plan with the people who’ll execute it. Test assumptions. Make constraints visible early. Ask hard questions before you commit to owners. When you do real planning upfront with trade input, your first ask is based on data. You don’t need a second yes because you got it right the first time.

If you want to learn more we have:

Discover Jason’s Expertise:

Quality & Continuous Improvement

Posted on March 27, 2026March 27, 2026 by Jason Schroeder

Read 30 min

Are You Lean? It’s Hard to Say Because I Wasn’t Here Yesterday

Your company sent everyone to Lean training. You implemented Last Planner. You created visual management boards. You do pull planning on sticky notes. Leadership congratulates themselves for being Lean. Then you ask whether anything actually got better from yesterday to today. Whether quality improved. Whether waste decreased. Whether crews asked someone to check their work before moving on. And the answer is no. Nothing changed except the tools you use. The work is the same. The problems are the same. The quality is the same. You implemented Lean theater, not Lean thinking.

Here’s the truth most companies miss. Lean is not a set of tools. It’s continuous improvement. The question is not whether you use Last Planner or visual boards or Takt planning. The question is whether you got better from yesterday to today. A consultant once visited a company that asked if they were Lean. He kept saying it’s hard to say. After the tenth time, they got frustrated and demanded an answer. He said I can’t tell you because I wasn’t here yesterday. If you’re not improving daily, you’re not Lean. Period. You might use Lean tools, but you’re not practicing Lean thinking.

The deeper problem is that construction doesn’t understand what quality and continuous improvement actually mean yet. We claim to care about quality, but we don’t train crews to stop, call, and wait when they find defects. We claim to pursue continuous improvement, but we do things the same way we did them 100 years ago. Airport toilets still splash urine back on people because nobody questioned whether we could design them better. That’s construction’s relationship with improvement. We accept broken systems because that’s how we’ve always done it. And until we treat every day like day one, questioning everything and improving relentlessly, we’ll never become Lean no matter how many tools we implement.

The Real Pain: Tools Without Improvement

Walk into a company that claims to be Lean and look closely. They have visual boards on every project. They do pull planning sessions. They track PPC. Leadership talks about respect for people and continuous improvement. But ask what improved this week and nobody knows. Ask whether crews check their work before moving on and they look confused. Ask whether anyone questioned a wasteful process and changed it and you get blank stares. The tools are there but the thinking is absent. They implemented Lean as a program, not as a culture of relentless daily improvement.

The pain shows up in quality failures that repeat project after project. Crews install work wrong. Inspectors catch it later. Crews rework it. Then the same mistake happens on the next project because nobody asked why it happened or how to prevent it. Japanese manufacturing plants train workers for a month on one principle: stop, call, wait. If you see a problem, stop working. Call for help. Wait until someone addresses it. That prevents defects from moving downstream. But construction crews move on even when they know something’s wrong because stopping feels like failure and nobody trained them that catching problems early is success.

The worst part is that we don’t even know we’re failing at continuous improvement because we’ve normalized stagnation. Airport toilets have splashed urine on people for 100 years. Architects still specify them. Manufacturers still sell them. Nobody questions it because that’s how it’s always been. That same acceptance of broken systems pervades construction. Schedules that require miracles. Coordination that depends on heroes. RFI processes that waste weeks. Trade stacking that creates chaos. We know these systems are broken but we don’t fix them because fixing them would require admitting we’ve been doing it wrong for decades. So we just keep doing it, calling ourselves Lean while improving nothing.

The Failure Pattern: Implementing Tools Instead of Building Culture

Here’s what companies keep doing wrong. They treat Lean like a recipe. Send people to training. Implement the tools they saw. Visual boards. Pull planning. Daily huddles. PPC tracking. Check the boxes. Declare victory. Call yourself Lean. But Lean is not about tools. It’s about culture. A culture where everyone from laborers to executives questions waste daily. Where crews stop work when they find defects instead of covering them up. Where teams experiment with improvements instead of accepting how things have always been. You can’t buy that culture at a workshop. You build it through relentless daily practice of continuous improvement.

They also confuse being Lean with using Lean tools. A company implements Last Planner perfectly. They track constraints. They measure PPC. They do pull planning sessions. And they think they’re Lean. But if they’re doing all that and nothing improved from last week to this week, they’re not Lean. They’re performing Lean theater. Real Lean means measurable improvement from yesterday to today. Did quality get better? Did waste decrease? Did flow improve? Did workers’ lives get easier? If the answer is no, you’re not Lean no matter how many tools you implemented. The tools are meant to enable improvement, not replace it.

The failure deepens when companies don’t understand flow efficiency versus resource efficiency. Most construction companies optimize for resource efficiency. Keep everyone busy. Maximize utilization. Fill every hour with activity. But that creates waste. Work waits in queues. Coordination fails. Rework multiplies. Flow efficiency means optimizing for how fast work moves through the system from start to finish with quality. Sometimes that means people wait because waiting prevents rework. Sometimes it means slowing down because speed without quality creates more waste than it eliminates. But construction culture celebrates busyness over flow, so we optimize the wrong thing and call ourselves Lean while destroying value.

The System Failed You

Let’s be clear. When companies implement Lean tools without building Lean culture, it’s not because people are lazy or resistant. It’s not because crews don’t care about quality or teams refuse to improve. It’s because the system never taught them what continuous improvement actually means. Nobody modeled questioning waste daily. Nobody trained crews to stop, call, and wait when they find problems. Nobody created environments where experimentation is celebrated and failure is learning. The system taught people that Lean is a program you implement, not a way of thinking you practice every day. And programs fade while culture persists.

The system fails because Western thinking wants recipes and Eastern thinking that created Lean is holistic. We want five steps to Lean success. Do this, get that. But Lean is not a recipe. It’s a mindset. Are we treating every day like day one, questioning everything and improving relentlessly? Are we respecting people and resources by eliminating waste that makes work harder? Are we creating stable environments that flow and bring problems to the surface? Are we engaging everyone in total participation using visual systems? Are we continuously improving standards instead of accepting how things have always been? Those are not steps. They’re principles that guide thinking. And thinking cannot be reduced to recipes.

The system also fails because we don’t know what quality and continuous improvement really mean yet in construction. We claim to care about quality but we don’t train it. We claim to pursue continuous improvement but we accept airport toilets that have splashed urine on people for 100 years without questioning whether we could design them better. We’re so far from real quality and continuous improvement that we don’t even know how far we have to go. And that ignorance prevents progress because you can’t pursue what you don’t understand. We need to experiment. Start with one crew. One project. Train them like Lexus trains plant workers. Stop, call, wait. Check your work before moving on. Fix defects at the source. And measure whether they improve from yesterday to today.

What Real Continuous Improvement Looks Like

Picture this. A crew installs work. Before moving on, they ask someone to check it. Not an inspector days later. Someone right now. They catch a defect. Instead of covering it up or blaming someone, they stop. Call for help. Wait until it’s addressed. They fix it at the source instead of letting it move downstream where it’s ten times more expensive to correct. This becomes habit. Check before moving on. Stop when you find problems. Fix them now. Quality at the source becomes culture, not theater.

The team also treats every day like day one. They question everything. Why do we coordinate this way? Why does this process take three days when it could take three hours? Why do we accept this waste? They experiment with improvements. Small changes tested daily. Some work. Some don’t. But the ones that work become new standards that everyone follows. Then they improve those standards. Continuous improvement is not a program that starts and stops. It’s a daily practice that never ends. Are we better today than yesterday? That’s the only question that matters.

Leadership measures what actually matters:

Did quality improve from last week to this week? Track defect rates, rework hours, and whether crews catch problems before inspectors do.
Did waste decrease? Measure time spent waiting, coordination failures, and activities that don’t add value to the customer.
Did flow get better? Track cycle time from start to finish and whether work moves smoothly without queuing or stopping.
Did workers’ lives get easier? Ask the people doing the work whether their day improved, not whether utilization increased.

The tools enable improvement but they don’t create it. Culture creates it. And culture is built through daily practice of questioning waste, stopping for quality, and improving relentlessly. If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow.

Most importantly, companies create anchor projects where they experiment with quality and continuous improvement at levels construction hasn’t seen yet. They pick one crew. One project. And they train that crew like Lexus trains plant workers. Stop, call, wait. Check your work before moving on. Fix defects at the source. Continuous improvement as core culture. They don’t try to transform the whole company at once. They create one example of what’s possible. Then they scale what works. That anchor project proves the concept and creates believers who spread the culture. Without anchor projects, improvement stays theoretical. With them, it becomes real.

Why Continuous Improvement Matters

Continuous improvement is what separates Lean thinking from Lean theater. You can implement every tool perfectly and still fail if nothing improves from yesterday to today. The tools are scaffolding. Improvement is the product. When you focus on tools, you get temporary compliance that fades when the champion leaves. When you focus on improvement, you build capability that persists because people learned to think differently. That thinking multiplies across projects and over time. Tool implementation creates activity. Continuous improvement creates results.

Continuous improvement also protects quality at the source instead of inspecting it in later. When crews check their work before moving on, defects get caught when they’re cheap to fix. When they stop, call, and wait upon finding problems, issues get resolved before they cascade downstream. When they fix defects at the source, rework drops dramatically. That saves money and time. But more importantly, it respects people by not forcing them to redo work that should have been right the first time. Quality at the source is respect for people made tangible through systems that prevent waste.

Most importantly, continuous improvement keeps you from accepting broken systems just because that’s how they’ve always been. Airport toilets splash urine on people. We’ve known this for 100 years. We have better designs. But we keep specifying the bad ones because nobody questions it. That same acceptance of broken systems pervades construction. We keep doing things that waste time, money, and people’s lives because that’s how we’ve always done it. Continuous improvement culture means questioning everything and fixing what’s broken. Not someday. Today. Every day. Until we’re truly Lean.

How to Build Continuous Improvement Culture

Start by understanding that Lean is not tools. It’s continuous improvement. The question is not whether you use Last Planner or visual boards. The question is whether you improved from yesterday to today. Measure that. Track it. Make it visible. Did quality improve? Did waste decrease? Did flow get better? Did workers’ lives get easier? If yes, you’re practicing Lean thinking. If no, you’re performing Lean theater regardless of what tools you use.

Train crews on quality at the source. Not quality inspection after the fact. Quality built into work from the start. Teach stop, call, wait. If you see a problem, stop working. Call for help. Wait until someone addresses it. Train crews to check their work before moving on. Not days later through inspection. Right now through peer review. Make catching defects early a success metric, not a failure indicator. Quality at the source requires cultural change, not just process change. Build that culture through training and daily practice.

Treat every day like day one. Question everything. Why do we do it this way? Why does this take so long? Why do we accept this waste? Experiment with improvements. Small changes tested daily. Measure whether they work. Keep what improves things. Discard what doesn’t. Create new standards from what works. Then improve those standards. Continuous improvement is not a program with a start and end date. It’s daily practice that never stops. Make it part of how you think, not something extra you do when you have time.

Create anchor projects where you experiment with quality and continuous improvement at levels construction hasn’t seen yet:

Pick one crew and one project where you can control the experiment without company-wide resistance.
Train them like Lexus trains plant workers: stop, call, wait principles practiced until they become instinct, not just policy.
Build quality at source into every task by having peers check work before it advances to the next step.
Make continuous improvement part of daily huddles where the team identifies one thing to improve and tests it that day.
Measure results obsessively so you can prove the concept works and show skeptics the data.

Don’t try to transform everything at once. Create one example. Prove the concept. Then scale what works. Anchor projects turn theory into reality and create believers who spread the culture.

The Challenge

Here’s your assignment. Ask whether you improved from yesterday to today. Not whether you used Lean tools. Whether things actually got better. Quality. Waste. Flow. Workers’ lives. If the answer is no, you’re not Lean regardless of what tools you implemented. Start practicing continuous improvement as culture, not just using it as program.

Train one crew on quality at the source. Stop, call, wait. Check work before moving on. Fix defects now instead of letting them move downstream. Make quality at the source core culture, not inspection theater. Create one anchor project. One example of what’s possible. Prove that construction can achieve quality and continuous improvement at levels we haven’t seen yet. Then scale what works.

Stop accepting broken systems because that’s how we’ve always done it. Airport toilets have splashed urine on people for 100 years. We know better designs exist. But we keep specifying the bad ones. That same acceptance pervades construction. Question it. Fix it. Improve it. Every day. Are you Lean? It’s hard to say because the real question is whether you improved from yesterday to today.

Nicholas Modig’s question about whether a company is Lean deserves repeating: “It’s hard to say because I wasn’t here yesterday.” Lean is not about the tools you use. It’s about whether you improved from yesterday to today.

On we go.

FAQ

How do you measure whether you improved from yesterday to today?

Track quality metrics. Defect rates. Rework hours. Track waste. Time spent waiting. Coordination failures. Track flow. Cycle time from start to finish. Track whether workers say their lives got easier. Make improvements visible. Graph them. Review them daily. Real improvement shows up in measurable results, not just tool adoption.

What does stop, call, wait actually mean in practice?

When a crew member finds a defect or problem, they stop working immediately instead of covering it up or moving on. They call for help from a supervisor or quality lead. They wait until someone addresses the issue before continuing. This prevents defects from moving downstream where they’re ten times more expensive to fix.

How do you train quality at the source when inspection happens later anyway?

Change the culture so peers check work before moving on, not inspectors days later. Make catching defects early a success metric. Train crews that quality is their responsibility, not something inspection does for them. Build systems where work doesn’t advance until it’s verified correct at the source.

What if treating every day like day one feels exhausting?

Continuous improvement should energize, not exhaust. The exhaustion comes from accepting broken systems that make work harder. When you question waste and fix it daily, work gets easier over time. The joy is in the journey of improvement, not just the destination. Small wins daily create momentum, not burnout.

How do you create an anchor project without executive support?

Start with one crew you control. Train them on quality at source and continuous improvement. Measure results. Prove the concept. Show that it works. Then use that evidence to get support for scaling. You don’t need company-wide buy-in to experiment with one team. Prove it works small before asking for big investment.

If you want to learn more we have:

Discover Jason’s Expertise:

Helping a Struggling Team!

Posted on March 27, 2026March 27, 2026 by Jason Schroeder

Read 29 min

How to Keep Your Team’s Head Up When Projects Go Sideways

Your project is in trouble. The schedule slipped. Costs are climbing. The owner is frustrated. And your response is to focus on production control or schedule recovery or trade partner coordination. You bring in consultants who analyze the critical path. You implement new reporting systems. You buy software. And nothing changes because you’re treating symptoms instead of diagnosing the disease. The real problem isn’t the schedule or the production system. It’s that your team’s head is down.

Here’s what that means. When you ride horses up steep mountains, you keep the horse’s head up with the reins. Head down and the horse stumbles. Head up and it stays on its feet even on dangerous terrain. Teams work the same way. When their heads are down, they can’t see where they’re going. They stumble over problems they should have anticipated. They lose focus. They fight each other instead of the work. And all your schedule recovery efforts fail because the team isn’t functional enough to execute them. But most project recovery attempts ignore team dynamics completely. They focus on technical fixes while the leadership is broken, trust doesn’t exist, and nobody has a clear performance goal. You can’t recover a project with a dysfunctional team no matter how good your technical solutions are.

The real recovery happens when you fix three things: leadership, team behaviors, and performance goals. The project manager and superintendent must be cohesive and working together. The team must embrace the five crucial behaviors of trust, healthy conflict, commitment to goals, mutual accountability, and focus on results. And everyone needs a strenuous but achievable performance goal that keeps their eyes focused on what they can control instead of what they can’t. Fix those three components and projects recover. Ignore them and your technical interventions accomplish nothing because the team can’t execute.

The Real Pain: Heads Down While Everything Falls Apart

Walk onto a troubled project and you’ll see it immediately. The PM and superintendent don’t talk unless they have to. When they do talk, it’s tense. The team senses the division and takes sides. Office hates field. Field hates office. Nobody trusts anyone. Meetings are theater where people pretend to agree then do whatever they were going to do anyway. There’s no healthy conflict because conflict just means fighting, not problem solving. Goals exist on paper but nobody’s committed to them. Accountability means blame, so people hide problems instead of surfacing them. And results suffer because the team is too dysfunctional to execute even good plans.

The pain compounds when leadership tries to fix it with technical solutions. They bring in schedulers to fix the schedule. They implement new production control systems. They hire consultants to analyze the critical path. And all of it fails because a dysfunctional team can’t execute functional plans. You can have the best schedule in the world, but if the PM and superintendent aren’t talking, nobody’s coordinating the work that schedule describes. You can implement Last Planner perfectly on paper, but if the team doesn’t trust each other, they won’t surface constraints or hold each other accountable for make-ready. Technical excellence means nothing without team functionality.

The worst part is the negativity spiral. When teams have their heads down, they focus on what they can’t control. Change orders. Owner delays. Designer mistakes. Weather. And the more they focus on things outside their control, the more powerless they feel. That powerlessness creates negativity. The negativity destroys morale. And low morale guarantees poor performance. Meanwhile, nobody’s focusing on what they can control because everyone’s too busy complaining about what they can’t. The team needs their head up, focused on strenuous but achievable goals within their control. But leadership keeps letting them spiral on things that don’t matter.

The Failure Pattern: Treating Symptoms Instead of the Disease

Here’s what companies keep doing wrong. They diagnose project problems as technical failures. Schedule failure. Cost overrun. Production breakdown. Then they apply technical solutions. New software. Better tracking. More meetings. Tighter controls. But they never look at team dysfunction. They never ask whether the PM and superintendent are cohesive. They never assess whether trust exists or whether the team can engage in healthy conflict. They never check whether people are committed to goals or just pretending. And they wonder why their technical fixes don’t work when the team is too broken to implement them.

They also tolerate leadership dysfunction because changing leaders mid-project feels destructive. The PM and superintendent hate each other. Everyone knows it. But leadership hopes they’ll figure it out. They encourage them to work together. They suggest lunch meetings. And when that doesn’t work, they just live with the dysfunction because removing a leader feels like admitting failure. So they leave broken leaders in place, watching the project sink while hoping things improve. Sometimes they do. Sixty percent of the time, you can get a PM and superintendent working together through proximity, personality profiles, and team building. But forty percent of the time, someone needs to be replaced. And avoiding that decision just extends the suffering.

The failure deepens when teams have no clear performance goal. They know they’re supposed to finish on time and on budget. But those are outcomes, not goals. A strenuous performance goal is immediate, specific, and within the team’s control. Finish the next two months of work without missing a single daily commitment. Eliminate all outstanding RFIs within 30 days. Get every trade to green on make-ready for the next phase. Those are goals that focus attention and create momentum. But most teams just drift, reacting to problems instead of pursuing clear wins. And without that magnetizing goal pulling everyone forward, the team fragments and loses direction.

The System Failed You

Let’s be clear. When project teams are dysfunctional, it’s not because individuals are bad people. It’s not because the PM is incompetent or the superintendent is difficult. It’s because nobody taught them how to function as a team. Nobody facilitated trust building. Nobody showed them how to engage in healthy conflict instead of fighting or avoiding. Nobody helped them commit to goals or hold each other accountable. The system assumed that putting smart people together would automatically create a functional team. And that assumption is wrong. Teams need leadership that knows how to build cohesion, vocabulary to discuss team health, and systems that reinforce the five crucial behaviors.

The system fails because it treats team building as soft skills that don’t matter. Leadership focuses on technical execution, scheduling systems, cost controls, and production metrics. Team dynamics get ignored because they seem touchy-feely compared to hard data. But team dysfunction kills projects faster than any technical problem. A cohesive team with mediocre technical systems outperforms a dysfunctional team with excellent technical systems every time. Because execution depends on people working together, not just on having the right processes documented.

The system also fails because it doesn’t give teams clear performance goals that keep their heads up. Companies set outcome goals like finish on time and on budget. But those don’t direct daily behavior. A strenuous performance goal is something the team can pursue this month that’s challenging but achievable. It focuses attention on what they can control instead of what they can’t. It creates momentum through wins. And it keeps heads up instead of down. But most companies never create these goals because they’re focused on outcomes, not on the process of getting there.

What Keeping Heads Up Looks Like

Picture this. A project is struggling. Office and field are fighting. The PM and superintendent barely talk. So leadership intervenes. They require the PM and superintendent to go to lunch twice a week. No phones. No work talk. Just proximity. Getting to know each other. They visit each other’s homes. They go camping. They create isolation like two enemies stuck on an island who become friends because they have to. And sixty percent of the time, this works. The relationship improves. Trust builds. The team senses the cohesion and follows.

For the other forty percent where proximity doesn’t work, leadership makes the hard call. They remove the leader who can’t or won’t change. Not because that person is bad, but because the team can’t recover with broken leadership. Sometimes it’s the superintendent eight months from retirement with no motivation to adapt. Sometimes it’s the project manager stuck in 1980s corporate management who won’t let the team hold each other accountable. Either way, leadership acts instead of hoping things improve. They bring in someone new, teach them the systems, and watch the team transform.

The team goes through the Patrick Lencioni books together:

The Motive teaches leaders why they lead and whether they’re serving the team or themselves.
The Five Dysfunctions of a Team builds vocabulary for trust, conflict, commitment, accountability, and results.
Death by Meeting transforms meetings from time-wasting theater into productive sessions that drive decisions.
The Advantage creates organizational health by aligning everyone around the same clarity, reinforcing behaviors, and over-communicating priorities.

They read, reflect, and implement through facilitation. This gives them language to discuss trust, conflict, commitment, accountability, and results. It creates vocabulary for team health instead of pretending dysfunction doesn’t exist. And it builds systems that reinforce the five behaviors instead of just hoping people figure it out.

Most importantly, leadership gives the team a strenuous performance goal. Not finish on time, that’s an outcome. Something immediate and achievable. Stabilize the project using Last Planner. Implement Takt planning so everyone can see the strategic plan together. Eliminate all open RFIs within 30 days. Finish the next phase without a single safety incident. Something challenging but possible that focuses attention on what the team controls. That goal magnetizes everyone toward higher performance. It keeps heads up instead of down. And it creates momentum through wins instead of spiraling on problems.

Why Keeping Heads Up Matters

Keeping heads up enables execution. You can have perfect technical systems, but if the team is dysfunctional, nothing executes. A cohesive team with trust, healthy conflict, commitment, accountability, and results focus can execute mediocre plans better than a broken team can execute perfect plans. Team functionality multiplies every other capability. Dysfunction divides it. This is why projects with the best people and worst team dynamics still fail while projects with average people and great team dynamics succeed.

Keeping heads up also protects morale. When teams focus on what they can’t control, change orders, owner delays, designer mistakes, they feel powerless. Powerlessness creates negativity. Negativity destroys morale. And low morale guarantees poor performance. But when teams focus on strenuous goals within their control, they feel capable. Capability creates optimism. Optimism builds morale. And high morale enables performance. The difference is where you point their attention. Down at problems they can’t solve or up at goals they can achieve. If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow.

Most importantly, keeping heads up enables recovery. Projects get in trouble for many reasons. But they recover when teams become functional. The right leadership, multiplier leaders who believe in people and work through people instead of controlling them. The five crucial behaviors of trust, conflict, commitment, accountability, and results. And strenuous performance goals that focus attention on what teams control. Fix those three components and technical problems become solvable. Ignore them and technical interventions fail because the team can’t execute.

How to Keep Your Team’s Head Up

Start with leadership cohesion. If the PM and superintendent aren’t working together, nothing else works. Require them to have lunch twice a week. No phones. No work talk. Just proximity and relationship building. Have them visit each other’s homes. Go camping. Create isolation where they have to become friends or at least functional partners. Sixty percent of the time, this works. For the other forty percent, make the hard call. Remove the leader who can’t or won’t change. Yes, it’s disruptive. But a broken leader guarantees project failure. A leadership change at least gives you a chance.

Implement the five crucial behaviors systematically:

Build trust through vulnerability and follow-through, not team building exercises that feel forced and fake.
Practice healthy conflict by surfacing disagreements constructively instead of avoiding them or letting them turn into fights.
Commit to goals publicly so everyone knows what success looks like and can hold each other accountable.
Hold each other accountable without blame by creating clarity around expectations and following through on commitments.
Focus on results, not politics or looking good, by measuring what actually matters to project success.

Read the Patrick Lencioni books as a team. The Motive. The Five Dysfunctions of a Team. Death by Meeting. The Advantage. Read, reflect, and implement through facilitation. Learn the vocabulary of trust, healthy conflict, commitment, accountability, and results. Practice these behaviors systematically. Use personality profiles to help people understand each other. Create proximity through regular interaction.

Give the team a strenuous performance goal. Not an outcome like finish on time. Something immediate, specific, and within their control. Stabilize the project. Implement Last Planner. Implement Takt planning. Eliminate all open RFIs in 30 days. Finish the next two months without missing a single daily commitment. Something challenging but achievable that magnetizes everyone toward higher performance. Focus attention on what the team can control, not what they can’t. Stop letting them spiral on change orders and owner delays. Point them at wins they can pursue this month. That goal keeps heads up instead of down.

The Challenge

Here’s your assignment. Assess your project against three criteria. Do you have cohesive leadership where the PM and superintendent work together? Do you have a team engaging in the five behaviors of trust, conflict, commitment, accountability, and results? Do you have a strenuous performance goal that’s immediate, specific, and within the team’s control? If any of those three are missing, you can’t recover the project with technical fixes alone. Fix the team first.

If leadership is broken, act. Require proximity between the PM and superintendent. If that doesn’t work within a month, make the hard call and change leadership. If team behaviors are missing, read the Lencioni books together. Build vocabulary. Practice the five behaviors. If you don’t have a strenuous performance goal, create one this week. Something the team can pursue this month that’s challenging but achievable. Point their attention at what they control instead of what they can’t.

Stop treating project recovery as a technical problem when it’s a team problem. You covet what you see. You go where you’re looking. Keep your team’s head up by focusing them on goals within their control. Build cohesive leadership. Implement the five behaviors. Create momentum through wins. And watch dysfunctional projects transform.

Keep the horse’s head up and it stays on its feet even on dangerous terrain. Keep your team’s head up and they recover even troubled projects.

On we go.

FAQ

How do you get a PM and superintendent to work together when they hate each other?

Require lunch twice a week with no phones or work talk. Proximity builds relationships. Have them visit each other’s homes. Go camping. Create isolation where they must become functional partners. This works sixty percent of the time. For the other forty percent, remove the leader who won’t change.

What if removing a leader mid-project feels too disruptive?

Leaving broken leadership in place is more disruptive than changing it. A dysfunctional leader guarantees project failure. A leadership change gives you a chance to recover. Yes, transitions are hard. But they’re less destructive than months of continued dysfunction while you hope things improve.

How do you create a strenuous performance goal?

Make it immediate, specific, and within the team’s control. Not finish on time, that’s an outcome. Something like eliminate all open RFIs in 30 days. Implement Last Planner system. Finish next two months without missing daily commitments. Challenging but achievable. Focuses attention on wins the team can pursue this month.

What if the team resists reading books and doing facilitation?

Frame it as systems work, not soft skills. Team dysfunction kills projects faster than technical problems. The five behaviors are infrastructure for execution. Without them, technical excellence means nothing. If people still resist, leadership must require participation or replace resisters.

Can you recover a project without fixing team dynamics?

No. Technical solutions fail when teams are dysfunctional. You can have perfect schedules, but if the PM and superintendent don’t talk, nobody coordinates the work. You can implement Last Planner, but if trust doesn’t exist, people hide constraints. Fix the team first. Then technical solutions work.

Word Count: 1,999 words

If you want to learn more we have:

Discover Jason’s Expertise:

General Offerings

Company Offerings

Systems

Are You Setting Realistic Deadlines or Just Telling People What They Want to Hear?

The Real Pain: Deadlines Nobody Can Hit

The Failure Pattern: Guessing Time Instead of Estimating Effort

The System Failed You

What Realistic Deadlines Look Like

Why Realistic Deadlines Matter

How to Set Realistic Deadlines

The Challenge

FAQ

Are You Leaving Good Decisions on the Table by Not Asking?

The Real Pain: Needs That Go Unmet Because You Won’t Ask

The Failure Pattern: Assuming No Without Ever Asking

The System Failed You

What Asking Right Looks Like

Why Asking Matters

How to Ask for What You Need

The Challenge

FAQ

Are You Lean? It’s Hard to Say Because I Wasn’t Here Yesterday

The Real Pain: Tools Without Improvement

The Failure Pattern: Implementing Tools Instead of Building Culture

The System Failed You

What Real Continuous Improvement Looks Like

Why Continuous Improvement Matters

How to Build Continuous Improvement Culture

The Challenge

FAQ

How to Keep Your Team’s Head Up When Projects Go Sideways

The Real Pain: Heads Down While Everything Falls Apart

The Failure Pattern: Treating Symptoms Instead of the Disease

The System Failed You

What Keeping Heads Up Looks Like

Why Keeping Heads Up Matters

How to Keep Your Team’s Head Up

The Challenge

FAQ

SUBSCRIBE NOW !

Subscribe to our newsletters and stay updated!

Important Scam Alert: Fake Elevate Construction Job Emails

Related Books

The First Planner System: The Project Planning System for Executives, Project Managers, and Superintendents in Pre-construction - Book 2

Pull Planning For Builders: How to Pull Plan Right, Respect People, and Gain Time (The Art of the Builder)

The Ten Improvements to Production Planning: What Lean Builders Can Do To Improve Short Interval Planning (The Art of the Builder)

Related Books

The First Planner System: The Project Planning System for Executives, Project Managers, and Superintendents in Pre-construction - Book 2

Built to Fail: Why Construction Projects Take So Long, Cost Too Much, And How to Fix It

Related Books

The First Planner System: The Project Planning System for Executives, Project Managers, and Superintendents in Pre-construction - Book 2

The 10 Myths of CPM: How The Critical Path Method Systematizes Disrespect for People

Calumet "K"

faq

General Training Overview

Superintendent / PM Boot Camp

Takt Production System® Virtual Training

Onsite Takt Simulation

Foreman & Field Engineer Training

Testimonials

Testimonials

agenda

Day 1

Foundations & Macro Planning

day2

Norm Planning & Flow Optimization

day3

Advanced Tools & Comparisons

day4

Buffers, Controls & Finalization

day5

Control Systems & Presentations

faq

UNDERSTANDING THE TRAINING

VALUE AND RESULTS

PLANNING AND SCHEDULING TOPICS

APPLICATION & TEAM ADOPTION

VIRTUAL FORMAT & ACCESSIBILITY

faq

GENERAL FAQS