Two movements have made the case: HR freed and lifted, leaders enabled and confident. But a case is not a change. The hardest part remains — actually leading the shift, inside the function and then across the organisation, without recreating the very dependency the whole effort set out to break.
It is tempting, having made the argument, to treat the rest as logistics — pick a tool, run a project, declare a transformation. That instinct is exactly how good intentions become shelfware. The change this series describes is not an event to be launched. It is a capability to be grown, deliberately, over time.
And it carries a particular danger the earlier parts have earned the right to name: a change effort designed to break a dependency can quietly build a new one — on a consultant, a platform, a permanent “transformation team.” Part III is about leading the change so it makes itself unnecessary.
How an organisation pictures the change determines how it behaves. Picture an event, and you get a big bang, a deadline, and a let-down. Picture a journey, and you get momentum, learning, and value at every step.
This is not a one-day journey, and pretending otherwise is the first failure. Deliver value along the way — so the effort earns its own support, step by step, rather than asking for faith in a distant payoff.
Having spent two movements taking apart an arrangement that no longer serves, we would be foolish not to watch for its return in new clothing. These are the traps that catch well-run transformations — and the ones Part III is built to avoid.
External help that designs, builds and runs the change — and quietly becomes as indispensable as HR once was. Capability is rented, never owned. When they leave, it leaves with them.
A shiny new system that promises everything, locks in your data and process, and makes you captive to its roadmap and its price. The dependency simply moves from a person to a licence.
A change function that, having justified its existence, finds reasons to continue indefinitely — becoming the new bottleneck everything routes through. The rescue role, reincarnated.
Everything in Part III follows from one test, applied to every decision: does this build capability that stays, or a dependence that lingers? Use consultants to leave skill behind, not to own the work. Choose tools that augment where the work already happens, not platforms that take you captive. Run the change through people who hand it back, not a team that holds it forever.
This is simply the case of the whole series, turned on the change effort itself. We freed HR so it could let go. We enabled leaders so they could stand alone. The change must do the same — stand up the capability, then step back.
Done this way, success has a clear and unusual signature: the moment you can no longer point to “the transformation,” because it has dissolved into simply how the organisation works.
From roadmap to delivery model to tooling to what good looks like — each move applies the same principle: grow capability, avoid new traps, deliver value along the way.
Not a one-day trip and not a big bang. A sequenced path — HR first, then the organisation — that banks value at every step, keeps investment proportionate, and is built from the start to avoid creating new dependency traps.
Who does the work — and how to use external help to leave skill behind rather than become the next thing you can’t live without. The honest question every change must ask of its own delivery model.
Tool-agnostic and pragmatic: a sensible early on-ramp through the systems you already own, how to layer onto expensive legacy rather than rip-and-replace, and how to weigh enterprise off-the-shelf without buying captivity.
The signature of success, how to know it’s working, and the horizon beyond. A close not just for Part III, but for the whole arc — back to where it began.
A strategic discussion series making the psychological and strategic case for AI augmentation in HR. If it landed for you, the next conversation is about your function.
Start the conversation →