Operating Model & Org Design

Learning objectives

By the end you can:

1. Define an operating model, from first principles, as the joint design of five levers (structure, process, governance and decision rights, capabilities, and metrics) and state precisely why redesigning structure alone (the boxes-and-lines trap) changes nothing real, naming the mechanism, not just the symptom.
2. Diagnose and redesign organizational structure using span-of-control and layer-count arithmetic, recognize a "ghost layer" (a layer whose average span is too thin to justify its own coordination overhead), and make a defensible centralize-versus-decentralize call using a stated test.
3. Choose, on purpose, among functional, divisional, and matrix structure archetypes for a given strategy and coordination need, naming each archetype's core trade-off rather than selecting one by imitation or fashion.
4. Map a core end-to-end business process, identify handoff and queueing waste, and redesign it with a quantified cycle-time improvement you can defend line by line.
5. Build a correct RACI matrix and a delegation-of-authority (DOA) table for a real decision, diagnosing and repairing the "too many Accountables, no real Responsible" failure pattern, and design the governance cadence (the standing forums) that keeps decision rights current as the organization grows.
6. Run a capability audit (a skills heatmap against the authority you are about to delegate) and make a defensible train-versus-hire-versus-redeploy call, correctly distinguished from CN6.02's deal-scale build-buy-partner decision.
7. Build a metrics cascade linking a strategic objective down to team-level measures, and name and defend against the vanity-metric trap and Goodhart's law (a single unpaired metric invites gaming the measure instead of the outcome it stands for).
8. Run a full worked operating-model redesign end to end (structure, governance/RACI, capabilities, metrics) on a single organization, correctly sequenced, and hand off the rollout/change-management journey to CN7.02.
9. (Productivity objective: R10 duality.) Use AI to draft first-pass RACI matrices, structure-option memos, and KPI-tree scaffolds, while owning every decision-rights judgment yourself and verifying every borrowed structural fact against a primary source before it reaches a client.

The duality, stated once (R10). Objectives 1–8 are the understanding objective the mastery gate rewards, you earn this node by designing a defensible operating model by hand, through a case or drill, with no tool doing the judgment for you. Objective 9 is the productivity payoff you keep afterward: AI can draft a serviceable first-pass RACI skeleton or a KPI-tree template in seconds; knowing exactly which parts, every decision-rights assignment, every DOA threshold, every capability call, remain yours to make and defend is the point.

Prerequisites & connections

Builds on. CN3.02 (Corporate, Growth & Customer Frameworks) already taught the McKinsey 7-S framework as a diagnostic lens (Strategy, Structure, Systems, Staff, Skills, Style, Shared Values) and its own practice set already showed you the symptom this module names: an "agile" strategy announced while the chart, promotion criteria, and management behavior all stay frozen (CN3.02 P10). This module does not re-teach 7-S's diagnostic categories; it teaches the construction toolkit that turns a 7-S diagnosis into an actually-built operating model: span-of-control arithmetic, a real RACI and DOA table, process redesign, a capability audit, and a metrics cascade, the mechanics 7-S names but does not itself supply. CN0.02 (The Engagement) taught delegation at the individual-task level, matching one task to one team member, with a success criterion and a check-in cadence. This module operates one level up: decision rights across a permanent organizational structure, who is accountable for a whole category of recurring decisions, not who does one task this week. The two are cousins, never the same tool: CN0.02's formula tells a Principal how to hand a market-sizing model to a Consultant; this module's RACI tells an entire company who owns pricing authority for the next three years. CN6.02 (Portfolio, Build-Buy-Partner, PMI & Divestitures) already previewed this module's toolkit under a deal clock: its Integration Management Office and 100-day PMI plan are a specific, time-boxed application of the same governance-and-capability machinery this module teaches in general form. CN6.02's build-buy-partner framework operates at the scale of acquiring an entire capability through a transaction; this module's capability lever operates at the scale of developing or reassigning the people you already employ, organic, not transactional, and Worked Example 4 states the distinction with numbers. From the Finance galaxy, the M5.01–M5.10 sector playbooks own each industry's specific operating rhythms (a bank's three-lines-of-defense, a retailer's merchandising calendar) in the depth only a specialist needs; this module teaches the generic method that adapts to any of them, the same relationship CN4.01 established for industry-reading. M4.01–M4.02 supply the "what the organization must execute" input a structure design has to serve: assumed already decided here.