The challenge
L&D transformations often look like systems work from the outside: new LMS, new AI tools, new workflows, new teams. Inside the organization, people experience them as risk.
Admins worry about losing control. Managers worry about team disruption. Learners worry about access and expectations. Content teams worry about quality and rework.
The challenge was to make change feel usable before people had enough experience to trust it.
The approach
I treated change as operating work. Every rollout needed role clarity, manager enablement, support paths, and post-launch evidence.
I also watched workarounds. Workarounds tell the truth. If people keep a side spreadsheet, avoid the tool, or ask the same question every week, the change is not embedded yet.
The goal was to create enough readiness that people could use the new way when pressure returned.
Downloadable takeaway
A one-page version of the model with the decision questions, sequence, metrics, and red flags someone can use after reading the case.
What I built
LMS migrations
Each migration required more than technical cutover. Users needed guidance, admins needed rehearsal, and leaders needed confidence that data and reporting were protected.
The strongest adoption work happened before launch: who owns what, what changes for the user, and where support lives.
AI adoption
The AI rollout needed trust before productivity. We made experimentation visible, tied AI output to quality gates, and kept the team involved in the rules.
That made adoption feel like shared learning instead of a replacement threat.
Global team build
Team growth changed roles, decision rights, and communication habits. Change management had to include manager support and calibration.
People needed to know what was changing, why it mattered, and what good looked like in the new model.
Operating artifacts
These are sanitized work-product examples. They show the kind of artifact I would expect the team to use. They are sanitized and exclude confidential company material.
Change Impact Map
Change Impact Map
A view of who feels the change and what support they need.
Adoption Evidence Board
Adoption Evidence Board
The post-launch board used to see whether the change was sticking.
Manager Enablement Brief
Manager Enablement Brief
The short artifact managers need before they are asked to support adoption.
The results
The operating insight
The old change myth is that a large percentage of initiatives fail by default. I build from observable adoption: what people use, avoid, repeat, and work around.
The out-of-the-box move was treating workarounds as data. They show where the change is weak without waiting for a formal survey.
What this proves
- I can manage change across technology, AI, team structure, and workflow.
- I know adoption has to be measured after launch.
- I build manager support into the change instead of assuming communication is enough.