The answer lives in this podcast

Answer extracted from the Beyond The Plan podcast — listen to the full episode below.

🎧 Listen to the episode on Listenly

Why must collaborative working culture be designed to be enduring beyond individual relationships?

September 7, 2026 Beyond The Plan · Brett Ackroyd

← See the Beyond The Plan fiche

Collaborative culture must be embedded in processes and shared values rather than depending on specific individuals, because personal relationships are inherently fragile—they shift when people move roles, projects change phase, or new stakeholders enter the work. When relationship management becomes structural, collaboration survives these inevitable transitions.

The fragility of relationship-based collaboration becomes apparent in complex, multi-year projects. When trust exists only between two people—say, a project manager and a vendor account lead—what happens the moment one of them leaves or rotates to a different assignment? The institutional knowledge of how decisions are really made, what behaviors are expected, and how conflicts get resolved walks out the door with them.

This is why Brett Ackroyd discusses the ISO 44001 framework, which codifies collaborative behaviors and relationship management into organizational systems. Rather than relying on personalities to drive collaboration, elite delivery teams make collaboration predictable. The values—trust, transparency, mutual accountability—become documented principles that new team members inherit the moment they join, regardless of who they're replacing.

Building collaboration into the operating system, not just the people

The real work lies in examining your processes and systems to see whether they actually support the collaborative behaviors you claim to value. A team might say it believes in transparency, but if the contract structure encourages each party to hoard information for leverage in disputes, transparency will fail the moment pressure arrives.

When you design collaboration into roles, approval workflows, risk-sharing mechanisms, and reporting cadences, it survives the personnel churn that is inevitable in long-running infrastructure and government projects. A new commercial manager arriving mid-project can immediately see how decisions flow, how conflicts are escalated, and what behaviors are non-negotiable—because these are embedded in the system, not hidden in the relationships of their predecessors.

"You will know a collaborative culture exists when one party will take it on themselves to actually act to their detriment for the other party, because that allows for the achievement of the overall outcome."

That definition points to the depth required: true collaboration isn't just politeness or regular meetings. It's a structural setup where each party accepts short-term costs for long-term collective gain—and that only happens when the system makes such behavior the path of least resistance, not a heroic choice dependent on individual goodwill.

As Ackroyd explains in this episode, the moment a key relationship owner leaves a project, the entire foundation shouldn't crack. The values, the escalation paths, the problem-solving routines—all of it should remain intact for whoever arrives next. That's endurance. That's institutional resilience.

See also