Kaizen Master - Solution for Technical Debt (and Legacy Code)

(a short cookbook is at the bottom of the page) ~70% of developers call technical debt the main obstacle in their job. The problem scale estimates ~$2.4 trillion/year loss only in the US (e.g. CISQ report , AEIdeas Post ). Yeah, that much! Programmers and managers notice: the first 1-2 years a product is fine, but then you see 30-60% time being spent on fixing. The company becomes nearly paralyzed. As an engineering manager, I thought about it and during the last 1.5 years tried an approach based on Kaizen. Its goal is to gradually reduce technical debt without rewiring much resources. And, chief, it gave results! Speed-Quality Dilemma Devs often don’t have time to study a case deeper and find a better solution. Instead, they commit a fast one. It causes accumulative quality decline, including system effect - when several problems cause more damage than a simple sum of them. You get a hole in your pocket, through which resources crumble. Gentler deadlines or maintenance procedures add