Charging Complexity Cost Back to the Team
Why do team restructurings stall?
Four structural forces push back. Inverse Conway's Law freezes past developer culture in the product, so a restructure fights the history in the code. Building new systems is more prestigious than maintaining what exists, so people assigned to new teams want a resume entry. Teams resist losing autonomy, because they cannot ship without waiting on other teams. Transition cost is rarely budgeted: restructurings uncover management holes, leave teams headless, and make specialized roles redundant. McKinsey's finding, cited in the article, is that roughly two-thirds of transformation programs fail, mostly for social and emotional reasons.
How should a company charge complexity back to the people who created it?
Treat complexity the way FinOps treats cloud spend. Tag every fast-path feature with the team that shipped it, the leader who approved it, and the Sync Tax increment it created. Show each team its accumulated complexity cost quarterly. Charge it back to the team budget when the cost exceeds a threshold. A bonus tied to a quarterly Sync Tax Multiplier below a threshold, the article uses 1.1 as the example, pays the team that kept the system clean. Without the metric, the person who prevented the failure stays invisible.
Get notified when new content drops