Adoption died after launch. A champion program revived it.
A beautiful intranet launched to fanfare — then usage collapsed within a quarter. Staff drifted back to email attachments and desktop folders, and leadership was ready to write off the investment.
The launch went perfectly. Then everyone went back to email.
On paper, this project was already finished. The nonprofit had a genuinely well-built intranet — clean navigation, branded pages, sensible libraries — and it launched to real fanfare: an all-staff announcement, a walkthrough, applause. Nobody disputed that it was better than what came before. For the first stretch after launch, people clicked around, and the numbers on the launch-day dashboard looked like success.
Then usage collapsed, within a quarter. Not because anything broke — because habits won. The launch training had shown everyone the same generic tour, so nobody had actually learned how their work was supposed to move onto the new sites. Under deadline pressure, staff did what they had always done: program documents went back out as email attachments, working files drifted back into desktop folders, and the intranet quietly became a place where announcements went to be ignored. Every person who fell back to the old way made the intranet less current, which gave the next person one more reason not to trust it.
By the time leadership looked hard at the situation, they were ready to write off the investment entirely. The uncomfortable part was that the intranet itself was not the problem — the organization had bought a good system and skipped the harder work of changing how people actually work. The question they brought to us was blunt: is this rescuable, or do we stop pretending?
No rebuild. A people plan.
We didn't redesign a single page — the intranet was fine. Adoption is a people problem, so the program was built around people: training that matched real jobs, champions inside every department, help where staff already look, and usage data that kept everyone honest.
No generic "this is a document library" tour. Each session was built from the department's own sites, their own documents and their own everyday tasks — so finance practiced finance work and program staff practiced program work, in the places they'd do it on Monday.
One person per department, trained deeper than their colleagues and known as the first port of call. Questions get answered at the next desk instead of dying in a help queue — and champions feed back what's confusing people, so problems surface early.
Plain-language how-tos for the tasks staff actually do, published right on the home page where everyone lands. When someone forgets how to share a link instead of an attachment, the answer is one click away — not buried in a training folder.
Adoption measured from real usage data, not anecdotes or good intentions. Every quarter, leadership sees who is using what, champions see where to focus next, and the question "is anyone actually using this?" gets a factual answer instead of a shrug.
The intranet they almost wrote off became the default.
Adoption here isn't a feeling — it comes straight from the usage data the quarterly reports are built on.
Launched an intranet nobody opens?
Book a free 30-minute audit — we'll read your actual usage data, find where adoption stalled, and show you what a champion program would look like for your team.