Adoption Recovery
Rescuing a stalled tool adoption from 30% to 85%—without switching tools or starting over.
The Problem
The organization had invested in a new work management platform 6 months prior. Adoption stalled at 30%. Teams reverted to spreadsheets and email. Leadership was frustrated.
The platform vendor's support team had run their standard onboarding, but it didn't stick. People attended training, nodded along, and went back to their old ways within a week.
Sound familiar?
The Constraints
- Could not switch tools again—the organization had already committed budget and political capital
- Had to work with what was already purchased
- Team morale around "process changes" was low
- Leadership was losing patience but didn't want to mandate usage
This wasn't a technology problem. It was a change management problem masquerading as a technology problem.
What We Did
Phase 1: Listening Sessions
Before touching any configuration, we ran listening sessions with each team. We asked:
- What were you hoping this tool would do for you?
- What frustrations have you encountered?
- What are you doing instead, and why does it work better for you?
- If you could change one thing about how this is set up, what would it be?
The answers were illuminating. The original setup had been designed for an "ideal workflow" that didn't match how teams actually worked. People felt like they were fighting the tool rather than using it.
Phase 2: Simplification
We simplified the setup dramatically:
- Removed 40% of unused fields that created confusion and friction
- Eliminated mandatory fields that blocked quick task creation
- Consolidated statuses from 12 options to 5 clear stages
- Archived inactive boards that cluttered navigation
The goal was to reduce the cognitive load of using the tool to near-zero for common actions.
Phase 3: Role-Specific Quick-Start Guides
Instead of comprehensive documentation that no one reads, we created one-page quick-start guides for each role:
- Project Manager: How to create a project and track status
- Team Member: How to see your tasks and update progress
- Executive: How to view portfolio dashboards
Each guide focused on the 3-4 actions that role needed 90% of the time.
Phase 4: Workflow Labs
We ran "workflow labs" where teams rebuilt their own processes with guidance. This was crucial—people adopt what they help create.
Each lab was 90 minutes:
- 15 min: Review what's working and what isn't
- 45 min: Hands-on reconfiguration with facilitation
- 30 min: Test the new setup with real work
Teams left each lab with a working setup they understood and owned.
The Result
Adoption jumped to 85% within 8 weeks. Support tickets dropped. Teams started requesting new features instead of workarounds.
The shift was remarkable: people went from avoiding the tool to advocating for it. Several team leads became internal champions who helped onboard new hires.
"The first training felt like they were teaching us someone else's system. The workflow lab felt like we were building our system. That made all the difference." — Team Lead
Tools Used
- Monday.com
- Google Workspace
- Loom
Key Takeaways
- Listen before you act: The solution was obvious once we understood the real problems
- Simplify aggressively: Every unused field is friction that pushes people back to spreadsheets
- Co-create, don't mandate: People adopt what they help build
- Role-specific guidance: One-size-fits-all training fails because roles have different needs
- Make the easy thing the right thing: If updating status is harder than not updating it, people won't update it
When to Consider Adoption Recovery
Not every stalled implementation needs a full recovery effort. Consider it when:
- You've invested significant budget in a tool that isn't being used
- Switching tools isn't financially or politically viable
- People aren't opposed to the tool—they just find it frustrating
- The original setup was designed without input from end users
If people are actively hostile to the tool or if it genuinely doesn't fit your use case, a recovery effort might not be the right move. But if the bones are good and the implementation was rushed or misaligned, there's often a path to adoption that doesn't require starting over.
Share this article
Dealing with something similar?
Lets talk about how we can help your team work more effectively.
Get in TouchRelated Posts
Portfolio Operations Overhaul
How we helped a cross-functional team managing 40+ projects gain real-time visibility and reduce status meeting time by 60%.
Case StudyTool Migration & Integration
Consolidating parallel systems into a single source of truth while active projects continued—and cutting weekly reporting time from 4 hours to 15 minutes.

