Debt accumulating in our user interfaces is created by similar means as technical debt in code: Unclear direction, undocumented decisions, pressure to meet deadlines… It is also impossible to refactor without affecting (end)users.
I wonder if we should include this kind of debt, too (since many of the causes and effect follow a similar pattern) or if we might create another discussion on it (since it has some unique features and represents itself in UI, not code)