6% of users eat 18% of your maintenance

Today's warm-up: Sunset Or Spin-Off (Senior PM · Stakeholder Management)

A legacy feature set has 6% MAU usage but consumes 18% of maintenance capacity — and complicates onboarding for everyone else. Engineering says it drags velocity and grows the bug surface. Sales says a few accounts depend on it; no surprises. The CFO's position: if it stays, it should pay for itself. Sunset it with a migration plan, spin it into a paid add-on, or leave it alone? Somebody's roadmap is about to lose 18% of its capacity either way.