What’s Slowing Your Engineering Organization Down

Engineering leaders often say: You ship your org chart. It’s another way of describing Conway’s Law—the idea that system architecture tends to mirror organizational structure. But there’s another implication that gets discussed much less: you also ship the debt inside that organization chart. It’s the hidden cost of decisions made in org charts instead of code. Every engineering leader understands technical debt. The shortcuts in code, the migrations that stalled, the tests that never got written. We have frameworks for it, we budget for it, and we talk about it in every planning cycle. But there’s a twin that lives in the org chart, and it’s at least as dangerous. I call it organizational debt. Organizational debt accumulates when the people side of an engineering organization evolves through expedience rather than design. It’s the structural compromises you make, reasonable in the moment, that quietly compound until they constrain everything you’re trying to do. If technical debt is the mismatched LEGO pieces in your castle, organizational debt is something else entirely. It’s building that castle with a crew where only one person understands how the drawbridge works, half the team is on loan, and the blueprints exist only in someone’s head.…