Operating model redesign in a mid-market business is harder than in an enterprise because the team running the business is also the team running the redesign. Get the sequence right and the change embeds without stalling delivery. Get it wrong and operations suffer for the duration of the program. This is the six-step approach we use - deliberately tuned for businesses where the sponsor is part-time and the change capacity is finite.
This is a companion to What is an operating model? which covers the components, archetypes, and shapes in detail. This article focuses on the doing: how to take a current operating model and make it the one the strategy actually needs.
Why redesign at all
Operating models are not redesigned because the model is broken in the abstract. They are redesigned because something specific is no longer working. Five triggers account for almost all mid-market operating model redesigns.
- The business has outgrown the model. The operating model that worked at £10m turnover stops working at £30m, then breaks at £50m. The symptoms are decision bottlenecks, fragmented data, and senior time consumed by exceptions. See Five signs your business is growing faster than its operating model.
- The strategy has shifted. A new product line, a new geography, a new channel, a shift from owning to platforming. Whenever the strategy genuinely changes, the operating model needs to change with it.
- An acquisition or merger has happened. Two operating models now have to become one, or be deliberately kept separate. This decision is the most common cause of synergy underperformance after a deal. See Why acquisition synergies fail.
- A PE investment has been made. The investment thesis sets out specific operational outcomes the operating model must support. Redesign typically begins in the first 100 days. See Operational excellence in private equity portfolios.
- Regulation or external pressure has changed the operational requirement. Consumer Duty, building safety legislation, operational resilience requirements, cyber regulation. The operating model has to absorb the new obligation by design rather than by retrofit.
The first thing to be clear about, before any redesign work, is which of these is actually driving the decision. Redesign for strategic shift looks different from redesign for scale, which looks different from redesign for integration. The sequence and the emphasis differ.
Preconditions for success
Operating model redesigns fail more often when one of three preconditions is missing. None of these is optional.
1. A clear strategic intent the operating model is meant to serve
If the strategy is unclear, contested, or in flux, fix that first. Redesigning the operating model on top of an unclear strategy produces a working machine for the wrong destination. The strategy does not have to be perfect; it does have to be specific enough that operating-model decisions can be tested against it.
2. A single accountable sponsor with the authority to decide
The redesign needs a named executive who owns the outcome, can resolve cross-functional disagreements, and is present enough in the work to make decisions without escalating to the board. In a mid-market business this is usually the CEO, COO, or CFO. Without this, every decision becomes a committee and the timeline doubles.
3. Honest assessment of change capacity
Operating model redesign lands on the same people who are also running the business. If the change load is greater than what the business can absorb, operations degrade and the redesign stalls. Change capacity is not a soft constraint; it is the binding constraint in most mid-market redesigns. Be specific about how much change the business can take in any given quarter.
The single best preparation: before commissioning the redesign, secure the sponsor's commitment to spend at least one focused half-day per fortnight on the work for the duration. Sponsors who promise more and deliver less are a more common failure mode than those who commit appropriately from the start.
Step 1: Establish the strategic intent the operating model must serve
Establish the strategic intent
Duration: 1-2 weeks. Output: strategic-intent document, agreed by SLT.
Document the business strategy in enough detail that operating-model decisions can be tested against it. The strategic-intent document should cover:
- Where the business is heading - the three-year picture of revenue, geography, customer mix, product mix
- What competitive advantages the operating model must support - speed, quality, cost, customer intimacy, scalability
- What strategic shifts are already committed to - product launches, geography expansions, channel changes, acquisitions
- What constraints are fixed - regulatory requirements, capital constraints, founder/board commitments
- The two or three operational outcomes that matter most over the next 12-18 months
This is not a re-running of the strategy. It is the translation of the existing strategy into the specific operational implications the operating model has to deliver.
Common pitfall: starting with the operating model and inferring the strategy. The work is always strategy-first. If the strategy is unclear, the redesign stalls until it is fixed.
Step 2: Map the current operating model honestly
Map the current model
Duration: 2-4 weeks. Output: current-state map across all eight components.
Document how the eight components of the operating model actually work today - not how the org chart suggests they should, and not how the leadership team would describe them in an idealised version. The eight components (from the operating model pillar) are: value chain, structure, people, technology, data, locations, suppliers, governance.
The mapping methodology:
- Value chain map. Map the end-to-end flow from customer demand to fulfilled outcome. Document the handovers between stages, the typical cycle time, and where rework happens.
- Decision-rights matrix. Who can commit money? Who can change priorities? Who approves exceptions? Document by category (financial, operational, people, customer). The matrix usually surfaces ambiguity that leadership did not know existed.
- Capability assessment. What capabilities does the current operating model rely on? Where are they strong? Where are they thin or single-point-of-failure?
- Technology and data assessment. What systems are in place? Where is data fragmented? What integrations exist or are missing?
- Governance audit. What meetings, reporting cycles, and decision forums exist? Are they well-attended, well-run, and producing decisions?
Honesty is the binding constraint of this step. The leadership team's instinct will be to defend the current model where it works. The job is to map what is, not what is intended. Use evidence: data, observed behavior, named examples. Avoid value judgements at this stage.
Common pitfall: relying on self-assessment from each function rather than examining evidence. Self-assessment produces a tidy picture; evidence produces an accurate one.
Step 3: Identify the binding constraints
Identify the binding constraints
Duration: 1-2 weeks. Output: ranked constraints with EBITDA sizing.
Not everything that is broken in the current operating model needs to be fixed. The job is to identify the two or three constraints that account for most of the underperformance against the strategic intent, and to size each.
Constraint identification follows from the gap between current-state mapping and strategic intent. Where does the current model fail to support what the strategy requires? Common patterns in mid-market businesses:
- Decision-rights ambiguity at the layer below SLT, causing decisions to wait for senior intervention
- Capability gaps in one or two functions that others are constantly compensating for
- Data fragmentation that prevents the leadership team from agreeing on operational reality
- Governance overload - too many meetings, too much reporting, too little decision-making
- Structural friction at handovers between value-chain stages where work loses momentum
Size each constraint in EBITDA terms where possible. Not exact figures - reasonable ranges. The point is to surface that some constraints matter more than others and to focus the redesign on the ones that matter most.
Common pitfall: trying to fix everything. Mid-market change capacity does not support broad redesigns. Pick two or three constraints; ignore the rest until those are resolved.
Step 4: Design the target operating model
Design the target
Duration: 3-6 weeks. Output: target-state design across all eight components, with the deltas from current state.
Design the target operating model that the strategic intent requires and the constraints diagnostic surfaced. Specify each of the eight components in the target state, identify what changes from current state, and confirm that the target is internally consistent.
Choose the archetype and shape
Select the operating-model archetype that best fits the strategy: functional, divisional, matrix, geographic, customer-centric, product-led, federated, or platform. Then decide where the target sits on the standardisation-versus-integration grid (the MIT CISR four shapes). Most mid-market businesses are hybrids; the design specifies which dimensions are standardised, which are integrated, and which are deliberately variable.
Specify the eight components in target state
For each component, document the future state and the delta from current. Be concrete:
- Value chain: new flows, new handover points, new metrics
- Structure: new groupings, new reporting lines, new decision rights matrix
- People: new capabilities required, hiring needs, development paths, role design
- Technology: what stays, what changes, what investment is needed
- Data: single source of truth, governance, quality standards
- Locations: footprint changes, hybrid working policy, where decisions get made
- Suppliers: what is sourced externally, what comes in-house, partner relationships
- Governance: meeting cadence, reporting structure, escalation paths
Pressure-test the design
Run the target design against the constraints identified in step 3. Does the design genuinely remove the constraint, or just relocate it? Test the target against three operational scenarios: a normal quarter, a high-stress quarter, and a structural shock. A design that cannot absorb a structural shock is fragile by definition.
Common pitfall: designing the org chart in step 4. The structural change should follow from the value chain, decision rights, capabilities, and governance work. If structure is the first thing decided, the rest of the design retrofits to it - which is the wrong direction.
Step 5: Sequence the transition
Sequence the transition
Duration: 2-3 weeks. Output: phased implementation plan with named workstreams, owners, and outcomes.
The sequence in which changes are made determines whether the transition lands or stalls. Three principles apply.
1. Address the highest-leverage constraint first
Whatever the diagnostic in step 3 surfaced as the binding constraint, that goes first. Resolving it produces visible benefit, builds credibility for the wider redesign, and frees capacity for the next phase.
2. Sequence by change-capacity envelope, not by theoretical ideal
The right sequence is the one the business can actually deliver, not the one that looks neatest on paper. Concurrent changes that exceed change capacity produce delivery failure across the board. Stagger.
3. Build in stabilization periods
Between waves of change, deliberately plan periods where no new structural change happens. The new ways of working need time to embed before the next wave lands. Mid-market redesigns that run three or four waves of change with no stabilization almost always produce drift back to the prior state.
The phased plan
The output is a phased plan with three or four phases, each lasting two to four months, with named workstreams, named owners, defined outcomes, and explicit stabilization periods. The total timeline is typically 6 to 12 months for a meaningful mid-market redesign.
Common pitfall: big-bang transitions. Big bang feels decisive and looks tidy. In practice, mid-market businesses do not have the change capacity, the data systems, or the people-management bandwidth to absorb large operating-model shifts in a single move. Phased is more reliable.
Step 6: Run the transition with delivery discipline
Run the transition
Duration: 4-12 months. Output: target operating model embedded, with measurable performance change.
The redesign now becomes a delivery program like any other transformation - with the additional sensitivity that it is reshaping how the business operates while it operates.
Program governance
A named program lead with end-to-end accountability. A steering group meeting on a regular cadence (typically monthly) with the sponsor in the chair. Workstream leads accountable for their specific changes. Weekly status, monthly steering, quarterly portfolio review. Standard delivery discipline.
Benefits tracking
Each constraint identified in step 3 had a sizing. Each change in step 4 was designed to remove some part of that constraint. Track the benefits realized against the benefits expected, on the same cadence as the steering review. Where benefits are not landing, investigate why - it is usually a sign that the design did not address the actual constraint, or that the change has not embedded.
Cultural and people support
Operating-model redesigns change how people work, who they report to, what they are accountable for, and how they are measured. The change-management activity sits inside the program, not bolted on afterwards. Communication, training, role design, and individual support for people whose roles change materially.
Stop-the-clock criteria
Define upfront the conditions under which the program pauses or recalibrates. If operations degrade beyond a defined threshold, the program pauses. If a phase delivers materially worse than expected, the next phase is reviewed before starting. Without stop-the-clock criteria, programs plough through evidence that the design is not landing.
Common pitfall: declaring victory at go-live. Operating models settle in over time. The new ways of working need three to six months of operating before they can be assessed properly. Post-go-live review, embedded handover, and explicit close-out are the difference between a redesign that sticks and one that drifts back.
Governance throughout the work
Three governance forums run for the duration of the redesign, each with a specific role.
| Forum | Cadence | Purpose |
|---|---|---|
| Sponsor check-in | Fortnightly, 60-90 minutes | Sponsor, program lead, and key workstream leads. Decision-making forum for issues requiring sponsor authority. Quick, structured, decision-oriented. |
| Steering group | Monthly, 90-120 minutes | Sponsor, SLT, program lead. Strategic oversight: progress vs plan, risks and issues, benefits trajectory, change-capacity assessment. |
| Workstream forums | Weekly, 30-45 minutes each | Workstream lead and their team. Operational delivery: tasks, blockers, dependencies. Owned by the workstream lead, not the program lead. |
Beyond these three, governance should be minimal. Mid-market redesigns fail more often through governance overhead than governance underinvestment. The test is whether each meeting produces decisions or just status.
Pitfalls and how to avoid them
Five pitfalls account for most mid-market operating model redesign failures. Each has a counter-pattern.
1. Restructuring before designing
The org chart is the visible artefact, so it gets changed first. The structural change locks in before the value chain, decision rights, capabilities, and governance work has been done - and the redesign retrofits to the new chart. Counter: structure is the output of operating model design, not the input. Do not move boxes until the design is agreed.
2. Designing for a strategy the business does not yet have
A target operating model that requires capabilities, technology, or culture the business does not have and has no plan to build. Counter: ground every design choice in what the business can credibly build to within 12-18 months. Aspirational designs that require capabilities the business cannot acquire produce frustration and drift.
3. Underestimating change capacity
Scheduling three concurrent changes when the business can absorb one. Counter: explicit change-capacity planning at the start, with a stated quarterly limit. When the limit is hit, queue the next change rather than start it.
4. Cutting governance corners
"We do not need a program lead for this; we will run it through the existing functions." Operating model redesign without dedicated program governance is the most common cause of stalled redesign. Counter: name a program lead with end-to-end accountability and budgeted time.
5. Stopping at go-live
Declaring success when the new structure starts operating, then withdrawing the redesign investment. Counter: schedule a 90-day post-go-live review with explicit criteria, and budget for the adjustment work that the review will surface.
Realistic timelines
Three timeline patterns are common. The right one depends on starting point and ambition.
| Pattern | Total duration | When it fits |
|---|---|---|
| Targeted redesign - one or two specific constraints | 4-6 months | The business knows what is broken and has the capability to fix it. Diagnostic confirms scope; design and transition are tight. |
| Broad redesign - multiple components, sequenced waves | 9-12 months | The operating model needs material change across several components - typical post-strategy-shift or scale-up redesigns. |
| Transformational redesign - move to a fundamentally different operating model | 12-18 months | Post-acquisition, major regulatory change, or a strategic pivot that requires a different operating archetype entirely. Phased over multiple stabilization cycles. |
Timelines that look much shorter usually skip steps; timelines that look much longer usually have governance problems. The honest range for a meaningful mid-market operating model redesign is six to eighteen months end to end.
Conclusion
Operating-model redesign is harder than it looks because the design work is the easy part. Most redesigns fail not in design but in transition - the work of moving from current to target while continuing to run the business. The six-step playbook in this article is deliberately built around that constraint: strategic intent first, honest current-state mapping second, binding constraints third, target design fourth, sequenced transition fifth, delivered with discipline sixth.
The shortest path to knowing whether your business needs a redesign at all is a focused diagnostic. The Executive Discovery Scan and the deeper diagnostic engagements are designed exactly for this purpose: surface whether the constraints are systemic and operating-model in nature, or local and functional. The right next step depends on the answer.
Is your operating model the constraint?
Independent diagnostic that identifies whether redesign is the right intervention, what scope it should cover, and how to sequence it. Fixed scope, partner-led, no obligation.
