We definitely need to do a better job of explaining technical debt if we continue to use the term.

I don't think I would move away from using it, but I also tend to let the product owners or my clients know when they are rushing something through or doing something that causes tech debt to be created. Right then I will give them a proposal with a time and cost estimate for the tech debt vs if we slowed down to not have to introduce tech debt.

It's kind of like reminding them of the saying of choose either fast, cheap or high quality. When they have to acknowledge the cost up front they tend to be more understanding when tech debt needs created.