Problem spotlight: How to encourage developers to reduce legacy tech debt as they go?

Let's admit this: there's never time for a wholesale code refactor. Even if there were, it's too risky. The practical alternative for teams that want to keep their velocity at its peak? Promote the developers who can reduce tech debt in systems adjacent to the tickets they're working on. The "Impact Provenance" report spotlights developers who exhibit this repo-saving behavior:

Historical provenance
A developer rewriting code older than two years deserves accolades