If you're going to have to spend the time doing the work, you might as well talk about it in a way that's actually beneficial to the organization as a whole.
Sorry, but I don't think those examples are really technical debt. They are just routine maintenance projects. By your description, anything could be technical debt.
Real technical debt is a substantial risk to the business in some way. Something that comes up in company wide executive meetings because it is a such a big deal.
For example, the code is on an old JS framework that is unsupported and you can't hire anyone to work on it anymore. Or you are behind on the version of Elasticsearch and it will take months to do the upgrade.
Real technical debt projects are big major problems.
Sorry, but I don't think those examples are really technical debt. They are just routine maintenance projects. By your description, anything could be technical debt.
Real technical debt is a substantial risk to the business in some way. Something that comes up in company wide executive meetings because it is a such a big deal.
For example, the code is on an old JS framework that is unsupported and you can't hire anyone to work on it anymore. Or you are behind on the version of Elasticsearch and it will take months to do the upgrade.
Real technical debt projects are big major problems.