Product Management5.0 · 0 ratings

Feature Kill Or Keep Decision Memo

Evaluates a low-performing feature against usage, cost, and strategy to recommend keep, fix, or sunset with a migration plan.

Role-Based

Prompt

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.

How to use this prompt

  1. 1

    Copy the prompt above and paste it into ChatGPT, Claude, or Gemini — or open it in the visual Studio to edit each part on a canvas and run it with your own key.

  2. 2

    Replace any bracketed placeholders with your specifics. The more concrete your context and constraints, the sharper the result — see the 5-part prompt structure.

  3. 3

    Run it, then refine. Ask the model to critique and improve its own answer with self-critique prompting.

Techniques in this prompt

Role-Based

Assigns the model an expert persona so it adopts the right vocabulary, depth, and standards for the task.

Learn this technique

Recommended models

claudegpt-4ogemini

Build on this prompt

Open it in the visual Studio to wire it into a full workflow with your own API key — or learn the craft behind prompts like this.

Open in Studio How to prompt AI correctly

More in Product Management

Pressure-Tested Product Requirements Document

Drafts a complete, engineering-ready PRD with problem framing, scope boundaries, success metrics, and explicit non-goals.

Read prompt

RICE Prioritization Scoring Engine

Scores and ranks a backlog using RICE with transparent assumptions, sensitivity flags, and a defensible recommendation.

Read prompt

Jobs-To-Be-Done Interview Synthesis

Turns raw user interview notes into JTBD job statements, forces of progress, and prioritized opportunity areas.

Read prompt

Quarterly Product Roadmap Narrative

Builds an outcome-driven quarterly roadmap organized by themes and bets, with confidence levels and dependencies surfaced.

Read prompt