Conventional wisdom says pilot new collaboration tools with an enthusiastic, low-risk team, learn, then scale. There is a case for the opposite. If the executive office adopts the platform first and visibly, the rest of the organization stops asking whether the change is real.
That was the bet on the transition-to-digital-platform workstream of a provincial Crown insurer’s transformation program.
Prove the platform can carry the program
Before the pilot, we had to decide what would manage the transformation itself. I led a proof of concept between the advisory partner, the platform vendor’s experts, the insurer’s business leads, and PMO leadership to evaluate whether a dedicated transformation-management platform could handle the program and its initiatives. A proof of concept with all four parties in the room is slower than a demo and far more honest, because the people who will live with the result are the ones testing it.
A pilot site for the people with the least patience
I led a team of two business analysts, an architect, and a developer to provision a pilot SharePoint Online site for the executives. The design constraint was blunt: an executive will give a new tool one attempt. Navigation had to match how they already thought about their work, permissions had to be right the first time, and nothing could require a help ticket.
Training was white glove, one to one, at their desks, on their documents. That extended to the province’s Crown investment corporation, whose team worked with the insurer’s board materials.
The workflow that made it stick
The moment the platform became indispensable was small. Board meeting minutes had been reviewed and approved through email chains and printed copies. I configured a review and approval workflow in Power Automate, using SharePoint Online external sharing so the investment corporation’s reviewers could participate without accounts on the insurer’s tenant. Approvals became traceable, versions stopped multiplying, and the executives had a reason to open the site every month that had nothing to do with a training plan.
Then the unglamorous part
With the pilot standing, I documented the transition requirements for moving content from the network share to OneDrive and the pilot sites: what moves, what is archived, who owns each folder, what metadata comes along. This is where migrations succeed or fail, and it was easier to get right because the people whose content it was had already seen the destination working.
The pattern
Start where credibility is scarcest and the audience least forgiving. Give that audience one workflow that solves a real irritation. Document the migration only after they trust the destination. It is a change management pattern more than a technology one, and it has held up in every migration I have led since.