Adoption is content-shaped, not tool-shaped
The default adoption approach for many M365 deployments is generic toolset training — 'this is SharePoint, this is Teams, here's how a library works.' This training has its place, but it consistently underperforms in the moment that matters: a user trying to do their actual job in the new environment.
Better adoption is content-shaped. Users learn the new environment by walking through their content — their site, their libraries, their files. The training is anchored to real scenarios: 'where do I save this report,' 'where did the policy I needed go,' 'how do I share this draft with my colleague.' This works because users are oriented by their work, not by an abstract tool.
Start every training session by walking through the user's new environment, not by explaining the tool. The tool comes up naturally as they learn how their work fits into the new structure.
The structured training flow
A consistent format works across audiences and migration waves:
-
1. Walkthrough of the new environment. Show users their site, their hub, their libraries. Explain navigation. Show where different types of content now live. Anchor on their actual content.
-
2. Core task-based training. Walk through common day-to-day activities: uploading and organizing documents, working in libraries, understanding access, sharing, finding information.
-
3. Migration-specific guidance. Help users handle the practical realities of migration: bulk uploads if needed, finding content that didn't migrate, where to put late-arriving content from legacy systems.
Delivery model
| Approach | When | Investment |
|---|---|---|
| Instructor-led group training | Initial wave; high-touch areas; complex change. | High effort per session; works for cohorts of 10–25. |
| Self-led learning portal | Ongoing reference; users at different paces; post-migration deep-dives. | Moderate effort to build, low effort to deliver. |
| Department champions | Local point of contact in each area; reinforces good practices; first line of help. | Recruit, train, and support. Pay back is large. |
| Lunch-and-learns / Community of Practice | Post-rollout, ongoing; specific topics; cross-area exchange. | Light per session; sustained over time. |
| 1:1 power-user coaching | For Site Owners, Brokers, Information Managers; people doing platform work daily. | High per-person; high return for the small group. |
Combine instructor-led group training during initial rollout (cohort-based), self-led materials for ongoing reference, a champion network for local support, and a Community of Practice for sustained learning. No single delivery channel works for everyone; the combination does.
Champion network
Department champions are the multiplier. Each business area has 1–3 champions — people who are interested in the platform, willing to help peers, and trusted locally. Champions are not Site Owners (though some may be); they are the user-side support layer.
-
Recruitment. Volunteer-based with manager endorsement. Don't draft people.
-
Onboarding. Initial half-day session; deeper than end-user training.
-
Ongoing support. Monthly champion call; private Teams channel for questions; early access to platform changes.
-
Recognition. Champions get visible recognition. Lunch invites, exec acknowledgement, occasional swag.
-
Backstop. Champions are not the only support — central help and the Information Manager team backstop them.
Supporting materials
-
Quick reference guides. One-page documents for the highest-frequency tasks. Print-friendly.
-
Videos. 2–5 minute clips for specific tasks. 'How to upload a document,' 'How to share with a colleague,' 'How to find a file using search.'
-
Playbooks. Longer-form guides for specific scenarios — onboarding to a new site, managing a library, organizing project content.
-
FAQs. Living document; updated as new questions arrive.
-
Walk-throughs. Recordings of training sessions, organized by topic, available on-demand.
Materials that aren't maintained become misleading within months. Update cadence is real work — assign an owner. The Community of Practice is a good source of feedback on which materials are out of date or missing.
Post-rollout enablement
Training doesn't end at cutover. Post-rollout enablement keeps adoption advancing:
-
Lunch and learns. Monthly informal sessions on specific topics — search, Copilot, advanced library features, building a Power Automate flow.
-
Community of Practice. Sustained venue (see Doc 3.5) for cross-area learning, troubleshooting, and platform improvements.
-
Targeted office hours. Open-door sessions where users can drop in with questions. Run by the Information Manager team or champions.
-
Regular comms. Monthly or quarterly platform update — what's new, what's coming, what's been fixed.
Impact's role-based training material (under training/) provides standup playbooks for Brokers, Information Managers, Tenant Administrators, and end-users — consistent across engagements. The Community of Practice and Learning Portal patterns (Docs 3.5 and 3.6) operationalize sustained adoption work.
Discussion Questions
• Are we training on the toolset or on users' actual content and scenarios?
• What delivery mix fits our organization — heavy instructor-led, heavy self-led, hybrid?
• Do we have a champion network model? How are champions identified and supported?
• What materials exist today, and what's the cadence for keeping them current?
• What sustained enablement runs after rollout — lunch-and-learns, CoP, office hours?
• Who owns adoption metrics? How do we know if adoption is succeeding?
• What's the trigger for additional training waves — new features, low adoption, user feedback?
• How do we handle late-arriving users (new hires, transfers) — onboarding into the new platform?