Kill switch criteria: when to sunset an internal platform tool

Our org has an internal developer portal that launched 18 months ago with great fanfare. Current adoption: 23% of engineering teams, 40% decline in monthly active users quarter-over-quarter. The original team that built it has moved to other projects. What are your concrete kill switch criteria for internal platform products? We're tracking: - DAU/MAU ratio (currently 0.12) - Support ticket volume (increasing, not decreasing) - Alternative tool adoption (teams building shadow solutions) Looking for frameworks that separate 'needs iteration' from 'needs termination.' Bonus if you've done this without burning political capital — the original sponsor is now VP.