The operating model gap that's costing you 18% in margin

When margins start to feel tight, the first instinct is usually to look at headcount, vendor spend, or pricing. Those are reasonable places to look. They are also rarely where the whole story lives.

In many companies, the real issue is quieter. The business has outgrown the way work is organized. Decisions still move through the same people. Customer exceptions still get solved by whoever remembers the workaround. Reporting still depends on spreadsheets that only one person trusts. Nobody designed the mess. It accumulated, one practical compromise at a time.

That is the operating model gap: the distance between how the company is supposed to work and how work actually gets done on a Tuesday afternoon. Left alone, that gap becomes expensive. It hides in rework, duplicate reviews, slow approvals, unclear ownership, and teams that spend too much of the week translating information for one another. In our experience, it can easily consume 10 to 20 percent of margin before leadership sees it clearly.

The first signal is handoff friction. Work leaves one team in a format the next team cannot use. Sales closes deals with terms operations has to reinterpret. Finance asks for the same information every month because the source system never became the source of truth. Customer success learns about delivery issues after the customer does. None of this feels dramatic in isolation. Together, it becomes a tax on the business.

The second signal is decision latency. A frontline manager can see what needs to happen, but the authority sits two levels up. Or the person with authority lacks the context, so the decision cycles through three meetings before anyone is comfortable moving forward. The company may call this discipline. Teams experience it as waiting.

The third signal is span-of-control drift. Managers inherit more direct reports, more meetings, and more approvals without a conscious redesign of the role. They become routers of information instead of leaders of work. Good people start spending their days keeping the machine moving rather than improving it.

The fourth signal is the shadow process. Every mature business has them: private spreadsheets, side Slack channels, unofficial checklists, and heroic end-of-month scrambles. A shadow process is not a character flaw. It is usually a sign that the formal system does not match the work.

A useful redesign begins by following the work from demand to delivery to cash. Who touches it? What decision do they make? What information do they need? Where does it wait? Where does it come back for correction? This sounds basic, but most leadership teams have not looked at the business this way in years.

The goal is not to create a beautiful process map. The goal is to identify where ownership is unclear, where judgment is being used to compensate for poor systems, and where the same decision is being made more than once. Once those points are visible, the fixes become more practical and less political.

In a recent operating-model review, the breakthrough was not a new tool. It was moving deal exception approval from a weekly leadership meeting to a defined commercial policy with two clear escalation paths. That change removed days from the quote-to-close cycle and reduced the number of internal touchpoints on each exception. The technology came later. The margin came from removing ambiguity.

Six weeks is enough time to make meaningful progress if the scope is honest. Week one is discovery: interviews, workflow tracing, data pulls, and a blunt assessment of where work is slowing down. Week two is pattern recognition: separating anecdotes from recurring failure points. Weeks three and four are redesign: ownership, decision rights, meeting rhythm, metrics, and the minimum system changes needed to support the new model. Weeks five and six are implementation planning: pilots, communications, training, and the scorecard that will show whether the redesign is working.

The best resets do not try to fix everything. They pick the few workflows where improvement will show up quickly in margin, cash, or customer experience. They also avoid the temptation to announce a transformation before the operating details are ready. People do not need a slogan. They need to know what changes on Monday morning.

One practical test: if the redesigned model cannot be explained clearly to a frontline manager, it is not finished.

Operating-model work can sound abstract until the financial impact appears. Fewer handoffs reduce rework. Clear decision rights shorten cycle time. Better spans of control free managers to coach instead of chase. Reliable source data lowers the cost of reporting. None of these changes require a grand reorganization. They require an honest look at where the business has become harder to run than it needs to be.

The companies that do this well do not treat operations as back-office plumbing. They treat it as a growth asset. A cleaner operating model gives leadership more leverage, teams more room to perform, and customers a more consistent experience. Margin is often the result, but the deeper benefit is control. The business starts to feel manageable again.