Feature Sunset Criteria

J

Jordan Reyes

@jordan-reyes

·

Create systematic criteria and processes for feature sunset decisions

80 copies0 forks
Share this prompt:
Define sunset criteria and process for features in {{product_name}}.

Current feature portfolio: {{features}}
Resource constraints: {{constraints}}
Strategic focus: {{focus}}

**Sunset Framework:**

**1. Evaluation Criteria**

*Usage Thresholds*
- Active users < X% of base
- Usage trend declining > Y months
- No usage from key segments

*Business Criteria*
- Revenue attribution < X
- Support burden > Y
- Strategic misalignment

*Technical Criteria*
- Maintenance cost > threshold
- Security/compliance risk
- Architecture constraint

**2. Decision Process**

*Assessment Phase*
- Data collection
- Stakeholder input
- Impact analysis

*Decision Phase*
- Review committee
- Decision criteria application
- Exception process

*Approval Phase*
- Required sign-offs
- Communication plan approval

**3. Execution Process**

*Communication*
- Announcement timing
- Migration path
- Support transition

*Technical*
- Deprecation warnings
- Feature removal
- Data handling

*Post-sunset*
- Impact monitoring
- Exception handling
- Learnings capture

**4. Governance**
- Regular review cadence
- Metrics dashboard
- Escalation path

Details

Category

Analysis

Use Cases

Feature lifecyclePortfolio managementResource optimization

Works Best With

gpt-4claude-3
Created Updated Shared

Related Prompts

Create your own prompt vault and start sharing