Briefs · product
Feature Kill / Keep Decision
Decide whether to invest in, fix, or kill an underperforming feature.
You walk away with
A clear kill / keep / fix verdict with the reasoning and next step.
Decidi convenes
◻️ The Minimalist🔬 The Data Skeptic💎 The Customer Success Lead🙋 The End-User Advocate🎯 The Product Strategist😈 The Devil's Advocate
Recommended level: Standard — Proven pro models — the everyday default.
What the council debates
We have a feature that is underperforming and we need to decide: double down, fix, or kill it. THE FEATURE: [describe the feature, why it was built, and the original goal] THE DATA: [usage, retention impact, support load, maintenance cost — whatever you have] THE CASE FOR KEEPING: [who loves it, what it enables] THE CASE FOR KILLING: [the cost, the distraction, the alternative use of effort] Debate: 1. Is this underperforming because it is wrong, or because it was under-built / under-marketed. 2. The true ongoing cost of keeping it (maintenance, complexity, cognitive load on users). 3. What killing it would actually cost — users, trust, edge cases. 4. The opportunity cost: what else could that effort do. FINAL SYNTHESIS: - A verdict: KILL, KEEP-AND-INVEST, or FIX-THEN-REASSESS. - The reasoning in three lines. - If keeping: the smallest change to make it earn its place. If killing: how to do it cleanly.
Related briefs
Pre-Launch App UX Audit
An exhaustive UX teardown of your app before you launch it.
Pre-Launch App UI Audit
A visual and UI teardown of your app — hierarchy, type, polish, dark mode.
Product Roadmap Prioritisation
Decide what to build next quarter and what to deliberately not build.
Pricing & Packaging Strategy
Design pricing, tiers and the value metric that scales with what you deliver.