Filling in the canvas is the same as designing the operating model.

The canvas is a framing and communication tool, not the whole design effort. It structures the conversation and exposes misalignment, but each element still needs real design work behind it — process design, organization design, sourcing decisions, systems architecture. A completed canvas is the one-page summary of that work, not a substitute for it.

The six elements are independent boxes to be filled in by different teams.

The canvas is built around the value delivery chain in the Processes element; the other five elements exist to support it. Treating the boxes as parallel workstreams — HR fills in Organization, IT fills in Information — reproduces exactly the fragmentation the canvas is meant to prevent. The point is designing the elements together so they reinforce each other.

The Operating Model Canvas only works for large enterprises.

The canvas is scale-agnostic. It can describe the operating model of a whole enterprise, a single business unit, a function, or a new venture being stood up. Smaller scopes often benefit most, because a one-page model is genuinely achievable at that level of detail.

The Organization element makes the canvas a fancy org chart.

The Organization element covers one design question — how people are grouped and how they work around the core processes — and it sits alongside five others. An org chart shows reporting lines; the canvas shows whether the structure, locations, systems, sourcing, and management approach together deliver the strategy.

Operating Model Canvas

A one-page visual framework for designing and communicating how an organization will deliver its strategy. It breaks the operating model into six elements — Processes, Organization, Locations, Information, Suppliers, and Management System (POLISM) — arranged around the core work that delivers the value proposition.

Definition

The Operating Model Canvas is a strategic design tool that answers the question the Business Model Canvas leaves open. While the Business Model Canvas describes how an organization creates, delivers, and captures value — the what and why of the strategy — the Operating Model Canvas describes how that value will actually be delivered day to day. The canvas is built around the core value creation work of the organization, captured in the Processes element as a value delivery chain. The other five elements then describe how everything else supports that chain: how people are organized around the work (Organization), where the work happens (Locations), what systems and data the work depends on (Information), which work is done by partners rather than in-house (Suppliers), and how the whole operation is planned, measured, and steered (Management System). Because all six elements sit on a single page, the canvas forces the design conversation that separate org charts, systems maps, and process documents tend to avoid: whether the pieces actually fit together, and whether together they deliver the strategy.

Origin & Context

The Operating Model Canvas was created by Andrew Campbell, Mikel Gutierrez, and Mark Lancelott and published in their 2017 book, Operating Model Canvas. The authors positioned it as an operations-side companion to the Business Model Canvas: once a business model defines the value proposition, the Operating Model Canvas works out the processes, organization, locations, information, suppliers, and management system needed to deliver it.

Why It Matters

It provides a simple, visual, and holistic way to design and communicate an operating model. Operating model design work usually fragments into separate documents — an org design deck, a systems roadmap, a sourcing strategy, a location study — each owned by a different team and each optimized in isolation. The canvas puts all six elements on one page, which makes misalignment visible: an organization structure that cuts across the core processes, a supplier decision that strands a critical capability, an information landscape that does not serve the value chain. For business architects, it is a practical facilitation tool: senior leaders who will not read a fifty-page target operating model document will argue productively over a single page. It works both for describing the current operating model and for sketching design options for a target operating model before committing to detailed design.

Common Misconceptions

Myth: The Operating Model Canvas is the same as the Business Model Canvas.: Reality: The Business Model Canvas is about the what and why of the strategy — the value proposition, customers, and revenue logic. The Operating Model Canvas is about the how: the processes, organization, locations, information, suppliers, and management system that deliver the value proposition. The two are complementary, and the Operating Model Canvas was explicitly designed to pick up where the Business Model Canvas stops.
Myth: Filling in the canvas is the same as designing the operating model.: Reality: The canvas is a framing and communication tool, not the whole design effort. It structures the conversation and exposes misalignment, but each element still needs real design work behind it — process design, organization design, sourcing decisions, systems architecture. A completed canvas is the one-page summary of that work, not a substitute for it.
Myth: The six elements are independent boxes to be filled in by different teams.: Reality: The canvas is built around the value delivery chain in the Processes element; the other five elements exist to support it. Treating the boxes as parallel workstreams — HR fills in Organization, IT fills in Information — reproduces exactly the fragmentation the canvas is meant to prevent. The point is designing the elements together so they reinforce each other.
Myth: The Operating Model Canvas only works for large enterprises.: Reality: The canvas is scale-agnostic. It can describe the operating model of a whole enterprise, a single business unit, a function, or a new venture being stood up. Smaller scopes often benefit most, because a one-page model is genuinely achievable at that level of detail.
Myth: The Organization element makes the canvas a fancy org chart.: Reality: The Organization element covers one design question — how people are grouped and how they work around the core processes — and it sits alongside five others. An org chart shows reporting lines; the canvas shows whether the structure, locations, systems, sourcing, and management approach together deliver the strategy.

Practical Example

Consider a low-cost airline using the canvas to design its operations. The core Processes are the value delivery chain: fly aircraft safely and on time, turn planes around quickly, and sell tickets directly to customers. The Organization is structured around pilots, cabin crew, and ground staff, with minimal management overhead and no functions that do not serve the core chain. The Locations are secondary airports with low landing fees and fast turnaround slots. The Information element centers on a direct booking platform and operational systems for scheduling and crew rostering. Suppliers handle work deliberately kept out of house, such as catering and heavy maintenance. The Management System steers the whole model on operational discipline — punctuality, aircraft utilization, and cost per seat — rather than on service breadth. The value of the canvas is that each choice visibly reinforces the others; a premium lounge or a complex fare structure would look immediately out of place on this page.

Industry Applications

Manufacturing: Designing the production and supply chain operating model: which processes run in which plants, what work is sourced from suppliers, and how the management system steers cost, quality, and delivery across locations.
Healthcare: Mapping how a hospital or care network delivers patient care: clinical processes at the center, with staffing models, facility locations, clinical information systems, and outsourced services designed around them.
Financial Services: Sketching target operating models for banks and insurers during transformation — for example, how a shift to digital channels changes the process chain, the branch and office footprint, the systems landscape, and partner relationships.
Government and Public Sector: Communicating how an agency delivers services to citizens: core service delivery processes, departmental organization, office locations, case management information, and contracted providers on one page for policy and budget discussions.
Technology and Software: Designing the operating model behind a product organization: development and support processes, team topology, distributed or remote locations, tooling and data platforms, third-party services, and the metrics that steer delivery.

Related Terms

Operating Model: The Operating Model Canvas is a tool for designing and communicating an operating model on a single page.
Target Operating Model: The canvas is often used to sketch and compare target operating model options before detailed design work begins.
Business Architecture: Business architects use the canvas as a facilitation tool alongside capability maps and value streams when working with leadership on operating model design.
Value Stream: The Processes element at the center of the canvas is a value delivery chain, closely related to how business architecture describes value streams.
Business Capability Model: A capability model describes what an organization must be able to do; the canvas describes how work, people, places, systems, and partners are arranged to do it.