An enterprise operating model is not an org chart. It is the working system that turns strategy into daily execution — decision rights, incentives, ownership, workflows, and the decision architecture that sits above them.
It is also the artefact that Digital Transformation programmes most consistently fail to change, and the artefact that Digital Reengineering starts with.
What an operating model actually is
An operating model has four load-bearing components.
- Decision rights. Who is allowed to decide what, on what timescale, with which sign-offs. This is not an org chart question — it is a real-behaviour question. Two enterprises with identical org charts can have entirely different decision-rights realities.
- Incentives. What behaviours the compensation and promotion system actually rewards, distinct from what leadership says it rewards. The gap between the two is often where transformation programmes stall.
- Ownership. Who is measured on the outcome of a given workflow or capability, in a way that shows up in their scorecard. Diffuse ownership is a common failure mode; every function "contributes" and no function is measured on the result.
- Workflows. The actual sequences by which work moves through the enterprise — including the informal handoffs, workarounds, and shadow processes that don't appear in the documented procedure.
The operating model is the interaction of these four components. Changing any one without adjusting the others tends to produce visible activity and invisible results.
Why leaders should care
Every technology decision an enterprise makes is either constrained by, or reinforcing, its operating model. There is no neutral technology decision.
Deploy a new CRM into an operating model whose incentives point at last year's sales structure, and the CRM will be used to record what the old process required. Deploy an AI-assisted workflow into an operating model whose decision rights still route every exception to a legacy approval chain, and the AI's outputs will queue up behind that chain.
The technology functions. The productivity does not materialise. The pattern is structural, not accidental.
What a well-designed operating model looks like
There is no single right answer — operating models are context-dependent. But several qualities distinguish the ones that hold up.
- Decision rights are aligned to the speed the market demands. A three-week approval cycle for a decision the market rewards in three days is a structural failure, not a governance strength.
- Incentives point at the outcome the enterprise is trying to deliver, not at the outcome the enterprise historically measured.
- Ownership is legible. For any material capability, one leader can be pointed to whose scorecard visibly reflects that capability's performance.
- Workflows are honest. The documented process and the actual process are the same process. Where they diverge, the divergence is intentional and understood, not a shadow curriculum operators have accumulated because the documented process cannot cope.
The role of the operating model in reengineering
The founder-locked claim behind Digital Reengineering is that the operating model precedes the technology decision. That claim rests directly on the observation that operating-model failures reproduce themselves across generations of technology choice.
Redesigning the operating model is politically expensive. It touches compensation, reporting lines, and executive turf. This is why most transformation programmes avoid it and default to platform selection instead. It is also why so many transformation programmes converge on the same failure pattern.
Where to start
Two questions expose an operating model quickly.
First: pick a decision the enterprise made in the last quarter that took longer than the business needed. Ask which of the four operating-model components — decision rights, incentives, ownership, workflow — caused the delay.
Second: pick a KPI the CEO cares about that has not moved in eighteen months. Ask which of the same four components is misaligned with that KPI.
If either question produces an unclean answer, the operating model has structural work to do — and no technology decision will substitute for it.
Further reading
- Digital Reengineering: A Practical Guide for Enterprise Leaders — the discipline of redesigning the operating model before choosing the technology that serves it.
- Why Most Digital Transformations Fail at the Org Chart, Not the Tech Stack — the detailed argument for why operating-model failures reproduce themselves across technology cycles.
- The Reengineering Playbook — the four-option decision framework that operating-model design constrains productively.
Sources
- Michael E. Porter — "What Is Strategy?", Harvard Business Review, November–December 1996. Anchors the distinction between operational effectiveness and strategic positioning, which maps directly onto the operating-model level of the argument.