Structural Debt: What It Costs and Why It Has No Due Date

Structural debt in an organization has no due date. But you can certainly see it and feel it. An approval hierarchy built for what the company looked like three reorganizations ago; a reporting line that made sense under a leader who left years earlier; a system that changed hands twice after it was purchased and that nobody has clearly owned since: none of it comes with a date attached. It can compound for years, without anyone being required to address it. That’s how an organization ends up explaining the same dysfunction to its third consecutive change leader, each one diagnosing the problem fresh because nothing ever forced an earlier fix.

I’ve written two earlier pieces on structural debt: a blog post and a LinkedIn Article, both published earlier this year. Both cover the same ground: Ward Cunningham's technical-debt analogy applied to organizational design, and three examples of what structural debt looks like. This article assumes you’re familiar with what structural debt is and expands on what those articles only touched on briefly. What does the lack of a due date do to an organization, and why does the bill go unnoticed until it's too big to ignore? Even a balloon payment, the kind that lets you pay next to nothing for years before one lump sum comes due, still has a date on the calendar. Structural debt doesn't even get that.

McKinsey's 2020 survey of 50 CIOs at financial-services and technology companies with revenue above $1 billion found that technical debt already consumed 20% to 40% of the value of the entire technology estate, and that another 10% to 20% of the budget earmarked for new products was being redirected to service it instead. Roughly 60% of the CIOs said their debt load had risen over the prior three years.

That study is six years old, and it measures technology debt load, not the organization as a whole. It’s a useful reference anyway. It is a documented figure for the same underlying mechanism: deferred maintenance diverting a growing share of forward capacity. Unfortunately, I found no comparable figure for structural debt at the organizational level. The harder problem is that structural debt resists this kind of measurement in the first place. No line on a balance sheet captures slow decision-making, processes bogged down by approvals nobody remembers assigning, or hierarchies built for a version of the company that no longer exists. None of it can be tied to a single line item the way financial debt can.

Financial debt appears as an expense on a statement, a line item anyone can understand even if you’re not a finance professional. Structural debt buries the same expense inside "the way we've always approved things here," where nobody has been assigned to look at why the approval happens that way. The cost is real. The lack of a due date is what keeps it off anyone's task list.

This is where the two kinds of debt stop behaving alike in a way that matters for who ends up owning the problem. A CFO inherits a balance sheet with the debt already itemized. A new CHRO or a new country manager inherits an org chart with the debt built into the reporting lines, undocumented, and is expected to diagnose it from scratch. Every leadership transition in a structurally indebted organization repeats the same discovery work the last one already did, because nothing about the structure ever forced anyone to pay it down.

One CEO came to me already convinced he knew the problem: "We have weak leadership. They can't handle stress. They keep burning out." He was right about the burnout. His leaders truly were overwhelmed. Where he was wrong was in his diagnosis. He'd looked at a symptom and diagnosed a disease without running a single test.

If we had moved forward with his diagnosis, I would have built and delivered a strong leadership development program. And it would have failed. Worse, it would have exacerbated the situation by piling on more workshops, more training, more time pressure onto people who were already stretched too thin. You cannot treat a disease with the wrong cure, and in this case the wrong cure wouldn’t have just missed the problem. It would have made it worse.

So before taking his diagnosis at face value, I asked him and several of his leaders to each complete the Organizational Adaptability Pulse Check on their own, the test his original diagnosis had skipped. What came back pointed somewhere else entirely. The leaders were not weak. They were operating in a structure working against them.

The Pulse Check is only quantitative, though. It told us the direction was structural debt, not where the debt actually lived. For that, we moved to the full Adaptive Capability Diagnostic, which located it. It was unclear governance, tangled approval chains, and decision-making nobody could fully account for.

Time was the clearest example. Managers were burning out and leaving, and the reason, repeated in nearly every conversation, was too many meetings and too little time for the work the job actually required. I started by asking one leader to share his calendar with me.

He had accepted a standing meeting years earlier, during a major project where he was deeply involved and his input shaped real decisions. His part in the project ended. The meeting did not. He kept attending despite no longer contributing anything useful, because nobody had ever revisited the invitation once the reason for his involvement disappeared. Roughly half his week looked like that meeting: present, silent, uninvolved in whatever got decided.

Multiply that by 27 managers carrying the same kind of inherited obligation, add approval chains nobody could currently explain and sign-offs required from people whose actual responsibility had moved on years earlier, and what looked like one overbooked executive's problem turns out to be standard operating procedure.

The real barrier wasn't logistics. Leaders were afraid that declining a meeting would look rude, or like they weren't supporting the initiative it belonged to. So the fix started with permission, not a script. I asked the CEO to tell his leadership team directly that stepping back from meetings where they added nothing was good leadership, and that he supported it.

Once that was said out loud, leaders started sending their own versions of the same message: something like, "Based on the last few meetings, I don't think I'm adding value here in terms of decisions or information. Could you remove me from future invites? Happy to rejoin if that changes." Multiplied across the leadership team, and paired with unwinding the legacy approval chains alongside it, that shift changed the numbers directly: their calendars went from 92% of working hours booked in meetings to 41%. What remained were the meetings where they were actually needed, to make a decision, give input, or get information that mattered.

None of that ever showed up as a cost anywhere leadership was looking. Their prior work culture was expensive. It just never had a line item on a budget sheet, so nobody had ever addressed it.

Technical debt has instruments: static analysis, dependency graphs, a number a CIO can put on a dashboard. Structural debt has none of that. A skeptical reader is right to ask how anyone measures something with no dashboard attached to it. The answer is that structural debt gets assessed rather than metered: a calendar reviewed, questions asked, a pattern found and multiplied across the people carrying it, not a single number pulled from a dashboard. That’s not a weaker method. It is the right one for debt that lives in decisions and relationships rather than in code, and it is the model the Adaptive Capability Diagnostic uses for exactly this reason.

None of this changes the basic asymmetry. Financial debt sends a statement: a due date, a balance, a warning before a missed payment becomes a real problem. Structural debt sends nothing. No notice goes out when an approval chain from a reorganization five leaders back is still routing decisions nobody remembers assigning, or when a standing meeting invented for one project outlives that project by years. The debt accrues either way. Financial debt tells you when it is due. Structural debt tells you nothing at all, and sends a person instead of a statement: a leader, then another, each one inheriting a structure nobody was ever forced to look at sooner.

If any of this sounds familiar to your organization, the Organizational Adaptability Pulse Check is a free starting point: twelve questions and about five minutes. For anyone who already knows the answer, a conversation with me is the next step.

One more thing before you go. A short survey on organizational adaptability is open right now. It only takes a few minutes and is for anyone leading or living through transformation this year. It is not a big industry study, just a pulse check, and the results become a public report anyone can cite. Worth a few minutes if useful to you: take the survey. It closes September 30.