Leaders Take a Systems Thinking Perspective for Making Change

Systems Thinking in Lean Construction: The Missing Piece That Explains Why Lean Stalls

In 2020, Jeffrey Liker revised the first of Toyota’s fourteen management principles for the second edition of The Toyota Way. The revision was small in word count and significant in implication. The principle now reads: base your management decisions on long-term systems thinking. That addition was not a minor update. It was Liker’s acknowledgment of something that had been embedded in Toyota’s practice since the 1950s but had never been made fully explicit: the entire Toyota Production System is built on a view of organizations as open systems, and you cannot successfully implement any part of it without understanding the system in which the implementation is happening.

This is the missing piece that explains why so many Lean construction implementations stall. The tools are not the problem. The tools are straightforward. The problem is that the tools are being added to a system that was not designed to accommodate them, and the system left unchanged pushes back until the new practice is abandoned and the old one resumes.

What a System Actually Is

When the word system is used in this context, it does not mean software, mechanical systems, or continuous industrial processes. It means an open system, one where people are actors affecting the behavior and performance of the system through their decisions, habits, policies, expectations, and mental models. Economies are open systems. Workgroups are open systems. Construction projects are open systems. Companies are open systems. The actors inside the system both shape the system and are shaped by it.

Two insights from the study of systems are particularly important for anyone trying to change how a construction organization or project team operates.

The first is the iceberg effect. The events visible above the waterline, the missed milestone, the failed pull plan session, the superintendent reverting to directive scheduling are produced by what lies below: patterns of behavior that repeat, structural conditions that reinforce those patterns, and the mental models that make those structures feel normal and inevitable. Responding only to the visible events without examining the patterns, structures, and mental models underneath them is what produces the feeling of addressing the same problems over and over without making progress. The root cause is always below the waterline.

The second is that seemingly unrelated acts are connected through flows of resources and reinforcing loops. Learning the basics of a subject creates the capacity for learning more advanced aspects, a reinforcing loop. But the time available for learning competes with the demands of ongoing work, a counteracting flow. When the competing demands win, the stock of learning capacity decreases and the reinforcing loop weakens. Understanding these dynamics explains why Lean learning in organizations so often loses to the urgency of daily project work, and it points toward the intervention needed: reducing the competing demands rather than simply asking people to do more.

Why Lean Practices Stall After Implementation

The existing practices on any project or in any organization are not random. They are coherent with each other. The prescriptive scheduling practices are matched to the performance metrics. The performance metrics are matched to the expectations of stakeholders. The expectations are matched to the mental models of what good project management looks like. This coherence is what makes the system stable and what makes it resistant to introducing new practices without adjusting the system as a whole.

When collaborative pull planning is introduced alongside prescriptive CPM scheduling, the two practices are in conflict. One requires trade partners to declare their own activities and commitments collaboratively. The other requires compliance with a sequence determined upstream. Trying to run both simultaneously does not produce a hybrid benefit, it produces a destabilized system where neither practice works well and the team eventually defaults to whichever practice has stronger institutional support, which is almost always the familiar one.

The Lean leaders who succeed at implementing Lean practices understand this dynamic and work with it rather than against it. They recognize that adding a new practice requires adjusting the surrounding system stopping some things, starting others, continuing what remains consistent. Three questions make this systematic:

What will we start doing? What will we stop doing? What will we continue doing?

These questions apply to processes and to leadership style simultaneously. The superintendent who wants collaborative pull planning to succeed must also shift from directive leadership to facilitative leadership not as a personality change, but as a deliberate adjustment to the role the superintendent plays in the planning meeting. The pull plan session facilitated by a superintendent who is used to giving direction will not produce the same result as one facilitated by a superintendent who brings questions rather than answers and creates the conditions for the foremen to think through the sequence together. The practice and the leadership style must adjust together for either one to work.

Delay as an Enemy of System Stability

One of the most direct applications of systems thinking to Last Planner practice is the timing of the daily stand-up or huddle. The purpose of the daily commitment management meeting is to manage promises among project participants to give each trade partner’s foreman the opportunity to report on the completeness of their commitments, make new ones, ask for help, and offer help, all in service of the team’s larger commitment to the phase milestone.

The systems thinking argument for holding that meeting at the end of the day rather than the beginning is straightforward: the more delay you have in a feedback loop, the less able you are to steer the system. If a commitment from yesterday was not met, waiting until tomorrow morning to communicate that variation creates an entire night of unnecessary urgency accumulation. Trades who need to adjust their plan, materials that need to be restaged, sequences that need to be reorganized, all of those adjustments can happen more smoothly and at lower cost if the information travels at end of day rather than at the start of the next morning.

This is not a minor scheduling preference. It is a systems principle: timely feedback enables steering. Delayed feedback undermines it. Making feedback timely, prompt notice of variation to plans, deliveries, quality outcomes, and staff availability is one of the highest-leverage adjustments a project team can make to the system of how it manages its commitments.

If a morning huddle is also needed to address site safety, crane time limitations, or material deliveries, there is nothing preventing one. And the morning huddle should communicate what actions are being taken in response to the variation that occurred yesterday which the end-of-day commitment review has already surfaced and processed.

Here are the warning signs that a project team is adding Lean practices without adjusting the surrounding system:

• CPM scheduling and pull planning are running simultaneously with no deliberate decision about which governs production planning.
• Leadership style in planning meetings has not changed, so collaborative tools are producing directive outcomes.
• New Lean practices are added to an already full agenda without stopping anything that the new practices are designed to replace.
• Variation in commitments is communicated at the next morning’s meeting rather than at end of day when the variation occurred.
• The team reports that Lean is adding work rather than reducing it, a sign that the system has not been adjusted to accommodate the new practices.

Connecting to the Mission

At Elevate Construction, the integrated production control system, First Planner, Takt, Last Planner is designed as a coherent whole precisely because individual tools added to a non-Lean system produce the stalling described above. The system is designed together so that each component reinforces rather than conflicts with the others. The Takt plan informs the pull plan. The pull plan informs the look-ahead. The look-ahead informs the weekly work plan. The weekly work plan informs the day plan. The day plan is communicated in the morning huddle. And the end-of-day commitment review provides the feedback that steers the next day’s execution. Nothing in that chain is optional because removing any link destabilizes the whole. If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow.

Systems thinking is not an academic exercise. It is the lens that explains why the tools work when the system is right and fail when it is not and it is the lens that guides the adjustments that make the system right.

On we go.

Frequently Asked Questions

What is an open system and why does it matter for Lean construction?

An open system is one where people are actors who affect the system’s behavior through their decisions, habits, policies, and mental models. Construction projects and organizations are open systems which means Lean practices must be implemented with attention to the system conditions they are entering, not just to the practices themselves.

Why does adding a new Lean practice without stopping old practices create conflict?

Because existing practices are coherent with existing policies, metrics, and expectations. Adding a new practice destabilizes that coherence without creating a new equilibrium. The system pushes back until the new practice is abandoned unless the surrounding system is deliberately adjusted at the same time.

What are the three questions for adjusting a system when introducing new Lean practices?

What will we start doing? What will we stop doing? What will we continue doing? These questions ensure that new practices replace rather than add to the existing system, which is what prevents Lean from becoming an additional burden.

Why should commitment management stand-ups happen at end of day rather than the start of the next day?

Because the more delay in a feedback loop, the less able the team is to steer the system. End-of-day reporting of variation gives the team time to adjust before the next day’s work begins, rather than discovering the variation at the moment it affects the next crew’s ability to start.

What is the iceberg effect in systems thinking?

The visible events above the waterline, the missed commitment, the failed implementation are produced by patterns, structural conditions, and mental models that lie below. Addressing only the visible event without examining what produced it is what generates recurring problems.