An operating model is how an organization actually runs. It is the set of structures, processes, decision rights, capabilities, technology, locations, suppliers, and management cadence that turns a strategy into delivered outcomes for customers. Get it right and execution feels effortless. Get it wrong and every quarter the business burns capacity firefighting problems the operating model should have prevented.
This guide is written for leaders of mid-market organizations - typically £10m to £100m turnover, private, PE-backed, or listed - who are trying to scale a business whose operating model has not kept pace. It covers what an operating model is, the components it contains, the archetypes leaders actually choose between, the financial impact of getting it right or wrong, how to tell when yours is broken, and how to redesign it without stalling the business.
What is an operating model?
An operating model is the way an organization delivers value: the structures, processes, capabilities, technology, locations, suppliers, decision rights, and management cadence through which strategy becomes work, and work becomes outcomes. It is both a description of how the organization runs today and a design for how it should run to achieve its goals.
Put a different way: a business model says what value you create and capture. An operating model says how you create and capture it, day to day. The strategy says what to do; the operating model is the machine that does it.
An operating model is not an organization chart, not a process map, not a technology stack, and not a list of locations. It is the integrated system that connects all of those. Most operating-model problems in mid-market businesses are not problems with any single component - they are problems at the seams between components.
Working definition: An operating model is the integrated system - people, processes, structure, technology, data, locations, suppliers, and governance - through which an organization delivers its strategy and produces measurable outcomes. It exists whether you have designed it or not. The question is whether the one you have is the one you would have chosen.
Operating model vs business model vs organization chart
Three terms get used interchangeably and shouldn't. The distinctions matter because the work needed to fix each is different.
| Concept | What it answers | Typical artefact |
|---|---|---|
| Business model | What value do we create? Who pays for it? How do we capture margin? | Business model canvas, commercial strategy, pricing architecture |
| Operating model | How do we organise people, processes, technology, data, and partners to deliver that value? | Operating model canvas, value chain map, capability model, decision-rights matrix |
| Organization chart | Who reports to whom? | Org chart, headcount plan, role descriptions |
The organization chart is the most visible artefact - and therefore the most often confused with the operating model itself. It is not. The same organization chart can support very different operating models depending on how decisions are made, how work flows, how performance is measured, and how technology supports the work. Conversely, two organizations with identical operating models can have very different org charts.
Common synonyms and adjacent terms for operating model: target operating model (TOM), operating framework, delivery model, capability model, operating system of the business. They all point at roughly the same thing.
The eight components of an operating model
Different frameworks use different lists. Bain emphasises six. Wikipedia lists ten. The Operating Model Canvas by Andrew Campbell uses the POLISM mnemonic with seven. The differences matter less than the underlying point: an operating model is a system, and any component is only meaningful in the context of the others.
The eight components below cover the ground all the established frameworks address, in language that maps cleanly onto how mid-market organizations actually talk about their businesses.
1. Value chain (processes and flow)
The end-to-end sequence of activities that turns inputs into customer value: plan, source, make, deliver, service, improve. The shape of the value chain determines where customer experience is created and where cost accumulates. Most operating-model problems show up first as friction at handovers between value-chain stages.
2. Structure (organization and decision rights)
How work is grouped, how authority is distributed, and where decisions get made. The visible artefact is the org chart; the invisible substance is decision rights - who can commit money, change priorities, approve exceptions, hire, and escalate. Two organizations with identical org charts can have radically different decision rights.
3. People (capabilities and culture)
The skills, experience, mindset, and behaviors required to operate the model effectively. Includes hiring approach, development paths, performance management, and the cultural norms that determine how people behave when no one is looking. The most common mistake here is designing an operating model that requires capabilities the organization does not have and has no plan to build.
4. Technology (systems and architecture)
The platforms, applications, and infrastructure that enable the operating model. Includes core systems (ERP, CRM, finance), specialist applications (sector-specific platforms), integration architecture, and the operational technology that supports core work. Technology is an enabler, not the operating model itself - a common confusion in transformation programs.
5. Data (information and insight)
What gets captured, where it lives, who can access it, how it is governed, and how it becomes the insight leadership uses to make decisions. In mid-market businesses, data is almost always more fragmented than leadership realises, and the operating model assumes a level of data quality that the actual data does not support.
6. Locations (footprint and assets)
Where the business operates - offices, plants, warehouses, depots, retail sites, customer-facing locations - and the physical assets that support delivery. Includes the hybrid-working policy and the implications it has for how work is coordinated, how decisions are made, and how culture is sustained.
7. Suppliers (partners and sourcing)
The third-party relationships through which capability is acquired rather than built in-house. Includes outsourced functions, technology vendors, professional services, and any strategic partnership through which the business accesses capability it does not own. Increasingly important as mid-market organizations build leaner internal teams.
8. Governance (cadence and controls)
The management rhythm - meetings, reporting cycles, decision forums, performance reviews - through which the operating model is run. Includes the controls that ensure compliance, risk management, and quality. Governance is the heartbeat of the operating model; without it, the other components drift.
The seven archetypes of operating models
Mid-market organizations rarely design an operating model from a blank sheet. They choose - implicitly or explicitly - from a small number of well-understood archetypes, each of which has known strengths, known weaknesses, and known situations it fits.
The seven archetypes below cover the operating model choices that account for the vast majority of mid-market businesses. Each is described with its definition, when it fits, when it does not, and the failure mode it tends to produce.
1. Functional
Work is organised by specialist function - sales, marketing, operations, finance, technology - and each function reports to its own head. Decisions about priorities are made by the SLT cross-functionally.
Fits when: the business has a single product or service line, the market is reasonably stable, and depth of functional expertise is the primary source of competitive advantage. Common in mid-market manufacturing, professional services, and single-product SaaS.
Failure mode: as the business grows beyond one product line, functions optimize locally and the SLT becomes a bottleneck for cross-functional decisions. Customer experience fragments at handovers.
2. Divisional
Work is organised by business unit - each unit serves a distinct customer segment or product category, owns its own P&L, and runs its own functions. Corporate center is light, focused on capital allocation and shared services.
Fits when: the business has multiple genuinely distinct lines of business with different customer needs, different competitive dynamics, or different go-to-market motions. Common in mid-market groups, holding companies, and businesses post-acquisition.
Failure mode: duplication of cost across divisions; loss of cross-selling because units compete internally; cultural fragmentation that makes the group hard to lead as one business.
3. Matrix
People sit at the intersection of two reporting lines - typically function and product, or function and geography, or function and customer segment. Resources are shared; priorities are negotiated.
Fits when: two dimensions of the business genuinely need equal weight (e.g. function and product line), and the organization has the maturity to manage the resulting complexity. Common in larger mid-market technology, professional services, and pharmaceutical businesses.
Failure mode: dual reporting becomes accountability ambiguity; meetings multiply; decisions slow. Mid-market organizations frequently underestimate the managerial maturity matrix requires.
4. Geographic
Work is organised by region or country, with each region running most functions locally. Corporate center coordinates strategy, brand, and capital allocation.
Fits when: local market nuance, regulatory variance, or physical delivery means decisions and operations must happen close to the customer. Common in mid-market retail, logistics, housing, and field-services businesses.
Failure mode: regional barons protect local autonomy at the expense of group performance; cost duplication across regions; capability uneven across the footprint.
5. Customer-centric
Work is organised around customers or customer segments. Account teams own the customer relationship end to end, drawing on functional capability as needed.
Fits when: a small number of large customers generate most of the revenue, and customer outcomes depend on integrated delivery across multiple functions. Common in B2B professional services, complex sales environments, and outcome-based contracts.
Failure mode: functional expertise fragments because specialists are dispersed across accounts; cost per account inflates; consistency across customers suffers.
6. Product-led
Work is organised around products. Each product has a dedicated team owning the product lifecycle, with shared functions providing technology, finance, and people support.
Fits when: the business has multiple distinct product lines that evolve independently, customers can self-serve, and product development cadence is the primary competitive lever. Common in SaaS, technology platforms, and consumer products.
Failure mode: products optimize for their own metrics at the expense of customer experience across products; shared platform capability becomes contested; cross-product opportunities go unrealised.
7. Platform / networked
The organization provides the platform - a set of standards, technology, data, and governance rules - through which a network of partners delivers customer value. The core is small; the network is large.
Fits when: the value created depends on coordinating a network of partners rather than performing the work directly. Common in marketplaces, franchise networks, MGA insurance, and broker-platform businesses.
Failure mode: platform leadership cannot move faster than the network can adopt; partner quality drifts; the platform becomes hostage to the largest partners.
Most mid-market businesses operate a hybrid - functional for some activities, geographic for others, matrix-lite at the executive layer. The point of naming the archetypes is not to force a pure choice; it is to make the design explicit so leadership can see where the operating model is internally consistent and where it is contradicting itself.
The four operating model shapes
The MIT CISR research team (Jeanne Ross, Peter Weill, David Robertson) developed a four-quadrant model that is now the most-cited typology in operating-model literature. It plots an organization against two dimensions: business process standardisation (how much the same way of working is required across units) and business process integration (how much units need to share data and coordinate end to end).
Diversification (low integration, low standardisation): independent business units sharing little. Each unit serves different customers and operates differently. Common in conglomerates and holding companies; appropriate when units are genuinely independent.
Coordination (high integration, low standardisation): units share customers and data but operate distinctively. Common in universal banks, hospitals, and integrated professional services. The challenge is information sharing without forcing operational uniformity.
Replication (high standardisation, low integration): the same operating model rolled out across many independent sites. Common in franchises, multi-site retail, depot networks. The challenge is maintaining standards across the network while allowing local adaptation.
Unification (high standardisation and integration): one business operating one way globally. Common in single-brand global retailers, parcel networks. The challenge is the cost and rigidity of the central machine.
The seven archetypes earlier and the four shapes here are complementary, not competing. The archetypes describe how work is grouped (functional, divisional, matrix and so on). The four shapes describe how integration and standardisation are balanced across that grouping. A divisional structure can be operated as Diversification (independent divisions) or as Coordination (divisions sharing customers and data). The combination is what defines the operating model.
The three main principles of operating model design
Across the strongest operating-model literature - MIT CISR, Andrew Campbell, the Bain six-pillar model, McKinsey's nine elements - three principles recur. Any good operating model satisfies all three; failing operating models usually fail on the same one repeatedly.
1. Internal consistency
The components support and reinforce one another. Decision rights match the structure; capabilities support the processes; technology supports the value chain; governance cadence matches the speed of the work. When components contradict each other - for example, a functional structure with cross-functional outcomes-based incentives but no cross-functional decision authority - the operating model produces friction in proportion to the contradiction.
2. Alignment with strategy
The operating model is fit for the strategy. A strategy of premium customer experience cannot be delivered by an operating model optimized for low-cost replication. A strategy of rapid product innovation cannot be delivered by an operating model with quarterly governance cadence and 12-month change cycles. Misalignment between strategy and operating model is the most common reason transformation programs underperform.
3. Capacity for change
The operating model can be adapted as the strategy evolves. Operating models that are rigid - locked in by inflexible technology, ossified processes, or sclerotic governance - become liabilities. The best operating models build in capacity for change as a first-order design property, not as an afterthought.
How operating model choice flows through to EBITDA
Operating model is often treated as a soft topic. It isn't. The financial signature of an operating model choice shows up in five places, and the gap between a well-designed operating model and a poorly-designed one in the same business is reliably worth several percentage points of EBITDA.
From the State of Mid-Market Transformation 2026 benchmark dataset, the cumulative gap between an operating model in the top quartile and one in the bottom quartile across all seven performance themes runs from 8 to 25 percentage points of EBITDA in the same business. The five mechanisms are below.
| Mechanism | How operating model affects it | Typical EBITDA range |
|---|---|---|
| Cost-to-serve | Duplication across units, headcount that supports a structure rather than work, technology spend that supports legacy ways of working | 1-7% |
| Cycle time | Handover delays, decision deferral, rework caused by process gaps | 1-6% |
| Customer experience | Inconsistency across touchpoints, slow resolution, account fragmentation | 1-5% |
| Capacity allocation | Senior time consumed by exceptions the operating model should prevent; investment misallocated across priorities | 1-4% |
| Resilience and change capacity | Program stalls, regulatory rework, key-person dependency, M&A integration friction | 0.5-3% |
The point is not that every business can capture all of this. The point is that operating-model choice is a primary lever on financial performance, comparable in scale to commercial pricing and product mix decisions, and treating it as a soft topic systematically under-prioritises it.
Signs your operating model is broken
Most operating-model failures are not announced. They show up as recurring symptoms that the leadership team has stopped noticing because they have always been there. The list below is the diagnostic short-list - if three or more apply, the operating model is the primary constraint on performance and no functional fix will move the dial.
- The same problem recurs. The leadership team solves a problem; six months later it is back. The fix is functional; the cause is operating model.
- Decisions wait. Material decisions sit on the agenda for weeks because no single forum has authority. Decision rights are unclear or constantly negotiated.
- Reports disagree. Different parts of the business produce different numbers for the same thing. Leadership time is spent reconciling, not deciding.
- Senior time is consumed by exceptions. The SLT is making decisions the operating model should handle without them.
- Cross-functional initiatives stall. Programs that need two or more functions die in coordination overhead.
- Customer experience varies by who handles the request. The same customer gets a different experience depending on the person, channel, or location.
- New hires take six months to become productive. The operating model is undocumented and resides in individual memory.
- Key-person risk is acute. If one named person left tomorrow, a workstream would stop. The operating model has not built capability redundancy.
- The company has outgrown its founder operating model. Decisions still flow to the founder or single executive. See: Five Signs Your Business Is Growing Faster Than Its Operating Model.
The single most reliable test: ask the SLT to list, in five minutes, the three biggest operational constraints on next-year EBITDA, with sizing. If they cannot agree, or if the constraints are functional rather than systemic, the operating model is part of the problem - because a fit-for-purpose operating model surfaces these constraints and aligns the team around them.
How to redesign an operating model
Operating model redesign in a mid-market business looks different from enterprise transformation. The team is smaller, the sponsor has less time, and the cost of stalling the business during the change is higher relative to total turnover. The six-step approach below is the one we use - it works because it produces a working operating model in a sensible timeframe, not because it is the most theoretically elegant.
Step 1: Establish the strategic intent the operating model must serve
Document the business strategy in enough detail that operating model decisions can be tested against it. If the strategy is unclear or contested, fix that first - operating model redesign on top of unclear strategy produces a working model for the wrong destination.
Step 2: Map the current operating model honestly
Document how the eight components actually work today, not how the org chart suggests they should. Pay particular attention to decision rights, data flows, and handovers between stages. Most leadership teams overestimate how well they understand the current operating model.
Step 3: Identify the binding constraints
Diagnose the two or three operating-model gaps that account for most of the underperformance. Typical patterns: decision rights are unclear so decisions wait; one function lacks capability so the others compensate; data quality cannot support the reporting cadence the leadership team wants.
Step 4: Design the target operating model
Select the archetype and shape that best fit the strategy. Specify how each of the eight components changes from current to target. The target is concrete - new structures, new decision rights, new processes, new technology, new governance cadence - not abstract.
Step 5: Sequence the transition
Identify which changes go first and why. The right sequence usually addresses the highest-leverage constraint first (so early wins fund the rest), then sequences the dependent changes after. Avoid big-bang transitions in mid-market businesses - they fail more often than they succeed.
Step 6: Run the transition with delivery discipline
The target operating model needs to be implemented like any other program: a named accountable owner, governance cadence, benefits tracking, and an explicit close-out. Without delivery discipline, the redesign becomes a slide deck.
The full sequence runs 6 to 12 months in a typical mid-market business. The first phase - diagnosis through to target design - runs 4 to 12 weeks depending on complexity. The transition phase varies by scope.
Common mistakes in operating model redesign
Five mistakes account for most operating model redesign failures. None of them are technical; all of them are leadership.
1. Designing the org chart first
Reorganising boxes and reporting lines is not operating model redesign. It is a visible change that may or may not address the underlying issue. The structural change has to follow from decisions about value chain, decision rights, capabilities, and governance - not lead them.
2. Copying another business's operating model
The operating model that worked at the comparable business worked because of that business's strategy, capabilities, customers, and culture. Lifting it wholesale ignores all of those. The right design is the one that fits this business.
3. Underestimating change capacity
Operating model redesign lands on the same people who are also running the business. If the change load exceeds change capacity, the redesign stalls and operations suffer. The most successful mid-market redesigns explicitly manage change capacity as a constraint.
4. Treating it as a technology program
ERP, CRM, or platform implementations sometimes get described as operating-model redesigns. They are not. They are enablers of an operating model - if the operating model has not been designed independently, the technology implementation will entrench whatever is already there.
5. Stopping at go-live
Operating models settle in over time. The first version is rarely the final one. Without a post-go-live review and a planned period of adjustment, the new model drifts back toward the old one because the old habits are still in place.
Operating models in special contexts
The standard framework applies; the emphasis shifts. Four contexts where operating model decisions are particularly consequential.
PE-backed portfolio companies
The investment thesis defines the strategic intent, which defines what the operating model must support. PE operating partners drive operating model redesign to release EBITDA against the value creation plan, usually within the first 100 days of investment. See: Operational excellence in private equity portfolios.
Post-acquisition integration
Two operating models become one. The choices are: full integration (target one Unification model), preserved autonomy (keep two Diversification units), or selective integration (one shared back office, two front offices). Most acquisition synergy targets fail because the operating model integration choice was made implicitly rather than explicitly. See: 100-day integration plan, Why acquisition synergies fail.
Scale-up transition
The founder operating model is functional, fast, and centralised. Beyond £10-30m turnover, it breaks. The transition is to a structured operating model that the founder can step back from without the business losing momentum. The mistake is hiring senior people into the founder operating model rather than redesigning the model first.
Regulated industries
Regulatory requirements impose operating-model constraints (segregation of duties, audit trails, evidenced controls). The operating model must satisfy regulation by design rather than by retrofit. Common in financial services, insurance, healthcare, energy, and housing. The strongest operating models in regulated sectors treat compliance as a design property, not as a tax on operations.
Conclusion and next steps
An operating model is the system through which strategy becomes outcomes. It has eight interconnected components, comes in seven well-understood archetypes, and balances standardisation and integration across four classic shapes. Get it right and the business runs; get it wrong and every quarter the leadership team burns capacity on problems the operating model should prevent.
For mid-market businesses specifically, the operating model question is usually not whether to have one - everyone has one, designed or not - but whether the one currently in place still fits the business. The signs that it does not are well-known. The redesign approach is well-understood. The risks of getting it wrong are large enough that operating model design belongs on the SLT agenda, not the operations agenda.
If you are reading this because the symptoms in Section 8 sound familiar, the smallest sensible first step is a structured diagnostic. The Velocity Readiness Survey is the free, 10-minute version. The Executive Discovery Scan is the 5-day version that produces a board-ready brief. Either is a defensible way to make the operating-model question visible to the SLT without committing to a program.
Operating model not keeping pace?
Independent diagnostic, fixed scope, senior-led, no obligation. Find out where your operating model is the constraint - and what to do about it - before committing to a redesign.
