Everything so far has been the case and the craft. This is the plan. It starts exactly where we are — with the small changes we're already carrying and disputing — and builds, deliberately, toward leading the organisational change that makes all of it cohere. The roadmap begins in one place: our own plan around the Change quadrant.
The Change quadrant of our partnering model is where the connected picture lives. So that's the first move — not more strategy, but a clear, honest inventory of the change we're already handling, joined up for the first time.
You can't lead a picture you can't see. Before we plan twelve months ahead, we make the present visible: every small change, its status, and what's tangled in dispute.
Lay them all out — every roster shift, location move and hours change — and mark honestly which are quietly proceeding and which are stuck in dispute. This is the raw material of the roadmap. (Illustrative below; the real version is ours to populate together.)
Seen together, a pattern jumps out: the disputed items aren't random. They're the small, disconnected changes we pushed up on their own — exactly as Part 1 warned. The map isn't just an inventory. It's a diagnosis.
Here's where Part 3's craft meets the map. When a roster change is "in dispute," that's the industrial surface. Underneath is an individual who hasn't moved through ADKAR. Diagnose the missing block and the real problem shows itself.
The instinct is to treat it as an industrial problem — argue the clause, prepare for the Tribunal. But run it through ADKAR and the truth surfaces: this was never an industrial problem. It's an awareness-and-desire problem wearing an industrial costume.
A missing block is never just a gap in a model — it's a person feeling something. We spend so much time strategising change that we forget to connect with how it feels. So before we plan the next move, we look underneath.
Whatever the change is on paper, what matters is what it represents to the leader, the team and — above all — each individual. When someone resists, they're rarely arguing about the roster. They're protecting something deeper. It almost always lives in one of three places.
The agency question. When change is decided about people without them, what they lose is control. Much "resistance" is really someone reclaiming a say in their own working life.
The belonging question. Change disrupts the felt sense of being looked after. Underneath the dispute is often: is anyone protecting me through this?
The dignity question. So much resistance is a person defending their worth. When change feels like it erases their contribution, they push back to be seen.
Run the disputed roster change through these and it deepens: the missing Awareness and Desire weren't just unprovided information — they landed as a Power & Control wound ("my priorities didn't count") and a Respect one ("no one valued what this does to my life"). Fix what it represents, not just what it says, and the change finally has somewhere to land.
This is the strategic heart of the roadmap. Fighting each small change on its own is a losing game — Part 1 showed why. The way out is to flip the direction entirely.
A roster change arrives with no context. We take it to the workforce and unions on its own merits. With no bigger story to anchor it, there's nothing to say yes to — so it's disputed.
Repeat for every fragment. We exhaust ourselves and never reach the strategic change underneath.
Lead the culture and leadership change first — the compelling "where we're going and why." Now each small change is a visible step toward something people understand.
The roster change isn't an isolated ask anymore. It's part of the story. The big change becomes the anchor that lands the small ones.
Culture and leadership aren't the last thing we get to — they're the engine that makes everything else land. Drive the why from the top, and the small changes stop being battles and start being chapters.
Honest and sequenced. Heavy on visibility and the floor early — because that's where we are — building toward the organisational change that anchors the rest. We start now.
This change pack doesn't stand alone. It's one of three threads we've been weaving, and the roadmap is where they converge into a single way of working — not three competing initiatives.
Operations, Engagement, Outcomes and Change — how we partner across the organisation. Change leadership is the 4th frame, and the discipline that powers the move into all four. Revisit the journey →
The craft of leading people from today to tomorrow — the floor, the practitioner's tools, and this roadmap. It's how the partnering shift, and every change beneath it, actually lands.
AI woven through it all — mapping change and resistance, drafting narratives and comms, freeing our time for the human work. The force-multiplier on both threads above. Explore the augmented function →
The Partnership tells us what to do. The Change Leader tells us how to make it real. The Augmented function helps us do it faster and at scale. One practice, three threads.
No grand launch required. The roadmap starts with small, concrete acts — most of them firmly in "see it," where we should be.
One page, the Change quadrant, every change we're carrying. Even half-finished, it's more than we have today.
Run it through ADKAR as a team. Find the missing block. Prove to ourselves the diagnosis works.
Draft, roughly, the "where we're going and why" these small changes belong to. The anchor starts as a sentence.
Use it to structure the inventory, map likely resistance and draft the first narrative — then bring our judgement.
We began by losing small battles. We end with a plan to stop fighting them — by connecting the picture, standing firmly on the floor, practising the craft, and driving the organisational change that makes every small change make sense.
See it. Steady it. Lead it. Embed it. That's how we turn change from the thing that exhausts us into the thing we're known for.
Back to Part 3 · The Practitioner of Change