Installing the platform is the easy half; it completes in an afternoon. The hard half is that four hundred people already have habits — email threads, a legacy chat tool, a shared drive with folklore attached — and every habit is a small investment they will defend. Rollouts fail technically almost never; they fail behaviourally, constantly.
Start With a Pain, Not a Feature
Nobody changes tools for a feature list. People change tools when a current pain gets named and removed: "status meetings exist because nobody can see the plan" or "files have six final versions". Find the two pains your organisation actually complains about, and build every communication around removing them. Feature announcements produce compliance; pain removal produces adoption.
The Pilot: Small, Loud, and Honest
- Pick one department with a respected manager and a genuine collaboration load — not IT, who love anything new.
- Run four to six weeks with weekly feedback sessions; fix the top three irritations visibly and fast.
- Let the pilot group tell the story. Peer testimony outweighs executive memos by an order of magnitude.
- Publish what went wrong in the pilot alongside what went right; honesty buys credibility for the waves that follow.
Champions Are the Distribution Network
Recruit one champion per twenty or thirty users: volunteers, not conscripts, given early access, a direct line to the project team, and permission to spend an hour a week helping colleagues. Champions answer the hundred small questions that otherwise become tickets or, worse, reasons to abandon the tool. Budget for them explicitly; unpaid invisible labour evaporates by month two.
Retire the old tool on a date, in public
Parallel running feels kind and is fatal: everyone waits for the other to switch. Announce the retirement date of the legacy chat or drive months ahead, freeze it read-only on the day, and keep exports available. Grief is real and brief; ambiguity is endless.
Communication Waves That Respect Attention
- Why now — the pains, the decision, the timeline; from a named executive, in person where possible.
- What changes for me — role-specific one-pagers: what stops, what starts, what stays.
- How to learn — short guided sessions recorded for reuse, plus this handbook's everyday chapters as reference.
- Where to get help — a dedicated channel with champions inside, response-time promise published and kept.
Measure the Transition, Not the Launch
Track weekly: active users against licence count, messages per active user, and — the honest one — the share of meetings still ending without a written follow-up. When a metric stalls, investigate behaviour, not technology: usually a missing habit (where decisions get posted) rather than a missing feature.
The First-Ninety-Days Arc
Days one to thirty: enthusiasm and confusion coexist; over-support deliberately. Days thirty to sixty: the dip, where novelty fades and old tools tempt; this is when champions and visible fixes matter most. Days sixty to ninety: habits form; celebrate the first team that ran a quarter entirely in the new space and tell everyone who they are.
Rollout gets people in the door; metrics tell you whether they stayed. The next chapter covers which adoption numbers deserve a dashboard — and which are vanity.
