Technical debt is a phrase coined by wiki creator, Ward Cunningham, that refers to an approach where best practices haven’t been followed in the short run. This creates a context in which the same work will cost more in the long run instead of applying the best overall solution.
During the 2020 Salesforce TrailheadDX , Principal Success Guides, Joshua Maples and Chauncey Canfield discussed reasons why Salesforce orgs get cluttered with the technical debt and what can be done to resolve it.
To begin, it’s best to understand what kind of state you’re currently working in. Symptoms such as complexity, confusion, slower performance, or project delays are typical of a cluttered Salesforce org. Some potential root causes for those symptoms are: