The hidden cost of process fragility in mid-market businesses.
Most mid-market operating models do not break in obvious ways. They quietly accumulate dependencies on key people, manual reconciliations, and tribal knowledge — until growth or change exposes the fragility all at once.
- By Malik Asad Ali
- March 2026
- 12 min read
In this article
The leadership team usually senses something before the numbers do. A decision that should have been routine somehow took three weeks. A report that used to land Monday morning now arrives Wednesday, and arrives wrong. The same operations manager is on the same urgent call for the third time this quarter. None of it triggers an alarm on its own. None of it shows up in the financials yet. But the operating model has started to slip — and by the time it shows up clearly, the cost of recovery is materially higher than the cost of prevention.
This is the failure mode we keep encountering at Infinikey. Not the dramatic kind that shows up as a margin collapse or a regulatory finding, but the quiet kind: operating-model debt, accumulating in the background, paid down by the same three people who happen to know where the bodies are buried.
01
A failure that hides
Process fragility is not the same as process inefficiency. An inefficient process runs, just slowly. A fragile process runs reliably right up until the moment a key person leaves, a system changes, or volume rises past a particular threshold — at which point it stops running, with no advance warning.
We’ve seen the same pattern across mid-market construction, field service and care businesses: the operating model that got the business to its current size is structurally different from the operating model needed to hold that size. Founders and leadership teams adapt — they extend the spreadsheet, they add a registry, they have one more weekly meeting — and the business keeps moving. But each adaptation is a load-bearing patch on a foundation that hasn’t been redesigned.
The operating model that got the business to its current size is structurally different from the operating model needed to hold that size.
The cost of this is rarely visible in a P&L. It shows up instead as the senior leader who can’t take a clean two-week holiday because three operational decisions a day land on their desk. It shows up as the project review where everybody nods at the dashboard but adjusts the actual numbers separately, in conversation. It shows up as the recurring complaint that “we have all this data and still can’t see what’s happening.”
02
The four signs of operating-model debt
Mid-market businesses tend to accumulate operating-model debt in four distinct ways. We’ve named them because naming them makes them harder to ignore.
1. Key-person dependency
A handful of named individuals — usually long-tenured, often unrostered as critical — are the only people who know how a particular process actually runs. The org chart says the work is owned by a department; the reality says it’s owned by a person. The cost shows up the day they take leave, change roles, or resign.
2. Manual reconciliation
Two or more systems contain the same data, but the data doesn’t match, and somebody is reconciling the two manually before reporting it upward. The reconciliation step is invisible to leadership but consumes meaningful hours each week and introduces a delay between operational reality and management visibility.
3. Tribal knowledge
Critical operational know-how exists only in conversation. There is no document. The new project manager learns how variations get approved by being told, in passing, by the experienced project manager. When the experienced PM moves on, that knowledge moves with them, and the new PM starts from a different position than the role description suggests.
4. Reporting-trust gap
The reports the leadership team receive are technically accurate but not trusted by the people receiving them. So leaders run a second mental check during every meeting — “is this number current?” “did this come out of the system or did someone adjust it?” — and decisions slow down accordingly. The data integrity is fine. The data trust is broken.
03
Why mid-market businesses accumulate it
Mid-market businesses accumulate operating-model debt for three structural reasons, and none of them are anybody’s fault.
First, the businesses we work with usually grew faster than the structure that supports them. A construction business that ran two concurrent projects when it was eight people now runs eleven when it’s eighty, and the project-management discipline that worked for two projects was never explicitly redesigned for eleven. It evolved. Which is to say, it accumulated patches.
Second, the cost of a fragility is invisible until it is large. There is no quarterly board paper titled “manual reconciliations consuming 14 hours of senior time per week.” The leadership team feels it as friction, not as a number. By the time it becomes a number, it’s usually a number attached to a more dramatic event — a project loss, a regulatory finding, a key resignation.
Third, the people who would have to redesign the operating model are the same people who are currently keeping it running by working around it. There is no slack capacity in the people who hold the workaround in their heads. So the redesign keeps getting deferred to the next quiet quarter, which never quite arrives.
04
How to diagnose it this week
A leadership team can run a useful first-pass diagnosis in a single ninety-minute meeting. Not a formal diagnostic — the kind we run with clients takes two to four weeks — but a credible self-assessment that surfaces where the debt is sitting.
01
Take a recent operational decision that should have been routine but wasn’t, and trace why it slowed down. Where did the friction sit? Whose desk did it land on? What information was missing or untrusted?
02
Ask each direct report to name the three processes in their area that would break if they were unreachable for two weeks. The frequency of the same names coming up is the signal.
03
Look at one full reporting cycle — weekly, monthly, whatever your rhythm is — and identify every place where data was manually moved, adjusted or reconciled between systems. Count the touches.
04
Read the last set of meeting minutes from your senior operations forum. Count how many of the discussion items are recurring (have appeared in three or more consecutive meetings without resolution). Recurring items usually point to structural friction, not just individual delivery.
The diagnostic principle
Operating-model debt is structural, not individual. If the same workaround would exist regardless of who held the role, the fragility is in the model — not in the person.
05
What to fix first
Once the debt is named, the temptation is to try to fix all of it. That’s the wrong move. Most mid-market businesses can’t absorb a full operating-model redesign on top of running the business — and they shouldn’t try to.
The order that has held up across our engagements is this: fix the reporting-trust gap before anything else. The reason is mechanical. If the leadership team doesn’t trust the data, every other decision — about systems, about people, about process — is being made with one hand tied. Restore trust in a small set of weekly metrics, then use that restored trust as the platform for the next layer of redesign.
Key-person dependency comes second, because the longer it sits unaddressed, the higher the consequences of the eventual departure. Manual reconciliation and tribal knowledge come third and fourth — meaningful, but less acute than the first two.
06
The principle that holds
The deepest mistake leadership teams make on operating-model debt is treating it as a productivity problem. It isn’t. It’s a structural decision that hasn’t been made yet — and the longer it goes unmade, the more the business pays in delayed decisions, missed signals and senior overload.
Naming the debt is the first move. Most of the work after that is unglamorous: redesigning the structure that holds the work, not just the work itself. But the businesses we’ve seen come out the other side share one quiet characteristic — their leadership teams can take a clean two-week holiday without three calls a day. That, more than any KPI, is the practical signal that the operating model has caught up with the business it supports.
MA
Malik Asad Ali
Founder, Infinikey Consulting
Malik works with mid-market businesses across construction, field service and care to redesign the operating model when growth has outpaced the structure behind it. He writes from inside the engagements.
More from Insights
Continue reading.
Construction
Why variations and claims get lost in mid-market construction.
Systems
Why ERP implementations fail to deliver the visibility they promise.
02
Start Here
Begin with a Transformation Diagnostic.
A short, structured engagement that shows where control is breaking down across workflows, systems, reporting and accountability. And what to fix first.
- 2–4 Weeks
- Senior-Led
- Fixed Scope
- A clear view of the biggest operational bottlenecks across your workflows, systems, and reporting layer.
- A 90-day plan that prioritises the changes most likely to unlock control and margin.
- Conducted personally by senior consultants, not handed to a team of analysts.