Article · 10 min read
When to sunset a feature
Lenny Rachitsky · Lenny's Newsletter Freemium Intermediate
A practical checklist drawn from many product leaders on the exact question of when a feature has earned its removal. It gives you the concrete signals (low usage, high maintenance, off-strategy) and how to actually retire something without burning the few users who rely on it. This is the closest thing to a decision framework for your question.
- Look at usage, maintenance cost, and strategic fit together, not one alone
- Set a clear bar in advance so the call is not emotional
- Give the few remaining users a real off-ramp and an explanation
