Why most operating models fail (and what actually works instead)

Most organisations have an operating model.

On paper, it usually looks clear. Roles are defined. Teams are structured. Governance is in place.

But when you look at how work actually runs day to day, a different picture emerges.

Things stall. Decisions take too long. Priorities compete. Teams are busy, but outcomes are inconsistent.

The issue is not that there is no model. It is that the model does not reflect how work actually moves.

What most operating models get wrong

Most operating models focus on:

• Structure — teams, roles, reporting lines.
• Process — stages, approvals, governance.
• Ownership — who is accountable for what.

These are all necessary. But they are not sufficient.

They describe how an organisation is arranged, not how it operates under pressure.

This becomes particularly visible in areas like digital delivery, where work is interdependent and constantly evolving. As seen in legal services, organisations often assume structure will translate into delivery.

It rarely does.

Where things actually break

The failure point is usually the same: the gap between direction and execution.

Strategy exists. Teams exist. But the way work flows between them is unclear.

This shows up as:

• Work starting before it is ready.
• Teams working in isolation.
• Decisions being revisited repeatedly.
• Delivery slowing down as complexity increases.

On the surface, this looks like a capacity issue. In reality, it is a coordination issue.

Why adding more people does not fix it

When delivery slows, the instinct is often to add more people. More engineers. More project managers. More oversight.

But if the way work runs is unclear, adding people increases complexity faster than it increases output. More handoffs. More dependencies. More communication overhead.

This is why organisations can grow in size but not in effectiveness.

It becomes even more visible when budgets tighten, because inefficiencies can no longer be absorbed.

What actually works instead

What makes the difference is not a better structure. It is a clearer way of running work.

At the centre of this is a defined operating layer. Not as a concept, but as something tangible:

• How work is prioritised.
• How decisions are made.
• How teams coordinate.
• How progress is made visible.
• How issues are surfaced and resolved.

This is what allows teams to move with clarity, even in complex environments.

Without it, even strong teams struggle. With it, delivery becomes predictable.

A simple test

You can usually tell whether an operating model is working by asking a few questions:

• Do teams know what matters most right now?
• Are decisions made at the right level, at the right time?
• Can work move without constant escalation?
• Is progress visible without needing multiple meetings?

If the answer to most of these is no, the issue is not the people. It is how the work is being run.

Most operating models fail not because they are wrong, but because they stop at structure and never define how work actually moves.

Practical takeaway

If you are trying to improve delivery, do not start by redesigning the organisation chart.

Start by understanding how work actually flows today:

• Where it slows down.
• Where it gets stuck.
• Where coordination breaks.

Then make that visible and deliberate. That is the foundation of an operating model that works in practice, not just on paper.