I agree with this. I also find it useful for the team once they have identified an area or specific aspect of what they perceive as technical debt to tackle to

I agree with this. I also find it useful for the team once they have identified an area or specific aspect of what they perceive as technical debt to tackle to take the various ideas they have for tackling it and do a very rough value Vs effort exercise together. Just having that conversation can reduce both perceived technical debt (people explain to other people why it works in that way and that's the right solution) but also team angst about the issue as they get to tell other people about it. Whatever is the easiest, highest value things normally pop out and you can slowly work through them with better understanding. It also means you don't start work on the hardest to solve peeve of a single individual just because they are the loudest voice.