A Simple Framework for Putting Integrated Project Delivery (IPD) Into Action

The Lean Project Delivery System: A Complete Operating Framework

Integrated Project Delivery begins with a contract that aligns the financial interests of all project participants around shared success. But aligning incentives does not automatically produce an efficient team. It produces a team with a reason to be efficient which is necessary but not sufficient. To actually perform at the level the IPD model promises, the team needs a way of working that removes traditional silos, speeds up communication, reduces rework, and enables continuous improvement across the full life of the project.

That way of working is the Lean Operating System. It is the operational layer between the contract structure and the project outcomes, the specific practices, tools, and processes that transform a financially aligned team into a high-performing one. Without it, teams find that IPD contracts produce collaboration in principle and traditional dysfunction in practice. With it, the contract’s potential becomes the project’s reality.

The Lean Operating System for IPD operates across three domains: defining and documenting customer value, creating that value through streamlined processes, and improving those processes continuously through deliberate feedback cycles.

Defining Customer Value

The first domain begins before the design begins. IPD teams are brought into the project at the earliest stages often before the owner’s business case is finalized precisely because understanding why the project exists before developing conceptual designs gives the team the freedom to explore diverse options for delivering value. That early engagement produces the validation study: a collaborative report that captures the final business case, budget, schedule, and program. It is the shared foundation from which all subsequent decisions are made.

Set-based design extends this principle into the design process itself. Traditional design practice pushes teams toward early decisions selecting a structural system, committing to a mechanical approach, choosing a cladding type before enough information exists to make those decisions well. Set-based design takes the opposite approach: advance multiple design alternatives into further development stages simultaneously, and make the final decision when enough information has been generated to make it confidently. By continuing to advance multiple sets rather than committing to one early, the team makes better decisions and eliminates the costly negative iterations that occur when a prematurely selected option turns out to be unviable.

A3 thinking provides the structured process for documenting problems, exploring options, proposing solutions, and committing to action plans in a collaborative, visible, single-page format. The discipline of the A3 is not the document itself, it is the collaborative process of reaching consensus first on the problem statement before moving to solutions. Teams that cannot agree on what the problem is will not produce solutions that actually resolve it.

Choosing by Advantages provides the decision-making framework for situations where a large group of people with differing goals and values must reach a shared decision. By focusing on the advantages of each option rather than on a pros-and-cons comparison, CBA removes the defensive dynamic that conventional option evaluation produces and makes the cost-versus-advantage trade-offs transparent to everyone in the room simultaneously.

Streamlined Processes for Efficient Value Creation

The second domain is where the work gets done and where traditional operating systems generate the most waste. On conventional projects, communication flows through a chain of intermediaries, accountability is diffuse, and the physical and organizational separation of design and construction creates constant friction at their intersection. IPD teams using a Lean operating system replace those structures with direct collaboration, shared information systems, and the planning discipline that makes commitments reliable.

The Last Planner System manages the team’s activities from early feasibility studies through construction and commissioning. High-level milestones are established first. Phase pull plans are developed as each phase approaches, with all participants collaboratively building the sequence from the final condition required backward to the starting point. Look-ahead planning identifies and removes constraints six or more weeks ahead of execution. Weekly work planning converts readiness into specific commitments. And learning measured through percent plan complete and variance analysis closes the loop between what was promised and what was actually accomplished.

Co-location is the physical infrastructure that makes collaboration possible at the speed and depth that IPD requires. When the owner, designers, and builders share a single office environment, five to fifteen or more companies working in the same space, the communication that would otherwise travel through formal channels and wait in queues happens in real time, face to face, across the room. Smaller projects that cannot sustain full co-location develop compressed collaborative working sessions or digital collaboration platforms that replicate as much of the co-location benefit as the project context allows.

Building information modeling, used to the level of detail the project actually requires, supports coordination, prefabrication, scheduling, cost estimating, and facilities management. The key is that the decision about which BIM elements to develop is made collaboratively by the owner, designers, and builders based on desired outcomes, not defaulted to a standard level of detail that may over-produce in some areas and under-deliver in others.

Information management closes the loop on the information flow itself. With an integrated team working at high speed, the flow and control of project information can still become wasteful if it is not deliberately designed. IPD teams establish a central point of storage for each type of project information, using cloud-based platforms with systematic naming structures, and document the processes for using and sharing information so that every team member can access what they need without creating parallel or competing records.

Here are the signals that a Lean operating system is functioning correctly within an IPD project:

• Phase pull plans were built by the people who will execute them, with genuine trade partner input into the sequence.
• The make-ready look-ahead is actively removing constraints six weeks ahead of execution, not just documenting them.
• A3s are used for significant decisions, and consensus on the problem statement precedes development of solutions.
• BIM use is calibrated to outcomes the team defined collaboratively, not to a default standard.
• Project information lives in one accessible system that everyone uses not in individual email chains and personal folders.

Continuous Improvement Through Deliberate Feedback

The third domain is the feedback system that allows the team to improve its processes across the life of the project rather than repeating the same mistakes. High-performing IPD teams are self-aware of their processes and the places where those processes break down and they create structured opportunities to reflect and improve rather than accepting the breakdowns as the nature of complex projects.

PDCA, plan, do, check, adjust is the core improvement cycle. A process is implemented with an expected outcome. Actual outcomes are measured against expectations. The drivers of variance are identified through root cause analysis. And countermeasures are integrated into the revised process before the next cycle begins. The cycle is continuous; there is no point at which the team declares its processes optimized and stops checking.

The 5 Whys provides the root cause analysis tool that prevents the team from treating symptoms rather than causes. When a deviation from the expected outcome occurs, asking why five times each time drilling one level deeper into the causal chain drives the analysis from the visible symptom to the underlying system condition that produced it. Changing that condition prevents recurrence. Addressing only the symptom allows the same condition to produce the same result again.

Plus/Delta provides the lightweight, daily-practice version of the improvement cycle. At the end of each meeting and significant event, the team takes five minutes to identify what went well and should be repeated, and what did not go well and should be changed. Each delta is assigned to a specific person with an action plan and a commitment date. Over the life of a project, this practice compounds, each iteration of the process is slightly better than the previous one, and the cumulative improvement over a multi-year IPD project is substantial.

The Operating System Is Not the Culture

The Lean operating system provides the processes and tools. It does not provide the culture that makes those processes real rather than performative. A team can run pull planning sessions, maintain a make-ready log, and hold plus/delta meetings without any of those practices producing genuine improvement, if the culture does not support honest communication, genuine vulnerability, and the willingness to surface problems rather than manage appearances.

This is why IPD is described as a three-part system: the contract aligns incentives, the Lean operating system provides the processes, and the culture determines whether both actually function as designed. All three are necessary. None is sufficient alone.

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

Align the team. Design the operating system. Build the culture. In that order, all three together.

On we go.

Frequently Asked Questions

What is a Lean Operating System in the context of IPD?

It is the set of practices, tools, and processes that transform a financially aligned IPD team into a high-performing one covering how customer value is defined, how work is planned and executed efficiently, and how the team improves its processes continuously across the project life.

What is set-based design and why does it reduce rework?

Set-based design advances multiple design alternatives simultaneously into further development before committing to one. By making final decisions with more information, the team avoids the negative iterations that occur when a prematurely selected option turns out to be unviable.

Why is co-location important for IPD performance?

Because it replaces the formal, queued communication channels of traditional project delivery with real-time, face-to-face collaboration. The speed and depth of coordination that IPD requires is very difficult to sustain across organizational and physical distance.

How does Plus/Delta function as a continuous improvement tool?

By creating a five-minute structured reflection at the end of every meeting identifying what worked and should be repeated, and what did not work and should change with specific ownership and commitment dates for each delta. Over a multi-year project, this practice produces substantial cumulative process improvement.

Why is the Lean operating system not sufficient on its own to make IPD work?

Because processes and tools produce genuine improvement only when the culture supports honest communication, problem surfacing, and collaborative reflection. Without the cultural foundation, Lean operating system practices become compliance exercises rather than genuine improvement mechanisms.