64 lines
961 B
Markdown
64 lines
961 B
Markdown
# Communication Templates
|
|
|
|
## Stakeholder Update Email
|
|
|
|
Subject: Product roadmap update - [Period]
|
|
|
|
Hi [Audience],
|
|
|
|
Here is the [weekly/monthly/quarterly] product update.
|
|
|
|
- Progress:
|
|
- KPI movement:
|
|
- Risks/blockers:
|
|
- Decisions needed:
|
|
- Next period focus:
|
|
|
|
Thanks,
|
|
[Owner]
|
|
|
|
## User-Facing Release Notes Template
|
|
|
|
# Release [Version/Date]
|
|
|
|
## Highlights
|
|
- [User value outcome]
|
|
|
|
## New
|
|
- [Feature + benefit]
|
|
|
|
## Improved
|
|
- [Improvement + impact]
|
|
|
|
## Fixed
|
|
- [Issue + user-facing resolution]
|
|
|
|
## Known Limitations
|
|
- [If applicable]
|
|
|
|
## Internal Release Notes Template
|
|
|
|
# Internal Release [Version/Date]
|
|
|
|
## Scope
|
|
- Included workstreams and commit range
|
|
|
|
## Operational Notes
|
|
- Rollout plan
|
|
- Monitoring checks
|
|
- Rollback criteria
|
|
|
|
## Risks
|
|
- Known issues and mitigations
|
|
|
|
## Feature Announcement Template
|
|
|
|
Title: [Outcome-focused headline]
|
|
|
|
1. The problem:
|
|
2. The new capability:
|
|
3. Why this matters:
|
|
4. Who should use it:
|
|
5. How to start:
|
|
6. Feedback channel:
|