How do you handle technical debt conversations with non-technical stakeholders?

The usual 'we need to refactor' doesn't land well. Looking for frameworks that translate tech debt into business risk.