5 Levels of the Last Planner System

Posted on April 17, 2026April 17, 2026 by Danny Jiménez⁩

Read 20 min

Pull Planning Step by Step: Last Planner Made Simple

The Last Planner System is sometimes described as complex, but its underlying logic is as clear as the altitude metaphor that coaches Dan Fauchier and Dave Umstot use to introduce it. Looking out of a plane at thirty thousand feet, you see the broad shape of the landscape major milestones, overall sequence, the rough outline of a project. At ten thousand feet, you see more detail phases, handoffs, major constraints, the shape of each section of work. At a thousand feet, you can see individual activities and begin to see which of them are ready to execute and which have something blocking them. And at ground level, you see exactly what is happening right now, who is doing what, and whether the plan is being executed as committed.

The five levels of the Last Planner System correspond to this progression of altitude. Should, Can, Will, Did, Learn. Each level answers a different question at a different level of detail. And the system only produces what it is designed to produce predictable workflow, rapid learning, reliable commitments, and genuine collaboration when all five levels are operating together.

Level One: What Should Be Done

The first level operates at the highest altitude. Milestone planning for the entire project and phase planning for the next two months or so establishing the shared understanding of scope, major milestones, key constraints, and the logical sequence of work that will get the team from the project start to substantial completion.

The primary tool at this level is pull planning. Working backward from specific milestones, last planners the people who will actually make the assignments and execute the work build the sequence together. Each trade partner declares what they need from the preceding trade to begin their work, creating a chain of handoffs that clarifies the conditions of satisfaction for every major transition in the project. This process delivers bad news early the grey areas between contract scopes, the gaps in project scope, the coordination conflicts between trades while there is still time to explore solutions at the planning wall rather than in the field with crews already mobilized.

The goal of Level One is a shared understanding. Not just a schedule that has been communicated. A plan that the people executing it participated in creating, whose logic they understand, and whose commitments they made with genuine confidence rather than passive acceptance.

Level Two: What Can Be Done

The second level zooms in to the six-to-eight-week horizon the make-ready planning window in which the team actively screens every upcoming activity for constraints. This is the critical distinction between a look-ahead schedule and genuine make-ready planning. A look-ahead asks: is this task approximately scheduled to start in the next six weeks? Make-ready planning asks: is this task genuinely ready to execute, and if not, what needs to happen and by when to make it ready?

The eight flows of Lean construction provide the trigger categories for constraint screening: information, design, materials, labor, equipment, external conditions, space, and preceding work. Every upcoming activity is evaluated against each flow. Anything that is not fully cleared becomes a constraint that is logged with an owner and a last responsible moment the latest date by which the constraint must be removed for the task to proceed as planned. The constraint log is actively managed at every weekly meeting, not treated as a document that gets reviewed when there is time.

The principle at this level is straightforward: work that should be done is only added to the weekly work plan when it genuinely can be done. The discipline of making work ready before committing to it is what makes the weekly work plan reliable rather than aspirational.

Level Three: What Will Be Done

The weekly work plan evolves from the make-ready plan as activities are confirmed to be constraint-free. At this level, last planners make specific, reliable promises for the next two weeks of work. Not estimates, not hopes, not targets promises. The reliability of those promises is what makes the production system work.

There are five conditions for a reliable promise. The person making it has assessed their own competence for the task. They understand the conditions of satisfaction that define what done looks like. They have included realistic time for quality and safety requirements. They have confirmed that the required capacity is actually available and allocated. And they are aware of any unspoken conversations or competing commitments that might conflict with the promise. If any of these conditions cannot be confirmed, the answer must be no not a qualified yes, not a maybe, but an explicit no that triggers a path-clearing conversation.

Saying no to a commitment that cannot be reliably kept is not a failure. It is the most important thing Last Planner changes about how planning works. In traditional scheduling, the plan is built on optimistic commitments that nobody expected to push back on. In the Last Planner System, the plan is built on honest commitments from people who have thought carefully about whether they can actually do what they are promising. That honesty is what makes the Percent Promises Complete metric meaningful it measures genuine commitment reliability, not compliance with what the master schedule suggested.

The weekly work plan also includes a workable backlog a Plan B of tasks that are constraint-free and ready to execute if Plan A activities encounter new blockers during the week. This buffer of ready work is what makes the system resilient: when something unexpected stops a crew, they do not become idle or pull work out of sequence. They execute from the backlog while the constraint on Plan A is being resolved.

Level Four: What Was Done

The fourth level tracks the execution of the weekly work plan through the daily huddle and updates the commitment status in real time. When a last planner completes an activity, they mark it done. When the next trade or the site superintendent confirms the work is genuinely complete and ready for the next operation, it is marked done-done. The distinction matters because done-done is what actually releases the downstream work not done as the completing trade defines it, but done as the receiving trade needs it.

Percent Plan Complete is calculated at this level not as a performance judgment of individual trade partners but as a measurement of how well the system is working and how reliably the team is coordinating together. When commitments are missed, the reason for the missed commitment is logged against the activity, always from a system perspective rather than a blame perspective. Deming’s observation is the operating assumption: approximately 94 percent of the time, the system is at fault, not the individual. The reasons for missed commitment list reflects this bad planning, prior work not complete, design issue, materials not available, equipment not available, information not available all of them system conditions rather than individual character failures.

Here are the signals that Level Four is functioning correctly in a Last Planner implementation:

The done-done standard is actually applied, not glossed over in favor of easier percent complete estimates
Reasons for missed commitments are classified as system issues, not person issues
PPC is trended over time and used to identify the categories of systemic failure most affecting the project
The daily huddle produces real decisions and adjustments, not just status updates
The distinction between Plan A and workable backlog is maintained and actively used

Level Five: What the Team Needs to Learn

The fifth level is where the system closes the loop and where most implementations fall short. Learning happens at every level of the Last Planner System, indicated in the schematic by arrows that point upward from each level to the levels above. Plus/delta at the end of every meeting. Takeaways from the daily huddle. Five-why analysis of the most significant reasons for missed commitment. Root cause analysis workshops for the issues with the greatest schedule impact.

The purpose of learning at this level is not to generate documents. It is to change the system conditions that produced the failures to take what was learned in Level Four and use it to make Level Three planning more reliable, Level Two constraint removal more thorough, and Level One phase planning more accurate. When the learning loop is functioning, each successive phase of the project starts from a higher floor than the previous one, and PPC improves over time rather than cycling at a steady state of acceptable mediocrity. The purple arrows in Ballard’s schematic are not decorative. They represent the mechanism by which the system improves itself. Without them, the Last Planner System produces a record of what happened. With them, it produces an organization that gets better at building.

At Elevate Construction and LeanTakt, all five levels of the Last Planner System are implemented together, integrated with the Takt production plan that provides the zone-by-zone sequencing context and the First Planner System that establishes the production design before mobilization. The system is only as strong as the discipline of the team running it. If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow. Should. Can. Will. Did. Learn. Five levels. One system. Run it all.

On we go.

Frequently Asked Questions

What are the five levels of the Last Planner System?

Should what should be done, established through milestone and phase planning. Can what can be done, established through make-ready planning and constraint removal. Will what will be done, established through the reliable weekly work plan. Did what was actually done, tracked through daily huddles and PPC. Learn what the team needs to learn from misses to improve the system.

What is the difference between a look-ahead schedule and make-ready planning?

A look-ahead schedule identifies what activities are coming up. Make-ready planning actively screens each of those activities for constraints using the eight flows of Lean construction information, design, materials, labor, equipment, external conditions, space, and preceding work and assigns ownership and deadlines for removing anything that is not clear.

Why must last planners say no when they cannot make a reliable promise?

Because a yes that is not backed by genuine confidence in meeting the five conditions for a reliable promise is not a commitment it is an optimistic guess. And optimistic guesses are what produce the pattern of consistently missed weekly work plan targets that most projects accept as normal. The no that triggers a path-clearing conversation is more valuable than the yes that obscures a constraint.

What is done-done and why does it matter?

Done as the completing trade defines it means the work is finished from their perspective. Done-done means the work has been confirmed as complete and acceptable by the receiving trade the next person in the sequence who depends on that work being correct. Done-done is what actually releases downstream work and reduces rework.

Why does the Last Planner System need a qualified coach to implement?

Because the first exposure a team receives to any new system is the one that shapes their relationship with it. A poor initial implementation one that skips levels, applies partial elements, or misses the commitment reliability discipline produces a team that has experienced LPS as something that does not work, which is much harder to correct than starting from no experience at all.

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

Construction is Broken

Posted on April 17, 2026April 17, 2026 by Danny Jiménez⁩

Read 17 min

The Illusion of Control: Why More Controls Do Not Give You Control

Here is a paradox worth examining. The construction industry has been identified as broken, by governments, by researchers, by owners who have paid for projects that arrived late, over budget, and with reduced scope since at least the 1930s. The UK government alone has commissioned more than fifteen reports over ninety years reaching essentially the same conclusions. And yet 55 percent of industry practitioners who operate within the dominant paradigm are satisfied with how it works.

That is not denial. That is something more fundamental: the inability to see a system from inside the system. People in the construction industry were taught the dominant paradigm as apprentices, as students, as early-career professionals. It is all they have experienced at work. When they look at what is happening around them, it seems perfectly normal. It seems okay. The dysfunction has become invisible because it has been normalized absorbed into the background of what construction simply is.

This is the central challenge of Lean transformation in construction. It is not that the tools are unavailable or that the evidence is insufficient. It is that the paradigm shapes what people are able to see. And you cannot change what you cannot see.

What the Dominant Paradigm Actually Produces

The dominant paradigm is coherent. It has an internal logic. Bilateral adversarial contracts that assume neither party can be trusted produce parties that protect themselves through bureaucratic defensive actions because the contract told them that is what they should do. Risk transferred down the supply chain to levels where it cannot be adequately managed produces inflated prices because the parties at the end of the chain have to cover the risk they have absorbed. Separation of design from production produces buildability issues and RFIs and change orders because the people who will build the project were not present when the decisions that affect buildability were made.

The paradigm does not produce these outcomes accidentally. It produces them systematically, because it was designed around assumptions that predict exactly these outcomes. Minimizing first cost produces value engineering that reduces scope and quality. Telling workers what to do based on a schedule not grounded in reality produces schedule slippage and firefighting. Investing nothing in training, research, and prefabrication produces a workforce and a set of practices that cannot improve.

The outputs of this system, projects late 61 percent of the time, over budget 70 percent of the time, with rework consuming five to thirty percent of total cost, and the client paying for all of it are not anomalies. They are the designed outputs of a paradigm that was built to produce them.

Why the Paradigm Persists

The paradigm persists for reasons that are each individually rational and collectively catastrophic. Small margins are used as reasons not to risk trying something new, even though the waste produced by the current system is what is destroying those margins in the first place. Fragmentation means no single organization speaks for the industry, so no one has both the incentive and the authority to drive systemic change. The legal standard of care doctrine rewards doing what has always been done because departing from it creates liability exposure. And most owners, particularly in the public sector, know of no alternative, so they continue demanding the same broken delivery method and receiving the same broken results.

There is a particularly perverse dynamic in how the industry handles learning. In theory, lessons-learned sessions at project close should build organizational capability over time. In practice, they are of limited value because it is not safe to honestly admit to errors and omissions that have not been disclosed to other project parties, to do so is to invite a legal claim. The legal structure that was supposed to protect parties from each other has also protected the industry from learning from its own failures.

And the productivity data tells the underlying story with uncomfortable clarity. Since the mid-1960s, construction productivity has fallen steadily while manufacturing and agricultural productivity have risen dramatically over the same period. At the same time, buildings are increasingly complex, owners want more for less and faster, and material prices are rising. The gap between what the industry is asked to deliver and what the dominant paradigm is capable of delivering has been widening for sixty years.

What Changes When You Change the Paradigm

The contrast between practitioners inside the dominant paradigm and those who have implemented Lean is not subtle. They see the same industry very, very differently, not because one group is optimistic and the other pessimistic, but because they are actually operating in different systems and experiencing genuinely different outcomes.

Lean construction is a different and equally coherent paradigm. Every element of the dominant paradigm has a Lean counterpart. Bilateral adversarial contracts become relational procurement agreements. Risk transfer down the supply chain becomes collaborative risk management. Separation of design and production becomes integrated project delivery. Schedules not grounded in reality become Takt plans built with the people who will execute them. Zero investment in training becomes continuous people development at every level. And the systematic learning that the dominant paradigm legally prevents becomes the improvement engine that makes each project better than the last.

Here are the conditions that indicate a team or organization has genuinely shifted paradigms rather than added Lean tools to a traditional system:

Pull planning is a commitment process, not a scheduling exercise trade partners made the plan and own the commitments in it.
Make-ready planning happens six weeks ahead as a discipline, not reactively when the crew arrives and finds the zone unready.
Problems are surfaced early and treated as system feedback rather than hidden to avoid claims.
Learning moves from project to project through documented standard work rather than dispersing with the team at project close.
The weekly work plan is built from genuine readiness, not from optimistic pressure.

Starting Where You Are

One of the most important truths about Lean construction is that the paradigm shift does not require a perfect contract structure to begin. Lean construction started within the context of bilateral, transactional, adversarial contracts because that is the context most practitioners work in. Significant improvement is achievable within those constraints. The transformation becomes dramatically easier when owners engage in relational procurement and when the commercial terms align the financial incentives of all participants with the project’s success. But the absence of ideal conditions is not a reason to wait.

Find the bottlenecks in the production process. Apply the Lean construction principle that addresses the bottleneck. Let the work flow again. Learn from that experience. Move the rate of flow until the next bottleneck surfaces. Address that one. This is the continuous improvement cycle operating at the project and organizational level not a one-time initiative but a sustained practice of getting better, project by project, until the cumulative capability looks nothing like the dominant paradigm that was the starting point.

As Deming said: it does not matter when you start, as long as you begin today. Nothing is so good that it cannot be made better.

At Elevate Construction, the consulting model is built on exactly this sequence starting where the organization is, finding the constraints, designing the production system improvements that address them, and building the organizational capability that makes each subsequent project better than the last. The paradigm shift is not a single decision. It is an accumulation of better choices, made consistently, over enough projects that the old way of working becomes genuinely unacceptable by comparison. If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow. The construction industry is at the tipping point. The practitioners who can see the system for what it is are the ones positioned to build what comes next.

On we go.

Frequently Asked Questions

Why do most construction practitioners believe the current system works even though the evidence says otherwise?

Because they have never experienced anything different. The paradigm shapes what is visible as normal and acceptable. People trained and experienced entirely within the dominant paradigm cannot easily see its failures as failures, they see them as the nature of construction.

Why does the legal structure prevent construction from learning from its failures?

Because admitting errors and omissions that have not been disclosed to other project parties invites claims against the admitting party. The legal protection designed to manage disputes has also protected the industry from the honest reflection that improvement requires.

What does productivity data reveal about the dominant paradigm?

That it has been producing declining construction productivity for sixty years while every other major industry has been improving. The gap between what the industry is asked to deliver and what the dominant paradigm can produce has been widening for six decades.

Why does the industry continue using CPM scheduling if it does not work for construction production?

Because it is the paradigm standard, and departing from the standard creates legal and institutional risk. The legal standard of care doctrine rewards familiar practice and penalizes innovation even when the familiar practice is demonstrably inadequate.

Can Lean construction be implemented within traditional adversarial contracts?

Yes, this is where it began and where most practitioners must start. Relational procurement makes transformation faster and deeper, but significant improvement is achievable within conventional contract structures through pull planning, make-ready discipline, and the cultural shift that treats problems as system feedback rather than as liability exposure.

If you want to learn more we have:

Discover Jason’s Expertise:

On we go

The History of the Development of the Last Planner System

Posted on April 17, 2026April 17, 2026 by Danny Jiménez⁩

Read 17 min

10 Improvements Takt Planning Enables Within the Last Planner System: The History Behind the Tool That Changed Construction

Before exploring how a tool works, it is worth understanding where it came from because the origin of the Last Planner System tells you something essential about why it is structured the way it is, why it addresses what it addresses, and why its development has continued to evolve rather than hardening into a fixed methodology.

The Last Planner System is not a manufacturing tool adapted for construction. It was developed by construction practitioners, from construction experience, specifically for the challenges that construction production presents. That distinction matters. It means the principles embedded in the system reflect the real conditions of multi-trade, location-based, complex project production not the stationary assembly line logic that Lean construction sometimes has to translate away from rather than toward.

How It Began: The 1980s Precursor

The research and practice that eventually became the Last Planner System started in the 1980s, when Glenn Ballard was serving as Productivity Improvement Manager for Brown and Root’s Construction operations in the United States. At that time, Ballard was studying crew planning the level at which foremen actually assigned work to their crews and discovering the gap between what the master schedule called for and what the crews were actually able to execute.

Two principles emerged from that work that would become foundational to the full system developed years later. The first was make-ready the discipline of ensuring that all the conditions required for a task to be completed were in place before the crew was expected to execute it. The second was shielding workers from bad assignments the recognition that asking crews to start work that was not genuinely ready was a form of waste that consumed their time, degraded their effectiveness, and eroded the reliability of the production system. Both principles reflected a fundamental respect for the people doing the work: if the system was not set up to allow them to succeed, asking them to push through was not a solution. It was a management failure.

The Formal Development: 1990s Consulting Work

The Last Planner System formally emerged in the early 1990s from Glenn Ballard and Gregory Howell’s consulting work in the industrial construction sector. The initial principles were clear and have not changed: improve workflow reliability and improve plan predictability. Those two goals making work flow and making plans trustworthy remain the foundation of everything the system does.

The history of the LPS would be incomplete without acknowledging its early connection to Lauri Koskela’s seminal 1992 work on the application of production principles in construction. Koskela’s Transformation-Flow-Value model of production provided the theoretical framework that explained why traditional project management tools were not adequate for managing construction production. The combination of Ballard and Howell’s practical system with Koskela’s theoretical foundation created what is now called Lean Construction. This union led directly to the formation of the International Group for Lean Construction in 1993, with its inaugural conference held in Espoo, Finland where the term “Last Planner” was first formally introduced and published.

The first real-world experiments with the LPS on construction projects occurred between 1993 and 1994. A full implementation was carried out on a major refinery project in Venezuela between 1995 and 1996 one of the most significant early demonstrations that the system could function in the field on a complex, large-scale industrial project. Those results established the credibility that allowed broader adoption to begin.

Key Developments in the System’s Evolution

The Last Planner System has not been static since its initial development. Several specific additions have significantly shaped how it operates today. In 1996, the link between look-ahead planning, the make-ready process, and their impact on Percent Plan Complete was formally discovered and incorporated. This was a critical finding it demonstrated that the reliability of weekly commitments was directly connected to the quality of the make-ready work done in the preceding weeks. Teams that actively identified and removed constraints six weeks out consistently achieved higher PPC than teams that planned without looking that far ahead. This established make-ready planning not as an optional enhancement but as a structural requirement of a reliable production system.

Glenn Ballard’s 2000 doctoral thesis “Last Planner System of Production Control” became the most cited publication on the LPS in academic literature, with hundreds of citations from researchers and practitioners around the world. The thesis formalized the theoretical underpinnings of the system and provided the scholarly foundation that has informed both academic research and practitioner education on every inhabited continent.

The system has also been integrated with other tools and disciplines as they have developed. Building Information Modeling provides the three-dimensional coordination environment that can be connected to production planning sequences. Location-Based Management Systems, including Takt planning, provide the spatial and rhythmic logic that makes the production plan visible in terms of zones and trains of trades. Visual management makes the plan, the constraints, and the performance metrics visible at the level where the work is being done. Each of these integrations has expanded what the Last Planner System can do without changing what it fundamentally is.

What the Evidence Shows

Written evidence of Last Planner System implementation has been documented in sixteen countries across all major continents. The exponential growth in adoption represents one of the most significant shifts in construction management practice that has occurred since the development of CPM scheduling in the 1950s and it is a shift in the opposite direction. Where CPM moves planning authority away from the people doing the work and toward the people managing the schedule, the Last Planner System moves planning engagement toward the last planners the foremen and superintendents who are closest to execution.

The outcomes documented from genuine LPS implementations consistently show improvement in cost performance, schedule performance, productivity, and safety. The improvement is not guaranteed by the tool alone it requires the discipline to run all five parts of the system, the management behavior that treats last planners as partners in planning rather than recipients of schedules, and the organizational commitment to continuous learning that the system’s metrics are designed to support.

Here are the signals that an organization has genuinely internalized the Last Planner System rather than performed it:

Make-ready planning is treated as the most important weekly activity, not as an administrative requirement
Trade partners participate in phase planning collaboratively and with genuine investment in the commitments they make
PPC is tracked honestly and root causes of misses are examined and acted on at the system level
The daily huddle produces real adjustments, not just status confirmations
The system is treated as a daily discipline rather than a project-phase initiative

The Benchmark Work

Glenn Ballard’s current work on developing a Last Planner System benchmark with inputs from both practitioners and academics represents the next phase of the system’s development the effort to standardize what best practice actually looks like, provide clear guidance on the most common implementation questions, give organizations a way to measure their LPS implementation against the ideal state, and align the language the industry uses when referring to different components of the system. This standardization is the natural next step in the maturation of a tool that has been in active development for more than three decades.

The benchmark will not freeze the system. The LPS has always evolved through the combination of practice and theory, with findings from real projects and rigorous research continuously incorporated. That dynamic has been one of its greatest strengths the willingness to improve the system rather than defend a fixed version of it.

At Elevate Construction and LeanTakt, the Last Planner System is implemented as part of the Integrated Production Control System combined with the First Planner System for preconstruction design and the Takt Production System for location-based production control. The combination gives every project the strategic production design, the collaborative commitment cycle, and the short-interval control that genuinely transforms how projects are delivered. If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow.

The Last Planner System was built for construction, by construction people, from construction experience. That is exactly why it works.

On we go.

Frequently Asked Questions

Where did the Last Planner System come from?

It was developed by Glenn Ballard and Greg Howell from their consulting work in industrial construction in the early 1990s, building on Ballard’s earlier research on crew planning in the 1980s. It was developed specifically for construction not adapted from manufacturing.

What were the original principles of the Last Planner System?

Improve workflow reliability and improve plan predictability. Those two foundational principles have not changed since the system was first formulated, though the list of supporting principles and integrated tools has grown significantly through ongoing research and practice.

What was the significance of Lauri Koskela’s 1992 work to the development of LPS?

Koskela’s work on production principles in construction provided the theoretical framework that explained why traditional project management tools were insufficient for construction production control. The union of Koskela’s theory with Ballard and Howell’s practical system created what is now known as Lean Construction.

What was the most significant research finding in the system’s early evolution?

The 1996 discovery that look-ahead planning and the make-ready process were directly connected to Percent Plan Complete reliability. This established make-ready planning as a structural requirement of the system rather than an optional enhancement.

How has the Last Planner System integrated with other tools over time?

It has been integrated with Building Information Modeling for coordination, Location-Based Management and Takt planning for spatial production control, and visual management for real-time plan communication. Each integration has expanded the system’s capability while maintaining its core purpose.

If you want to learn more we have:

Discover Jason’s Expertise:

On we go

Lean Construction Won’t Happen and Here’s Why

Posted on April 17, 2026April 17, 2026 by Danny Jiménez⁩

Read 20 min

Why the AEC Industry Resists Lean: Ten Root Causes and the Path Forward

There is a version of this conversation that happens at Lean construction conferences, in LinkedIn comment threads, and in the offices of general contractors and owners who have invested in training and tools for years. The vocabulary is established. The principles are understood. The sticky notes have been used. And yet the evidence that projects are being delivered faster, cheaper, and at higher quality because of Lean is thinner than the enthusiasm for Lean would suggest.

The hard truth that the construction industry has been slow to name directly is this: despite two decades of serious effort, Lean has not yet transformed how most construction projects are delivered. Not really. The question worth asking is why not defensively, but diagnostically. Because the principles are sound. The case is made. And something is still preventing the transformation from taking hold at the scale the industry needs.

Here are ten reasons that, taken together, explain the gap.

The Ten Root Causes

The first is capitalization and fragmentation. Construction relies on a very large number of small, lower-capitalized entities, each using different systems for accounting, scheduling, estimating, and document production. The interoperability required for an integrated production system is almost impossible to establish when every participant operates from a different software environment and has neither the capital nor the organizational capacity to change it.

The second is underinvestment in research and development. As a percentage of revenue, construction invests far less in R&D than manufacturing or healthcare. The knowledge base from which innovation could emerge is correspondingly thinner. Industries that invest in understanding their own systems get better at those systems. Construction largely does not, and the improvement rate reflects that.

The third is software fragmentation and ineffective utilization. The platforms employed across the industry do not talk to each other well, and even the platforms that offer genuine capability are rarely used to their potential. A BIM model that could support real-time cost and schedule analysis at the concept stage is used primarily for clash detection. The technology exists for far more than most teams ask it to do.

The fourth is regulatory infrastructure. The permitting process in most jurisdictions still relies on paper-based review systems and technologies that have not meaningfully updated in decades. The constraint is not over-regulation; it is that the regulatory systems were not designed for integrated digital project delivery and have not been redesigned for it.

The fifth is owner procurement practice. The majority of owners, particularly in the public sector, continue to use design-bid-build and show limited interest in alternatives. Even owners who are aware of collaborative delivery methods often conclude that the institutional and legal risk of departing from the traditional approach outweighs the potential benefit. Without owner demand for Lean delivery, the transformation of the supply chain is significantly constrained.

The sixth is a misunderstanding of coordination. Architects should provide a coordinated design. Contractors should coordinate the work of trades in the field. What has happened instead is that contractors have absorbed the coordination of both dealing with design gaps, clash resolution, and missing information while simultaneously managing field execution. This leads to mistakes, delays, and cost overruns that the system treats as normal rather than as evidence of a structural failure in the delivery model.

The seventh is fragmentation through specialization. Architects who once served as master builders are now one among many in a loose collaboration of consultants and specialty contractors assembled, often for the first time, to deliver a project. The integration that made master builders effective has been replaced by a handoff chain that loses information at every boundary.

The eighth is misplaced values. The industry, reflecting broader societal patterns, has learned to prioritize money over time. Lowest first cost is optimized even when it increases total cost. The waste of time and the waste of money compound each other because the tradeoff is not honestly evaluated.

The ninth is legal risk aversion. The transfer and mitigation of risk in contracting has created a powerful incentive not to innovate. The legal standard of care doctrine encourages every participant to do what has always been done, because departing from standard practice is the condition that creates legal exposure. Innovation, by definition, departs from standard practice. The system punishes the departure.

The tenth is a declining human resource base. Economic conditions and cultural stigmas associated with construction work relative to technology or finance careers have reduced the pipeline of talent entering the industry. Firms that are stretched thin on human capacity are not positioned to invest in learning and implementing Lean practices that require genuine behavioral change.

What the Honest Alternative Actually Looks Like

The path through this list is not incremental. It is structural. The contract is the place to start. Standard design-bid-build agreements institutionalize adversarial incentives. Replacing them with relational agreements where overhead and profit are fixed, where profit is distributed at successful project completion, and where interim billings cover only documented direct costs aligns every participant’s financial interest with the project’s success. Working together becomes the only rational strategy. Trust becomes the driving factor.

Location-based scheduling also called flow line or line of balance is a more honest representation of how construction production actually works than CPM. It uses space and location alongside time, activity, and resources to schedule and manage productivity. It surfaces trends before they become overruns. It enables course correction while correction is still inexpensive. The continued use of CPM in construction is not a technical necessity, it is an institutional habit, and it is a habit that costs the industry dearly.

Building information modeling used to its actual potential at the 5D level that integrates cost and schedule from the concept stage would eliminate a significant percentage of late-stage RFIs, coordination failures, and change orders. The software exists. The barrier is the will to use it and the contractual structure that would make using it in the owner’s and builder’s shared interest.

Prefabrication, when considered from the inception of design rather than brought to the table late in the construction documents phase, removes one of the most significant sources of field installation waste and quality variability. The advantage is lost almost entirely when prefabrication is an afterthought rather than a design intent.

Target Value Design establishing a realistic baseline cost and schedule at the concept level and refining it continuously as design progresses eliminates the value engineering exercise that most project teams experience as both demoralizing and wasteful. Designers who resist responsibility for cost and schedule are not serving their clients. The uncertainty they are trying to avoid is unavoidable; the question is whether it is confronted honestly from the beginning or discovered painfully at bid time.

Here are the signals that a construction organization is genuinely moving toward Lean delivery rather than performing it:

Contracts are relational rather than transactional; profit is tied to shared success rather than individual margin extraction.
The design team and the construction team are at the same table from the beginning, not sequenced.
Prefabrication is considered in the design phase, not proposed by the contractor after design is complete.
Scheduling is done with location-based methods that reflect production reality rather than CPM logic diagrams.
BIM is used for real-time cost and schedule analysis, not just clash detection.

The Tipping Point

The construction industry is closer to the tipping point of genuine transformation than the persistence of old habits suggests. The organizations that have revised their delivery approach from design-bid-build to design-build, made their subcontract relationships relational rather than transactional, deployed location-based scheduling and productivity management, and built prefabrication into their design process from the start, these organizations are attracting investment and producing results that the traditional approach cannot match.

The barrier is not knowledge. The principles have been available and documented for two decades. The barrier is the accumulated institutional momentum of a system that was designed to do what it does and that has successfully avoided being redesigned because the disruption of changing it feels riskier than the ongoing cost of keeping it. That calculation is changing. Owners who have experienced collaborative delivery do not easily go back. Contractors who have built genuine Lean capability compete differently. And the evidence base for what the transformation produces is becoming hard to argue with.

At Elevate Construction, every engagement exists to close the gap between where an organization is and where the transformation is available to take it. Not theoretically. On real projects, with real trade partners, in real contract structures that may or may not be ideal but that can still support meaningful improvement. If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow.

The industry is on the tipping point. What side of it your organization lands on is a choice being made right now, in how you structure the next contract and how you approach the next project.

On we go.

Frequently Asked Questions

Why has Lean construction not produced broader industry transformation after two decades?

Because the structural conditions that prevent it, fragmented capitalization, adversarial contracts, design-bid-build procurement, regulatory paper systems, and legal risk aversion have not changed at the systemic level that Lean transformation requires. Tool adoption without structural change produces limited and temporary results.

Why is design-bid-build specifically identified as a barrier to Lean?

Because it separates design from production, which is the root cause of the majority of coordination failures, late RFIs, change orders, and value engineering exercises. Construction is the only remaining economic sector that still systematically separates these two functions.

What is location-based scheduling and why is it better suited to construction than CPM?

Location-based scheduling uses space and location alongside time, activity, and resources to represent how production actually moves through a building. It surfaces productivity trends in real time and enables course correction before delays compound. CPM was developed for project types where location is not the primary production variable and does not serve construction’s location-based production reality.

What does a relational contract mean in practice?

Overhead and profit are fixed for the project. Profit is distributed at successful completion rather than extracted margin by margin throughout execution. Interim billings cover only documented direct costs. Every participant’s financial success depends on the project’s success which makes genuine collaboration the rational strategy rather than the aspirational one.

What role does prefabrication play in a genuinely Lean delivery model?

Prefabrication, when integrated from the concept stage of design rather than proposed after construction documents are complete, removes significant field installation waste, quality variability, and schedule risk. The advantage disappears almost entirely when it is treated as a contractor optimization rather than a design intent.

If you want to learn more we have:

Discover Jason’s Expertise:

On we go

Culture Matters in Design and Construction

Posted on April 17, 2026April 17, 2026 by Danny Jiménez⁩

Read 19 min

The Lean Project Delivery System: How Projects Should Actually Be Structured

The current system of project delivery is dysfunctional. Not occasionally. Systematically. It is replete with waste and redundancy, organized around adversarial incentives that reward opacity, obfuscation, and secrecy, and structured to protect individual company interests at the expense of project outcomes. That is not a provocative claim, it is the observable result of a delivery paradigm that has produced, for decades, projects that finish late, over budget, with quality compromises, and at the cost of the people building them.

The first requirement for changing this system is a belief that it can be changed, that the dysfunctions are designed in, not inherent to construction, and that they can be redesigned out. Without that belief, no one will accept the paradigm shift that collaborative project delivery requires. And without the paradigm shift, the industry will keep designing the same waste and calling it construction.

This blog is about what the collaborative approach actually requires: the core beliefs that make it possible, the six values that shape the behaviors it depends on, and why culture is the mechanism that makes all of it real.

Three Core Beliefs

The first belief is that the current system is broken and can be fixed. This is the gateway. People who believe that “this is just how construction works” will not invest in changing it. People who believe that the dysfunction is designed and therefore designable differently will.

The second belief is that teams build projects, not individual companies. Despite the contractual borders that separate GCs from designers from owners from trade partners, those borders must be crossed by individuals who are willing to put the project’s interests ahead of their company’s short-term protective instincts. The project is the unit of success. Every company that participates benefits when the project succeeds. Every company loses when it fails regardless of what the contract says about who bears which risk.

The third belief is that individuals must be both willing and empowered to behave as project-first team members. Willing means they genuinely choose to prioritize project outcomes. Empowered means their companies have given them permission to make decisions that serve the project rather than directing every choice through the lens of company protection. Organizations that send individuals into collaborative environments with protective mandates undermine the collaboration before it starts.

The Six Core Values

Visibility and transparency form the first value. The trailer walls of a collaborative project contain all the information that matters, the plan, the budget, the schedule, the current state, the pending constraints. Everything the team needs to know is visible. Transparency goes further: costs, profit margins, labor projections, peripheral program costs, all of it freely shared. No hidden agendas. No secret reserves. The openness that feels uncomfortable in an adversarial contract becomes the competitive advantage in a collaborative one, because the team that can see everything can optimize everything.

Collaboration is the second. Once visibility and transparency are established, the team is free to actually work together not just to share information but to make sense of it together, to develop the best project plan within the applicable constraints, to hear all voices and develop multiple options before converging on the best solution. Real collaboration requires physical proximity and shared space. It requires that ideas are visible, that all voices are actually heard, and that the process produces innovation rather than just the lowest common denominator of what everyone already knew. Collaboration also has a secondary benefit that its advocates sometimes understate: it builds trust.

Trust is the third value and the most important. The current delivery paradigm has systematically excluded trust from the process competitive bidding produces massive assumptions, incentive structures reward opacity, and the legal framework assumes that every party is trying to exploit every other party. The results are predictable: teams that cannot have honest conversations, commitments made without confidence in the commitments they depend on, and the constant friction of self-protective behavior applied to problems that require collaborative solutions.

Trust develops through the repeated experience of face-to-face collaboration of seeing that other team members are candid, capable, creative, and genuinely committed to the project’s success. It also exposes the team members whose behaviors are not open or constructive, which is valuable information for the team’s composition. The ability to face that possibility, address it, and rely on those who remain is at the heart of trust-based teams.

Commitment is the fourth value. Design and construction are among the most difficult industries in which to ask people to make and keep commitments because every commitment depends on the reliability of the preceding commitment. The trade partner cannot commit to starting zone two on schedule if they cannot trust that the preceding trade will actually clear the zone on time. The designer cannot commit to design packages aligned with the construction sequence if they cannot trust that the construction sequence is genuine rather than aspirational. Commitment networks require trust networks. You cannot have reliable commitments without reliable predecessors.

Achievement is the fifth value. People do better work when they are happy, when they have positive views of the organization and its people, and when they are primarily motivated by the work itself. This is not a soft management principle; it is empirical research. Daniel Pink’s work on intrinsic motivation establishes that autonomy, mastery, and purpose drive higher performance than external incentives in complex cognitive and creative work. Achievement is self-reinforcing: the experience of doing good work that matters to the people it serves is its own incentive to do more good work. Achievement also calls for recognition and celebration, making the accomplishment visible so that the team understands what they built and why it mattered.

Knowledge is the sixth value. Every project generates extraordinary learning about what worked, what failed, why specific approaches succeeded in specific conditions, what assumptions were wrong, and what new capabilities the team developed. Almost none of that learning is captured or shared across the full team. Most of it evaporates when the project closes and the team disperses. Knowledge capture including the metrics used to measure project success, the analysis of whether those were the right metrics, and the project delivery guides that carry insights to future teams is how the industry builds on its own base of knowledge rather than starting from the same place on every project.

Here are the behaviors that the six values produce and require in the people on a collaborative project team:

Candid and truthful: saying what is real even when it is uncomfortable.
Communicative: sharing information proactively rather than waiting to be asked.
Cooperative and collaborative: working toward the project outcome rather than the company outcome.
Creative and innovative: bringing fresh thinking to problems rather than defaulting to what has always been done.
Curious: asking questions, exploring alternatives, remaining open to being wrong.
Patient: accepting that complex processes are not linear and that quality requires time to develop.
Respectful and loyal: to the people on the team, the project, and its purpose.
Trustworthy: doing what they said they would do, telling the truth about what they know.

Culture as the Implementation Mechanism

Contracts cannot produce these behaviors. This is one of the most important truths in all of project delivery. Contracts can create consequences for certain behaviors. They cannot create the behaviors themselves. The behaviors that deliver the best project outcomes are produced by culture by the shared beliefs, values, and unspoken understandings that the team develops together through the way it works.

Culture is the stuff the team believes in so much that it teaches it to those who join. It is the common understanding of how the team operates that does not need to be written down because it is demonstrated every day. And it is built not through aspirational posters or values statements but through organized space, tools, processes, and the consistent modeling of the behaviors the team says it values.

Each company that participates in a collaborative project brings its own culture. The cultures will not perfectly align. The goal is not to homogenize the companies; it is to create a project-level culture strong enough that individuals can bring their full capability to the project rather than their company’s protective instincts. That project culture is designed deliberately, maintained actively, and expressed through the behaviors that are encouraged, commended, and rewarded in every interaction.

At Elevate Construction, every consulting engagement is an exercise in building this kind of project culture. The alignment meeting establishes the shared beliefs. The pull planning session builds the collaborative commitments. The visual management systems make everything visible. The conditions of satisfaction create the transparency. And the daily huddles and zone walks maintain the culture through constant, consistent reinforcement. If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow. Behaviors deliver projects. Culture produces the behaviors. Design the culture deliberately.

On we go.

Frequently Asked Questions

What are the three core beliefs required for collaborative project delivery?

That the current system is dysfunctional and redesignable, that teams build projects rather than individual companies, and that individuals must be both willing and empowered by their organizations to behave as project-first team members.

Why is trust described as the most important ingredient on project teams?

Because without trust, genuine commitment is impossible. Commitments depend on reliable predecessors and reliability requires trusting that other team members are genuinely invested in the project’s success rather than in protecting their own position.

Why can’t contracts produce the behaviors that collaborative delivery requires?

Because contracts create consequences, not motivations. The behaviors that deliver best-value projects, candor, creativity, genuine commitment, collaborative problem-solving are produced by culture, not by legal obligation.

What is knowledge capture and why does it matter?

It is the deliberate practice of documenting what was learned on a project, what approaches worked, what failed, what metrics were right, and what the team would do differently and making that learning available to future project teams. Without it, every project starts from the same floor.

How does a project team build its own culture when each participant comes from a different company culture?

By creating a shared set of values, explicit agreements about behaviors, and a physical and operational environment that reinforces those values daily. The project culture does not replace company cultures; it creates a collaborative layer above them that individuals can participate in as project-first team members.

If you want to learn more we have:

Discover Jason’s Expertise:

On we go

Poor Communication In Construction

Posted on April 17, 2026April 17, 2026 by Danny Jiménez⁩

Read 18 min

Poor Communication in Construction: Seven Failure Modes and How to Fix Every One

Here is a confession worth making before anything else. The person writing this blog is not a natural communicator. Grew up as an only child in the high desert of Southern California, nearest house a mile away, genuinely comfortable spending hours inside his own head convinced that everyone around him automatically understood what he was thinking because he had been thinking it so clearly. The gap between what was happening in the head and what was being communicated to the people who needed to act on it has been a recurring professional problem. The overcompensation for that gap has been videos, blogs, and every format that allows communication to be prepared rather than improvised.

That context is worth knowing because every one of the seven failure modes below is personal. This is not a list of other people’s bad habits. It is a list of patterns that are common enough in construction to be worth naming honestly and fixable enough to be worth addressing deliberately.

One: Assumptions

The most expensive word in construction communication is the unspoken assumption. “You know what to do, right?” And the other person does not know. They have a different picture in their head. The task goes in the wrong direction, at the wrong scope, by the wrong person, at the wrong time because the full thought stayed in the communicator’s head rather than leaving it.

The fix is to stop assuming that the mental image you are working from is shared by the people you are working with. It is not. They have different context, different priorities, different recent experiences. Write it out. Use an impact filter. State the task, the owner, the deadline, the quality expectation, and the reason and confirm that the person received the actual message rather than a fragment of it.

Two: Vague Expectations

Closely related to assumptions, and equally common. “Hey, can you go do the thing?” And moving on before the other person can respond. Not waiting for acknowledgment. Not defining what done looks like, by when, to what standard, and why it matters.

The discipline required is brief and specific: state the task with the done definition, name the deadline, describe the quality expectation, explain the context. Wait for confirmation that the message was received. Then move on. The extra thirty seconds required to be specific eliminates the multiple conversations that follow when the person delivers something other than what was needed.

Three: Failure to Follow Up

Giving a clear assignment and then disappearing is not delegation. It is abandonment with paperwork. Following up is not micromanagement is controlling how the work is done. Following up is caring whether the work is going well, checking whether the person has what they need, offering earlier and more frequent draft reviews that allow course corrections when they are still easy.

“How is this going? Do you need anything? Can I look at an early draft?” Those questions are not signs of distrust they are signs of investment. They create quicker iteration cycles, which produce better final products and build the trust that makes the relationship more productive over time.

Four: Emotional Reactions

When someone brings a problem, a struggle, or a miss the leader’s emotional reaction in that moment determines everything that follows. An emotional reaction of frustration or disappointment signals that bringing problems is dangerous. The person on the receiving end of that signal does not bring fewer problems they batch the problems, hide the problems, work around the problems, and eventually deliver a product at the end that reflects all the unaddressed problems that never surfaced. The spiral is predictable and entirely preventable.

The replacement is a simple, consistent response to problems: “That’s fine. Let me help. What do you need?” The tone matters as much as the words. Creating safety for problems to surface early is not softness it is production intelligence. Early problems are small. Late problems are crises.

Five: Meeting Chaos

Meeting to meet is batching. Every meeting that could have been a voice message or a two-line text is a block of time extracted from everyone in the room for a purpose that did not require their simultaneous presence. The construction site runs on meetings and most of them are longer than they need to be, less frequent than they should be in some areas, and more frequent than useful in others.

The voice message is an underused tool. Opening WhatsApp, recording a sixty-second voice note that covers a check-in, a question, and a request, and sending it costs almost nothing and can be responded to asynchronously when it is convenient. Twice the speed, a fraction of the coordination overhead, and no calendar required. Reserve structured meetings for decisions, planning sessions, and collaborative problem-solving. Use faster channels for everything else.

Six: No Written Clarity

There is a gap between what was communicated verbally and what the person receiving it actually wrote down and will act on. This gap is widest in fast-moving project environments where people are absorbing information from multiple directions simultaneously and cannot reliably hold all of it.

The solution is written clarity not long emails, but clear, structured instructions that give the person a reference they can return to. AI tools are genuinely useful here: take the verbal instruction that you have in your head, put it into a prompt, ask for clear bullet-point instructions, and review what comes back for accuracy. What the person receives is specific, actionable, readable, and savable. They are not holding something in their short-term memory hoping they got it right. They have a document. The quality of what they produce reflects the quality of what they received.

Seven: Lack of Feedback Loops

The mistake that produces the most rework and the most frustration is waiting for a finished product before engaging in the review process. The person works for a week on a deliverable that the reviewer will see for the first time at delivery. The reviewer sees a direction they did not intend. The rework starts. And everyone involved wonders why.

Feedback loops solve this. Not review at completion review at draft, at outline, at early sketch, at conceptual framework. Multiple short touchpoints that allow course corrections at every stage while the cost of correction is still low. The feedback loop is not overhead. It is the quality assurance system for any piece of work that requires interpretation rather than pure execution.

Here are the patterns worth watching for in a construction project or organization:

Assignments given without confirmation that the person understood the scope, the deadline, and the quality expectation
Problems that surfaced at the weekly planning meeting that could have surfaced three days earlier if the environment had made that safe
Meetings scheduled to discuss information that could have been communicated through a voice message or a text channel
Deliverables that required significant rework because the direction was never confirmed at draft stage
Communication that lives entirely in someone’s head and produces behavior that puzzles the people around them

Connecting to the Mission

The Last Planner System only works when the people operating it communicate reliably when commitments are stated clearly, misses are reported honestly, and adjustments are made in real time rather than accumulated for the next meeting. The morning worker huddle only builds a team when the plan is communicated specifically enough that every worker knows what they are doing before they step into the zone. And the retrospective at the end of a phase only produces learning if the team is safe enough to be honest about what actually happened rather than what they wish had happened.

Every one of these communication practices is not a soft skill sitting adjacent to the production system. It is the nervous system of the production system. Communication is how the plan reaches the people executing it, how problems surface before they compound, and how learning transfers from one project to the next.

If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow. These seven things are straightforward to name and genuinely difficult to practice consistently. Work on them every day.

On we go.

Frequently Asked Questions

What is the most common communication failure on construction projects?

Assumptions the belief that the mental picture in the communicator’s head is automatically shared by the person receiving the communication. It almost never is, and the gap between the two pictures produces misdirected effort, rework, and frustration on all sides.

What is the difference between micromanagement and following up?

Micromanagement controls how the work is done. Following up checks whether the work is going well, whether the person has what they need, and whether early course corrections are possible. Following up is an expression of investment, not distrust.

How do emotional reactions to problems create a communication breakdown?

Because they signal to the person bringing the problem that bringing problems is dangerous. That signal causes people to batch and hide problems rather than surface them early which means problems grow larger before they are addressed and the rework cost escalates accordingly.

Why are feedback loops more important than a single final review?

Because direction errors caught at draft stage cost almost nothing to correct. Direction errors caught at completion require rework that consumes time, money, and trust. Multiple short feedback loops throughout the process are the quality assurance mechanism for any work that requires interpretation.

Why should meetings be reserved for specific purposes rather than general communication?

Because meetings require everyone’s simultaneous presence, which is expensive. Information exchange, check-ins, and quick questions are better served by voice messages, text channels, and other asynchronous tools that allow the receiver to respond at the right time without interrupting productive work.

If you want to learn more we have:

Discover Jason’s Expertise:

On we go

What Is The Last Planner System

Posted on April 17, 2026April 17, 2026 by Danny Jiménez⁩

Read 21 min

Last Planner System Explained: The Complete Overview and the Missing Connection

There is a temptation that every team faces when they first encounter the Last Planner System. The system has multiple parts, and the first instinct is to treat it like a menu to select the pieces that feel most accessible, implement those, and leave the rest for later or skip them entirely. Pull planning looks valuable, so that gets implemented. The weekly work plan seems practical, so that goes in. The percent plan complete tracking adds some accountability, so that gets adopted. And the make-ready planning and the daily huddle and the root cause analysis of misses get deferred because there is not enough time and the project is already under pressure.

This approach consistently produces disappointing results. Not because pull planning or the weekly work plan are ineffective they are not. But because the Last Planner System is a holistic system: each of its parts supports the others, and the parts that tend to get skipped are often the ones doing the most important work. Resist the temptation to treat it as a menu. The system is only as strong as the discipline with which all five parts are practiced.

What the Name Actually Means

The Last Planner System of Production Control is a registered trademark of the Lean Construction Institute, and its full name reveals its purpose. Production control not just planning, not just scheduling, but the ongoing management of production to support working toward planned accomplishments, to do what can be done to move along the planned path, and when that becomes impossible, to determine alternative paths that accomplish the desired goals.

The term “last planner” refers specifically to the people responsible for making the final assignment of work to specific performers and ensuring those performers have everything they need to complete their assignments: materials, equipment, and information. During the design phase, last planners are typically architectural and engineering project managers. During construction, they are typically foremen and superintendents for the trade contractor crews. The people who are closest to the actual execution of work are the people whose planning is most critical to making that work reliable. The system is named for them because it is designed to engage them genuinely, collaboratively, at every stage.

Part One: Master Planning

Master planning happens at the very beginning of the project and focuses on identifying the major milestones that will gauge whether the project is progressing at a pace that leads to successful completion. These milestones mark the completion of each major project phase and the dates for releasing the purchase of major long-lead items the procurement trigger points that must be hit to have materials available when the production sequence requires them.

Ideally, both design phase and construction phase last planners participate in developing the master planning schedule. This is the first departure from traditional scheduling practice, where the schedule is produced by schedulers and project managers and handed down to the people responsible for execution. When the people who will build the project participate in defining the milestones, those milestones carry a fundamentally different commitment than milestones that arrived from above.

Part Two: Phase Planning

Phase planning happens two to three months before the beginning of each phase a Taktphase being a portion of the project that makes sense to consider as a complete unit, bounded by the beginning and completion milestones identified in master planning. The goal of phase planning is to develop a genuine agreement between last planners on how all the work between those two milestones will be completed.

Phase planning uses a pull planning approach. Last planners are explicitly clear about the sequence of requests and commitments they are making with each other. The approach starts from the final required condition to complete the phase and works backward each trade partner declaring what they need from the preceding trade to be able to do their work, building the sequence through a series of customer requests and performer commitments that define clearly how work will be released from one operation to the next.

This is the primary opportunity for the team to determine how to pace the work so that it progresses at a steady rate with limited variation the Takt rhythm embedded into a collaborative sequence that every trade helped design. When trade partners build the plan, they own the plan. That ownership is what transforms the weekly work plan from a reporting exercise into a genuine commitment.

Part Three: Make-Ready Planning

Make-ready planning is where the most implementation failures occur, and it is the single most important factor in preventing production workflow breakdown. The team looks ahead typically six weeks, though complex projects may warrant longer to evaluate whether there are constraints to upcoming tasks identified during phase planning.

A constraint is any condition that prevents a planned task from being completed: labor availability, material delivery, equipment access, document conflicts, permit timing, or any other blocker that sits between the current state and the task being executable. Each constraint is logged with ownership and a commitment date for removal. That log is actively managed at every weekly meeting. The discipline of making work ready before crews arrive to execute it is what separates projects that flow from projects that perpetually firefight.

Make-ready planning also includes the detailed refinement of phase planning tasks into the specific operations required for daily and weekly execution, and the collaborative design of first run studies for operations that the team will encounter for the first time. This is where the production plan gets specific enough to be executed not just planned.

Part Four: The Weekly Work Plan

The weekly work plan is where each last planner commits to the specific tasks their team will complete each day of the following week. This is the commitment layer not aspirations, not targets, not estimates, but specific promises made by specific trade partners to specific predecessor and successor trades about what will be completed, to what standard, and by when.

Reliability is the critical attribute here. The weekly work plan is only as valuable as the honesty with which commitments are made and tracked. A plan full of optimistic commitments that consistently fall short teaches the team nothing and builds no trust. A plan built only from work that the trade partner has genuine confidence is ready to execute backed by the make-ready planning that confirmed readiness produces the reliable commitments that make downstream planning possible.

Part Five: Learning

The fifth part of the system is learning and it is where the gap between compliance with the system and mastery of it is most visible. Learning in the Last Planner System happens in two primary ways.

The daily coordination meeting the morning huddle is where last planners confirm whether their teams accomplished the planned work from the previous day and make the adjustments required to stay on plan for the week. These daily adjustments are critical: adjustments that happen daily are manageable. Adjustments that wait until the weekly planning meeting are significantly harder. Adjustments that wait until monthly reviews are crises. The daily huddle makes production visible at the interval where course correction is still cheap.

The learning metrics make the system’s performance visible in a form that drives improvement. Percent plan complete measures the percentage of weekly committed tasks actually completed as planned the primary reliability indicator. Tasks made ready measures what percentage of tasks identified during phase planning were actually ready to begin as planned the primary indicator of make-ready quality. Tasks anticipated measures how many tasks in the weekly work plan were previously identified in the look-ahead the primary indicator of planning depth and foresight.

Here are the signals that the Last Planner System is functioning correctly rather than being performed:

Trade partners make commitments to the weekly work plan only when they are confident the work is genuinely ready to execute
Percent plan complete is tracked honestly and root causes of misses are examined and acted on not explained away
The make-ready log is actively managed with clear ownership and deadlines, not maintained as a compliance document
The daily huddle produces actual adjustments that keep the week on track, not just status updates
The phase plan was built by the people who will execute it, not for them

The Non-Negotiables

Two conditions make the difference between a Last Planner System that produces results and one that produces reports. The first is management behavior. The system cannot function in a command and control environment where the plan is produced by management and compliance is the expectation. Project leaders must see themselves as coaches and facilitators of the planning and learning by last planners removing obstacles, asking questions, and supporting the system rather than directing the outcomes. Respect for people is not a value statement in this context. It is the operational condition the system requires to function.

The second is discipline. The Last Planner System is a practice like an athletic discipline or a musical instrument. Proficiency requires daily practice. Mastery requires sustained commitment over many projects. The teams that treat it as a continuous practice, running the full system on every project with genuine engagement at every level, develop the capability that transforms project performance. The teams that treat it as an initiative, running it when convenient and setting it aside when pressure increases, find that it produces exactly the limited results they invested in it.

If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow.

The Last Planner System is the most powerful collaborative planning tool construction has. Run all five parts. Practice it every day. And let the learning compound.

On we go.

Frequently Asked Questions

Why is it a mistake to implement only selected parts of the Last Planner System?

Because the parts support each other. Pull planning produces commitments that the make-ready planning must confirm are executable. The weekly work plan only reflects genuine commitments when the make-ready work has been done. The learning metrics are only meaningful when the commitments they measure were honestly made. Each part depends on the others.

Who are the “last planners” the system is named for?

The people who make the final assignment of work to specific performers and ensure those performers have what they need to complete their assignments. During construction, these are typically foremen and trade superintendents the people closest to actual execution whose planning reliability determines whether the project flows.

What is the most commonly skipped part of the Last Planner System and why does it matter?

Make-ready planning is most frequently underdeveloped. It is the single most important factor in preventing workflow breakdown without it, crews arrive to zones that are not ready, commitments miss, and the weekly planning cycle produces unreliable results regardless of how well the pull plan was executed.

What should the PPC target be and how is it achieved?

The target is always 100 percent every committed task should be completed as planned. The way to achieve this in a variable environment is to commit only the work that the make-ready process has confirmed is genuinely ready, and to maintain workable backlog for the remaining capacity rather than over-committing and accepting regular misses.

Why does the Last Planner System require a different management approach?

Because it depends on last planners making honest commitments rather than compliant ones, which requires an environment where surfacing constraints early is rewarded rather than punished. Command and control environments produce managed appearances rather than genuine reliability. The system needs coaches, not directors.

If you want to learn more we have:

Discover Jason’s Expertise:

On we go

How to Identify Waste

Posted on April 17, 2026April 17, 2026 by Danny Jiménez⁩

Read 19 min

Why Most Problem Solving in Construction Only Scratches the Surface

Peter Drucker said it directly: there is nothing so useless as doing efficiently that which should not be done at all. That statement is the most important challenge in construction problem-solving, and it points to the limitation of most corrective actions taken on project sites. The problem appears. Someone fixes it. The fix is efficient, competent, and fast. And the underlying condition that produced the problem remains unchanged, ready to produce the same problem again in a different location, in a different phase, on a different project, through a different crew.

Root cause analysis is the practice of going far enough into the causal chain to find the condition that must actually change for the problem to stop recurring. Not just who made the error but what in the work system allowed the error to occur in the way it did, and how the system must be redesigned so that future people making the same best choices they know how to make do not produce the same bad outcome.

The Mental Model Behind Every Project Failure

Every project failure is caused by choices. Not bad people, not careless workers, not incompetent trades choices made moment to moment by people doing their best to do the right thing based on how they understand the world and the system they are operating in. Deming said it precisely: every work system has inherent limits on how well it can produce a quality result. No one can outperform the limits of the system in which they work.

This means that root cause analysis, taken far enough, will always arrive at the underlying mental models the assumptions about how work should be organized, how incentives should be structured, how trades should interact that shaped the choices that produced the problem. Lasting improvement is not the corrective action that patches the visible failure. It is the system redesign that changes the conditions that made the failure predictable.

The Lean Fundamentals provide the lenses that make system conditions visible. Customer-defined value, workstream, flow, pull, and continuous improvement applied to the evidence of a waste walk reveal not just what went wrong but why the system was designed in a way that made it likely to go wrong.

The Waste Walk and the Template

The waste walk the Japanese practice of going to Gemba, the shop floor is the simplest and most powerful waste identification tool available. Walk the project site with Lean lenses and ask what you see. Not what you think you know about the site. What you actually see in front of you, right now.

A simple documentation template supports this practice: photograph the situation, name the waste categories evident in it, identify the immediate cause, and begin tracing the causal chain backward through the workstream. Evidence is what the photograph shows. Causes take digging. The first answer to “why did this happen?” is almost never the root cause it is the most visible cause, the closest to the point of discovery. The root cause is further upstream, in the design of the system that allowed the sequence of events to unfold.

The Misaligned Flange: What It Actually Reveals

A pump anchored to a formed pedestal. A tank installed correctly. A prefabricated pipe spool that was supposed to connect them with a flange that does not line up. The visual defect is immediate and obvious. The root cause requires tracing.

The investigation reveals that a critical survey marker, placed in an unprotected location in a high-traffic area, had been displaced by heavy equipment moving through the site. The pump pedestal was placed from the moved marker. The pipe spool was prefabricated offsite not from field measurements of the actual installed locations, but from design dimensions because it was a long-lead, costly item that had to be ordered before the field conditions were confirmed.

Every individual in this chain made a reasonable choice given their constraints and their incentives. The surveyors placed the marker. The equipment operators did not know the marker was critical. The field crew set the pedestal from the available marker. The fabricator worked from the design dimensions as instructed. No one was careless. The system designed them into a collision.

The commercial structure reinforced the failure at every level. Each subcontractor worked under a low-bid contract with no incentive to coordinate with other trades in ways that would consume time not built into their margin. Earned Value Analysis rewarded the highest claimable percent complete at the earliest possible date, which meant each trade was incentivized to claim and move on rather than to wait for confirmation of interface conditions. The production system performed exactly as it was designed. It was designed to produce exactly that result.

The Pipeline Sequence: The Five Whys in Practice

The stainless pipeline installation at the oil field site illustrates the Five Whys in its most useful application tracing a linear causal chain through sequential workstream decisions until the system-level condition that produced the failure is visible.

Why were pipe spools installed out of sequence? Because some spools were missing and other diameter spools were available to the crew that needed work. Why were some missing and others available? Because delivery batches mixed different spool sizes, and the fabrication logistics office was optimizing trailer capacity utilization rather than installation sequence. Why was fabrication not sequenced to field demand? Because the fab shop and the field installation were separate corporate divisions, each evaluated on capacity utilization without regard to the effect on the project’s overall production flow. Why didn’t field and fabrication coordinate demand and supply? Because the project organization and the corporate structure it operated within treated those two functions as independent profit centers rather than as elements of one integrated production system.

The superintendent reported that field demands that could interfere with fab shop capacity decisions were explicitly discouraged by management. That is the root cause. Not the missing spool. Not the delivery batch. Not the out-of-sequence installation. The organizational model that treated utilization of the fabrication capacity as more important than the flow of the installation sequence and that created no mechanism for the field to pull the supply chain based on actual installation readiness.

The customer paid for every day of delay in a form they never invoiced deferred revenue from the water cleaning plant that the lines were supposed to feed.

Here are the diagnostic questions that a waste walk and Five Whys process should drive toward:

What choices did the people involved make, and what led them to make those choices?
What in the system structure the contracts, the incentives, the organizational divisions, the information flows made those choices the rational ones given each party’s constraints?
What would have to change in the system for people in the same situation, making the same kind of reasonable choices, to produce a different outcome?
Is this a local deviation or a pattern is this type of failure appearing in multiple locations because the conditions that produce it are systemic?

The Cluttered Site: 5S as the System Response

The photographs of cluttered, disorganized site areas excess inventory, work in process, safety hazards embedded in the disorder illustrate the cumulative effect of a production system that has not been designed for flow. When the underlying assumption is to keep resources working on installation regardless of sequence or readiness, the site accumulates the evidence of that assumption: materials in the wrong place, equipment blocking access, inventory that has been moved multiple times and will be moved again.

5S is not a cleaning program for these sites. It is the systematic design of the work environment to support the production system rather than fight it. Sorted, organized, standardized, visually managed work areas eliminate the searching, the double-handling, and the setup waste that consumes crew time in cluttered environments. The properly organized tool storage and material staging area that emerges from a genuine 5S implementation does not just look better it performs differently. And that performance difference shows up in the weekly work plan, in the daily percent plan complete, and ultimately in whether the project finishes on schedule or absorbs another six weeks of avoidable delay.

The reservation of eight to fifteen percent of crew capacity for 5S maintenance, constraint removal, and workable backlog rather than committing that capacity to the weekly plan is what makes 100 percent plan completion achievable and sustainable. The site that is trying to commit 100 percent of capacity to installation will always find that capacity consumed by the motion, searching, rework, and correction that a poorly organized environment generates.

At Elevate Construction, waste walks are built into the zone control walk practice not as occasional events but as daily production management. The superintendent who walks the zones every day with Lean lenses is constantly collecting evidence of what in the system needs to change before it becomes a schedule impact. If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow.Take the waste walk. Photograph what you find. Trace it back. Change the system.

On we go.

Frequently Asked Questions

What is the purpose of a waste walk in construction?

To develop the trained perception to see waste that the normal work environment has made invisible and to document it specifically enough to support the root cause analysis that will identify what in the system produced it.

Why is the first answer to “why did this happen?” rarely the root cause?

Because the first answer is almost always the closest visible cause the most recent failure in a chain of system conditions. Root cause analysis requires tracing the chain backward through the workstream to the organizational, contractual, or procedural condition that made the failure predictable.

What is the Five Whys and when should it be used?

It is a root cause analysis technique that asks why a problem occurred five times, each time directing the inquiry one level deeper into the causal chain. It works best for relatively linear failure chains where each cause can be traced to a single predecessor condition.

What does “optimize the sub system while sub optimizing the whole system” mean?

It describes the failure mode in which each trade, division, or party maximizes its own performance metrics while producing outcomes that are collectively inferior. The fabrication shop optimizing trailer capacity is a perfect example the sub-system wins, the project loses.

Why does cluttered, disorganized site condition persist even when everyone knows it is a problem?

Because the underlying assumption is to maximize installation activity regardless of sequence or readiness. In that assumption, 5S maintenance is overhead rather than production. Lean production planning turns that assumption around proper organization of the work environment is what enables the installation to flow, not what competes with it.

If you want to learn more we have:

Discover Jason’s Expertise:

On we go

10 Forms of Wastes

Posted on April 17, 2026April 17, 2026 by Danny Jiménez⁩

Read 20 min

The Ten Wastes of Construction: What Muda, Mura, and Muri Actually Look Like in the Field

Taiichi Ohno’s seven classic production system wastes, later expanded to eight by Jeffrey Liker’s addition of unused human potential, and completed by the two systemic wastes of unevenness and overburden, give construction practitioners a complete diagnostic framework for seeing what is actually happening on their projects. Not just the obvious waste of damaged materials and excess inventory, but the deeper process wastes that consume more than half of construction time without producing a dollar of value for the customer.

The Japanese terms are worth knowing Muda for the eight operational wastes, Mura for unevenness in workflow, and Muri for overburden of people and equipment. But the more important thing is being able to see what they look like in real project conditions. The framework is only valuable when it produces recognition in the field.

The Eight Forms of Muda

Defects are any work done incorrectly, incompletely, or out of compliance with the requirements of the next person who receives it. In design, defects come from incorrect assumptions, miscalculations, and misunderstood requirements across the stakeholder group. In construction, defects have multiple root causes: design gaps, procurement errors, incorrect installation, work covered before quality was confirmed. The Last Planner System’s practice of requiring the receiving trade to accept completed work as genuinely done before it is marked complete is a direct defect-prevention mechanism. A best practice for preventing defects before they occur is to look for BIM clashes, unverified component specifications, and the reasons behind incomplete weekly work plan commitments these are the upstream signals that defects are likely to appear downstream.

Overproduction is sometimes called the mother of all wastes because it creates so many of the others. In construction, overproduction is driven by the pressure to keep crew resources utilized regardless of whether the work being done is the right work at the right time. A crew mobilized to a zone that is not ready for their scope because they are available and the schedule shows the work should be starting is producing out of sequence, creating conditions that the trades behind them will have to work around. Earned Value Analysis creates specific perverse incentives for overproduction by rewarding the percentage of scope installed rather than the quality of the flow in which it was installed. Takt planning, pull planning, and line of balance are the production planning responses that balance resource deployment against actual production targets rather than against financial reporting incentives.

Waiting is one of the most visible wastes and one of the most revealing diagnostics. When people are waiting for work or work is waiting for people, it is always a sign that planning and coordination have broken down somewhere upstream. In construction, waiting waste at the work face is almost always caused by upstream failures: design gaps, procurement delays, or predecessor work that was not completed to the standard required for the next trade to enter the zone. Every RFI sitting unanswered for two weeks is waiting waste. Every crew that arrives to a zone before the preceding work is cleared is waiting waste. Incomplete tasks on the weekly work plan are the measurement of waiting waste in real time.

Unused human potential the eighth waste is the failure to utilize the knowledge, experience, problem-solving capacity, and improvement ideas of the workers and trade partners closest to the work. In a construction industry organized around top-down direction, the person installing the work is rarely asked what would make that installation easier, faster, or higher quality. That unutilized capacity is waste. Lean construction through First Run Studies, worker huddles, and 5S improvement cycles specifically exists to convert unused human potential into organizational improvement.

Transportation is the unnecessary movement of materials, equipment, information, or people. Every time a material is moved from the delivery truck to a staging area, from the staging area to a temporary storage location, from storage to the zone, it is being transported and each movement consumes time, labor, and risk of damage. The closer the delivery point to the installation point, the less transportation waste. Just-in-time delivery eliminates the need for intermediate staging by bringing materials to the work face only when they are needed.

Inventory and work in progress are the buffers that accumulate when production is unreliable. Large material piles in the zone represent over-ordered or early-delivered stock. Work in progress the pipe spool that is sixty percent installed waiting on a missing component, the wall that has been framed but not inspected, the system that cannot be tested because three valves have not been delivered is inventory of the most expensive kind, consuming space, creating coordination overhead, and blocking the sequence of work that depends on its completion. The goal is not zero inventory some buffer is always appropriate to manage variability. The goal is right-sized inventory, placed at the end of the sequence where it can absorb the most variation with the least disruption.

Motion is the waste of inefficient physical work at the task level the worker who climbs down the scaffold to retrieve a tool that should have been staged at height, the field engineer who walks to the job trailer for drawings that should be accessible on a phone, the crew that reorganizes the gang box at the start of every shift because nothing has a designated location. Motion waste is what 5S specifically addresses: organizing the work environment so that everything needed is within reach, properly labeled, and returned to its location after use.

Excess processing is doing more work than the customer values the extra inspection step that adds no new information, the submittal process that requires three reviews of the same unchanged document, the tack-welded temporary support that will require cutting out and repairing when the permanent component finally arrives. In design, the greatest leverage for eliminating excess processing is early designing out the features and tolerances that create complex field work before they are built into the documents.

Mura: Unevenness in Workflow

Mura gets at the systemic pattern that the eight Muda wastes create in combination. When waste accumulates in a production system when waiting, overproduction, and missing components all interact the result is uneven workflow. People waiting for work, work waiting for people, zones with too much activity crowded together and zones with no activity. Unevenness is not just an operational symptom it is evidence that the planning and production control system is not working. Takt planning addresses Mura directly by designing production so that every trade moves at the same speed through the same sequence, eliminating the pile-up and sprint cycle that uneven flow produces.

Muri: Overburden

Muri is the waste of exceeding the appropriate capacity of people and equipment. The management tradition of setting stretch goals at 110 percent of capacity is based on the assumption that workers are holding back. It produces the opposite of its intended effect overburdened crews make quality errors, miss commitments, and create the rework and downstream disruption that consume far more capacity than the stretch production gained. Overburden of equipment shows up as breakdowns and waiting. Overburden of people shows up as overtime, burnout, defensiveness, and missed commitments.

The relationship between Muri and Percent Plan Complete is worth understanding precisely. The appropriate target for PPC is always 100 percent every commitment made should be met. The way to achieve that in a variable environment is to commit only 80 to 90 percent of available capacity to the weekly work plan, maintaining a workable backlog of make-ready work that absorbs excess capacity when commitments are met early. It is far better to reliably meet all commitments and use the remaining capacity for 5S, make-ready, and quality improvement than to commit 100 percent of capacity and consistently miss 15 to 20 percent of the plan.

Here are the field signals that indicate one or more of the ten wastes is actively present:

Materials in the zone that are not needed for the current week’s scope
Workers moving to retrieve tools or materials that should be within arm’s reach
Any crew waiting for preceding work, for materials, for information, or for permissions
Work that has been started but cannot be finished because a component or decision is missing
Rework of any kind at any stage
Commitments on the weekly work plan consistently falling short of what was promised

Connecting to the Mission

Learning to see the ten wastes is a skill that develops over time with deliberate practice. Every Gemba walk is an opportunity to apply the framework. Every weekly work plan miss is an opportunity to classify the waste that caused it and address the upstream condition that produced it. At Elevate Construction, the diagnostic process that opens every consulting engagement the Lean Assessment is fundamentally a waste identification exercise: what in this production system is producing Muda, Mura, and Muri, and what would need to change for the system to flow? If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow.

See the waste. Name it correctly. Find its upstream cause. Change the system.

On we go.

Frequently Asked Questions

What is the difference between Muda, Mura, and Muri?

Muda describes the eight specific forms of operational waste. Mura describes the systemic unevenness in workflow that results when Muda accumulates in a production system. Muri describes the overburden of people and equipment that results from mismanaging capacity. All three interact and reinforce each other.

Why is overproduction called the mother of all wastes?

Because it creates so many of the others. Work produced out of sequence creates inventory that must be stored and transported. Materials delivered before they are needed create motion and transportation waste. Work started without full kit creates waiting and rework. Overproduction is upstream of most other waste forms.

Why should PPC always target 100 percent even though 85 percent is often cited as acceptable?

Because 100 percent is the correct target for reliability. The way to achieve it in a variable environment is to commit only 80 to 90 percent of available capacity, maintaining a workable backlog to absorb excess capacity when commitments are met early rather than committing fully and accepting 15 percent misses as normal.

What is work in progress waste and why is it so costly?

WIP is work that has been started but cannot be completed because a required component, decision, or preceding activity is not in place. It consumes space, blocks downstream work, creates coordination overhead, and accumulates rework risk. It is the most expensive form of inventory waste.

How does 5S specifically address motion waste?

By organizing the work environment so that everything needed for the current scope is within reach, properly labeled, and returned to its designated location after use. This eliminates the searching, traveling, and repositioning that consumes worker time without adding any value to the installation.

If you want to learn more we have:

Discover Jason’s Expertise:

On we go

Why is Culture Important?

Posted on April 17, 2026April 17, 2026 by Danny Jiménez⁩

Read 19 min

The Culture Calculation: Why Love, Care, and Compassion Are the Most Practical Tools in Construction

There is a phrase worth sitting with before anything else: if you are not intentional about your culture, you are being intentional about your culture. It may not be the culture you want. It may not be the culture your team deserves. But a culture is forming regardless shaped by the values, ethics, and behaviors of every person in the organization, and most powerfully by whatever behavior the leadership is willing to tolerate. The culture is always there. The only variable is whether it is designed or defaulted.

The construction industry has defaulted for a long time. Not because the people in it are bad, they are overwhelmingly not but because the industry has historically treated culture as a soft concern rather than a production variable. What has that produced? More than one million open jobs. Skilled trade workers leaving the industry at five times the rate of those entering. Negative stereotypes that make it harder to attract the next generation of builders. And on individual projects, the invisible cost of teams that cannot have honest conversations, cannot surface problems early, and cannot sustain the collaborative relationships that Lean construction requires.

This blog is about the foundation beneath all of that, the four words that unlock culture, and why the construction industry’s discomfort with them is exactly why they need to be said.

Love, Care, Compassion, People

These four words do not appear often in construction management writing. They are not on most project charter documents. They are not discussed in most preconstruction meetings. And that absence is a diagnostic, it tells you something about what the industry has decided matters and what it has decided is too soft to name directly.

The irony is that these are exactly the four words that determine whether everything else works. Pull planning works when people care enough about each other’s scope to make honest commitments. Last Planner commitments are reliable when people trust each other enough to say “I’m not going to make this” before the deadline rather than after. Root cause analysis surfaces the real cause when people feel safe enough to be honest about what actually happened. The morning worker huddle builds a team when the superintendent shows up with genuine care for the people in the room rather than as a compliance exercise.

Love, care, compassion, and people are not alternatives to the production system. They are the substrate that makes the production system function as designed rather than as performed.

Every Group Has a Culture

Jesse Hernandez’s personal story from this series is worth centering here because it illustrates the most important truth about culture: it is not good or bad by nature. It is powerful by nature. The methods for building and maintaining a culture of contribution are the same methods used to build and maintain a culture of something far less constructive. The older men in Jess’s neighborhood were practicing culture-building, they listened, they gave time, they made him feel like he mattered. And those same methods pulled an honor roll student toward choices that could have cost him everything.

The point is not that culture is dangerous. The point is that culture is inevitable. Every group of people has one. The cells of the body self-organize through mitosis, white blood cells gathering to attack foreign substances, cancer cells disguising themselves to evade the immune response. The people in an organization behave with similar self-organizing logic, clustering around the values and leadership models they are exposed to, developing the unwritten rules of the group whether those rules have ever been discussed or not.

Good people can easily succumb to a bad culture. They do not have to be convinced that the culture is good. They only have to feel that they matter within it. And if the culture that makes them feel they matter is one that is not serving them or others well, the effect is the same as if it were. Our role as leaders and every person who influences the people around them is a leader is to own that influence deliberately rather than exercise it accidentally.

Why People Show Up

The question beneath the million-open-jobs statistic is not “why can’t we find people?” It is “why don’t people want to stay?” And the answer, almost always, is culture. Not compensation alone. Not career advancement alone. People leave environments where they do not feel that they matter. They stay in environments where they do.

This is what Jen, Jess, and Hoots are showing up for at 4 a.m., twice a week. Not because the time is convenient. Not because the content is proprietary. Because they have built something together that is worth showing up for, a culture of genuine trust, genuine vulnerability, genuine care for each other’s growth. And that experience is not something any one of them can fully describe. It is something they have lived into, through consistent presence and the willingness to be changed by what they encounter.

Connecting to people or to a common purpose is what makes people show up the first time. Feeling genuinely valued is what makes them show up the second time. The experience of being part of something that is actually working where commitments mean something, where problems get solved instead of hidden, where the work itself feels meaningful is what makes them stay.

The Five Dysfunctions and Radical Candor

Patrick Lencioni’s Five Dysfunctions of a Team and Kim Scott’s Radical Candor both point to the same thing from different angles. Lencioni’s model establishes that trust is the foundation and that without it, healthy conflict is impossible, real commitment is unavailable, genuine accountability is resentful rather than productive, and results are left to chance. Scott’s framework adds the operational practice: caring personally while challenging directly. Not one or the other. Both simultaneously.

Caring personally without challenging directly produces the comfortable relationships that feel good and produce nothing. Challenging directly without caring personally produces the adversarial dynamic that the construction industry has normalized and that drives people out. The combination caring personally and challenging directly is what produces the radical candor that makes teams genuinely better over time.

The construction industry has more practice with challenging than with caring. The opportunity is not to abandon the challenge. It is to invest in the care that makes the challenge land the way it is intended as investment in the person rather than as judgment of them.

Here are the signals that a construction organization is building intentional culture rather than tolerating default culture:

People surface problems before they become crises because they trust that honesty is welcomed.
Workers can describe why they show up, not just the paycheck, but what the work means to them.
Leaders acknowledge when they are wrong in front of the people they lead.
New workers are onboarded into the culture deliberately, with someone whose explicit job is to make them feel they belong.
The team can have disagreements without the relationship becoming collateral damage.

The Construction Industry’s Discomfort Is the Work

The discomfort that these four words — love, care, compassion, people produce in many construction professionals is not a sign that they do not belong in construction. It is the sign that they are exactly what the construction culture needs most. The discomfort is the gap between where the culture is and where it needs to go. And the willingness to have the uncomfortable conversation, to name the four words out loud, to design the culture deliberately that is the work.

Not every person will be ready for that conversation at the same speed. Some will move faster. Some will need more time to process new relational environments. That variability is not a problem, it is a feature of any diverse human system. What matters is that the team keeps showing up, keeps building the conditions, and keeps extending the invitation to everyone who is willing to receive it without leaving behind those who need more time to get there.

At Elevate Construction, the mission is to build remarkable people who build remarkable things. The sequence is always people first. The things follow. If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow. The culture calculation: Love + Care + Compassion + People. Not soft. Not secondary. Foundational.

On we go.

Frequently Asked Questions

Why are love, care, compassion, and people described as practical construction tools?

Because they are the conditions under which every other Lean practice, pull planning, Last Planner commitments, root cause analysis, worker huddles functions as designed rather than as performed. Without them, the tools produce compliance. With them, the tools produce genuine improvement.

What does “if you are not intentional about your culture, you are being intentional about it” mean?

It means that culture develops whether you design it or not. The absence of intentional culture design is itself a design decision, one that defaults to whatever the most powerful behaviors in the environment produce. Intentional design produces a culture that serves the people in it. Default produces whatever emerges from unexamined habits and tolerances.

Why does the construction industry have more than one million open jobs?

Largely because the culture has historically communicated to workers that they do not matter through poor conditions, inadequate communication, and a failure to connect people to the meaning of their work. Workers leave environments where they do not feel valued. Addressing the culture addresses the workforce pipeline.

What is the connection between Lencioni’s Five Dysfunctions and this culture framework?

Lencioni’s model establishes that trust is the foundation of every team capability above it, conflict, commitment, accountability, results. The VTCA framework (Vulnerability, Trust, Conditions, Affirmations) operationalizes how trust is actually built in real teams, through the practices of showing up, leading with vulnerability, listening deeply, and affirming the impact of others.

Why is discomfort with these four words a sign that they are necessary rather than inappropriate?

Because discomfort points to the gap between where the culture is and where it needs to go. A culture that finds love, care, and compassion genuinely comfortable is already practicing them. The discomfort is diagnostic, it reveals what has not yet been normalized but needs to be.

If you want to learn more we have:

Discover Jason’s Expertise:

On we go

General Offerings

Company Offerings

Systems

Subscribe Now !

Sign Up & Start Learning

The Foundation of Construction Excellence

© 2026 elevate constructionist LLC. All Rights Reserved. |

SUBSCRIBE NOW !

Subscribe to our newsletters and stay updated!

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

CURRICULUM & OUTCOMES

LOGISTICS & FORMAT

PRICING & VALUE

SEO-BASED / HIGH-INTENT SEARCH QUESTIONS