How to Prepare the Launch

When the initiative is approved, create one plan with a bucket per workstream and give every task an owner and a due date as you make it. Note what each task waits on, and chase every unassigned line until it has a name or you cut it. The plan holds when a week of your absence would still leave every workstream knowing its next step.

Before launch week, decide per audience what each group needs to know, who tells them, through what channel, and when, covering the groups affected indirectly too. Sequence it so the people most affected hear first. Someone learning about a change to their own work from an all-staff email will remember it.

One to two weeks out, gather the people doing the work, tell them it is six months later and the initiative failed, and give everyone five minutes to write down why, in writing so the quiet people answer too. Group the repeats and take the top three into the plan with an owner and a mitigation each. The session worked only if a task actually changed.

Before launch day, write down who decides what once the initiative is live and on what rhythm reviews happen: workstream owners inside their lane, the initiative owner for anything larger, the sponsor when scope, budget, or dates move. Publish the routes with real names. The first escalation should follow a path you drew, not an argument about who owns the call.

After each launch, note which preparation paid off and which you wish you had done, and fold both into a one-page checklist in a shared location. Keep it to a page, because a checklist nobody finishes is one nobody runs. It is working when a launch you had no part in runs from it.