Adoption drops after launch because most programs invest all their energy into the launch event itself and none into what comes after. The teams that hold onto their gains build a small champion network before they need one, remove friction from what they're asking people to do, and give managers ownership before their teams hear about the rollout.
Every rollout has its moment in the sun. The kickoff email goes out, the onsite happens, the usage numbers spike.
Then the excitement fades, and so does the momentum.
Most teams treat that drop-off as a mystery, or worse, as proof the tool wasn't right. But the problem is rarely the technology.
This edition traces what separates programs that survive the weeks after launch from the ones that slowly fade, using three practitioners who've each built a different piece of the same puzzle.
What you'll learn:
- Why the launch event itself is the easiest part of a rollout, not the hardest
- How to identify and activate champions before you think you're ready
- What actually turns a skeptic into your loudest advocate
About Field Notes
Each week, we speak with industry experts and iorad users around the world to understand how they're solving challenges in Enablement and L&D. We share those stories through The Adoption Curve.
But across those conversations, patterns have started to emerge.
Field Notes is where we capture them: distilling insights from interviews, customer feedback, and real world experience into the trends that matter most.
Why do software rollouts lose momentum after launch?
Launch day gets all the attention. Slides get made. Leadership shows up. There's energy in the room.
Then everyone goes back to their day job, and the tool is just one more tab.
How do you keep momentum once the announcement is old news? Who's actually responsible for adoption in week six, when nobody's watching anymore? And what do you do with the people who were skeptical from day one?
It comes down to one thing: infrastructure.
The problem isn't the tool. It's what happens after.
Yasmin Gutierrez, Director of Culture & Capability Enablement at Phillips 66, has inherited more half-finished rollouts than she can count.
It's a small idea with a big implication. When adoption stalls, teams reach for the same lever: more training, another reminder email, a refreshed one-pager. But if the tool was never the actual solution, more content about the tool was never going to fix it.
The intent is good. The infrastructure is missing.
Build the champion network before you need it
Ryan Orner, Senior Manager of Customer Success Management at HubSpot, led the rollout of an internal AI tool to hundreds of customer success managers. The tool worked. The adoption strategy is the part worth stealing.
Before there was a formal program, there was a small group quietly pressure-testing the tool. No structure, just people curious enough to try it and honest enough to say what didn't work. That group became the seed of the real champions network, and Ryan was deliberate about who made the cut once it formed: not just top performers, but a genuine cross-section, including people who weren't sold on AI in the first place.
Most teams build a champions list after adoption stalls, as a fix. Ryan's team built one before the launch, as the plan.
Naysayers aren't the enemy. They're your future champions.
Every rollout has someone actively pushing back. The instinct is to route around them.
Yasmin has learned the opposite works better.
That's not a soft skill. It's a mechanism. A skeptic who feels heard and sees their feedback incorporated has more credibility with the rest of the team than an enthusiast ever will, because everyone already knows they weren't easy to convince.
Skepticism, handled early, converts into your strongest advocacy.
Remove friction. Don't just add content.
Nia Li, Senior Sales Enablement Manager at TierPoint, frames her entire job around one word: friction. Not content creation. Not course completions. Friction removal.
She learned this by watching what happened when a rollout wasn't immediately useful. If a new tool or process can't be applied the moment someone learns it, their attention moves on and the training becomes one more thing filtered out as noise. It has to be usable right away, or it doesn't stick.
That reframe changes what gets built.
A safety net is there when you need it and invisible when you don't. Training, by contrast, announces itself, interrupts the work, and asks for attention it hasn't earned yet.
Nia's team learned this the hard way with rollout communications, too. Before fixing anything, they measured how many emails, meetings, and reminders a single seller was already absorbing in a week. The number was overwhelming, and it explained why so much of it was being ignored.
That is not disengagement. That is triage. People aren't ignoring your rollout because they don't care. They're ignoring it because it hasn't proven it's worth the attention yet.
How you know it's working
Ryan's team didn't just watch for usage. They watched for a specific signal: whether people who used the tool once came back and went deeper.
His team hit two numbers: over 70% weekly active usage, and users asking two to three times as many follow-up questions per session as they had at launch. That second number matters more than the first. Hitting a usage target tells you people showed up. A rising number of follow-up questions per session tells you they trusted the tool enough to go further, which is the actual signal that adoption has taken root instead of just been logged.
Usage is a snapshot. Depth of use is the trend line.
The cultural shift
None of this works as a one-time project. Champion networks, friction audits, and naysayer conversations only function if someone treats them as ongoing infrastructure, not a launch checklist.
That starts with managers, and Ryan is specific about why.
For Ryan's team, that meant managers got briefed and equipped a week before their teams ever heard about the rollout, so they could answer questions and model the behavior instead of finding out alongside everyone else. It's a handoff of actual ownership, not a memo asking managers to remind their teams once.
That means a standing cadence for gathering feedback, a manager layer that's briefed ahead rather than looped in after the fact, and a willingness to keep listening well past the point where the launch felt like a success.
Behavior will follow attention. Attention has to be renewed, not assumed.
Where to start this week
- Identify three to five people already using whatever you're trying to drive adoption on, even informally. Don't wait for a formal program to find them.
- Deliberately include at least one skeptic in that group. Ask them directly what isn't working, and act on one piece of what they tell you.
- Audit what you're already asking people's attention for in a given week. Before adding a new communication, look for one you can cut or combine.
- Brief managers a week before their teams hear anything. They're the reinforcement layer, not an afterthought.
- Pick one depth-of-use signal, not just a usage count, and check it every two weeks.