Usage depth (who, how often, how central), maintenance cost, and strategic fit — the feature used weekly by your ten biggest accounts is not the same 'low usage' as the one nobody opened since 2024.
Where does the workflow go — a better feature, an export, a partner tool? Announce the path with the deprecation, never 'figure it out by June.'
In-app notices to affected users specifically, staged milestones (no new adoption → read-only → removed), and enterprise-customer conversations before the email blast — change management applies to subtraction too.
Retired code deleted (not flag-hidden forever), docs updated, and the maintenance capacity visibly redirected — sunsetting pays only if you actually collect.
Skipping the discipline this article describes until an incident, audit, or stalled project forces it — every practice above is cheaper adopted early than retrofitted under pressure.
Let's discuss how we can help you with feature sunsetting deprecation.