Taught teams to prioritize technical debt with data
I taught a two-hour hands-on Philips University workshop on finding and prioritizing technical debt with code-health analysis; its announcement reached 4,131 people and the program scored an NPS of 83.
- Teaching
- Quality
4,131
people reached
83
program NPS
What would have happened
Teams would treat technical debt as one long backlog, with no clear way to pick the high-impact, low-effort fixes.
The call
Show teams the hotspots in a codebase and start with high-impact, low-effort fixes.
What I did
Ran the hands-on workshop and announced a second session when demand continued.
What changed
The announcement reached 4,131 people and the program scored an NPS of 83.
Proof

Talk details
- Addressing technical debt with CodeScene5 March 2025
