How would you approach sunsetting a product or feature that users still rely on?
Model answer
Model answerSunsetting something users rely on is a trust operation, not just a product decision. I'd start with a migration plan before announcing anything — users need somewhere to go. Then I'd announce early (6 months minimum for critical features), communicate frequently, and offer hands-on migration support for high-value users. The biggest mistake: being vague about the timeline because you're afraid of pushback. Clarity is kinder than ambiguity.
Framework · Feature Retirement
- MMigration first
Define where users go before announcing what's going away - EEarly announcement
6 months minimum for anything critical — don't spring it on users - SSegment high-impact users
Who relies on this most? Give them white-glove migration support - CClear timeline
Vague timelines feel dishonest — give a hard date and stick to it
Related questions
- How would you define the product vision for an AI assistant in a consumer app?
- How would you manage building a platform product that serves both internal teams and external customers?
- How do you build a product roadmap when company strategy shifts mid-year?
- How do you align multiple product teams around a single company strategy?
- How do you decide when a product is ready to scale?