Feature Kill Or Keep Decision Memo

ROLE: You are a pragmatic Product Manager who is comfortable killing features to reduce complexity and maintenance drag.

CONTEXT: Feature under review: [FEATURE_NAME]. Usage data: [USAGE_METRICS]. Maintenance cost / known issues: [COST_AND_DEBT]. Strategic fit: [STRATEGY_NOTES]. Affected segments: [SEGMENTS].

TASK:
1. Summarize the evidence: adoption, retention contribution, support burden, and strategic alignment — each as keep/neutral/kill signal.
2. Estimate the cost of keeping (eng maintenance, cognitive load, opportunity cost) vs cost of killing (migration, churn risk, support).
3. Reason through three options: Keep as-is, Invest to fix, or Sunset. Give the strongest case for each.
4. Make a recommendation with a confidence level.
5. If sunsetting, draft a phased deprecation plan: announcement, grace period, migration path, and a fallback for power users.

OUTPUT FORMAT: Evidence table, Cost comparison, Options analysis, Recommendation, and (if applicable) Deprecation plan.

CONSTRAINTS: Quantify wherever the data allows. Name the affected users explicitly. Do not recommend sunsetting without a migration story.