Feature Sunset Communication

J

Jordan Reyes

@jordan-reyes

·

Plan thoughtful feature deprecation communications for all stakeholders

9 copies0 forks
Draft a communication plan for sunsetting {{feature_name}}.

Context:
- Why we are sunsetting: {{reason}}
- Users affected: {{affected_users}}
- Timeline: {{timeline}}
- Alternatives available: {{alternatives}}

Create:

**Internal Communication**
- Announcement to support/sales teams
- FAQ for handling customer questions
- Escalation path for exceptions

**External Communication**
- Initial announcement (email + in-app)
- Reminder communication schedule
- Final deprecation notice

**Migration Support**
- Self-service migration path
- Resources and documentation
- Hands-on support criteria

**Key Messages**
- Acknowledge impact on users
- Explain the reasoning honestly
- Emphasize continued commitment
- Clear timeline and next steps

**Objection Responses**
- Common concerns and responses

Tone: Empathetic but firm. Do not over-apologize.

Details

Category

Productivity

Use Cases

Feature sunset planningCustomer communicationChange management

Works Best With

gpt-4claude-3
Created Updated Shared

Create your own prompt vault and start sharing