Launch Playbook for Internal Tools (Products Your Own Team Uses)

The new internal CRM dashboard shipped on a Wednesday. By Friday, sales reps had three Slack threads open complaining about the old one. The PMM in charge had run a perfect external launch the month before — pre-briefed analysts, sequenced press, instrumented every page. The internal launch got a Loom and a calendar invite that 40% of the team declined.

Internal tools are products. They have users with jobs to do, switching costs, mental models, and the same capacity to quietly hate you for shipping something they didn't ask for. The difference is that nobody on the launch team treats them that way — and the people who suffer are the ones whose pipeline depends on the tool working.

An internal launch is a real launch. The audience is harder to win and easier to lose.

Why internal launches collapse

The pattern is consistent. The team that built the tool assumes adoption is automatic because the users are colleagues. The PMM team treats the launch as a ticket — write a Slack post, attach the Loom, mark it done. Engineering measures success by deploy date. Nobody owns the question of whether the people who need to use it actually do.

The result: a tool that exists, a directive that says use it, and a ground truth where the field still pastes notes into the old spreadsheet because the new flow takes one more click and nobody explained why the click is worth it.

The four audiences inside one launch

External launches have one audience and many channels. Internal launches have one channel — your own company — and four audiences who each need a different argument.

Most internal launches communicate to audience one and forget the rest. The damage shows up in week two when an adjacent team discovers their dashboard broke silently, or in month three when the funding exec can't defend the project's headcount.

The playbook

What to put in the announcement itself

Most internal launch posts are written like changelogs. They list what's new. The user has to translate that list into "what changes for me on Monday." Don't make them do the translation.

What this costs

The full playbook above runs roughly forty PMM hours for a tool used by a hundred people, plus ten hours of engineering or design time on the comms assets. That's two-thirds the cost of a small external launch.

If you can't hold forty hours, here's the twenty-hour version: write the one-page brief, pick three champions, sequence the announcement across three days, and instrument activation only. Skip the formal retro and replace it with a fifteen-minute review with the team lead at day thirty. Adoption will be lower than the full version but materially better than the Loom-and-calendar-invite default.

The download

What to do Monday

Pull up the last internal tool your team shipped. Ask three of its intended users what changed in their workflow. If they can't answer in one sentence, the launch didn't land — and the next one is your chance to fix the pattern, not the post.