Product Task
Review an unused product feature
A shipped feature shows weak use while it still adds maintenance, support, and future product constraints.
“This is costing me maintenance capacity while the feature’s present value and removal risk remain unclear.”
Outcome
The result to aim for
Choose to keep, simplify, retire, or investigate the feature with user dependency and removal risk visible.
Best practices
- Bring the feature definition, instrumented events, support records, known users, contracts, integrations, maintenance work, and accountable owner.
- Define the feature from reviewed events, inspect adoption and frequency, and document missing platforms, untracked paths, shared accounts, and occasional critical use.
- Choose keep, simplify, retire, or investigate; then record the evidence, contrary cases, maintenance effect, customer communication, migration plan, reversibility, and review trigger.
- Confirm that the decision states the analytics coverage and gaps.
- Do not retire a feature from adoption data alone.
Related sources
Further information
- Documented guidance: Hacker News: When users never use the features they asked for
- Related guidance: Hacker News: How do you build a bare minimum feature?