Case Study: What Changed When AI Adoption Got a Named Owner

Ask who owns AI adoption in your organisation. If the answer contains the word "everyone", the real answer is nobody¹ — and everything currently working is one resignation away from stopping.1A composite case, anonymised from several Fellow engagements. Numbers are representative of the pattern, not one client's audited results.

The situation

A retail group of about 2,000 people had enviable AI momentum, almost all of it traceable to one senior analyst who had made adoption a personal mission: she maintained the prompt library, ran the informal training, and fielded everyone's questions. Then she resigned. Within a month the library was stale, the sessions stopped, and usage in her division dropped by roughly a third^◦.By the numbers≈⅓drop in division AI usage within one month of the unofficial champion leaving

The readiness assessment, run during the aftermath, made the structural gap explicit: real usage across the scope, and no accountable owner anywhere in it.

Why "organic" adoption stalls

Champion-driven adoption feels healthy because it is enthusiastic, cheap, and self-starting. It is also structurally fragile^◦. The champion has no mandate, so every improvement is a favour. No budget, so tooling is improvised. No measures, so their impact is invisible until it disappears. And because five teams copy the champion five different ways, practices never converge into anything the organisation owns.DefinitionChampion risk Adoption that depends on a volunteer's personal energy — unbudgeted, unmandated, and gone the day they change roles

The failure is not the champion leaving. It is the organisation having rented its capability from one person's goodwill without noticing.

What we did

The fix was deliberately small — the opposite of a transformation office:

1. One named owner. A manager — not the busiest executive, and not a committee — with written decision rights over tooling requests, workflow priorities, and training time.
2. Three workflows, one measure each. Store-report drafting, merchandising copy, and supplier-email triage: each with a baseline, a target, and nothing else on the owner's scorecard until those moved.
3. A thirty-minute monthly review with the COO in the room. Not a steering committee — a working session with three numbers on one page. Leadership attendance, more than any mandate document, is what told the organisation this was real^◦.FigureOwnership becomes real the first time leadership sits in the review and asks about the number

The former champion's successors were folded in as workflow leads — the enthusiasm was kept, but it now reported into a structure instead of substituting for one.

What changed

Usage recovered past its previous peak within two months, and — the part that matters — it survived the next departure without a dip, because assets and accountability no longer lived in one head. At re-assessment, adoption ownership moved from the bottom of the profile to its strongest indicator^◦.By the numbers3workflows with a named owner and a monthly-reviewed measure — the entire initial governance structure, on purpose

What to steal

1. This quarter: name one adoption owner — a person with time and decision rights, not a working group.
2. Hand them exactly three workflows with one measure each. Refuse the temptation of a ten-item scope.
3. Put a monthly thirty-minute review on the calendar of the most senior person who will reliably attend. Attendance is the mandate.
4. Convert your champions into workflow leads inside the structure — celebrate them, and stop depending on them.

If your readiness report flagged real usage with nobody accountable, treat it as a countdown, not a description — the fix costs one job-description paragraph and a monthly half hour^◦.RelatedThe next step: turning owned workflows into compounding practice