Why most multi-site businesses don’t have an operating model — they have a collection of sites that share a name
There is a question that most multi-site operations leaders cannot answer cleanly.
If you took a senior leader from one of your sites and dropped them into another — same role, different location — how long before they felt genuinely at home? Not just familiar with the products or the people. Genuinely at home in the way the business operates. The rhythm of the reviews. The language of improvement. The tolerance for variance. The expectations of leadership behaviour. The standards that are non-negotiable everywhere versus the decisions that are deliberately local.
In a well-designed multi-site business, the answer is weeks.
In most multi-site businesses, the honest answer is much longer. Because what looks like one operating model from the outside is actually three or four distinct operating cultures, each shaped by the site’s history, its previous leadership, its local improvement journey, and the degree to which group expectations have ever been made genuinely explicit.
That gap — between the operating model that exists on paper and the one that actually runs each site — is one of the most expensive and least examined problems in multi-site manufacturing leadership.
This post is about how to close it.
1. The Illusion of Alignment
Walk into each of your sites and ask the same question.
Ask the site director: what are the three things that are absolutely non-negotiable here — the things that are true of how we operate regardless of what else changes?
Then ask the same question of the operations manager. The production supervisor. The quality lead.
Compare the answers.
In a genuinely aligned business, the answers converge. Not identically — language varies, emphasis varies — but the underlying content is consistent. People at every level, in every site, can articulate what the operating model is and what it requires of them.
In most multi-site businesses, the answers diverge significantly. Not because people are disengaged or unaware. Because the operating model has never been made explicit enough to be consistently understood.
There are group policies. There are KPI frameworks. There are audit standards and quality management systems and ERP configurations. There are functional reporting lines and governance structures. All of these create a degree of consistency.
But they are not an operating model.
An operating model is different. It describes not just what is measured but how the business actually runs. The management cadences. The improvement methodology. The escalation logic. The decision rights at each level. The leadership behaviours that are expected, developed, and held to account. The standards that define what good looks like — not on the audit sheet, but on the floor, in the meeting room, in the way a problem gets solved on a Tuesday afternoon when nobody is watching.
Most businesses have the governance architecture. Very few have the operating model underneath it.
2. How Sites Diverge
Understanding why sites diverge is essential to understanding what it takes to align them.
It is almost never the result of deliberate differentiation. Nobody decided that Site A would run a daily tiered accountability process and Site B wouldn’t. Nobody decided that Site C would have a mature problem-solving culture and Site D would still be operating largely in firefighting mode.
It happens because operating models, in the absence of explicit design, are shaped by whoever is leading the site.
A site director who came from a Toyota-supply-chain background builds a different culture than one who came from a cost-reduction programme. A site that has had three directors in four years looks different from one with a decade of consistent leadership. A site that went through a significant quality crisis three years ago has a different relationship with process discipline than one that hasn’t been stress-tested in the same way.
None of this is wrong. Leadership shapes culture. That is inevitable and, in many respects, desirable. Local leadership needs latitude.
The problem is when that latitude extends to the fundamentals. When different sites have genuinely different answers to questions like: how do we identify and escalate a problem? How do we prioritise improvement? What does a good daily management system meeting look like? What is acceptable variance in process adherence?
When those fundamentals vary, the multi-site business is not a system. It is a portfolio.
And portfolios are managed. Systems are led.
3. The Franchise Model
The clearest mental model for what a well-designed multi-site operating model looks like is not one that comes from manufacturing. It comes from the franchise industry.
A franchise business has solved, at scale, the problem that most multi-site manufacturers haven’t.
It has defined explicitly and precisely what is non-negotiable — the things that are identical in every location because they define the brand promise and the customer experience. And it has defined equally explicitly what is deliberately local — the things that individual franchise owners can adapt to their market, their team, and their circumstances.
That distinction — between the non-negotiable and the deliberately local — is the structural design of the operating model.
Most manufacturers have something that looks like the non-negotiable list. It is usually called a group standard, or a manufacturing excellence framework, or a minimum standard requirement. It covers things like safety compliance, quality system requirements, financial reporting, and ERP configuration.
What it almost never covers is the operating system — the management behaviours, the improvement cadences, the problem-solving methodology, the leadership standards — that determine whether the site actually performs at the level the metrics are designed to measure.
Those things are left to local discretion. Sometimes that produces excellent local innovation. More often it produces inconsistency that masquerades as site-specific context.
The operational franchise model says: define the non-negotiables with the same precision and the same enforcement rigour that a franchise business applies to its brand standards. Then give genuine latitude — intentional, designed, bounded latitude — to everything else.
4. Defining the Non-Negotiables
This is the hardest part. Not intellectually — the logic is straightforward. Politically.
Because defining non-negotiables means deciding that some things currently done differently across sites are going to be standardised. And that means some site directors are going to be told that their way — the way they built, the way they believe in — is not the way anymore.
That conversation requires both courage and precision.
Courage, because the instinct in most group organisations is to avoid the confrontation by making the non-negotiables vague enough that everyone can claim compliance. A standard that says “sites should have an effective daily management system process” is not a non-negotiable. It is an aspiration. Anyone can satisfy it by pointing at a meeting that happens every morning.
Precision, because the non-negotiables need to be specific enough to be auditable and meaningful enough to matter. Not a checklist of inputs — not “must have a visual management system board” — but a clear description of the capability the process is supposed to produce, how that capability is demonstrated, and what good looks like at each level of the organisation.
In practice, the non-negotiables in a well-designed operational franchise fall into four categories.
Management cadence. The rhythm of reviews, from daily team meetings through to monthly operational reviews. Not identical in format at every site, but consistent in purpose, frequency, and the standard of conversation they are expected to produce. What gets reviewed. How problems are surfaced. How escalation works. What a good meeting looks like versus an adequate one.
Improvement methodology. The approach to problem-solving is either consistent or it isn’t. In a system where every site uses a different improvement tool set, improvement knowledge doesn’t transfer. A kaizen that worked brilliantly in one site cannot be replicated in another if the people doing the replicating have never been trained in the method. The methodology doesn’t have to be rigid — but the logic, the language, and the core tools need to be common.
Leadership behaviour standards. What leaders at each level are expected to do — not just responsible for, but do. Where they spend their time. How they conduct observations. How they give feedback. How they develop their people. How they respond when a standard is missed. These leadership behaviours are the operating system of the management layer, and they determine more about site performance than any policy or process.
Data integrity and decision logic. The metrics are common. The definitions behind them must be too. A site that measures OEE differently from its peer site is not generating comparable data. A business that allows sites to define schedule adherence in ways that suit their local context is not running a common operating model — it is running a common reporting format over four different realities.
5. The Deliberately Local
The operational franchise is not a centralisation argument.
It is a clarity argument.
Once the non-negotiables are defined — and genuinely enforced — the space for local autonomy becomes productive rather than chaotic. Site leadership knows what the boundaries are. They know what flexibility they have. They can innovate within the operating model rather than around it.
The deliberately local should be genuinely significant. Not just the colour of the visual management system boards. Real decisions, real latitude, real accountability.
How the site structures its improvement programme within the agreed methodology. The specific capability investments it makes in its people. The sequencing of its improvement roadmap. The way it builds relationships with its local labour market. The operational decisions that are site-specific by nature — make-versus-buy within defined parameters, local supplier relationships, shift pattern design within agreed frameworks.
This matters because without genuine local latitude, the operating model becomes a compliance programme. Site directors become implementers rather than leaders. The creativity and local knowledge that makes multi-site operations genuinely powerful gets suppressed in favour of uniformity.
The best multi-site operating models feel liberating rather than constraining to site leaders. Not because they are loose, but because the constraints are in exactly the right places. The non-negotiables are things that genuinely must be consistent. The rest is yours.
6. How Knowledge Travels
One of the most significant practical benefits of a genuine operating model — one that is rarely articulated as a benefit — is that it creates the conditions for knowledge to travel between sites.
In a business where every site operates differently, a breakthrough at Site A is almost impossible to transfer to Site B. The improvement was designed for Site A’s management system, Site A’s data infrastructure, Site A’s terminology, Site A’s improvement culture. Transplanting it requires translation at every level. Often the translation fails and the learning stays local.
In a business with a common operating model, a breakthrough at Site A can be deployed at Sites B, C, and D with a fraction of the friction. The management cadences are the same. The improvement methodology is the same. The language is the same. The capability to implement has been built consistently. The transfer is replication, not translation.
This compounds over time in ways that are significant. A business that can transfer knowledge freely across its site network learns faster than one where each site is effectively reinventing. The improvement capability of the whole exceeds the sum of the parts — not because any individual site is exceptional, but because the system amplifies learning.
That is a structural competitive advantage. It is available only to businesses that have done the design work to create a common operating model. And it is available to every multi-site business willing to do that work.
7. The Integration Dividend
The operational franchise model has particular relevance for businesses growing through acquisition.
Acquisition creates the most acute version of the multi-site divergence problem. The acquired business has its own operating culture, its own management rhythm, its own improvement language, its own definition of what good looks like. Integrating it requires either imposing the acquirer’s operating model — which risks destroying what was valuable about the acquired business — or leaving it alone — which creates a permanent outlier in the portfolio.
Neither is right. Both are common.
The better path is explicit and bilateral. The acquiring business brings a defined operating model — the non-negotiables that apply to every site in the network. The acquired business brings its own operational intelligence — the things it does well that the acquiring business can learn from. The integration is a genuine exchange rather than a one-way imposition.
That requires the acquiring business to have a model worth bringing. And it requires the intellectual honesty to look at the acquired business not just as a business to be improved but as a source of capability that might improve the acquirer.
Businesses that approach acquisition with a defined operational franchise model integrate faster, retain more of the acquired capability, and extract more of the strategic value of the deal than those that approach integration as a process of making the new site look like the existing ones.
8. The Role of Group Leadership
Defining and sustaining an operational franchise model is not a task that can be delegated to sites.
It requires active design and maintenance at group level. Not micromanagement of sites — the opposite. The precise definition of what group is responsible for, and the deliberate release of everything else to sites.
Group leadership is accountable for defining the non-negotiables. Communicating them with clarity and consistency. Auditing adherence with precision. Developing the capability to meet them across the site network. And evolving them as the business learns — because the operating model should improve over time, incorporating the best practice that surfaces across the network and retiring the elements that no longer serve the model‘s purpose.
That is a different kind of group role than most businesses have designed. Most group functions are primarily financial — setting targets, reviewing performance, allocating capital. The operating model dimension — the active stewardship of how the business runs — is either absent or distributed so thinly across functional heads that it lacks coherence.
The businesses that get multi-site operations right have typically created an explicit ownership for the operating model — a person or function at group level whose job is to define it, develop it, deploy it, and hold it to account. Not a standards police. An architect.
9. Measuring the Model
The operating model needs its own performance measures.
Not just the output metrics that appear in the monthly review — those measure what sites produce. The operating model metrics measure how sites are operating.
Management system capability. The quality of the daily management system process — not whether it happens, but whether it is driving the right conversations and producing the right decisions. This is measurable through observation, not through reporting.
Improvement velocity. How many improvements are being identified, implemented, and sustained per site, per period? Not as a volume target, but as an indicator of whether the improvement methodology is genuinely embedded or is being applied periodically and superficially.
Knowledge transfer rate. How many improvements from one site have been successfully replicated in another within a defined period? This is a direct measure of whether the common operating model is enabling cross-site learning.
Leadership behaviour consistency. Whether leaders at equivalent levels across sites are demonstrating the agreed leadership behaviours — through observation, coaching conversations, and structured assessment rather than self-reporting.
These are not comfortable metrics. They require observation rather than data extraction. They require honesty rather than reporting. They require leaders at group level to spend time in sites — not in the boardroom or the conference call — watching what actually happens.
But they are the only metrics that tell you whether the operating model is real or whether it is a document.
10. The Long Game
An operational franchise model is not built in a transformation programme.
It is built over years. Through consistent expectation-setting, consistent development, consistent recognition of the right behaviours, and consistent intolerance of the wrong ones. Through the slow accumulation of shared language and shared practice that eventually becomes organisational identity.
The businesses that have it — that have genuinely built a common operating culture across multiple sites — share a recognisable characteristic. You can walk into any of their sites, at any hour, and see the same fundamental operating logic at work. The same quality of daily management system conversation. The same approach to problem surfacing. The same leadership behaviours at supervisor level, team leader level, site director level.
It doesn’t feel like compliance. It feels like culture.
The difference between compliance and culture is sustainability. Compliance requires enforcement. Culture requires only leadership — the visible, consistent modelling of the behaviours that define the model.
Getting from compliance to culture is a decade-long journey.
It starts with the decision to build a model worth the journey.
Final Thought
The multi-site business that operates as a genuine system — not a portfolio of individual sites — has a structural advantage that compounds over time.
It learns faster. It transfers knowledge more freely. It integrates acquisitions more effectively. It develops leaders more deliberately. It reduces the cost of coordination. It produces more consistent results with less management intervention.
All of that flows from one foundational design decision: defining, clearly and precisely, what is non-negotiable and what is deliberately local. And then building the capability, the cadence, and the culture to sustain it.
Most businesses haven’t made that decision yet.
They have a governance framework and a set of KPIs and a monthly review process.
They don’t have an operating model.
The gap between those two things is where performance leaks.
Three questions to sit with.
Could you write down — in one page, with genuine precision — what is non-negotiable in how your sites operate?
Would your site directors all write the same one page?
And if the answers diverge, do you know what that divergence is costing you?
adam
Leave a comment