Knowledge
Knowledge HubConcepts and strategic researchGlossaryDefinitions across six domainsFrameworksStructured strategy methodsTopicsConnected subject areasLibrary
PlaybooksPractical strategy guidesBooksBooks and long-form researchOperator VaultMember resources and toolkits
Explore Discover, the Knowledge Hub, playbooks, and the Operator Vault.
Glossary
Operating model
An operating model is the integrated design of how an organization translates strategy into coordinated day-to-day execution — spanning value streams, processes, decision rights, capabilities, technology, partners, and performance rhythms. It answers how work actually runs, not only who reports to whom.
Why it matters
Strategy fails in the gap between intent and repeatable execution. An operating model makes that gap explicit: which workflows create customer and economic value, where decisions sit, which capabilities and systems are required, and how performance is reviewed.
Organizational charts and tool stacks are inputs, not the model. Two firms can share similar boxes on an org chart and still operate differently if decision latency, process ownership, partner boundaries, and feedback loops diverge.
Keep the generic operating model distinct from The Strategy Stack’s Agentic Operating Model (AOM). AOM is a TSS framework for running the firm when AI agents participate in planning and action under human decision rights. “Operating model” remains the broader design object; AOM is one strategically specific form.
Example (enterprise): A multi-product software company redesigns its operating model after strategy shifts from project delivery to portfolio outcomes. It re-maps end-to-end value streams, clarifies which decisions stay with product leadership versus shared platforms, retires conflicting quarterly planning rituals, and only then changes reporting lines — so structure follows operating logic rather than the reverse.
A “target operating model” is not a synonym for operating model: it names a desired future-state design. The operating model is the integrated design of how work runs — current or target — only when decision rights, workflows, and feedback loops are actually specified (and, for a target state, when the path from current to target is explicit).
Mechanisms
- Define the value streams and core processes that convert strategy into customer and economic outcomes.
- Assign decision rights, accountabilities, and escalation paths for the choices that set pace and quality.
- Align capabilities, technology, partners, incentives, and review cadences so the system can run without constant heroic intervention.
Boundaries
- Operating model ≠ org chart; structure is one component of how work runs.
- Operating model ≠ strategy; strategy chooses direction and bets, the operating model operationalizes them.
- Operating model ≠ Agentic Operating Model; AOM is a TSS-specific agent-era design, not a synonym for every operating model.
- A slide titled “target operating model” is not an operating model until decision rights, workflows, and feedback loops actually change.
Related topics
None linked yet.