Culture Matters in Design and Construction

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.