Should we be discussing the technical debt only?

It seems that these days there's a lot of focus on technical debt. Technical debt is the result of not taking a systemic and holistic view on organization and its development in the area of IT architecture (systems, data, and infrastructure), but rather opting for quick wins and short-term solutions aiming at fixing the problem. However, the same thing could be said when looking at the area of Business Architecture (capabilities, organization, value streams, etc.) Most companies grow without thinking holistically about what needs to change and how to be able to develop their processes and organization in a systemic fashion. This usually creates enormous organizational debt that, sooner or later, will have to be dealt with.