Scale-Ready Operating Design
Scale-Ready Operating Design gives you a target operating model scoped for growth: the worked-out design for how your organisation runs as you serve more people - the core delivery model, the roles and decisions, the processes, the governance rhythms, and the capacity behind them - with the parts that stay fixed as you scale marked out from the parts local teams can adapt. We design it with your people, so the result is genuinely theirs.
Our Scale-Ready Operating Design gives you a target operating model built to grow, and we design eight parts: the design principles the model must obey to scale, the core model and its minimum specifications, the repeatable core processes, the roles and decision rights, the management system and governance rhythms, the capacity and unit economics of delivery, the information and sourcing requirements, and the quality guardrails with a transition roadmap to reach the model. You walk away with a design scoped for the scale you are moving to and ready to put into practice.
A model built to grow works when the people who run it helped design it. So we design with your people, drawing on the knowledge already inside the organisation and combining it with our outside insight and frameworks. The model comes out both accurate and owned, and you come away more able to redesign a part yourselves the next time growth exposes a seam.
Operating-model transformations that redesigned seven or more of the twelve operating-model elements together - process, roles, governance and systems as one set - were three times more likely to succeed than those that changed only a few. A model built for scale is a multi-part design, not a single-lever fix (McKinsey, 'Operating model transformations: Not all elements are created equal', 2021).
When scale-ready operating design helps
Scale-Ready Operating Design is the next step once you know the way you are organised will not carry the growth ahead - often straight after an audit has shown where it strains. These are the situations we are most often asked into. If one sounds like yours, this is a good place to start.
The situation | How it helps |
|---|---|
Growth has outpaced how you are organised | Designs a model sized for where you are heading, with the core processes, roles and capacity set for the scale you are moving to rather than the size you were |
Serving more people makes cost and complexity rise in lockstep | Builds the capacity and unit-economics logic into the model, so adding volume adds capacity in a planned way instead of adding headcount and firefighting |
What made the service good is starting to slip as you grow | Isolates the core of your delivery and codifies its minimum specifications, so the non-negotiables stay fixed while teams adapt the edges to local demand |
Every new site or team reinvents how the work is done | Writes the core delivery processes down so they run the same whether one team does them or ten, freed from tribal knowledge and heroics |
Decisions bottleneck at the founders as headcount climbs | Sets roles and decision rights for a bigger organisation, so growth does not force a return to founder-and-firefight mode |
You want a design your people will actually adopt as you scale | Builds it with the people who run the work, so it lands as theirs and holds up as the organisation gets bigger |
What we design
We design eight parts of the operating model, and make each one concrete enough to grow on:
- Design principles for scale - The handful of agreed rules the model must obey to grow - what stays standard, what can flex, what quality can never be traded - set with your leaders before any structure is drawn.
- The core model and its minimum specifications - The heart of your delivery isolated and written down: the non-negotiable steps that make the service work, held fixed, and the parts teams can adapt locally as you serve more people.
- Repeatable core processes - The delivery workflows written down so they run the same whether one team does them or ten, freed from tribal knowledge and heroics.
- Roles, structure and decision rights - Who owns what and who decides what as headcount grows, mapped so growth does not create bottlenecks, turf or a return to founder-and-firefight mode.
- Management system and governance rhythms - The planning, review, escalation and performance rhythms - and the metrics behind them - that keep a bigger organisation aligned and honest without slowing it down.
- Capacity and unit economics of delivery - How the model adds capacity as demand rises - the staffing, cost and workload maths - so serving more people does not make cost and complexity rise in lockstep.
- Information and sourcing at the principles level - The information flows, supporting systems and supplier or partner relationships the model needs before volume arrives - designed as requirements with your technology and finance leads, not built by us.
- Quality guardrails and the transition roadmap - The standards and checks that protect what makes your service good as it scales, plus the sequenced roadmap that moves you from today's way of working to the new model without dropping service on the way.
Why these eight
These eight are the parts that have to line up for an operating model to grow as one whole. New roles with vague decision rights bottleneck where the old ones did; clear decisions with undesigned processes still snag at the handoffs as volume rises; and a model with no minimum specifications either freezes the edges you needed to flex or lets the core drift until the service that made you worth scaling is gone. So we design them together, as a set built for growth.
The eight follow the established operating-model and scaling frameworks, so the design covers what a full model built to grow should - the principles and the core-model specs up front, the processes, capacity and governance behind them, and the roadmap to reach it - not just a bigger org chart. We use them to make sure the design is complete, rather than as a model to run at you.
How it works
The method produces one thing: a target operating model your organisation can grow on. It works by designing the model with your people rather than presenting one to them. Your organisation already holds most of the knowledge about how the work really runs and where it strains under load, so our job is to draw that out, combine it with the outside frameworks and pattern-recognition you bring us in for, and shape the two into a design that is both expert and genuinely owned. It works in four modes.
- We start with your design principles for scale - Before anything is designed, we agree a short set of principles with you - the rules the model has to follow to grow, like 'standardise the core, adapt at the edges' or 'decisions at the lowest capable level'. They turn every later trade-off, especially what stays fixed as you scale, into a matter of principle rather than politics.
- We design with the people who run the work - The people delivering the service know where the current model bends under volume in ways no org chart shows. We build with them, turning that knowledge into design choices - so the model fits how the work actually goes, and is owned by the people who will run it at scale.
- We bring the outside insight and the frameworks - An inside view on its own tends to design around today's people and habits, so we bring the outside pattern - what makes services like yours scale without losing their edge, and frameworks that check the design is complete and the parts line up before you commit.
- We leave the capability behind - Throughout, we work so your people learn to design, not just watch us design. By the end you have a scale-ready model and a sharper sense of how the decisions were made, so the next adjustment growth demands is one you can make yourselves.
The thinking behind the method
We design with your people rather than deliver to them because of a hard fact about scaling: the model that gets adopted beats the model that looks best on paper. An operating model built to grow is a set of new behaviours that thousands of daily decisions follow across more teams and more sites, and people follow a model they helped design - they understand why it is shaped the way it is, and they trust that it fits how the work really goes as it gets bigger.
So co-design gives you a model that is both right and real. The knowledge inside the organisation makes it accurate and shows where it strains under load; designing it together makes it owned; and the outside frameworks keep the two from simply reinforcing what already struggles to scale. Get all three and the model holds as you grow. Miss one and you get an expert model that gets rejected, an owned model that stays parochial, or a clever model that never survives contact with real volume.
What you get
By the end, you have four things:
- The scale-ready target operating model itself - a worked-out design across all eight parts, on a page and in the detail beneath it, with the core model's minimum specifications codified so it is clear what stays fixed and what adapts as you grow.
- A transition roadmap - the sequenced plan from today's way of working to the model you have designed, resetting decision rights first and then structure, with phasing and dependencies set out so you know what to do first and what it rests on.
- A design that is genuinely yours - built with your people, grounded in how you actually deliver, so it is owned and used rather than filed.
- The capability left behind - your people come out more able to design, so the next adjustment growth demands is one you can make yourselves.
The best scale-ready model is both fixed and flexible, and those pull against each other: fidelity wants to lock the core so quality holds, growth wants the edges free to adapt to each new place. Drawing that line well is the craft of the work.
How we hand it over - and what happens next
The point of the work is a target operating model your organisation can grow on, so we take care with how it lands. Because your people helped design it, the handover confirms something they already understand rather than revealing it cold. We walk through the finished model, the core-model minimum specifications and the transition roadmap - why it is shaped the way it is, what stays fixed as you scale, what teams may adapt, and what the first moves are.
From there, some organisations take the model and implement it themselves, now more able to. Others bring us alongside for the harder parts of making it real, which is where implementation picks up. The design has done its job when you can see the model built to grow clearly, believe in it because you built it, and know the first steps to get there.
Where this sits
Scale-Ready Operating Design is the second step in how we approach scaling. It follows the Scalability Audit, which reads where the way you are organised strains under growth today, and leads into implementation, which turns the model into how the organisation runs day to day. It also stands on its own - if you already know your growth will outpace how you are organised and want the operating model designed properly and owned, this is where to start.
Common questions
Is this just a set of workshops?
No - what you get is a designed target operating model scoped for growth, with the core model's minimum specifications codified and a transition roadmap to reach it. We work with your people in the room, because that is how the design becomes both accurate and owned, and the sessions are the means to that. You walk away with the worked-out model itself, and a design your people helped shape and are ready to grow on.
What exactly is a scale-ready operating model?
It is the design of how your organisation will run as it grows - the target operating model, scoped for growth. It brings together the core delivery model and its minimum specifications, the repeatable processes, the roles and decision rights, the management system and governance rhythms, and the capacity and unit economics as one joined-up whole, along with the roadmap to get there. What makes it scale-ready is the minimum specs - the non-negotiables held fixed for quality against the parts free to adapt as volume rises.
How is this different from the Scalability Audit?
The audit reads the shape you have now - where the way you are organised strains under growth, and why. Scale-Ready Operating Design is the next step: it produces the target operating model to build instead. The audit answers 'what will break as we grow'; this answers 'what to build to grow'. Many clients do the audit first, because designing on a clear read of the current state sets the design up well, but if you already have that clarity, you can start here.
How is this different from operating model design?
This designs a target operating model scoped for growth, not a steady-state one. General operating model design builds a model for how you run today. Scale-Ready Operating Design adds the scale-specific moves: design principles for growth, the core model's minimum specifications - what must stay fixed to protect quality against what local teams may adapt as you serve more people - and the capacity and unit economics of scaling, so the model holds as volume rises rather than describing the size you already are.
Does this cover our technology, systems and financial modelling?
At the level an operating model needs. We design the information, systems and sourcing the model depends on as principles and requirements, with your own technology and finance leads - what the model asks of your systems, what is done in-house and what is partnered. We design the capacity and unit-economics logic with your finance lead too. We design the operating model, not the IT architecture or the financial model itself, so where deep technical build is needed we shape it alongside the specialists who own it.
Why build it with our people rather than design it for us?
Because a model only holds as you grow if it is used. The model that gets adopted beats the one that only looks best on paper, and people adopt what they helped design far more readily than what is handed to them. Your people also hold knowledge about how the work really runs and where it strains under load that no outside team can fully see. Co-design combines that inside knowledge with our outside frameworks, so the model is both right and real.
Ready to design an operating model built to grow?
Tell us what is prompting the growth and where you sense the way you are organised will strain, and we will talk through what a Scale-Ready Operating Design would look like for you - and whether an audit first would set it up well. If you already know where you stand, we can go straight to designing the model, built with your people so it is genuinely yours.