Unfrozen · Free tool

Brief the managers before launch day.

A one-page brief for any new tool, system or process rollout. It lists the managers who will have to explain the change, the questions their teams will ask first, and who answers each one, before the change goes live.

Tools can now change faster than teams can change how they work. In my experience, most of the catch-up happens with the managers who explain each change to their teams. If they hear about it on launch day, the same day their team does, there's no time to work out what it means first.

This brief moves that conversation a week earlier. Fill it in with the managers who will carry the rollout, then check back two weeks after launch.

What's on the page

  1. The changeWhat's changing, the launch date, why now in one sentence, and what stays the same.
  2. Who will explain itEach manager, their team, and the date they were briefed, before launch day.
  3. What will each team ask first?Each question, who answers it, by when, and whether the answer is ready.
  4. Before launch dayFour checks, ending with: each manager can explain the change in their own words, including what it costs their team.
  5. Two weeks after launchWhich questions are still open, and what a team asked that nobody could answer.

This is my working bet from Edition 4 of Unfrozen, not a tested method. No study in the Atlas of the Middle tests whether briefing managers before launch closes the gap. If you use it, tell me what happened.

Preview of the one-page Pre-launch manager brief, with five sections: the change, who will explain it, what each team will ask first, before launch day, and two weeks after launch.