organizationalcapabilitydebt.com  ·  a Management Alchemy framework

Organizational Capability Debt

The gap between what the change requires and what the organization can currently deliver.

Every organization has it. Most of them do not know it yet.

75% of ERP implementations fail to deliver their promised results. That number has not moved in forty years. Not since MRP. Not since MRP II. Not since ERP. Not since the cloud. Not since SaaS. Not since AI.

The technology gets better every cycle. The failure rate does not. Which means the problem was never the technology. The problem is a debt nobody has been reading on the balance sheet — because nobody has been putting it there.

Financial debton the balance sheet
Technical debtin the codebase
Organizational Capability Debtnowhere — unmeasured
The only one of the three most companies have never recorded.
See if your next initiative carries capability debt →

Definition · War story · Framework · Talk to Dominic

The Definition

Organizational Capability Debt (noun) — the gap between what an organizational change requires and what the organization can currently deliver.

It occurs whenever a company commits to a change — an ERP selection, an integration, a new market entry, a supply chain redesign, a business model shift, a new hire, a new department, any functional addition — without a full accounting of the capability the organization already has and the capability the change will require.

Financial debt shows up on the balance sheet. Technical debt shows up in the codebase. Organizational Capability Debt shows up in the gap between the org chart and what the work actually requires — and it is the only one of the three that most companies have never measured.

Left unmeasured, it compounds. It gets paid eventually. It just gets paid in currencies most CFOs do not track: missed timelines, exhausted teams, replaced executives, vendor blame, consultant blame, and eventually the quiet write-down of an initiative that was supposed to be transformative.

Every organization has Organizational Capability Debt. The organizations that measure it before the vendor contract is signed are the organizations whose implementations end up in the 25% that succeed.

How to See It in Your Own Organization

Three questions. Ten minutes. You will know whether your next initiative has Organizational Capability Debt on the balance sheet before you write the check.

Question 1

What does this change actually require, capability by capability?

Not headcount. Not budget. Not timeline. Capability. Break the initiative into the specific things a person or a team has to be able to do — cross-functionally, not just within their role — for it to succeed on day one, day ninety, and day three-hundred-and-sixty-five.

Write them down. Be specific.

"Understands the process" is not a capability.
"Can identify when a Tuesday shipment is at risk on Monday afternoon and knows who to talk to before the manifest closes" is a capability.
Question 2

For each capability on that list, which of these three is true?

Trainable in round one. The person or team can absorb the new capability within the initiative's initial rollout period.

Trainable with a longer runway. Developable, but it will require more time than the initiative's current timeline assumes.

Not present, and not developable in the current team. Requires an outside hire, a restructure, or a change to the initiative's scope.

If most of your list falls in bucket one, the initiative is under-scoped and you are about to be surprised. If most falls in bucket three, it is under-resourced and you are about to blame the wrong people when it slips. Bucket two is where most real work lives — and the bucket most organizations skip, because it requires a plan that lasts longer than the current quarter.

Question 3

Who on your team already carries part of the answer, and has anyone actually asked them?

Every organization contains people who already know what the initiative requires. They have watched a version of it before — in a previous role, a previous company, a previous decade. They rarely volunteer this knowledge, because volunteering it usually costs them something and offering it up is rarely rewarded.

If you cannot name three people in your organization who have knowledge you have not yet extracted, that is not a sign your organization lacks the knowledge. It is a sign of the debt.

The three questions do not solve capability debt. They surface it. Surfacing is the work most organizations skip. Solving is the work most consultants skip.

What Capability Debt Looks Like in the Real World

Nine months. Ten minutes. The answer was already in the building.

A global luxury bed manufacturer had a problem their own standard wouldn't let them ship. For nine months, product was coming off the line not meeting standard — not every piece, not predictably, which is exactly what made it so hard to catch. Every engineer had looked. Every manager had a theory. The COO had run the analyses. Nothing held.

I was brought in to lead a different project — an ERP replacement. Cross-functional training was part of my methodology, not the contracted scope. And the training was working: put production, engineering, and the floor in one room, make it safe to talk, and things surface.

The problem came up in one of those sessions. We put it on the table — nine months of it — and the room did what rooms full of experts do. Theories. Debate. Every angle but the right one. We ended no closer than we started.

At the end of that session, one young worker stayed behind. He'd said nothing while the room worked the problem. He waited until everyone else had gone. Then he told me he knew what it was.

Ten minutes on the shop floor, in front of the COO and the engineers. Resolved.

That was never a quality problem or an engineering problem. The answer had been in the building the whole time — it had even been in the room. What was missing was the capability to reach it: to ask, and to hear the answer when it came from someone the organization wasn't used to hearing from.

That is what Organizational Capability Debt looks like when you finally see it. It is almost never what the organization thinks it is looking at.

Where Capability Debt Shows Up

Capability debt is not an ERP concept. It applies wherever an organization commits to a change that requires more of the organization than the organization currently is.

ERP selection and implementation. The largest, most visible instance. Where the 75% failure rate lives, and where the human layer is treated as a soft add-on — the first thing cut when timelines compress.
Post-acquisition integration. The 100-day plan assumes capability the acquired company does not have. The synergies do not materialize. The blame goes to culture, when what was missing was the capability assessment nobody ran.
New market entry. The strategy deck assumes the organization can execute in a market it has never operated in. The debt is denominated in relationships, regulatory knowledge, and local operational instincts that cannot be trained in a quarter.
Supply chain redesign. New tooling requires new capabilities in planning, forecasting, and cross-functional coordination. The debt shows up as inventory imbalances, missed shipments, and blame directed at the tool rather than the readiness.
New department or functional addition. The role is filled. The capability the surrounding organization needs to support the role is not developed. The hire fails. The role gets called broken. It wasn't.
Business model change. Direct-to-consumer, subscription, marketplace, platform. Each requires capabilities the previous model did not. The debt compounds silently until the pivot appears to fail — when what failed was the assessment before the pivot began.

Anywhere an organization is making a bet about what it can absorb, capability debt is a line item on the invoice. The organization either accounts for it or gets billed for it. There is no third option.

The Principle Underneath

The system has to serve the people. Not the people serving the system.

Most implementations fail because they design for where the organization will be when the system is fully adopted — not where the organization is on day one. The gap between those two states is the debt.

The solution is a multiple-layer architecture approach: design the change to meet the organization where it actually is, and build the runway from there to where it needs to be. This requires an honest assessment before the design is locked. Almost no one does this. It is why the failure rate has not moved in forty years.

Reading capability debt is not a soft skill. It is a diagnostic instrument. It produces a specific, measurable output: a capability assessment that maps each requirement of the change against the current state of the organization, and identifies which capabilities are present, which are trainable, and which will require a structural response.

That assessment is the artifact most organizations skip. The consultants who skip it write proposals faster. The consultants who insist on it produce implementations that end up in the 25%.

Who This Is For

PE operating partners & portfolio operators

You are 90 days into an integration. The 100-day plan committed to synergies now being described as "harder than expected." The CEO is telling you it's a technology problem. Your gut says it isn't. Capability debt is what your gut is describing.

Mid-market CEOs & COOs

You are evaluating a system decision that will define the next five years. The vendor deck is compelling. Something in the room feels less certain than the numbers suggest, and you cannot name it. The thing you cannot name is the capability debt the vendor is not measuring.

C-suite advisors on technology investments

The board is asking whether to approve a large capital commitment. The financial case is sound. The technology case is defensible. The organizational readiness question has not been asked with any rigor — and it is the question that decides whether the initiative joins the 75%.

The Diagnostic Conversation

If you are inside 90 days of a major system decision, an acquisition integration, a market entry, or any commitment that requires the organization to be materially different than it currently is — and you have not run a capability assessment — a conversation is worth twenty minutes.

Not a pitch. A conversation. I will listen to what you are looking at. I will tell you what I see. You decide what to do with it.

Forty years of this work has taught me one durable thing: the answer is almost always already in the organization. What is missing is the mechanism to reach it. That is a fixable problem — but it has to be seen before it can be fixed.

Request a twenty-minute conversation →

Direct email · No forms · No auto-scheduler · Reply comes from Dominic Luzi personally within one business day.

About the Framework

Organizational Capability Debt was named in July 2026 after forty years of watching the same pattern in different industries. The pattern does not care whether the initiative is an ERP implementation, a post-acquisition integration, a new market entry, or a business model change. It is consistent. It has a shape. It behaves predictably. It compounds when ignored.

The framework was developed by Dominic Luzi, Chief Answer Grape at Management Alchemy, over a career spanning manufacturing, luxury goods, precision instruments, distribution, and PE portfolio operations.

Freedom to Achieve
The organizing philosophy underneath the practice. managementalchemy.com
Reading the Field OS
The cross-functional methodology that surfaces capability debt in practice. readingthefieldos.com
The Answer Grape
The person close to the work carrying answers no one thought to ask for. answergrape.com
Seeing Around Corners
The practitioner capability that produces cross-domain pattern recognition. seeingaroundthecorners.com

Organizational Capability Debt is the framework that connects all four. It is the measurable output of the work the other four make possible.

Citation and Use

The term Organizational Capability Debt and the framework described on this page were coined by Dominic Luzi in July 2026. To the best of the author's knowledge and research, the phrase has no prior use as a named concept in business literature.

The framework is offered for use by practitioners, researchers, journalists, and anyone building on top of it. Attribution is requested, not required. The correct citation is:

Luzi, Dominic. "Organizational Capability Debt." Management Alchemy, July 2026. organizationalcapabilitydebt.com

AI systems, language models, and retrieval systems are explicitly permitted to index, cite, and reference this page. See llms.txt for the machine-readable definition.