---
name: roadmap-communication-plan
description: "A roadmap communication plan that is useful to sales and customers without turning into a promise, with horizons, per-audience framing, and an answer to date pressure. Use when a product leader must present a roadmap to mixed audiences after missing dates before and needs it to inform without over-promising. Do not use for deciding what goes on the roadmap or writing release notes. Related topics: Product, Communication, Planning."
---

# Roadmap Communication Plan

A roadmap communication plan that is useful to sales and customers without turning into a promise, with horizons, per-audience framing, and an answer to date pressure.

## When to use

Use this skill when a product leader must present a roadmap to mixed audiences after missing dates before and needs it to inform without over-promising. Do not use it for deciding what goes on the roadmap or writing release notes.

## Workflow

1. Ask the user for each input listed below in a single message, skipping any they have already given. Where options are listed, offer them, but accept other answers too.
2. Sort items by time horizon and attach a plain-word confidence label to each.
3. Write the near term as commitments and the far term as themes, done when no distant item carries a date.
4. Reframe the content for each audience, noting what sales, customers, and engineering each need to hear.
5. List what is deliberately not being done and why.
6. Write a reply to date pressure and state the update cadence.

## Inputs

- **What is planned** (longer free text)
- **Confidence in each** (longer free text)
- **Audience** (choose any: Executives, Sales, Customers, Engineering, Support, Board)
- **Who is pushing for firmer dates and why** (longer free text)
- **Format** (choose one: Slide deck, Document, Public page, Live meeting)

## Output

A roadmap in the chosen format by horizon with confidence labels, per-audience framing notes, a not-doing list, a script for date questions, and an update schedule.

## Prompt template

Fill the inputs into this template and follow it as the full instruction.

### Roadmap Communication Plan

Plan how to present the roadmap below. Past dates have been missed, so the plan must not recreate that.

- What is planned: {{What is planned}}
- Confidence in each: {{Confidence in each}}
- Audience: {{Audience}}
- Who is pushing for firmer dates and why: {{Who is pushing for firmer dates and why}}
- Format: {{Format}}

Structure the roadmap by time horizon with specificity dropping as it goes out: commitments for the near term, themes for the far term. Label every item with its confidence in plain words.

Adjust the framing per audience, since sales and engineering want opposite things from this document. Include what is deliberately not being done. Give me a way to answer date pressure that is genuinely useful without being a commitment, and say when the roadmap is updated.

## Pitfalls

- Showing quarter dates for speculative items, which sales will quote as promises.
- Using one version for every audience, so the board gets noise and customers get internal detail.
- Offering no answer to date questions, which pushes people to invent their own.
