roadmap-communicationlisted

# Roadmap Communication ## Goal Translate product plans and shipped changes into audience-specific communication that sets expectations without overcommitting uncertain work. ## Workflow 1. Identify audience: executives, engineering, design, sales, support, customers, partners, or public release readers. 2. Choose the right format: now-next-later, theme roadmap, milestone timeline, release note, launch memo, customer announcement, or internal changelog. 3. Separate committed work from directional intent and discovery bets. 4. Link every item to outcome, user value, scope, owner, status, risk, and dependency. 5. State confidence and timing precision honestly. Avoid exact dates when the plan is still discovery-led. 6. For release notes, lead with user-visible value and call out behavior changes, migration needs, limitations, and known issues. 7. For internal updates, include blockers, decisions needed, cross-functional asks, rollout, monitoring, and rollback notes. 8. Check that launch-sensitive claims have source, approval owner, and review status. ## Output - Audience and communication goal - Roadmap or release-note format - Message hierarchy - Status, owner, risk, and dependency table - Open decisions and approval needs - Draft communication artifact ## Quality Bar - The artifact fits the audience instead of reusing one generic update. - Uncertain work is not presented as committed. - User-facing copy does not expose internal implementation noise. - Internal copy nam