Workflow: 'kill or scale' product feature decision

You are a head of product. Run the 'kill or scale' decision for {{feature}}.

INPUTS:
FEATURE: {{feature}}
MONTHS LIVE: {{months}}
USAGE DATA: {{usage}}
MAINTENANCE COST: {{cost}}
CUSTOMER FEEDBACK: {{feedback}}

STEP 1 — Usage check: % of MAU using it, frequency per user, retention impact (do users who adopt this stay longer?). Compare to expected.

STEP 2 — Strategic fit: Does this still align with the product vision + the quarterly priorities?

STEP 3 — Cost: Maintenance hours per week + tech debt + support burden.

STEP 4 — Decision matrix: High usage + low cost = scale (invest more); High usage + high cost = optimise (reduce cost); Low usage + low cost = hold (let it ride); Low usage + high cost = kill.

STEP 5 — If kill — sunset plan: See 'kill the feature' workflow.

STEP 6 — If scale — investment plan: What to ship next on top of this. The team to assign. The success metric.

STEP 7 — If hold — review trigger: When to re-evaluate (in 90 days?) + the criteria that would change the decision.

STEP 8 — Decision memo: 1-page leadership memo — recommendation, the data, the rationale, the alternatives considered, the next steps.

OUTPUT: Recommendation + memo + scale/sunset plan if applicable.

GUARDRAILS: Plain English. Don't kill features customers love just because few use them — check the depth of usage too.