Your operating model is how your organization converts strategy into repeatable, measurable work. It arranges capabilities, processes, technology, and decision rights so that every team knows what to do, who decides, and how performance gets tracked. If your strategy is changing and your execution is not keeping up, the gap is almost always an operating model problem.
The immediate next step: run a short diagnostic to find your biggest strategy-to-performance gap before you touch structure, headcount, or technology.
30-day actions:
- Identify the top three places where strategy and execution diverge
- Map who currently owns each major decision and where authority is unclear
- Gather baseline KPIs: time-to-decision, cycle time, and cost-to-serve
60-90 day actions:
- Set 7–15 specific design principles to guide trade-off decisions
- Map your core capabilities and score each against strategic importance and current performance
- Choose a configuration archetype and draft a governance model
90-180 day actions:
- Launch a scoped pilot in one business unit or capability cluster
- Measure early indicators: decision speed, process cycle time, talent readiness
- Govern the pilot with a clear owner, a defined review cadence, and explicit success criteria before scaling
Key Takeaways
A well-designed operating model is the mechanism that converts strategy into measurable execution: and the diagnostic is always the right place to start.
| Point | Details |
|---|---|
| Define before designing | The operating model covers capabilities, processes, technology, governance, and talent: not just structure. |
| Use McKinsey’s 12 elements | Align all 12 elements as a system; improving one in isolation routinely degrades another. |
| Set 7–15 design principles | Specific, fact-based principles make trade-offs objective and prevent incumbency-driven design. |
| Pilot before scaling | Sequence pilots by strategic impact and sponsor readiness; measure clarity and speed within 90 days. |
| Commerce Catalyst diagnostic | Commerce Catalyst’s structured diagnostic turns workshop scores into a prioritized 90-day action plan with clear ownership. |
Table of Contents
- What is an operating model, and how does it differ from a business model?
- Why does operating model design produce measurable business outcomes?
- What are the core elements of an operating model?
- How do you design a target operating model step by step?
- Which operating model archetype fits your organization?
- How do you lead implementation without losing momentum?
- How do you measure success and plan realistic timelines?
- Which tools and frameworks should you use?
- What are the most common pitfalls, and what are the nine rules for getting it right?
- A practitioner diagnostic you can run in one leadership workshop
- How Commerce Catalyst helps you move from diagnostic to results
- Sources
What is an operating model, and how does it differ from a business model?
The operating model is the internal architecture that makes strategy executable. Academic research confirms the distinction is precise: the business model describes what you do and why customers pay for it: your value proposition and revenue logic. The operating model describes how you actually deliver that value, day after day, at scale.
Think of it this way: a business model is a promise. The operating model is the system that keeps it.
What an operating model covers:
- Organizational capabilities and how they are sourced (build, buy, partner, outsource)
- Core processes and how work flows across functions
- Technology and data infrastructure that enables work
- Governance and decision rights: who decides what, at which level
- Talent architecture: the skills, roles, and behaviors the model requires
What it intentionally excludes: high-level corporate strategy (the “where to play” choices), brand positioning, and financial capital allocation decisions. Those belong to the strategy layer above. The operating model translates those choices into operational reality.
The most common category error leaders make is treating structure as the operating model. Redrawing the org chart is not redesigning the operating model. Structure is one element. The operating model is a system of interdependent elements, and changing one without adjusting the others is why so many reorganizations fail to move performance.
Why does operating model design produce measurable business outcomes?
The case for investing in deliberate operating model design is not philosophical. McKinsey’s Organize to Value framework identifies four measurable outcomes a well-designed model delivers: clarity, speed, skills, and commitment. Each one has a direct line to financial performance.
Clarity means every team understands its mandate, its decision rights, and how its work connects to strategy. Organizations with high clarity reduce duplicated effort and cut time-to-decision, which shows up in faster product launches and lower overhead.
Speed is the operating model’s most visible output. When processes are designed around strategic priorities rather than inherited from history, cycle times drop. A consumer brand that redesigned its demand-planning process around a direct-to-consumer model, rather than a wholesale model it had outgrown, cut its order-to-ship cycle by weeks, not days.
Skills means the model is designed around the capabilities the strategy actually requires, not the ones the organization happens to have. This drives talent investment toward the strongest roles.
Commitment is the least-discussed outcome and often the most decisive. When people understand the model, see their role in it, and are rewarded for the behaviors it requires, discretionary effort follows.
Common drivers for redesign:
- A strategy shift (new market, new channel, new product category)
- Digital or AI transformation that changes where and how work gets done
- Evolving customer expectations that demand faster, more personalized service
- Regulatory change that alters compliance requirements or reporting structures
- Rapid scale that outpaces the current governance model
- Cost pressure that requires a different sourcing or footprint configuration
- Hybrid and distributed work that breaks legacy coordination assumptions
The KPIs that signal a healthy operating model include metrics such as time-to-decision, process cycle time for core workflows, cost-to-serve, and talent readiness scores tied to strategic capability gaps.
What are the core elements of an operating model?
McKinsey’s Organize to Value frames the operating model as a system of 12 interdependent elements. The power of this framing is not the list itself: it is the insistence that these elements interact. improving one in isolation routinely degrades another.
| Element | What it covers | Common misalignment signal |
|---|---|---|
| Purpose | Why the organization exists beyond profit | Strategy shifts without revisiting purpose |
| Value agenda | The specific bets that drive value creation | Too many priorities, none fully resourced |
| Structure | How work is grouped and reported | Structure inherited from a prior strategy |
| Ecosystem | External partners, platforms, and networks | Partnerships not integrated into governance |
| Leadership | Behaviors and capabilities of the leadership team | Leaders rewarded for old-model behaviors |
| Governance | Decision rights, forums, and accountability | Decisions escalated unnecessarily or made too slowly |
| Processes | How core work flows end-to-end | Processes designed around functions, not outcomes |
| Technology | Systems, data, and digital infrastructure | Tech investments not tied to capability priorities |
| Behaviors | The norms and ways of working that drive performance | Culture misaligned with new model requirements |
| Rewards | Incentives, recognition, and consequences | Incentives that reward old behaviors |
| Footprint | Where work gets done (geography, sites, remote) | Footprint decisions made on cost alone |
| Talent | Skills, roles, and workforce composition | Talent strategy disconnected from capability map |
The alignment test is simple: pick any two adjacent elements and ask whether a change in one would require a change in the other. If the answer is consistently “yes” and your organization is not managing those dependencies, you have a design risk.
Pro Tip: Assign a named owner to the operating model document itself: not a committee, a single accountable leader: and set a formal review cadence (at minimum annually, and triggered by any major strategy change). A model without an owner drifts.
How do you design a target operating model step by step?
The design process has six steps. Each builds on the last, and skipping any one of them is the most reliable way to produce a model that looks good on paper and fails in practice.
Step 0: Frame strategic outcomes and boundaries
Before any design work begins, the senior leadership team must agree on two things: the strategic outcomes the new model must deliver, and the boundaries of the redesign (which parts of the organization are in scope). Without this framing, design teams default to improving what they know rather than what the strategy requires.
Step 1: Diagnose the current state
A concise diagnostic identifies the top strategy-to-performance gaps. Practitioner experience shows that the most damaging gaps are rarely visible in the org chart. They live in the white space between functions: the handoffs, the unclear decision rights, the processes that were designed for a business that no longer exists. The diagnostic should surface: where decisions are slow or contested, where process cycle times are longest, where talent is misaligned to strategic priorities, and where technology is enabling or blocking work.
Step 2: Set design principles
Bain recommends drafting 7–15 specific, fact-based design principles before evaluating any structural options. These principles do the work of making trade-offs explicit and objective. A principle like “decisions about customer experience are made closest to the customer” is testable. A principle like “we will be customer-centric” is not. The difference matters when you are choosing between a centralized and a decentralized configuration.
Step 3: Map capabilities and make sourcing decisions
Deloitte’s capability-mapping approach starts by identifying every capability the organization needs to execute strategy, then scoring each on two dimensions: strategic importance (how critical is this capability to competitive differentiation?) and current performance (how well does the organization perform it today?). That scoring drives sourcing decisions.
| Capability score | Sourcing recommendation |
|---|---|
| High importance, high performance | Build and protect internally |
| High importance, low performance | Build urgently or acquire |
| Low importance, high performance | Consider outsourcing or partnering |
| Low importance, low performance | Outsource or exit |
Step 4: Choose configuration and design decision rights
Configuration answers the question of where work gets done and how authority is distributed. The main choices are centralized, decentralized, product-centric, and platform or ecosystem models. Decision-rights design: specifically, a RACI (Responsible, Accountable, Consulted, Informed) for each major decision type: is the mechanism that makes the configuration real. Without it, the configuration is theoretical.
Step 5: Design governance, KPIs, and a pilot plan
Governance defines who decides, who funds, and who measures. KPIs should be tied directly to the four outcomes: clarity metrics (decision-rights clarity scores, escalation rates), speed metrics (cycle time, time-to-decision), skills metrics (capability gap scores, training completion), and commitment metrics (engagement scores, voluntary attrition in key roles). The pilot plan sequences changes by impact and feasibility, not by organizational politics.
Step 6: Implement, pilot, and adapt
Deloitte’s guidance on designing for changing market needs emphasizes that next-generation operating models must be connected, dynamic, and agile. That means building adaptation into the governance model from day one: a named owner, a review cadence, and a budget for incremental changes. The pilot is not a test of whether the design is perfect. It is a structured way to learn what needs adjustment before scaling.
Pilot sequencing criteria:
- High strategic impact relative to implementation complexity
- A willing, capable sponsor in the pilot unit
- Measurable outcomes within 90 days
- Low enough disruption risk to allow honest learning
Which operating model archetype fits your organization?
Bain’s analysis of winning operating models makes a point that is easy to underestimate: similar companies in the same industry often run fundamentally different operating models and both succeed. The model has to fit the company’s strategy, culture, and organizational DNA: not an industry template.
Common archetypes:
- Centralized: Authority and shared services concentrated at the corporate level. Works well for organizations where consistency, compliance, and cost efficiency are the primary strategic levers.
- Decentralized: Business units or regions operate with significant autonomy. Fits organizations competing in diverse markets where local responsiveness is a differentiator.
- Product-centric: Teams organized around products or product lines with end-to-end accountability. Accelerates time-to-market and customer feedback loops.
- Platform or ecosystem: A core platform serves internal and external participants; value is created through network effects and ecosystem orchestration. Requires significant technology investment and governance sophistication.
- Hybrid: Combines elements of two or more archetypes, typically centralizing shared services while decentralizing customer-facing operations.
| Dimension | Centralized | Decentralized | Product-centric | Platform/Ecosystem |
|---|---|---|---|---|
| Best for | Large, compliance-driven organizations | Diverse, multi-market businesses | Fast-moving product companies | Digital-native or platform businesses |
| Speed to implement | Moderate | Moderate | Fast within product teams | Slow (infrastructure-heavy) |
| Cost/investment | Lower shared-service cost | Higher duplication risk | Moderate | High upfront |
| Disruption risk | High for field teams | Low at center | Moderate | High across the board |
| Centralization degree | High | Low | Medium | Variable by layer |
| Talent impact | Specialists at center | Generalists at edge | Product-focused T-shapes | Platform engineers + ecosystem managers |
| Adaptability | Lower | Higher at unit level | High within product scope | Highest at scale |
Choosing your archetype: three tests. First, strategic fit: does the archetype’s decision-rights structure match where your competitive advantage lives? Second, capability readiness: does your organization have the talent and technology the archetype requires, or can you build it within a realistic timeline? Third, change appetite: how much disruption can your organization absorb without losing performance during the transition?
How do you lead implementation without losing momentum?
Research on redesign success factors is unambiguous on one point: early and visible senior leadership involvement is the single most important variable. Without it, redesigns become exercises in defending the status quo. Leaders who are not aligned at the start will reliably protect their current scope, and the design will bend around their resistance rather than around strategic logic.
Securing alignment early means:
- A named executive sponsor with authority over the redesign scope
- A leadership team that has agreed on the design principles before any structural options are presented
- A governance forum that meets regularly and has real decision-making authority, not just advisory status
Governance for implementation follows a simple pattern: one person accountable for the overall redesign outcome, a steering group that approves major decisions and resolves escalations, and a delivery team that executes and reports progress against milestones. The steering group should include finance, HR, and technology leads: not just the business unit heads most directly affected.
People and incentives are where most implementations quietly fail. Talent selection for new roles should be based on the capabilities the new model requires, not on tenure or political capital. Incentive structures must be updated before the new model goes live, not after. Asking people to behave differently while rewarding them for old behaviors is a design contradiction that no amount of change management can fix.
Change-management checklist:
- Communicate the why before the what: leaders need to understand the strategic rationale, not just the structural outcome
- Identify and engage resistors early; their concerns often surface real design risks
- Create visible early wins in the pilot to build credibility for the broader rollout
- Build a communication rhythm: regular updates, honest progress reporting, and a clear escalation path for concerns
Transition risks and mitigations:
- Talent flight in key roles: mitigate by identifying critical roles early and making retention decisions before the redesign is announced
- Process gaps during transition: mitigate by running parallel processes during the pilot rather than cutting over immediately
- Governance vacuum: mitigate by activating the new governance structure before the old one is dissolved
How do you measure success and plan realistic timelines?
Success metrics should map directly to the four outcomes McKinsey identifies. The table below gives example KPIs for each, along with the window in which you should expect to see movement.
30-90-180 day milestone map:
- Days 1–30: Governance structure activated; pilot scope confirmed; baseline KPIs captured; design principles ratified by the leadership team
- Days 31–90: Pilot launched; early clarity and speed metrics tracked; first governance review completed; talent gaps identified and addressed
- Days 91–180: Pilot results reviewed; scale decision made; incentive structures updated; continuous improvement cadence embedded in governance
Cost and effort vary significantly by scope and organization size. A focused diagnostic and design sprint for a single business unit typically requires a small internal team (three to five people) plus external advisory support over six to twelve weeks. A full enterprise redesign is a multi-quarter program with dedicated program management, change management resources, and technology investment. The most common budget error is underinvesting in change management and talent transition relative to design and technology.
Review cadence: at minimum, review the operating model formally once per year and trigger an unscheduled review whenever a major strategy change, acquisition, or market disruption occurs. Deloitte’s guidance on digital transformation frames this as treating the operating model as a product: it needs an owner, a roadmap, and a budget for incremental improvement.
Which tools and frameworks should you use?
The right toolkit depends on where you are in the design process and the scale of the organization. No single tool covers the full journey.
Core tools and when to use them:
- Capability mapping: Use at Step 3 of the design process to inventory capabilities, score them on strategic importance and performance, and drive sourcing decisions. Deloitte’s architecting framework provides templates for this. A basic capability map captures: capability name, owner, strategic importance (1–5), current performance (1–5), and sourcing recommendation.
- Business Model Canvas: Use at Step 0 to align the leadership team on the value proposition and revenue logic before designing the operating model. It prevents the common error of designing an operating model for a business model that is already changing.
- Value chain analysis: Use during diagnosis to map how value flows from inputs to customer outcomes and identify where the biggest process gaps and cost inefficiencies sit.
- PESTLE analysis: Use during the framing phase to surface external drivers (political, economic, social, technological, legal, environmental) that should shape design principles.
- Strategic workforce planning: Use at Step 3 alongside capability mapping to size talent gaps and build a realistic plan for filling them.
- Enterprise architecture tooling (BOC ADOIT and comparable EA platforms): Use for larger organizations that need to record architecture artifacts, manage dependencies across systems, and maintain a living operating model at scale. For smaller teams, a lightweight capability map and a governance RACI in a shared document achieves most of the same purpose at a fraction of the cost and complexity.
Simple governance RACI template:
| Decision type | Responsible | Accountable | Consulted | Informed |
|---|---|---|---|---|
| Operating model design changes | Program lead | Executive sponsor | Business unit heads, HR, Finance | All affected teams |
| Pilot scope and budget | Program lead | Executive sponsor | Finance, Technology | Steering group |
| Talent selection for new roles | HR lead | Business unit head | Program lead | Executive sponsor |
| KPI review and escalation | Program lead | Steering group | Business unit heads | Executive sponsor |
Tool selection guidance: for organizations under 500 people, a well-maintained set of shared documents (capability map, RACI, design principles, KPI dashboard) is usually sufficient. For organizations above 1,000 people, or those running complex multi-geography or multi-entity structures, EA tooling like BOC ADOIT provides the artifact management and dependency tracking that spreadsheets cannot reliably sustain.
Pro Tip: Pair the Business Model Canvas with your capability map in the same leadership workshop. The canvas surfaces what the business model requires; the capability map reveals what the organization can actually deliver. The gap between them is your design brief.
What are the most common pitfalls, and what are the nine rules for getting it right?
Most operating model redesigns that fail do not fail because of bad design. They fail because of predictable, avoidable execution errors. McKinsey’s updated research on redesign success identifies nine rules that statistically improve outcomes.
Top pitfalls to avoid:
- Focusing the redesign on the org chart rather than on processes, decision rights, and capabilities
- Skipping the diagnostic and designing from assumptions rather than evidence
- Involving senior leaders only at the approval stage rather than throughout the design
- Redesigning structure without rewiring the core processes that cross functional boundaries
- Selecting talent for new roles based on incumbency rather than capability fit
- Building governance structures that exist on paper but have no real authority or meeting cadence
- Leaving incentive structures unchanged while expecting new behaviors
The nine rules for redesign success:
- Align the senior leadership team on strategic outcomes before any design work begins
- Diagnose the current state rigorously: surface process gaps and white-space failures, not just structural inefficiencies
- Set specific, fact-based design principles that make trade-offs objective
- Rewire core processes end-to-end, not just within functions
- Invest in people: select talent for capability fit, not tenure
- Tie incentives explicitly to the behaviors the new model requires
- Manage transition risk actively: run parallel processes during pilots, protect critical talent, and maintain service levels
- Build governance with real authority and a regular cadence from day one
- Treat the model as a living system: assign an owner, set a review cadence, and budget for continuous improvement
Pro Tip: The biggest behavioral trap in redesign is what practitioners call “design by default”: where the final model reflects the preferences and political capital of incumbents rather than the logic of design principles. The antidote is to present structural options anonymously, evaluated against principles, before revealing which option maps to which leader’s current scope.
A practitioner diagnostic you can run in one leadership workshop
The following diagnostic gives you a scored, repeatable instrument across ten dimensions. Run it with your senior leadership team in a two-hour workshop. Each dimension is scored 1–5 (1 = significant gap, 5 = strong fit). A total score below 30 signals a redesign is overdue. Scores between 30 and 40 indicate targeted improvements are needed. Above 40 suggests the model is broadly sound but may need tuning in specific areas.
Scoring dimensions:
- Strategy alignment: Does the current operating model reflect the current strategy, or a prior one?
- Capability fit: Are the organization’s highest-performing capabilities aligned to its highest-priority strategic bets?
- Decision rights clarity: Do people know who decides what, and are decisions made at the right level?
- Process health: Are core end-to-end processes designed around strategic outcomes, or around functional convenience?
- Technology enablement: Does the technology stack enable the work the strategy requires, or create friction?
- Talent readiness: Does the organization have the skills the strategy requires in the roles that matter most?
- Governance effectiveness: Does the governance model make decisions at the right speed with the right information?
- Incentive alignment: Are people rewarded for the behaviors the new model requires?
- Change capacity: Does the organization have the leadership bandwidth and change management capability to execute a redesign?
- Model ownership: Is there a named owner for the operating model with authority to drive updates?
Scoring guidance:
- Red (1–2): This dimension is a critical constraint. Address it in the first 90 days.
- Amber (3): Functional but suboptimal. Include in the 90–180 day plan.
- Green (4–5): Performing well. Monitor and protect during any redesign.
Translating results into a 90-day pilot plan:
- Identify the two or three dimensions scoring red
- For each, define a specific, measurable improvement target and assign an owner
- Sequence pilots around the highest-impact red dimensions that also have a willing sponsor and measurable outcomes within 90 days
When your diagnostic surfaces multiple red scores across governance, decision rights, and process health simultaneously, that pattern typically signals the need for external support. A fractional COO or an advisory engagement can compress the diagnostic-to-pilot timeline significantly. Commerce Catalyst’s DTC Operator Diagnostic is built for exactly this moment: a structured diagnostic that turns workshop scores into a prioritized action plan with clear ownership.
What the theory misses: and what actually moves the needle
The most common discovery in a diagnostic is not a structural problem. It is a process gap that everyone in the organization already knows about and has learned to work around. The gap between marketing and operations in a consumer brand, for example, is rarely a reporting-line problem. It is a handoff problem: a process that was never designed, a decision right that was never assigned, and an incentive structure that rewards each function for improving its own metrics rather than the shared outcome. The org chart looks fine. The work is broken.
The second thing that consistently surprises leaders is how much of their operating model was designed by default. Nobody decided that customer escalations would take three days to resolve. It just happened, because the process was never explicitly designed and nobody owned the outcome. Treating the operating model as a living product: with an owner, a roadmap, and a regular review: is the single most practical shift a leadership team can make.
How Commerce Catalyst helps you move from diagnostic to results
Designing an operating model is one thing. Getting your leadership team aligned, your capabilities mapped, and your first pilot launched within 90 days is another. Most organizations have the strategic intent. What they lack is the structured process and the outside perspective to cut through the internal noise.
Commerce Catalyst works directly with consumer brand founders and senior leaders to run the diagnostic, set the design principles, and build the 90-day pilot plan. The engagement shapes are deliberately flexible: a one-time financial health assessment to identify your biggest operating constraints, a scoped advisory project to design and pressure-test a target operating model, or an ongoing fractional COO engagement to own the implementation and keep the model current as your strategy evolves. No long-term retainer required to start. The diagnostic is the first step, and it produces a prioritized action plan you can take to your board within days.
Sources
The following sources are cited throughout this article and offer deeper value for leaders who want to go further.
- A new operating model for a new world: McKinsey
- Architecting an operating model: Deloitte Insights (PDF)
- Design principles for a robust operating model: Bain
- Opus: academic research on operating model distinctions
- Add value instead of changing the org chart: MacNY