Case Study #2: From Resistance to Ripple Effect: How One Bold Experiment Won Over an Entire Partnership Network

What do you do when your biggest partner is your biggest blocker?

That was the challenge during the mobilisation phase of a high-stakes infrastructure program.

With just 30 days to go live, we were tasked with establishing a 24/7 help centre to manage real-time service issues across more than 50+ active construction sites.

The function was critical, acting as a central coordination point to triage issues, support frontline teams and protect delivery outcomes during a complex, round-the-clock build.

The Challenge

Despite the operational need, private sector partners were hesitant to engage.

Concerns were valid around visibility, performance scrutiny and how information would be interpreted without context.

Trust was limited. Time was constrained. And alignment was essential for the model to work.

The Approach

Rather than attempting to secure broad agreement upfront, I focused on the most influential and resistant partner.

The proposition was simple:

Trial the model in a controlled, real-world environment, and assess its value based on outcomes. If it worked, they would support broader adoption across the network.

They agreed.

Working with the Right Expertise

Delivering this within tight timeframes required close collaboration with subject matter experts. I worked directly with the call centre manager and operational leads to:

  • design realistic service scenarios

  • refine triage processes and escalation pathways

  • strengthen frontline capability to respond with clarity and consistency

This was not developed in isolation. It required practical input, operational experience, and rapid real-time iteration to perform under live conditions.

The Turning Point

A controlled “mystery shopper” trial was implemented.

The partner’s team tested the system using real scenarios, without the call centre knowing who was on the line.

While there were initial technical issues, the core service response was strong:

  • issues were triaged effectively

  • responses were clear and actionable

  • frontline teams experienced faster resolution and better support

Most importantly, their crews felt the difference on the ground.

The Outcome

At the next partnership forum, the same partner shifted from critic to advocate.

Their endorsement influenced the broader network.

Adoption followed.
Confidence increased.
And a previously contested model became embedded in delivery.

During peak construction activity, supporting over 120,000 people and their daily movements, the system enabled:

  • faster issue identification and resolution

  • consistent communication across partners

  • real-time visibility of emerging risks

Key Insight

In complex environments, alignment is rarely achieved through process alone. It comes from:

  • working with the right expertise

  • testing in real conditions

  • and enabling influential stakeholders to experience value directly

Progress came from aligning expertise, not working around it.

Why This Matters

Large-scale programs cannot be delivered in isolation, particularly under time pressure.

They rely on:

  • collaboration with subject matter experts

  • trust across delivery partners

  • and shared ownership of solutions

When these elements come together, resistance can shift quickly into alignment, and alignment into momentum.

Previous
Previous

Case Study #1: The Influence Domino: How Aligning One Decision-Maker Unlocked Data Sharing Across Competing Stakeholders

Next
Next

Case Study 3#: Winning Hearts, Minds & $4.9M: How Storytelling Reframed a Politically Stuck Project