D4 · Adoption and Change Management

This domain carries 16% of the mock — roughly 8 of 50 items. It tests the difference between deploying AI and adopting it. The single most common enterprise-AI failure is not technical: it is licences bought, announced, and left unused. This domain covers adoption curves, champion networks, use-case libraries, incentives, the decisive role of first-line managers, and the communication that turns “another tool we’ve been told to use” into “the way we work now”. It is the human counterpart to the strategy domain’s embed phase and depends on the workforce domain’s enablement.

What you need to know

Adoption follows a curve: a few innovators and early adopters move first, an early and late majority follow if you make it easy and rewarded, and laggards move last. Champions — respected practitioners, not the AI team — carry adoption further than any top-down mandate. A living use-case library turns one team’s win into every team’s starting point. Incentives and, above all, manager behaviour decide whether the majority moves: people copy their manager, not the CEO’s email. The signature failure to recognise and prevent is the licence graveyard — seats provisioned, a launch email sent, and usage flat within a month because nobody changed how the work is actually done.

Learning objectives

By the end of this page you should be able to:

1. Locate a population on the adoption curve and choose the right intervention for each segment.
2. Design a champion network that scales adoption beyond the central team.
3. Build a use-case library that makes good practice the default starting point.
4. Align incentives and manager behaviour so the majority adopts.
5. Communicate change in a way that reduces fear and models real use.
6. Diagnose and prevent the licences-bought-but-unused failure.

4.1 The adoption curve

Adoption is not uniform. The population splits into segments that need different things, and the make-or-break gap sits between the early adopters and the majority.

  usage
    ▲            early      late
    │   early    majority   majority
    │  adopters   ████████   ████████     laggards
    │   ████                              ░░
    │ ██        THE CHASM ↑
    │██  innovators   (make it easy +
    └────────────────  proven + rewarded)──────────► time

The programme’s job is to get the majority across the chasm, and the majority does not respond to novelty — it responds to proof for its own role plus low friction. Announcements move innovators; they do nothing for the majority.

4.2 Champion networks

Champions are respected peers embedded in the business who demonstrate real use in the local context. They out-perform central mandates because the majority trusts someone who does their job, not the AI team.

A champion network converts a central programme into local behaviour change. It is the mechanism that carries adoption from early adopters into the majority, one team at a time.

4.3 Use-case libraries

A use-case library is a curated, living collection of proven ways people in this organisation use AI, with the prompt or workflow, the role it suits, and the benefit seen. It removes the blank-page problem that stalls the majority.

Title      : Weekly account summary for CSMs
Role       : Customer success
Problem    : 45 min every Monday compiling account status
Approach   : Prompt template + connected CRM notes
Benefit    : ~30 min saved / CSM / week; more consistent format
Owner      : J. Okafor (CS champion)
Reviewed   : governed workspace only; no customer PII in prompt

A stale, top-down library dies; a living one curated by champions and fed by users becomes the first place people look.

4.4 Incentives and manager behaviour

Incentives set direction, but manager behaviour is the strongest single adoption lever. Teams copy their immediate manager’s habits, not a mandate from three levels up.

The uncomfortable truth for the exam: a manager who does not use AI themselves will not produce a team that does, regardless of incentives. Adoption programmes therefore target managers first.

4.5 Communication that reduces fear

Bad AI communication triggers the workforce risk from D3: fear of replacement produces quiet resistance. Good communication is specific, honest and repeated.

Silence is the worst option: in the absence of a clear message, people assume the most threatening one and disengage.

4.6 The licence graveyard

The defining failure of enterprise AI: buy seats, send a launch email, celebrate the rollout — and watch active usage collapse within weeks because nothing about how the work is done actually changed.

  LICENCE GRAVEYARD                    LIVING ADOPTION
  ─────────────────                    ───────────────
  buy seats                            buy seats for a proven use case
  send launch email        vs          managers model + expect use
  measure licences issued              measure active use + value
  usage: spike → flatline              champions + library sustain it
  root cause: deployment,              root cause fixed: behaviour
  not adoption                          change, not tool access

The diagnosis is always the same: the organisation treated a behaviour change as a procurement event. The cure is proof-for-role, manager modelling, a use-case library, a champion network and metrics that count active use and value, not seats sold.

Decision framework

The A-D-O-P-T diagnostic

When adoption stalls, run these five checks in order to find the real blocker before spending more.

The order matters: measuring active use first tells you whether you have an adoption problem at all, before you invest in champions or communication.

Common mistakes

Scenario challenge

Scenario. Nine months ago your company bought 6,000 ChatGPT Enterprise seats and announced them with a keynote and an all-staff email. Today the dashboard shows 11% weekly active use, concentrated in the product and data teams. A board member asks whether the investment was a mistake and suggests either “buying a better tool” or “mandating usage with a target for every employee”. Your engagement data shows two things: the teams using it heavily had engineers who already loved it, and a survey found many staff “don’t know what they’d use it for in my role” and “my manager never mentions it”.

Expert reasoning trace.

1. Name the failure precisely. This is a licence graveyard, not a tool failure. Usage concentrated in innovator-heavy teams (product, data) and flat elsewhere is the classic chasm signature: the early adopters moved, the majority never did. Buying a different tool would reproduce the same curve.

2. Reject the two board suggestions as written. “Buy a better tool” misdiagnoses a behaviour problem as a product problem. “Mandate a usage target for everyone” produces gaming (open-and-close sessions to hit the number) and resentment, not value — activity is not adoption.

3. Run A-D-O-P-T. Active use is low (confirmed). Demonstrated value: the survey’s “don’t know what I’d use it for” is a role-proof gap — there is no use-case library for their jobs. Ownership: “my manager never mentions it” is the decisive finding — managers are not modelling or expecting use. Peer channels: no champions outside the early teams. Time/incentives: none allocated.

4. Sequence the fix by leverage. First, managers: make role-relevant AI use a normal expectation that managers model and review — because the majority copies managers, this is the highest-leverage move. Second, champions: recruit a credible practitioner in each lagging function. Third, use-case library: harvest the product/data teams’ wins and, via champions, create entries for finance, sales, operations so every role has a “here’s exactly what to do”. Fourth, communicate honestly about intent to defuse the unspoken job-loss fear surfacing as disengagement.

5. Change the metric. Report active use and value by role, not seats issued or raw logins, so the board sees real movement across the chasm rather than a vanity mandate.

Board-ready outcome: the diagnosis is behaviour, not tooling; the two proposed fixes are declined with reasons; the plan targets managers first, then champions, then a role-specific use-case library, with honest communication and value-based metrics — the levers that actually move the majority.

Assessment traps

Practice questions

Each item states how many responses to select. Commit before revealing.

Key takeaways

• Adoption follows a curve; the programme’s job is to move the majority across the chasm with role proof and low friction, not to impress innovators.
• Champion networks of respected practitioners carry adoption further than any top-down mandate.
• A living use-case library removes the blank-page problem and bakes in the governed way to work.
• Manager behaviour is the strongest single lever: teams copy their managers, so target managers first.
• Communicate intent honestly; silence about job impact breeds fear-driven resistance.
• The licence graveyard — seats bought, email sent, usage flat — is a behaviour failure, not a tooling one.
• Diagnose stalls with A-D-O-P-T; measure active use and value, never seats issued.