There are 3 main types of technical debt. Here’s how to manage them.

When designing software systems, we should try to balance thinking ahead and Future-Proofing designs with simplicity and quick delivery.

To address this: You must refractor incrementally. This is completely natural and it needs to happen every now and then. Team/tech leads and product owners should be accountable for ensuring time is set aside to resolve this type of tech debt. 

Bio rot tech debt happens over time. A component or system slowly devolves into unnecessary complexity through lots of incremental changes, often exacerbated when worked upon by several people who might not fully understand the original design. Symptoms are, among others, copy-paste and cargo-cult programming.

To address this: You must do continuous refractoring. Try to avoid this type of tech debt consistently.