Software Feature Sunset and Migration Planning Brief

Role: Principal Product Operations Lead specializing in software lifecycle governance and enterprise customer retention.

Context

• SaaS Platform: {{product_name}}
• Retiring Capability: {{deprecated_feature}}
• Replacement Architecture: {{migration_path}}
• Deprecation Schedule: {{sunset_timeline}}
• Impacted User Tier: {{impacted_customer_tier}}
• Maintenance Burden: {{technical_debt_impact}}

Task

Author an executive deprecation planning brief detailing migration milestones, client transition requirements, and operational fail-safes to retire {{deprecated_feature}} safely without customer attrition.

Method

1. Evaluate current usage telemetry for {{deprecated_feature}} across {{impacted_customer_tier}} to identify high-risk accounts.
2. Map functional discrepancies between the legacy component and {{migration_path}} to identify workflow gaps.
3. Establish phased transition gates across {{sunset_timeline}}, balancing release velocity against customer change fatigue.
4. Quantify operational savings and system stability gains tied to resolving {{technical_debt_impact}}.
5. Define high-touch outreach playbooks for enterprise accounts alongside self-serve guidance for standard tiers.
6. Specify telemetry triggers, API sunset warning headers, and hard cutover verification checks.
7. Formulate escalation protocols and temporary rollback criteria for critical production blockers.

Constraints

• MUST specify explicit, quantifiable rollback triggers for technical failure.
• MUST NOT propose indefinite dual-stack maintenance or open-ended grace periods.
• All milestones must fit strictly inside {{sunset_timeline}}.
• Keep recommendations prioritized by customer churn exposure.

Output format

Executive brief containing the following sections:

1. Deprecation Overview (max 100 words)
2. User Impact Assessment (3 key segments evaluated)
3. Milestone Execution Roadmap (table: Phase, Date, Deliverable, Owner)
4. Account Migration Playbook (step-by-step workflow)
5. Safeguards and Rollback Criteria (3 clear threshold triggers)

Self-review

• Ensure all 6 context variables are actively integrated into the plan.
• Verify rollback triggers have objective, measurable operational metrics.
• Confirm deprecation timelines align with enterprise notice norms.