product-roadmap-communicationlisted

# Roadmap Communication ## Purpose A roadmap presented as a single list of dated items is read by everyone as a set of promises, including the items that were speculative. When the speculative ones slip, the credibility of the committed ones goes with them. This skill separates commitment levels explicitly, matches date precision to real confidence, and fixes the rule for telling people when something changes. ## Prerequisites - **Inputs:** the item list with, for each, the current delivery status, the evidence behind its date, and whether it is funded and staffed. - **Required decisions:** who has authority to declare an item committed. If nobody does, everything is at most planned. - **Access:** the audience definition — internal delivery, internal executive, customer, or public. The same roadmap is communicated differently to each and should never be forwarded between them unchanged. If an item's commitment level cannot be established with its owner, do not publish it. An item on a roadmap with no stated level defaults, in the reader's mind, to committed. ## Data classification **Internal** for internal audiences; a customer- or public-facing roadmap is **Public** only after the commitment owner and, where a commercial relationship depends on it, your legal owner has approved it. Unreleased plans shared with a customer normally require a confidentiality agreement — check before sending. Do not include named customer commitments, deal-specific dates, or accou