Case Study: Turning Individual AI Wins Into Shared Capability

There is a readiness profile that looks like success and behaves like a plateau: strong foundations, capable people, real daily usage — and nothing compounding¹. The organisation is paying enterprise prices for individual productivity.1A composite case, anonymised from several Fellow engagements. Numbers are representative of the pattern, not one client's audited results.

The situation

A professional-services team of about 300 had done the hard part: licences everywhere, training completed, genuine enthusiasm. Yet output gains were confined to a handful of power users. The assessment showed the signature gap — high Foundations and Applied use, low Workflow integration — and one number told the whole story: the gap between the best user's productivity and the median user's was wide, and widening^◦.By the numbers5×difference in AI-assisted output between the team's best user and its median, at engagement start

Every win was private. Prompts lived in personal chat histories. Techniques spread by lunch conversation, or not at all. When a power user went on leave, their throughput went with them.

Why capability doesn't compound on its own

Individual skill decays and departs; only shared assets accumulate^◦. Without a place for practices to live, every person re-solves the same problems: the team had, we counted, eleven separately-invented prompt variants for the same client-letter task — none of them the best one.DefinitionCompounding When this quarter's improvements become the floor for next quarter — requiring assets that persist beyond the individuals who created them

Training alone cannot fix this. Training raises individuals; compounding requires infrastructure — however light.

What we did

1. Harvested the top five practices. Two workshop days: power users demonstrated their real workflows, the team voted on the five with widest application, and each was written up as a shared, named asset — prompt, checklist, worked example.
2. Gave each asset an owner. Not the original inventor by default — the person whose role most depended on the workflow. Owners maintain, coach, and retire their asset.
3. Co-built one assistant for the heaviest recurring workflow — client-letter drafting — with the people who own that work, not for them. Building it together is what made it theirs; assistants delivered as gifts get admired and abandoned^◦.FigureCo-building is the transfer mechanism: the team that builds the assistant is the team that keeps it
4. Changed the definition of done. Any AI win worth mentioning in a team meeting now ends with the same question: where does it live now? Sharing became a norm with a place to put things, instead of a value statement.

What changed

One quarter later the best-to-median gap had halved — not by slowing the best users but by raising the middle^◦. New joiners reached working proficiency in days instead of months, because the assets were the onboarding. And the original power users, freed from being the team's informal help desk, went back to inventing — now with somewhere for the inventions to land.By the numbers5× → ≈2×best-to-median output gap after one quarter of shared assets and one co-built assistant

What to steal

1. This month: run a two-day harvest — power users demo, team votes, top five practices become named shared assets.
2. Assign each asset an owner whose role depends on it. Inventorship is not ownership.
3. This quarter: co-build one assistant for your heaviest recurring workflow, with its owners in the room.
4. Add "where does it live now?" to every AI win discussion. A win without an address is a story, not an asset.

Capable people with nothing compounding is momentum quietly expiring — the harvest is how you bank it before it does^◦.RelatedA full worked example: one owned workflow, measured end to end