I work on Microsoft 365 and Copilot rollout projects — specifically on the change management and user training side. My job isn't configuring tenants or writing PowerShell scripts (though I touch that too); it's making sure that once M365 or Copilot is deployed, people actually use it, and use it well.
That gap — between "the tool is live" and "the org has actually adopted it" — is where I spend most of my time. And it's the gap I want to write about here.
What I keep running into
A few patterns show up in almost every project:
Rolling out a new feature is easy. Getting it embedded into daily workflows is the hard part.
Everyone agrees "we should use AI," but far fewer people know how, or why it matters for their specific job.
Training that works for one team completely misses the mark for another — there's no universal playbook.
None of this is really a technology problem. It's a people problem that happens to involve technology.
Why I'm writing this blog
I've kept most of this knowledge locked in internal reports and project decks. Starting now, I want to share it publicly — partly to build credibility in this space, and partly because I think change management and training don't get nearly enough attention in the M365/Copilot conversation compared to the technical setup side.
Here's what I'll be writing about:
Real change management challenges from Copilot rollouts (and what actually worked)
Lessons from designing and running user adoption training
Practical takeaways from M365 updates, seen through an adoption lens
Honest write-ups of things that didn't work, and what I'd do differently
Let's talk
If you're working on M365 or Copilot adoption in your org — or fighting the same "great tool, nobody's using it" battle — I'd love to hear how you're tackling it. Drop a comment or follow along; I'll be posting regularly.
Top comments (0)