Operating Model Design

Definition

A target operating model (TOM) is the blueprint that describes how an organization delivers value -- connecting its strategy to its people, processes, technology, and governance structures. McKinsey defines an effective operating model as one designed to deliver four measurable outcomes: clarity (who does what), speed (how fast decisions move), skills (right capabilities in right roles), and commitment (employee engagement with the model). [src1]

Key Properties

• McKinsey's four outcomes: Clarity, speed, skills, and commitment -- an effective TOM must deliver all four simultaneously
• Design layers: Strategy and design principles, value chain map, organizational structure, process architecture, technology platform, role design, KPIs, supplier contracts
• McKinsey evolution: From the classic 7-S framework to the "Organize to Value" system with 12 dynamic elements
• Deloitte's six dimensions: Process, people, service delivery, technology, data, and governance
• Typical timeline: 8-16 weeks for design; 6-18 months for implementation; redesigns occur every 3-5 years
• Common triggers: M&A integration, digital transformation, cost pressure, new strategy, regulatory change, or market disruption

Constraints

• Strategy-first requirement: The model must flow from strategic choices. Organizations designing without clear strategy deliver 50% less value. [src1]
• Implementation dominance: Design accounts for only 20% of effort. Implementation -- change management, alignment, adoption -- is where most TOM transformations fail. [src2]
• Differentiation, not uniformity: Different business units need different operating models. Forcing uniformity destroys value in diverse organizations. [src4]
• Redesign frequency: TOM redesigns occur every 3-5 years. More frequent changes create "reorganization fatigue" with 15-25% productivity loss per transition. [src2]
• Cross-functional ownership: Changes owned by a single function produce incomplete designs. Requires cross-functional authority spanning all six Deloitte dimensions. [src3]

Transformation Approach Selection Decision Tree

What is the primary organizational challenge?
|
+-- Full value delivery system needs redesign
|   (process, people, tech, governance, data)?
|   +-- Triggered by new strategy / strategic pivot?
|   |   --> operating-model-design (THIS UNIT)
|   +-- Triggered by M&A?
|   |   --> post-merger-integration
|   |       + operating-model-design (THIS UNIT)
|   +-- Triggered by digital transformation?
|   |   --> digital-transformation-framework
|   |       + operating-model-design (THIS UNIT)
|   +-- Triggered by cost pressure?
|       --> cost-reduction-playbook first
|           then operating-model-design (THIS UNIT)
|
+-- Only structure, roles, reporting lines?
|   --> org-restructuring
|
+-- People/adoption challenge?
|   --> change-management-kotter-adkar
|
+-- AI/technology operating model?
|   --> ai-adoption-roadmap
|
+-- Unsure: full TOM or narrower restructuring?
    --> Assess McKinsey's four outcomes.
        If 1-2 failing --> org-restructuring
        If 3-4 failing --> operating-model-design
  

Application Checklist

1. Define strategic design principles (Weeks 1-4)
   Inputs: Corporate strategy, competitive analysis, customer value proposition
   Output: 5-8 design principles translating strategy into TOM requirements
   Constraint: Must be approved by executive committee before detailed design
   Success metric: Principles agreed; baseline assessment of McKinsey's four outcomes
2. Map value chain and design target model (Weeks 4-12)
   Inputs: Design principles, Deloitte's six dimensions, current-state assessment
   Output: TOM blueprint covering all dimensions with explicit design choices
   Constraint: Each dimension must be explicitly designed -- no defaults by omission
   Success metric: Blueprint reviewed by all affected BU leaders; gap analysis completed
3. Design governance and decision rights (Weeks 8-14)
   Inputs: TOM blueprint, RACI matrices, decision rights framework
   Output: Governance model defining who decides what, at which level
   Constraint: Top 20 most consequential decisions must be explicitly defined
   Success metric: Decision rights validated through scenario testing
4. Implement in waves with change management (Months 3-18)
   Inputs: Implementation plan, Kotter/ADKAR program, training materials
   Output: Changes rolled out in 2-3 waves with measured adoption
   Constraint: First wave should be highest-impact to build momentum
   Success metric: Four outcomes improving in each wave
5. Stabilize and refine (Months 12-24)
   Inputs: Adoption metrics, performance data, feedback, continuous improvement
   Output: Model fully operational with adaptation mechanisms
   Constraint: Allow 6-12 months stabilization before declaring complete
   Success metric: All four McKinsey outcomes measurably improved vs. baseline

Anti-Patterns

Wrong: Starting with the org chart and working outward to the operating model.
Right: Start with strategy, then design processes and governance, then structure. Structure follows process, process follows strategy. [src1]

Wrong: Designing in a consulting engagement without involving the people who will operate it.
Right: Co-design with cross-functional teams from the operating level. Co-designed models have 2x higher adoption rates. [src2]

Wrong: Designing a single, uniform model for a diversified organization.
Right: Allow differentiated models for different BUs while maintaining enterprise coherence. Ask: "what must be common vs. what must be different." [src4]

Wrong: Treating TOM design as a one-time project with a "go-live" date.
Right: Build in adaptation mechanisms (quarterly reviews, continuous feedback, performance monitoring) so the model evolves with strategy. [src2]

Common Misconceptions

Misconception: An operating model is the same as an org chart.
Reality: An org chart shows reporting lines only. An operating model defines how work flows, where decisions are made, what technology enables processes, and how governance ensures quality. Structure is one of six or more dimensions. [src1]

Misconception: Designing the model is the hard part; implementation follows naturally.
Reality: McKinsey's research shows that implementation -- not design -- is where most operating model transformations fail. Change management, leadership alignment, and iterative refinement during rollout are the critical success factors. [src2]

Misconception: One operating model design fits all business units.
Reality: Different parts of the organization often need different operating models. A shared-services function requires a different model than an innovation lab or a customer-facing unit. The key is coherence, not uniformity. [src4]

Comparison with Similar Concepts

When This Matters

Fetch this when an agent is asked about designing or redesigning an operating model, connecting strategy to execution, or evaluating whether an organization's structure supports its goals. Essential for post-merger integration, digital transformation, and strategic pivots.