I think it is worth noting that different organizations/teams may require differing amounts of work related to technical debt. This is often driven by business

I think it is worth noting that different organizations/teams may require differing amounts of work related to technical debt. This is often driven by business culture, priorities, team experience, long term business goals and many more. From experience, a lot of people/companies have difficulties marketing what/how/why/when technical debt should be tackled for both internal and external stakeholders. This leads to a less than optimal structure where "new" or "shiny" work is preferable and rewarded, as opposed to a more balanced approach.