Adoption that wouldn't stick.
A SaaS scale-up had run two internal AI pushes. Both spiked, then sagged the moment the champions moved on. Roughly 30% of engineers were weekly-active and the number was drifting down. The tools were fine; the habit had no scaffolding.
They wanted adoption that survived a champion leaving — a self-sustaining curve, not another launch.
Conventions the team owns, on a scoreboard they read.
We installed shared conventions for how AI gets used in everyday work, and a team scoreboard that makes adoption and output quality visible to everyone. Then we handed both to the team's own leads — with the explicit goal that nothing depended on us after week four.
- Written conventions, embedded in the team's existing rituals
- A scoreboard the team reads in standup, not a dashboard nobody opens
- A self-assessment leads run each quarter to catch drift early
- A clean handover: the leads, not Whitescroll, own the model
"The scoreboard did the work a champion used to do — it kept everyone honest after the excitement wore off."
Conventions plus a scoreboard, then handover.
The scoreboard is the durable part. A visible number that the team owns outlasts any individual champion — which is exactly why the curve kept climbing after we were gone.