Sub-skill of product-roadmap: How to Communicate Changes (+1).
Scanned 9/9/2026
Install to Claude Code
Skills Directorynpx -y skills add vamseeachanta/workspace-hub --skill how-to-communicate-changes --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of How To Communicate Changes?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/vamseeachanta-how-to-communicate-changes)More formats (shields.io, HTML) on the badges page.
---
name: product-roadmap-how-to-communicate-changes
description: 'Sub-skill of product-roadmap: How to Communicate Changes (+1).'
version: 1.1.0
category: business
type: reference
scripts_exempt: true
---
# How to Communicate Changes (+1)
## How to Communicate Changes
1. **Acknowledge the change**: Be direct about what is changing and why
2. **Explain the reason**: What new information drove this decision?
3. **Show the tradeoff**: What was deprioritized to make room?
4. **Show the new plan**: Updated roadmap with the changes reflected
5. **Acknowledge impact**: Who is affected and how?
## Avoiding Roadmap Whiplash
- Do not change the roadmap for every piece of new information
- Batch roadmap updates at natural cadences (monthly, quarterly)
- Distinguish between "roadmap change" (strategic reprioritization) and "scope adjustment" (normal execution refinement)
- Track how often the roadmap changes
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
Designs system architecture, component specifications, and technical integration strategy. Use when: designing solutions, system architecture, technology stack, or integration approaches.
