Starting a Microsoft 365 Copilot adoption journey is one thing when you’re there from the beginning-but what happens when you step into an empty husk of an initiative that’s already underway? Even better – what if you have absolutely no idea what formal change management looks like, no training, and a healthy dose of imposter’s syndrome?

The answer: you figure it out! However, you don’t have to figure it out all on your own like I did with the help of attending this talk. In this session, take away valuable lessons learned from stepping into a newly-created M365 adoption and training role with very little internal support created yet and a boss who went unexpectedly OOO after your first morning on the job (it’s a whole story). See how to approach M365 Copilot adoption guerilla-style, boots on the ground, relying solely on your wits and your love for helping others be more productive.

You’ll gain insights into how to assess an ongoing (or stalled, or abandoned) adoption effort, finding your power users in a sea of anonymized Microsoft analytics, building relationships that count, and also somehow moving the org from less than a thousand Copilot interactions a day to 14,000+ a day (and climbing!) Join me into figuring out how to raise KPIs when you have no idea what a KPI is, and create a positive and productive user experience.

Assumed Knowledge:

You should know what M365 Copilot is and the basics of what it can do to gain the most from this session.

Practical Takeaways:

Guerrilla-style adoption strategies – boots-on-the-ground approaches that don’t require a formal change management background or big budget; Moving the needle on KPIs – how to identify, understand, and improve key metrics even when you’re new to the concept; Scaling Copilot usage dramatically – lessons from growing daily interactions from under 1,000 to 14,000+; Creating a positive user experience – keeping end users at the center of your adoption effort

Out of Session Scope:

We will NOT cover formal change management strategies or adoption methodologies – this is a case study.