How to Develop a Collaborative Culture on Every Project with James Pease

When I interviewed James Pease about integrated project delivery, he made an important correction: a collaborative contract does not automatically create a collaborative team. The structure mattered, but the culture still had to be built.

Shared risk only helps if the team works like a team

James traced the owner's move toward collaboration to repeated delays, budget trouble, and the need for earlier builder involvement. He also described one agreement with shared risk and reward as part of that shift. What the agreement could not do by itself was teach the team how to make reliable commitments or surface issues early.

You are hiring people, not logos

James put the selection problem plainly: "We're not really hiring companies." He added, "We're hiring people." That means a respected firm can still send the wrong team for a highly collaborative job.

Culture needs a deliberate start

His strongest operating lesson was just as direct: culture has to be built at the beginning of the job. Every project brings a different group together, so expectations around planning, commitments, voice, and issue escalation have to be rebuilt on purpose. Shared risk and reward help, but early behavior proves whether the team really plans to sink or swim together.