The technical debt log is valuable organizational artifact that should be visible especially to senior management. Please see next table for example.
The previous log doesn’t include attribution to any person. Instead it describes objectively the business situation which caused the creation of the technical debt.
For me the technical debt log should be under biweekly management review. It’s part of the organization sanity checking for its management and quality practices. Technical debt forms the real liabilities of the organization which are not commonly addressed in their financial statement.
Technical debt log is one input for product road-map because it can create the need for future projects for architecture enhancement. This log helps to understand the business value of architecture enhancement instead of limiting the business value to new features only.
The technical debt log can be proponent to drive process improvement on where is the highest return for the buck for process change. It is interesting to see how the business situations are repeatable indicating common pattern in our business practices. This is the essence of change management driven by real data of liabilities.