Skip to main content

Adoption & change management

RAPID succeeds or fails as a change programme, not a tooling rollout. The risk isn't that the agents underperform — it's that the people asked to work differently quietly don't, or that the people we most need to keep conclude the model has no place for them. This playbook structures adoption on ADKAR — Awareness, Desire, Knowledge, Ability, Reinforcement — with the honest conversations up front.

Awareness — the leadership narrative​

  • One narrative, told by leaders — a single consistent story built on the case for change: why now, what stops, what starts, and what it means for each role. Not seven versions per manager.
  • In person first, then in writing — town halls in the UK and India, then a written version everyone can point to when the corridor version drifts.
  • No spin on the hard part — an Awareness message that dodges the job question kills Desire before it starts.

Desire — handling replacement fear honestly​

  • Name the fear — "does this replace me?" is the question in the room whether or not it's asked. Address it directly, never with euphemism.
  • Answer with the career framework — pair every Desire conversation with the career framework addendum: the typing goes; scope of direction, review authority and capital deposited become the job and the progression currency. That's a real answer, not a slogan.
  • Metrics never rank individuals — say the anti-gaming rule out loud early and repeat it. Nothing feeds fear faster than a dashboard that looks like a league table.

Knowledge — the curriculum​

  • Role-based modules before the new way of working is expected — the training curriculum, foundation first, role modules per person.
  • STOP-first — the first module people take is on real remediation work, so learning happens where mistakes are recoverable.

Ability — supervised practice​

  • A first supervised agent-build for every directing role — real but low-risk work, paired with an experienced director (the squad onboarding pattern, applied to existing staff too).
  • Pairing rotation — experienced directors paired with newcomers until the muscle is real, not certificated.
  • The CoP as the standing help channel — the Community of Practice show-and-tell is where "I'm stuck" gets answered without ceremony.

Reinforcement — making it stick​

  • Champions network, UK + India — a nominated champion per squad in each geography: first-line help, the feedback channel back to the Toolkit Guild, and co-hosts of the CoP.
  • Day-in-the-life stories — a before/after story per role (PO, BA, Senior Dev, Intermediate Dev, Manual Tester, Auto Tester, SME, Support): what Monday looked like then vs now. The most persuasive adoption artefact we can produce, because it's specific and it's ours.
  • Comms cadence through STOP and GO — a regular drumbeat tied to the Stop · Go · Build tracks: what shipped, what was learned, what STOP savings funded. Progress made visible beats progress asserted.
  • Adoption metrics, watched for lagging cohorts — from the metrics platform: module completion, agent-assisted share of PRs, capital-deposit rate. Used to find teams that need help — never to rank them.
Pending — Leadership

Two inputs need Leadership before this plan can run: the signed-off narrative itself (Awareness) and champion nominations — one named champion per squad in each geography (Reinforcement).

Standards referenced: Prosci ADKAR.