Operations

Launch Communication Plan Prompt

Make sure the right people know — a launch comms plan covering who to tell, when, through which channel, and what to say if it goes wrong.

Overview

A technically perfect launch still fails if support is blindsided, stakeholders are surprised, or users hit a change with no notice. This prompt builds a launch communication plan: the audiences (internal and external), the message and channel for each, the timing relative to the deploy, and the pre-written holding statement for if the launch goes sideways.

Why This Works

Briefing support before launch turns surprise tickets into prepared answers
Audience-matched messaging stops users getting engineering detail they can't use
A pre-written holding statement saves the worst time to start writing one

Best for

Launches that affect users or multiple teams
Releases that will generate support volume
Teams where engineering ships without telling anyone

Not for

Purely internal, invisible deploys
Marketing campaign strategy — this is launch coordination

Use cases

Coordinating comms for a user-facing launch
Making sure support and on-call aren't blindsided
Pre-writing the statement for a launch that goes wrong

Customize This Resource

Opens this resource in the related tool with the fields pre-filled. Customize role, tone, and behavior rules — then generate your prompt.

Prompt Template

ROLE
You are planning the communication around a product or feature launch.

INPUT
The launch:
[What's launching, to whom, and when]

PRODUCE A COMMS PLAN
1. AUDIENCES: everyone who needs to know — on-call, support, sales, leadership, affected users, status-page subscribers.
2. MESSAGE: for each audience, the one thing they need to know, in their language (not the engineering detail).
3. CHANNEL & TIMING: where and when each audience hears it, relative to the deploy (before / at / after).
4. SUPPORT ENABLEMENT: what support needs to handle the questions this launch will generate.
5. IF IT GOES WRONG: a pre-written holding statement and who approves external comms during an incident.

RULES
- Internal audiences are briefed before external ones.
- Match the message to the audience — users don't need the architecture.

OUTPUT
A comms plan table (audience, message, channel, timing) plus the support brief and the holding statement.

Related Resources

Explore more resources that work well with this one.

Related Tools

Multi-Step Prompt Builder

Tip: Save time by exploring related resources and tools that integrate with this workflow.

Explore all resources