1. What Is the Ashridge POLISM / Operating Model Canvas?
The Ashridge POLISM / Operating Model Canvas is a practical framework for designing a target operating model (TOM). It provides a visual “canvas” that links your strategy and value proposition to the day‑to‑day building blocks of how the organization will run. POLISM is the underlying acronym that structures the canvas: Processes, Organization, Locations, Information, Suppliers, and Management system.
In plain terms: the canvas helps leadership teams make explicit choices about the work you do (value chains and processes), how you group and govern people (organization and management system), where you do the work (locations), what data and technology you rely on (information), and what you source externally (suppliers). Filling out the canvas creates a shared blueprint for execution—clear enough to guide real design and change, simple enough to align busy executives.
This is an organization design and operating‑model framework. It is commonly used by consultants and executives to translate strategy into a coherent TOM for enterprise transformations, post‑merger integrations, and function‑level redesigns.
2. Origin and Background
The Operating Model Canvas and the POLISM acronym were developed and popularized by Andrew Campbell and colleagues at the Ashridge Strategic Management Centre. Key reference: the book “Operating Model Canvas: Aligning Operations and Organization with Strategy” by Andrew Campbell, Mikel Gutierrez, and Mark Lancelott (2017).
Motivation: leaders often jumped from strategy to org charts, leaving critical operating choices implicit—process design, locations, information flows, sourcing, and the management system. The canvas codified these choices into a single, integrated view to reduce ambiguity and accelerate implementation. The framework spread through Ashridge publications, executive programs, and consulting practice, and is now widely recognized in target operating model work.
3. How the POLISM / Operating Model Canvas Works
The canvas sits between strategy and implementation. You start by clarifying your value proposition and value chains (the high‑level flows of work that create value for customers). Then you design each POLISM dimension so the pieces reinforce one another and deliver the strategy.
The POLISM Acronym (spell‑out and intent)
P — Processes: The core and supporting value chains and key processes that deliver the value proposition end‑to‑end (e.g., idea‑to‑market, lead‑to‑cash, issue‑to‑resolution). Clarify what is standardized, where you allow variation, and the critical handoffs.
O — Organization: The structural choices and roles that execute the processes—grouping logic (product, segment, geography, function), P&L ownership, governance bodies, spans and layers, and decision rights for the few pivotal decisions.
L — Locations: Where work gets done—countries, sites, hubs, near‑/offshore models, virtual/hybrid arrangements, and co‑location choices for tightly coupled teams. Consider regulatory, talent, cost, and proximity to customers.
I — Information: The data and technology that enable work—platforms, applications, data models, integration patterns (APIs), analytics, and how information flows support decisions and compliance.
S — Suppliers: What you source externally and how—strategic partners, contract manufacturers, BPO/managed services, cloud/platform providers, and sourcing models (single vs. multi‑vendor) with SLAs and governance.
M — Management system: How you steer and learn—planning and budgeting cadences, performance dialogues, KPIs/OKRs, incentive systems, risk/compliance controls, and leadership behaviors/rituals that reinforce the model.
The Canvas Structure
Top of the canvas: Value proposition and the major value chains (core and support). This frames what the operating model must deliver.
Body of the canvas: Six POLISM boxes where you specify the target choices for each dimension. The “Management system” usually spans across, because it steers all the others.
The logic is integrative. For example, a platform strategy (value proposition) often implies: standardized Processes, product‑centric Organization with platform ownership and clear decision rights, concentrated Locations for scarce talent, cloud‑first Information architecture, a curated Suppliers ecosystem, and a Management system that funds products quarterly and measures outcomes (e.g., time‑to‑value).
4. When to Use the Operating Model Canvas
Use the canvas when you need a clear, shared picture of how the organization must operate to deliver the strategy—without getting lost in 100‑page decks.
Post‑merger integration: Harmonizing processes, structure, platforms, sourcing, and management routines across entities.
Strategic pivots: Shifts to subscription/recurring revenue, solutions, marketplaces, or outcome‑based contracts.
Function or value‑stream redesigns: Designing shared services, GBS, product/engineering ways of working, or commercial operating models.
Scaling and professionalization: Moving beyond founder‑centric ways to a scalable, explicit model.
Especially powerful when: stakeholders need a common language and a one‑page view to align rapid decisions across multiple levers (structure, tech, sourcing, metrics).
Less suitable when: you need deep process engineering (use Lean/Six Sigma), detailed decision architectures (RAPID/RACI), or technology architecture specs; the canvas is the integrator, not the detailed blueprint.
Current practice: Teams often pair the canvas with agile/product operating models, OKRs, decision‑rights frameworks, organizational network analysis (ONA), and spans‑and‑layers analytics to make each POLISM element evidence‑based and executable.
5. How to Apply the Operating Model Canvas: Step‑by‑Step
Clarify strategy and value proposition.State who the priority customers are, the problems you solve, and the sources of advantage you will build (e.g., platform reuse, solution selling, customer success). Identify 3–5 critical capabilities the operating model must enable.
Map the value chains (top of the canvas).Define core and supporting value chains at a high level—idea‑to‑market, lead‑to‑cash, deliver‑to‑operate, issue‑to‑resolution, record‑to‑report. This anchors the canvas in end‑to‑end flows rather than functions.
Agree design principles.Write 6–10 principles that will resolve trade‑offs consistently (e.g., “platforms over point solutions,” “decisions pushed to product owners,” “global standards with 20% local choice,” “single‑threaded P&L by segment”). These guide all POLISM choices.
Draft the target POLISM choices (first pass).Work box by box to outline the target state succinctly:
Processes: Which are standardized vs. variable? What are the critical handoffs and stage gates?
Organization: Primary grouping, P&L location, key roles, governance forums, and decision rights for the few pivotal decisions (portfolio, pricing, platform standards).
Locations: Site/hub strategy (onshore/nearshore/offshore), co‑location needs, hybrid model policies.
Information: Platform ownership (product/platform teams), data model guardrails, API strategy, analytics/telemetry priorities.
Keep this crisp; the canvas is a design choice document, not a process manual.
Iterate for coherence.Test for alignment across boxes. Example: If Processes emphasize speed and experimentation, does Organization empower product owners? Do Information platforms support rapid releases? Does the Management system fund quarterly and measure time‑to‑value?
Validate with evidence and “tests.”Ground choices in data: decision latency, time‑to‑market, NPS/CSAT, spans/layers, ONA patterns, cost‑to‑serve, compliance incidents. Optionally run designs through recognized tests (e.g., market advantage, difficult links, accountability, feasibility) to surface risks and mitigations.
Translate into operating mechanisms and initiatives.For each box, define the 3–5 concrete moves to implement (e.g., stand up portfolio council with RAPID; consolidate telemetry on a common platform; establish nearshore data hub; sign a managed‑service SLA for L1 support; institute monthly outcome reviews).
Sequence and pilot.Prioritize by impact and feasibility. Pilot the model in one business unit or region, measure outcomes, and refine POLISM choices and interfaces before scaling.
Embed governance and metrics.Stand up a cadence to review progress (monthly/quarterly). Track a balanced scorecard—speed (lead time, decision latency), quality (first‑pass yield), customer (NPS/time‑to‑value), cost (cost‑to‑serve), people (engagement/attrition)—and adjust canvas choices as needed.
6. Example: The Canvas in Action
Company: A $800M global fintech expanding from SMB payments into mid‑market “payments + working capital” solutions.
Problem: Strategy required faster product experimentation, a unified data platform, and a shift to relationship‑led sales. The current operating model was functionally siloed; regional tech stacks diverged; incentives over‑weighted new logos vs. expansion and risk quality.
Applying the canvas:
Value chains: Idea‑to‑market (offer lifecycle), lead‑to‑cash (with risk underwriting), issue‑to‑resolution, and fund‑to‑settle.
Processes: Standardized offer lifecycle with discovery/validation/build/scale; global underwriting policy with regional thresholds; shared incident management with 24/7 L1/L2/L3.
Organization: Product‑centric BUs for Payments and Working Capital with P&L; shared platform engineering; regional go‑to‑market aligned to segments; governance via a portfolio council (prioritization) and a risk committee.
Locations: Platform engineering concentrated in two hubs; regional GTM hubs in NA, EU, APAC; nearshore analytics center; hybrid policy for product squads with mandatory co‑location for critical ceremonies.
Information: Single data platform (customer 360, risk, telemetry); standard API contracts; product analytics for activation/retention; unified CRM/CSM tooling.
Suppliers: Managed service for L1 support (with strict SLAs), multi‑cloud infrastructure, specialist KYC/AML providers, contingent labor pool for surge testing.
Management system: Quarterly product funding; OKRs around ARR, gross retention, time‑to‑first‑value, loss rates; monthly outcome reviews; revised incentives to balance new ARR, expansion, and risk quality; decision rights (RAPID) for pricing, risk policy changes, and roadmap priorities.
Results (two quarters): Time‑to‑first‑value fell 27%; underwriting decision time dropped 35%; expansion ARR improved by 8 points; incident MTTR reduced by 22%. Employee survey items on role/decision clarity and cross‑regional collaboration rose materially. The design scaled to a new vertical with minimal friction.
7. Strengths and Limitations
Strengths
Simple, visual, and comprehensive: One canvas captures the essential operating decisions without drowning teams in detail.
Integrative logic: Forces alignment across processes, structure, tech/data, sourcing, and management routines.
Action‑oriented: Naturally translates into a set of operating mechanisms and initiatives; easy to communicate and govern.
Scalable: Works at the enterprise level, for a business unit, or for a single value stream or function.
Limitations
High‑level by design: Requires complementary depth (process engineering, decision rights, capability modeling, architecture) to implement.
Subjectivity risk: Without data and clear principles, boxes can become opinion‑driven; the canvas then reflects politics, not strategy.
“Canvas theater”: Pretty diagrams without follow‑through on mechanisms, metrics, and incentives won’t change behavior.
Static snapshot risk: Operating models drift; the canvas needs a periodic refresh as strategy, tech, and scale evolve.
8. Common Pitfalls (and How to Avoid Them)
Jumping to Organization before Processes.What goes wrong: Org charts change, but end‑to‑end flow problems persist.
How to avoid: Start with value chains and critical process choices; then match structure and decision rights.
Confusing value chains with functions.What goes wrong: Canvas replicates silos; handoffs remain broken.
How to avoid: Define true end‑to‑end flows (idea‑to‑market, lead‑to‑cash, etc.); avoid listing departments.
Ignoring the Management system.What goes wrong: New structures run on old rhythms; behaviors revert.
How to avoid: Specify planning/funding cadence, performance dialogues, OKRs/KPIs, and incentives that reinforce the model.
Under‑specifying decision rights.What goes wrong: Decisions get relitigated; escalation overload.
How to avoid: Use RAPID/RACI for a short list of pivotal decisions (portfolio, pricing, standards); publish and practice them.
Technology first, design later.What goes wrong: Tools dictate process; workarounds proliferate.
How to avoid: Fit Information to Processes and Organization; enforce platform/data guardrails.
Overlooking Locations and Suppliers.What goes wrong: Talent constraints, regulatory friction, vendor lock‑in.
How to avoid: Make explicit hub/nearshore/offshore choices and sourcing boundaries with SLAs and exit options.
No link to economics.What goes wrong: Canvas feels academic; investment decisions stall.
How to avoid: Attach simple economics: investment phasing, cost‑to‑serve, productivity targets tied to canvas choices.
One‑and‑done.What goes wrong: Fit decays; shadow processes reappear.
How to avoid: Revisit the canvas after major events (acquisitions, platform migrations) and annually as part of planning.
9. How the Operating Model Canvas Relates to Other Frameworks
Galbraith Star Model: Strong complementarity. Star defines core levers (Structure, Processes, Rewards, People). The canvas extends with Locations, Information (tech/data), Suppliers, and an explicit Management system. Many teams design with Star and document/align with the canvas.
McKinsey 7S Framework: 7S checks alignment across Strategy, Structure, Systems, Skills, Staff, Style, Shared Values. Map POLISM to the S’s (e.g., Information and Processes within Systems; Organization to Structure; Management system across Systems/Style).
Kates–Kesler Five Milestones: The milestones are the process (how to design); the canvas is the artefact (what to design and align). Use the canvas in Milestones 3–4 to capture macro and micro choices.
Goold & Campbell Nine Tests: Use the tests to evaluate alternative canvas options (market advantage, difficult links, accountability, feasibility) and to define mitigations.
Deloitte Eight Dimensions: Similar TOM scope. The canvas offers a visual schema; Deloitte’s model provides a checklist and depth in governance/decision rights and culture/leadership.
Business Model Canvas (BMC): BMC describes how you create and capture value (customers, channels, revenue). The Operating Model Canvas describes how you deliver it internally (processes, org, tech, sourcing, management system). Use BMC upstream, the Operating Model Canvas downstream.
Choosing among them: Use the Operating Model Canvas when you need a shared, integrated TOM blueprint. Pair it with Star/7S for design depth, with Nine Tests for option evaluation, and with execution toolkits to operationalize each POLISM box.
10. Key Takeaways
The Ashridge Operating Model Canvas, structured by POLISM (Processes, Organization, Locations, Information, Suppliers, Management system), turns strategy into a clear TOM.
Start with value chains and design principles; then make explicit, coherent choices across all six dimensions.
Its power is integrative and practical—aligning structure, tech/data, sourcing, and management routines to change day‑to‑day behavior.
It’s a high‑level artefact; pair it with decision‑rights, process design, architecture, and talent methods to implement.
Keep it live: pilot, measure, iterate, and refresh the canvas as strategy and platforms evolve.
11. FAQs About the Operating Model Canvas (POLISM)
What does POLISM stand for?
POLISM stands for Processes, Organization, Locations, Information, Suppliers, and Management system. These are the six design dimensions you specify on the Operating Model Canvas to describe how the enterprise will run.
How is the Operating Model Canvas different from the Business Model Canvas?
The Business Model Canvas focuses on the market‑facing logic (customers, channels, revenue). The Operating Model Canvas focuses on internal execution—how you structure processes, people, technology, sourcing, and management routines to deliver the strategy.
Is this the same as a Target Operating Model (TOM)?
The canvas is a concise way to describe a TOM. It doesn’t replace detailed design; rather, it ensures all key TOM dimensions are chosen coherently and communicated clearly before you dive into detailed process, tech, or org design.
Can small or mid‑size companies use it?
Yes. Keep it lightweight: one‑page canvas, a handful of principles, and 2–3 concrete moves per box. You’ll get clarity and alignment without heavy bureaucracy.
How long does it take to build a canvas?
A focused effort can produce a draft in 2–4 weeks with the right stakeholders. Converting it into operating mechanisms and pilots typically adds 4–8 weeks, depending on scope and complexity.
Does the canvas work for digital/product operating models?
Very well. It helps codify product team structures, platform ownership, quarterly funding, data/telemetry, and supplier ecosystems—alongside the management routines (OKRs, outcome reviews) that make product models stick.
The canvas sits between strategy and implementation. You start by clarifying your value proposition and value chains (the high‑level flows of work that create value for customers). Then you design each POLISM dimension so the pieces reinforce one another and deliver the strategy.
Use the canvas when you need a clear, shared picture of how the organization must operate to deliver the strategy—without getting lost in 100‑page decks.
