This is not a one-day trip and not a big bang. It is a deliberate, sequenced path — HR first, then the organisation — where every stage banks real value before the next begins. Investment stays proportionate, momentum compounds, and the whole thing is built from the start to avoid creating new dependencies.
The overture set the principle: design the change to make itself unnecessary. The roadmap is where that principle meets the calendar.
Before any stage plan, one ordering decision shapes everything: you cannot enable leaders from a function still stretched and bound to rescuing. Change HR first; then change the organisation. Two horizons of one journey — never two competing projects.
Build the function's own AI fluency, capacity and confidence. Let practitioners personally feel the lift — so they become advocates, not resisters, and can finally afford to release the rescue role.
Extend structured support to leaders — toolkit, policy on tap, a place to prepare, clean escalation — with HR as architect and guardian. Confidence replaces dependence, at scale.
Click through the stages. Each shows what you actually do, the value banked on the way, and the dependency-trap guardrail for that step. The recognised change methods (Kotter's sequence) carry the structure; your context carries the content.
Every exec asks what it costs. The honest answer at this stage isn't a number — it's a set of principles that keep the investment proportionate, self-justifying, and free of the captivity traps. Get these right and the spend stays sane.
Spend small to prove it in HR; scale spend only as value is demonstrated. Investment follows evidence, never precedes it.
The earliest wins should run on tools and licences you already pay for — not a new platform. The cheapest on-ramp is the one already on people's desks.
Favour spend that leaves skill and ownership behind. Be wary of anything whose cost recurs forever because you can't run it yourself.
Hours reclaimed, faster decisions, fewer escalations, better records, reduced risk. The value shows up early — which is the point of delivering along the way.
Specific numbers belong in your own business case, staged to your context. The discipline here is the principle: proportionate, evidence-led, and free of recurring captivity. The detail of who and what you spend on is the subject of Parts 3·B and 3·C.
The overture named three traps a change like this can fall into. The roadmap answers each one structurally — not as a footnote, but as a design rule baked into how the journey runs.
The roadmap is led by your own people from Stage 1. External help advises; it never owns.
Early stages run on tools you already own. No big platform purchase before value is proven.
Stage 5 winds the scaffolding down on purpose. Ownership moves to the line and to HR-as-guardian.
A roadmap is only as good as the questions it keeps asking of itself. Two tests keep this one honest from the first stage to the last.
Every stage must bank something real before the next begins — reclaimed hours, faster decisions, better records, reduced risk. If a stage only “sets up” a future payoff, it's a risk, not a milestone. Value along the way is how the journey earns its own support, and how you keep the option to pause or stop without having lost anything.
Every stage must leave the organisation more able to carry the change alone, not less. Skill in your people, ownership in the line, content and guardrails held by HR. If a stage deepens reliance on an outsider or a platform, it has failed the series' founding test — and quietly rebuilt the very thing the whole effort exists to break.
A roadmap that pays as it goes and builds what stays can be paused, questioned, or proven at any step — because it never bet everything on a distant finish line.
That is what makes it safe to begin: not a leap of faith, but a series of small, value-bearing steps, each one leaving the organisation more capable of carrying the next alone.
The roadmap names the stages. Next: who actually does the work — and the honest question of whether external help builds your capability or quietly becomes the next dependency you can't live without.