There's a kind of debt that doesn't show up on your balance sheet. No creditor chases it. No invoice arrives. It doesn't trigger an alert in your accounting software or flag up in a board review. It accumulates inside the work itself – in the processes your team follows, the workarounds they've invented, the knowledge that exists only in someone's head.
This is operational debt. By the time most leaders notice it, it's already expensive to fix.
The Invisibility Problem
Financial debt has a paper trail. You can see the interest accruing. You know when it was taken on and what it's costing you.
Operational debt has no such clarity. It hides inside how work actually gets done – not the version on the process diagram, but the version your team has adapted, improvised, and normalised. It accumulates through inaction rather than decision. Nobody chose to take it on. It just grew.
Consider how familiar some of these might feel:
- A process designed for a 10-person team, still running unchanged at 50.
- A workaround someone built three years ago as a temporary fix – now simply "how we do it."
- A tool nobody officially owns but everyone depends on not breaking.
- Institutional knowledge that lives entirely inside one person's head because documentation was never a priority.
None of these feel like debt. They feel like the normal texture of a busy organisation. That's precisely why operational debt is so hard to see and so easy to ignore until it becomes a structural constraint on your ability to move.
What Operational Debt Looks Like in Practice
Operational debt tends to manifest in three overlapping forms: misaligned processes, accumulated workarounds, and unowned dependencies.
Misaligned processes
Processes get designed for the organisation that exists at a particular moment. The approval workflow that made sense at 10 people (high-context, trust-based, everyone in the same room) rarely gets formally redesigned as the organisation grows, it just gets stretched. Suddenly nobody knows why decisions are being blocked, or who's actually supposed to sign off on what. The process still runs, but it no longer fits.
The same pattern plays out with onboarding. "Show them around and let them figure it out" works tolerably well when the whole team sits together. Distributed across 20 people in different locations, it creates knowledge gaps that can persist for months.
Accumulated workarounds
Every organisation accumulates workarounds: The email ritual that exists because the system doesn't quite do what's needed; The manual step that automated tooling could handle, but nobody has made the time to set up; The spreadsheet that lives alongside the official system because the official system has a limitation nobody's got around to fixing.
Each workaround makes sense when you look at it in isolation. The problem is that they compound. One workaround creates a gap that generates another workaround, which creates another. The result is invisible drag; a collection of small inefficiencies that, taken together, slow everything down.
Unowned dependencies
This is the "go and ask Sarah" problem. Knowledge, tools, or processes that everyone relies on but nobody is formally responsible for. When Sarah leaves (or is unavailable for a week) the dependency becomes visible, and it's usually more fragile than anyone realised.
Unowned dependencies aren't a sign of poor management. They're a natural product of growth. The problem is that scale makes them riskier. What's a manageable gap at 10 people becomes a single point of failure at 50.
Why Operational Debt Compounds
The difficulty with operational debt isn't just that it's invisible. It's that the dynamics of growth make it worse, not better, over time.
The cost of change increases with scale
A process change affecting 10 people is low-risk and relatively straightforward. The same change affecting 50 people, with multiple dependent workflows and a team whose habits have formed around the old process, is a significant undertaking. The further you let operational debt accumulate, the more expensive it becomes to address
Workarounds multiply
When there's a gap in a process, people solve it individually. One team finds one workaround. Another team finds a different one. Over time you end up with five different ways to do the same thing, none of which are documented, and all of which are invisible to anyone not directly involved.
Ways of working protect the debt
Processes don't just get work done; they shape how people think about work. A process designed for a small, informal, high-context team creates a way of working: ad-hoc communication, decisions made on instinct, everything held in someone's head. As the organisation grows, people continue working the way the old process trained them to work, even after the process itself has been updated.
The result is a kind of cultural residue. People resist formalisation because informality has been normalised. "We've always done it this way" is more than inertia - it's a set of habits that formed around the old operating model and haven't been redesigned.
The reverse is equally true. In cultures that normalise moving fast and cutting corners, workarounds don't get flagged as problems. They get treated as resourcefulness. The debt accumulates by design, because the culture doesn't recognise it as debt.
How to Diagnose Operational Debt
Operational debt is diagnosable. It requires asking the right questions, and being honest about what the answers reveal.
There are four diagnostic questions worth working through.
What processes feel slow or don't fit how the business actually works?
Walk through a typical project or customer interaction from start to finish. Where do things slow down? Where do people complain about the way work gets handed off? Where are there approval steps that nobody can fully explain the purpose of?
You're looking for: "We have to do X because of Y – even though Y hasn't applied for two years."
Where have workarounds become permanent?
Ask your team directly: "What do you do that isn't in the official process?" Most people will have an immediate answer. You're looking for spreadsheets running alongside systems, email rituals, manual steps that exist because a tool has a gap nobody has closed.
The tell: "We know we should use the system, but it doesn't do what we need, so we..."
What knowledge or capability is locked in people rather than systems?
Think about the three or four people whose departure would cause the most operational disruption because of what exists only in their heads. What would you lose? Where is there no documentation, no handover process, no way to transfer what they know?
The tell: "Only Sarah understands how that actually works."
How do your ways of working perpetuate the debt?
This is the harder question, and the one most diagnostic processes skip. Does your culture normalise workarounds as acceptable? Is there resistance to formalising processes because it feels like overhead? Do people continue working the old way even when the process has changed, because that's how they learned?
Cultural dynamics are harder to see than process gaps, but they're often what makes operational debt so persistent.
What to Do About It: The Operations Review Approach
Diagnosing operational debt is the necessary first step. Then you need to determine what to actually do about it.
The answer isn't to fix everything at once. That's paralysing, and it's usually the reason nothing gets fixed at all. The approach that works is a structured, four-stage operations review.
Map what's actually happening - not what's supposed to happen, but what your team actually does.
Assess the impact of each piece of debt. Not all operational debt is equally costly. Some slows you down a little; some is constraining your ability to grow.
Prioritise based on what's limiting your next phase of growth, not what's technically most broken. A non-urgent inefficiency in a stable part of the business is a different problem from a process that's creating friction in the work that matters most right now.
Redesign the process and the ways of working that support it simultaneously. Redesigning the process alone doesn't address the cultural residue - the habits and norms that formed around the old way. Both have to change together.
The Point of Doing This
Most SME leaders are aware that things feel slower than they should. There's more friction in the business than there ought to be. The team is spending time on work that shouldn't take as long as it does.
Operational debt is usually the explanation. Not poor performance or bad luck, but accumulated process drift that nobody has addressed.
The organisations that get this right don't necessarily move faster to begin with. They move more deliberately. They stop, they look at how work actually gets done, they make assessments of what's no longer fit for purpose, and they fix the things that are constraining growth.
That's not a transformation programme. It's a periodic discipline. The earlier you build it in, the less expensive it becomes.
Ady Coles helps organisations reduce operational friction so strategy has a chance to work. He focuses on operational clarity, sensible governance, and the thoughtful use of automation; not optimisation for its own sake, but making work easier, decisions clearer, and scale more sustainable as organisations grow.