Feature Sunset Communication Plan

J

Jordan Reyes

@jordan-reyes

·

Plan comprehensive communications for feature deprecation

75 copies0 forks
Share this prompt:
Create a communication plan for sunsetting {{feature_name}}.

Sunset context:
- Reason for sunset: {{reason}}
- User impact: {{user_count}} active users
- Timeline: {{timeline}}
- Migration path: {{migration_option}}

Communication plan:

1. STAKEHOLDER MAPPING
| Stakeholder | Impact Level | Key Concerns | Comm Channel |
|-------------|--------------|--------------|---------------|

2. MESSAGING FRAMEWORK
- What is happening (clear, factual)
- Why this decision was made
- What users should do
- How we are supporting the transition
- What happens if they do nothing

3. COMMUNICATION TIMELINE
| Date | Channel | Audience | Message Focus | Owner |
|------|---------|----------|---------------|-------|
| T-90 days | | | | |
| T-60 days | | | | |
| T-30 days | | | | |
| T-14 days | | | | |
| T-7 days | | | | |
| T-day | | | | |

4. FAQ DOCUMENT
Anticipate and answer top 10 questions.

5. ESCALATION PATH
- Support tier handling
- Executive escalation criteria
- Exception request process

Details

Category

Productivity

Use Cases

Plan feature sunsetsCommunicate deprecationManage user transitions

Works Best With

gpt-4claude-3
Created Updated Shared

Related Prompts

Create your own prompt vault and start sharing