Dealing with problems begins with accurately identifying them. Emphasis on accuracy; so why disable accuracy from the very beginning by poor communication?
“Technical debt” is a trendy but weak-minded neologism that disguises what it refers to with an illusion of intelligence. Want to get started on this issue? Then drop the “technical debt” and call it what it is: unfinished work.
Work is probably unfinished because the developer wasted so much time writing useless unit tests, that being the fad of the last decade so some fraud could make money on a book. Drop the unit tests; hire separate QA people to write regression suites and have developers do just enough testing to not waste QA time finding bugs in core functionality.
And while you’re at it give back developers’ freedom to focus: drop all recurring meetings, get rid of the agile and scrum nonsense, work from requirements and functional specifications.
Go back to what worked before.
“Tech debt” (spits)