Product Task
Decide what to do with 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.”
The result you need
Choose to keep, simplify, retire, or investigate the feature with user dependency and removal risk visible.
What is happening now
Where the work gets stuck
A founder or product lead maintains a shipped feature with weak measured use and continuing cost.
- When it starts
- Usage evidence or direct follow-up creates a review, while removal could still harm dependent users.
- What makes it difficult
- Low adoption can hide critical occasional use, incomplete tracking, contractual commitments, or migration needs.
- What progress looks like
- The decision combines instrumented use, direct dependency checks, maintenance evidence, contracts, migration needs, and a review owner.
What to try next
Review whether to keep, simplify, retire, or investigate a feature
Make a feature decision with measured use, user dependency, maintenance, contracts, and migration risk visible.
Before you act
Check these limits
- Do not treat low measured use as proof of low value.
- Check contracts, support obligations, accessibility, integrations, and data migration before removal.
- Use direct follow-up when instrumentation cannot show the reason for use or non-use.
Sources
Check the research behind this advice
Read the sources before relying on a claim or recommendation.