Platform switch-ups fail quietly: launches happen, enthusiasm peaks in week one, and month three finds four competing chat tools and a spreadsheet tracking who agreed to what. Change management is a discipline with modest tools — sequencing, language, dates — and this chapter compresses it into a working week of planning steps.
The pilot is a test of habits, not a demo
A demo teaches features; a pilot teaches people whether the switch makes their day easier. Pick a team with a habitual flow — weekly planning, a lot of handoffs, a project-driven cadence — then measure the hours before the change so you can compare afterwards. Anecdotes succeed in pitch meetings; numbers persuade in steering committees, and you will eventually need both.
Bottom line
Champions are peers, not evangelists. The colleague who understands the software and also sits next to the sceptics is worth five posters. Give them a short list of likely questions, a channel where they answer in the open, and the standing permission to say “we haven’t decided that yet”. Honest colleagues in the room do more for adoption than any schedule of webinars.
Communicate in waves, not in one launch email
Three waves do more than one announcement. The first wave says when. The second says why — in the language the team actually uses, before anyone has to ask. The third is practical: the first task each person performs in the new habitat, and what disappears on what date.
Return the old tool, and retire it on a date
Adoption sticks when the old tool is retired in public, with a date. “Phasing out” reads as optional to the half of the company watching the calendar; a named morning when the old door locks is not mistakable for anything. Habits anchor to real dates — the platform becomes the default the first morning after one.
An orderly launch arc — pilot, wave one, wave two, retirement date — is worth at least a quarter. Plan a piece of it in the open, log the queries you fielded, and lend the next wave a heat map of where people were confused.
