You've sacrificed long-term stability for short-term gains. How will you tackle the technical debt?

- First and the most important thing is knowing your technical debts at hand. - If you know them then as you do with all other tasks prioritize them according to their importance or future blocking probabilities. - Technical debt is one of the sneaky risk of the business, keeping that in mind gives you great advantage because not only on technical level but also project management level it can be tracked and resource can be allocated when the time comes. - The Last and maybe one of the most important thing is that do not underestimate and never say we can have no technical debt from now on. It has to be ongoing process till the end.

It is important to record, track and prioritise tech debt, whether intentional or accidental. Not all tech debt is created equal. Tech debt that poses high risk to the business and is malignant, i.e., it spreads with every change to the system, needs to be prioritised for remediation. Benign tech debt can be isolated and should be deprioritised. Tech debt can be further ranked based on the ratio of the team effort it consumes over a period of time to the effort required to remediate it. For example, a recurring issue A consumes 24 hours a week and requires 16 hours of remediation effort. Another issue B also consumes 24 hours a week but requires 24 hours to remediate. The team may then prioritise A over B.