Seamless Project Teams: What Happens When We Stop Managing Contracts and Start Managing Relationships?
Beyond Clause 10Show Notes
EPISODE 3: Seamless Project Teams: What Happens When We Stop Managing Contracts and Start Managing Relationships?
Why do some NEC4 projects become highly aligned,high-performing delivery environments… while others descend into mistrust, defensiveness and process-driven conflict despite operating under the same contract? Perhaps the difference has less to do with the contractitself — and more to do with the quality of the relationships surrounding it.
SUMMARY In Episode 3 of Beyond Clause 10, Dom and Jon explore one ofthe most difficult and important questions in project delivery: What does it actually take to build seamless project teams under real commercial pressure? The discussion examines the fragile relationship between trust, competence, communication and accountability — and why Clause 10 can sometimes become weaponised rather than lived. Moving beyond contractual process, the episode explores psychological safety, productive conflict, leadership behaviours and the importance of deliberately designing project cultures that can withstand pressure without collapsing into adversarial behaviour. The conversation also introduces practical ideas around behavioural onboarding, collaborative leadership and selecting teams not only for technical competence — but for their ability to work constructively together.
INTRODUCING THE DISCUSSION Drawing on experience from live project environments, Dom and Jon challenge the assumption that collaboration naturally emerges once a contract is signed. Instead, they explore: • why relationships require active management, • how behaviours influence outcomes more than process alone, • why seamless teams must be intentionally designed, • and what happens when project teams prioritise solving problems rather than defending positions. The episode bridges NEC4 principles with wider behaviour and organisational thinking — including psychological safety and the Lencioni Five Behaviours model.
IN THIS EPISODE WE EXPLORE • Why Clause 10 can become weaponised in practice • The difference between process management and relationship management • Psychological safety and productive conflict • Trust as both behavioural and competence-based • The “operating theatre” analogy for project delivery • The Maister trust equation • Why some teams solve problems while others defend positions • Collaborative onboarding and behavioural alignment • Procurement as the first stage of team-building • The concept of a Collaborative Project Leader
REFERENCES AND THEMES • NEC4 Clause 10 • Lencioni Five Behaviours • Psychological safety • David Maister trust equation • Construction Playbook principles • Collaborative frameworks and alliancing • Behavioural leadership in project environments
REFLECTION The industry invests enormous effort into drafting contracts, defining scope and allocating risk. Yet comparatively little time is spent designing the relationships required to make those systems function under pressure. Perhaps seamless teams are not created through aspirational one. Perhaps they are built deliberately — through trust, clarity, accountability and continuous behavioural discipline.
More from Beyond Clause 10
EPISODE 4: Has the Industry Really Changed Since Latham, Egan and the Birth of NEC? The industry has spent more than three decades talking about collaboration, integration and better project outcomes. But has construction genuinely changed since Latham, Egan and the emergence of NEC — or have many of the same pressures, behaviours and commercial instincts simply evolved into new forms?
EPISODE 2 - Risk Intelligence vs Risk Transfer: The Procurement Choices That Decide Project Outcomes What if the biggest threat to collaboration is already embedded into the project before delivery even begins? In this episode, Dom and Jon explore how procurementstrategy, legal positioning and risk allocation often shape behaviours long before the first spade hits the ground.
EPISODE 1 - MUTUAL TRUST AND COOPERATION: WHY IT'S EASIER SAID THAN DONE The industry has spent decades talking about collaboration. So why do suspicion, defensiveness and adversarial behaviours still appear so quickly once projects come under pressure? Have we genuinely changed the culture of project delivery…or simply changed the language around it?
BEYOND CLAUSE 10 INTRODUCTION Everyone talks about collaboration in construction and infrastructure delivery. But when programme slips, commercial pressure tightens, risks materialise and interface tensions arise— why do so many projects still fall back into adversarial behaviour? And if NEC4 Clause 10 is intended to underpin mutual trust and cooperation… why can it remain so difficult to make real in practice?