What is Operating Model Debt?
Operating Model Debt is the gap that builds up when an organisation adopts a new machine but does not redesign who decides what around it.
Every generation of business gets a machine that changes what is possible overnight: the dynamo, the assembly line, ERP, CRM, agile, DevOps, and now AI. The machine usually works on the first afternoon. The organisation takes years to catch up.
That distance is the debt. It does not appear on a balance sheet. It shows up in the numbers that sit downstream of how work is actually organised: retention, payback, time to first value, adoption.
Where the idea comes from
The book Operating Model Debt follows the same pattern across three rooms, one hundred years apart.
- A 1920s factory floor. Electric power arrived instantly. Redesigning the factory around it took thirty years.
- A Toyota assembly line. A piece of rope, and the decision rights to pull it: the clearest operating model fix in industrial history.
- A boardroom today. AI is running the same experiment as every machine before it, faster, with the bill arriving sooner.
Look inside the book on Amazon
The four layers
The debt builds up in four places. Most organisations carry some of each.
| Layer | What the debt looks like |
|---|---|
| People & Organisation | Nobody owns the number. Incentives stop at signature. Headcount runs ahead of role clarity. |
| Process | No cadence catches the problem until a board, a renewal or a cancellation does. |
| Technology | No system ties spend, usage or cost to the individual customer or account. |
| Data | Key terms such as churn risk or lifetime value are not defined, so they are not calculated the same way twice. |
How it is measured
Operating Model Debt becomes visible in 15 business metrics, each tied to one of the four layers and a typical root cause, with a bad, good and better band for each. Net Revenue Retention, CAC Payback, Time to First Value and Core Product Adoption are four of the fifteen.
The free Operating Model Debt Check gives an indicative score in nine questions and about three minutes, and shows which of the four layers carries the most debt.
How it is managed
Measuring the debt is the first step. VALUEFLOW, software from POLARYN, tracks each transformation from intent to outcome, so the debt is paid down on purpose and not rediscovered each quarter.
What Operating Model Debt is not
- Not technical debt. Technical debt lives in code. Operating Model Debt lives in decisions, roles, processes and data.
- Not an AI problem. AI did not create it. AI accelerates whatever is already there, clarity or chaos, which is why the gap becomes visible faster now.
- Not a maturity score. It is a set of measurable gaps with named root causes, so each one can have an owner.
How the term is used here
Several writers and firms use the phrase “operating model debt” in different ways. This page describes the framework developed by Werner van Zyl and POLARYN and set out in the book Operating Model Debt (published 27 July 2026): four layers, 15 measurable metrics, a free check and software to manage the debt.
How to cite
van Zyl, W. (2026). Operating Model Debt. operatingmodeldebt.com.
Questions
Where does the term come from?
Several writers and firms use the phrase in different ways. This framework gives it a specific meaning for the AI era, with four layers, 15 metrics, a measurement check and software.
How is it different from technical debt?
Technical debt is about code shortcuts. Operating Model Debt is about the decisions, roles, processes and data that were not redesigned around a new machine.
How do I find out how much I carry?
Take the free Operating Model Debt Check, then compare your results with the bad, good and better bands.