Building operating models that actually scale

What breaks first is never what you expect

When scaling fleet operations across Australia and New Zealand, the operating model looked solid on paper. The processes were documented. The standards were agreed. But the first visible symptom of failure wasn’t a process breaking — it was variance creeping into cycle times and rework rates across regions.

The first thing that broke was consistency of interpretation, not process design. Different regions had interpreted key steps differently — especially around approvals, prioritisation, and what constituted an exception. Nobody was doing anything wrong. They were just solving their local reality. After 12 months, the “unified” operating model had become six regional variations.

Paper model vs real model

A paper model describes how work should flow.

A real operating model survives contact with local incentives, system limitations, and human shortcuts under pressure. The difference is not quality of design — it is whether the model was built to accommodate deviation or to ignore it.

The organisations that scale well design their operating models around principles, not just current structure. They define how decisions are made, how accountability flows, and how performance is measured — in a way that holds across different sizes, geographies, and operating contexts.

What makes a model actually scalable

• Decision rights that survive personnel change — the structure works even when individuals move on. Clarity lives in the model, not the person
• Standardised core with local tolerance at the edges — the non-negotiables are clear, everything else has room to flex without breaking the system
• Performance measurement that surfaces problems automatically — leaders see drift before it becomes a crisis, not because someone compiled a report
• Governance light enough not to slow things down — strong enough to maintain consistency. The test: do decisions get faster as the organisation grows, not slower?

The most common long-term mistake

The biggest issue I’ve seen is designing for alignment instead of adaptability. Organisations over-standardise early, assuming consistency will create control. But without built-in tolerance for local variation, the model starts to fragment under real operational load.

Ironically, the more rigid the design, the faster it drifts in practice. Teams find workarounds. The workarounds become standard practice. The standard practice diverges from the model. And 18 months later leadership wonders why the operating model “isn’t working.”

Signs your model is already drifting

• Cycle times vary significantly across sites without a clear reason why
• Exception rates are rising — more things require escalation than 12 months ago
• Workarounds have become standard practice at the team level
• Onboarding new sites takes longer each time, not shorter
• The same decision is being made differently in different regions
• Reporting requires manual aggregation rather than system visibility

What breaks scalability

Operating models designed around the current leadership team. When those people change, the model stops working because the knowledge was in the people, not the structure.

Inconsistent process execution. Every site doing things slightly differently in ways that compound over time. What starts as minor variation becomes fundamental divergence.

Reporting that depends on manual aggregation. When the reporting burden grows faster than the operation, leadership loses visibility exactly when they need it most.