What is Integrated Project Delivery Part 2: Lean Operating System

How to Build a High-Performing Construction Team: The IPD Model for Team Development

There is a question worth asking before any construction project begins. What if this project could exceed expectations instead of falling short? What if the building could be beautiful, efficient, useful, cost-effective, and sustainable, all at once, without compromise? What if the systems inside the building operated as a genuinely integrated whole rather than as multiple disparate components that happen to share a roof?

These are not rhetorical questions. They are the design brief that Integrated Project Delivery was developed to fulfill. The traditional delivery model, with its separated disciplines, adversarial contracts, and sequential decision-making, produces a predictable outcome: buildings that arrive late, over budget, and requiring more compromise than the owner anticipated when they began. IPD is the structural and cultural alternative to that outcome and the difference between how the two models work is visible in every element of how the project is organized and managed.

Worlds Apart: Traditional Delivery Versus Integrated Delivery

The American Institute of Architects has documented the differences between traditional and integrated delivery across multiple dimensions, and the contrast is comprehensive. In traditional delivery, decisions are made by whichever party holds them at that moment in the sequential process, the designer decides, then the contractor receives the decision and works with or around it. In integrated delivery, decisions are made as if all participants were employed by a single organization, with the standard being what is best for the project rather than what protects any individual party’s position.

In traditional delivery, leadership belongs to whoever has contractual authority in the relevant domain. In integrated delivery, people trust each other and share in leadership duties which means that the person with the most relevant knowledge leads the decision, regardless of their title or contractual relationship.

In traditional delivery, problems discovered late are typically someone else’s fault and someone else’s problem. In integrated delivery, team members thank each other for discovering problems early because early discovery is exactly what prevents the expensive late-stage conflicts and rework that consume project contingency and erode project scope.

In traditional delivery, new ideas from outside the expected source are often filtered, resisted, or simply not invited. In integrated delivery, team members create space for innovation by listening in dialogue rather than positioning to persuade and new ideas and approaches are welcomed and heard regardless of their origin.

That difference in how the team operates is not a personality difference between the people involved. It is a structural difference in how the project is organized, managed, and incentivized.

The Six Responsibilities of Integrated Project Management

In an IPD agreement, the management structure is defined in the contract itself typically through a Core Group or Project Management Team composed of representatives from the owner, designer, and builder. These leaders are committed to making best-for-project decisions rather than best-for-my-firm decisions. And they carry six specific responsibilities that determine whether the integrated model actually functions.

The first responsibility is developing a clear and common understanding of project values and goals. This is the foundation of the entire IPD project. Not just the owner’s stated program but the full picture of what the project needs to accomplish, what trade-offs are acceptable and which are not, what success looks like across all dimensions of cost, schedule, quality, sustainability, and operational performance. When this foundation is clearly established and genuinely shared by all key stakeholders, every subsequent decision has a reference point. When it is not, every decision reopens the same fundamental questions.

The second responsibility is communicating those values and goals to every participant. Not just the primary signatories, every trade partner, every consultant, every person who will contribute to the design or construction of the building. Leaders must onboard subcontractors and consultants into the project values as genuinely as they onboard the primary design and construction team. And they must reinforce those values continuously, through repetition and recognition, because the noise of daily project work competes with the team’s connection to the shared purpose.

The third responsibility is creating the functional physical and virtual space for co-location. The big room is not just a nice-to-have feature of IPD, it is the physical infrastructure that makes real-time, cross-disciplinary collaboration possible. Digital networks, collaboration systems, and document management platforms must be established before the project starts, not improvised as the project proceeds. The investment in getting this infrastructure right at the outset pays back in every hour the team does not spend hunting for information, waiting for responses, or working from misaligned document versions.

The fourth responsibility is defining project teams and selecting team members with appropriate diversity. IPD teams should be cross-functional with different viewpoints and perspectives and this diversity is not just a values statement. It is a performance strategy. Teams with diverse perspectives have more information to inform the design, and the productive tension between different viewpoints stimulates the creativity that produces genuinely better outcomes. Homogeneous teams converge too quickly on familiar solutions and miss the insights that outsider perspectives provide.

The fifth responsibility is providing training and mentoring throughout the project. This addresses three specific performance issues: the level and coordination of team member effort, the appropriateness of the strategies the team is using for the tasks at hand, and the degree to which the team is actually leveraging all of its members’ knowledge and skills. The third issue is the one most commonly underdeveloped, it is entirely possible for a team to have extraordinary collective knowledge and use only a fraction of it because the processes and culture do not consistently bring that knowledge into the decision-making.

The sixth responsibility is monitoring and adjusting team dynamics on an ongoing basis. Conflicting personalities, imbalanced participation, knowledge hoarding, and the gradual erosion of collaborative norms under project pressure are all predictable challenges in any multi-party team working under sustained load. The leaders of an IPD project do not wait for those dynamics to become crises, they review the team’s strengths and weaknesses regularly and make adjustments before the negative impacts compound.

Here are the signals that an IPD management team is executing its six responsibilities correctly:

• Every trade partner can articulate the project’s values and goals in their own words, not just repeat the owner’s program requirements.
• New team members are onboarded to the project culture within their first week, not left to absorb it gradually through proximity.
• The big room is genuinely used for collaborative work, not primarily for meetings while actual work happens in separate offices.
• The team’s decision-making process actively solicits perspectives from outside the primary disciplines on decisions that affect those disciplines.
• Team dynamics are discussed explicitly and adjustments are made visibly before conflicts escalate.

The Integrated Project Organization in Practice

The description of a truly integrated project organization where decisions are made as if everyone worked for the same company, where trust is genuine rather than contractual, where problems are celebrated when discovered early, and where innovation is welcomed from wherever it comes, sounds aspirational. It is not. It is the operational description of what IPD produces when all three of its components function together: the contract that aligns financial interests, the Lean operating system that provides the tools and processes, and the culture that makes both real.

The management structure is what connects all three. The Core Group that develops and communicates project values, builds the co-location infrastructure, assembles the right teams, provides the training, and monitors and adjusts the dynamics is the governance layer that keeps the contract’s promise from becoming theoretical.

At Elevate Construction, the engagement model for consulting clients reflects this structure. Alignment is not assumed, it is built through a deliberate process of establishing shared goals, defining conditions of satisfaction, and creating the visual management infrastructure that makes everyone’s understanding of the project visible and checkable. Trade partner onboarding is not a paperwork exercise; it is the genuine introduction to the project culture that determines whether the newcomer understands what this project is trying to accomplish and how it operates. If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow.

The question at the beginning of this blog, what if buildings could exceed expectations instead of falling short? has an answer. It requires integrated delivery, managed by leaders who take all six of their responsibilities seriously, every day, from the first conversation through the last commissioning walkthrough.

On we go.

Frequently Asked Questions

What makes integrated project delivery structurally different from traditional delivery?

In traditional delivery, each party optimizes for their own scope and financial position. In IPD, all parties are contractually and culturally aligned to the same outcome, decisions are made as if everyone worked for the same organization, with the standard being what is best for the project.

Why is early problem discovery celebrated in IPD rather than managed defensively?

Because early discovery prevents late-stage rework, change orders, and scope compromise, all of which are far more expensive than the cost of surfacing and resolving the issue early. The IPD structure removes the liability incentive that causes parties to hide problems in traditional delivery.

What does team diversity contribute to IPD performance?

Cross-functional teams with different viewpoints have more information available to inform design decisions, and the tension between diverse perspectives produces the creativity that leads to genuinely better outcomes. Homogeneous teams converge too quickly on familiar solutions.

Why must project values and goals be communicated to every participant, not just primary signatories?

Because every trade partner’s decisions affect the project’s success. A subcontractor who does not understand the project’s values cannot make the trade-offs that serve those values, they can only follow their contract requirements. Genuine integration requires genuine alignment at every level.

What does monitoring and adjusting team dynamics involve in practice?

Regularly reviewing the team’s collaboration patterns, participation balance, and interpersonal dynamics and making visible adjustments before conflicts or imbalances compound into performance problems. It is a leadership discipline, not a one-time team-building event.