The types of business operating models differ in two fundamental ways: the role the corporate center plays in relation to business units, and the organizational level at which design decisions are made. These are not stylistic variations on a single design. They reflect different theories of where value is created, how authority should flow, and what the organization needs to be able to do in order to execute its strategy.
Lotis Blue’s framework for thinking about operating model types uses two classification dimensions. The first is the corporate model archetype — one of four models that define the relationship between the corporate center and the business units it oversees. The second is scope — the organizational level at which operating model design decisions are applied. Understanding both dimensions, and how they interact, is the foundation for choosing the model that fits the strategy rather than the model that was inherited or that requires the least change.
Four Archetypes Define How the Corporate Center Creates Value
The four corporate model archetypes describe fundamentally different roles for the corporate center. Choosing an archetype is a strategic decision — it determines what the center is for, what it owns, and what value it is responsible for creating.
Portfolio Manager. In this archetype, the corporate center functions primarily as a financial investor. Business units operate with near-complete autonomy: they develop their own strategies, manage their own operations, and are evaluated primarily on financial returns. The center creates value through capital allocation — deploying resources to high-return units, managing the portfolio mix, and exiting underperforming assets. Operational integration between business units is minimal by design. The center does not attempt to generate value through cross-unit synergies; it generates value through the selection and financial management of the portfolio itself.
Strategic Leader. The corporate center aligns strategy across business units while preserving meaningful autonomy at the unit level. It defines the corporate strategy and the portfolio rationale, identifies where synergies across units can be captured, and may centralize services that are more efficient at the corporate level. Business units retain ownership of their operational decisions, but they operate within a shared strategic frame and compete for capital according to priorities the center has established. The center’s value-creation thesis is that strategic coherence across the portfolio produces outcomes that the individual units could not achieve independently.
Operational Leader. The corporate center takes shared accountability for operational results alongside the business units. It provides functional expertise — in areas such as finance, human resources, supply chain, and technology — that the units draw on, and it sets operational standards the units are expected to meet. Integration between center and units is deliberate: the center is involved in operational decisions, not just strategic ones. The value-creation thesis is that shared capability and operational discipline at the center produce better results than fully autonomous unit operations.
Operational Owner. The corporate center controls operations and makes decisions that in other archetypes would rest with the business units. Units have limited autonomy; the center drives execution, manages resources, and is directly accountable for operational results. This archetype fits organizations where tight coordination across units or operational consistency is a direct source of competitive advantage — where allowing units to operate independently would fragment a capability the strategy depends on.
Choosing the Right Archetype for Your Business
No archetype is universally correct. The appropriate model depends on two factors: the degree of strategic interdependence between business units, and where in the organization value is actually created.
When business units operate in fundamentally different markets, serve distinct customers, and require capabilities that do not transfer across the portfolio, the case for autonomy is strong. Tight central control over strategically independent units creates overhead without a corresponding source of value. The portfolio manager and strategic leader archetypes are designed for contexts where the units’ strategies do not need to be tightly integrated.
When business units share customers, capabilities, or go-to-market infrastructure — when the value of the portfolio depends on the units working together effectively — integration creates value that autonomy leaves unrealized. The operational leader and operational owner archetypes capture those synergies. The relevant question is not which archetype seems most efficient in the abstract, but which archetype reflects where value is actually created and who should be accountable for it.
The most common error is choosing by default. Organizations inherit their current archetype and continue operating within it without examining whether the strategy has evolved beyond what the model was designed to support. A company that grew through acquisition may have built a de facto portfolio manager model even though its strategy now requires operational integration across the acquired units. The archetype the organization operates under and the archetype its strategy implies are different and, that gap is the source of the dysfunction.
Operating Model Scope Determines Where Design Decisions Are Made
Archetype defines the role of the corporate center. Scope defines the organizational level at which operating model design decisions are applied. These are separate questions, and most operating model redesigns address one while leaving the other underspecified.
Five scopes are relevant for most organizations:
- Enterprise — decisions about how the entire organization is structured, governed, and resourced; the operating model at this level sets the terms for every level below it
- Business Unit — decisions about how an individual business unit is designed to compete within its own market; governed by the enterprise model but adapted to the unit’s specific strategy
- Functional — decisions about how a specific function (Finance, HR, Supply Chain, Technology) operates across the enterprise or within a unit; must be coherent with both the enterprise and business unit models
- Capability-Based — decisions about how a specific capability — customer analytics, digital delivery, innovation — is organized and resourced, regardless of where it sits in the reporting structure
- Leadership — decisions about how senior leadership is structured, how leadership teams function, and how decisions are made at the executive level
These scopes are not competing options. They coexist within every large organization. The enterprise model establishes constraints within which business unit models operate. Functional models must be coherent with both. Capability-based models cut across all of them. A leadership operating model affects every scope below it.
The practical implication is that a design effort must begin with a clear statement of which scope it is addressing — because the right design for one scope is not necessarily the right design for another. A leadership operating model redesign that does not account for the enterprise model it sits within, or the functional models it governs, is solving part of the problem.
When Scope and Archetype Work Against Each Other
The most damaging form of operating model misalignment occurs when the archetype implied by enterprise-level decisions is inconsistent with the design that actually governs business unit and functional behavior.
If the enterprise archetype calls for operational leadership — shared accountability, centralized expertise, tight integration across units — but business unit leaders are designed and incented to function as autonomous operators, the organization faces structural contradiction. The center expects integration; the units act with autonomy. Decisions that require coordination stall. Costs that the archetype was designed to eliminate accumulate instead.
After an aggressive inorganic growth strategy, a privately held automotive conglomerate with $10B+ in revenue and more than 25,000 employees found itself in exactly this position. The acquisition strategy had built a portfolio of businesses that the enterprise model treated as autonomous units. EBITDA had stagnated as enterprise function costs grew, work was duplicated, and post-acquisition synergies went unrealized. Collaboration patterns were misaligned and decision-making was slow. The executive team had lost credibility with the Director+ population following several initiatives that were announced but not completed.
Lotis Blue led a phased organizational redesign — beginning with alignment at the top three organizational layers before realigning the middle-management structure — and engaged 10 business unit leadership teams at the SVP and VP level in iterative, collaborative design workshops. The engagement addressed the root causes of misalignment: organization design, strategy misalignment, leadership gaps, and collaboration friction. The result was a three-year roadmap for $130M+ in run-rate savings, with $110M targeted in year one, exceeding project targets by three times. The executive leadership team was reduced by 30%, improving both team dynamics and decision-making speed. Internal change management capacity was built to prevent the reintroduction of unnecessary costs after the engagement ended.
The case illustrates what happens when an acquisitive growth strategy produces a de facto portfolio model without intentional design — and when the enterprise must shift toward a more integrated archetype to capture the value the acquisitions were intended to create.
The Right Operating Model Type Is a Strategic Decision
Choosing among the types of business operating models is not an organizational design exercise. It is a decision about where value is created, who is accountable for creating it, and what degree of integration between organizational units the strategy requires.
The archetype choice signals what the corporate center believes about how it adds value. The scope choice determines which level of the organization a given design effort is addressing. When the two are aligned — when the enterprise archetype is consistent with the design at the business unit and functional level — the model creates the conditions for the strategy to be executed. When they work against each other, the model becomes a source of cost and delay rather than a source of competitive advantage.
Organizations that treat the choice of operating model type as a structural preference — selecting an archetype because it looks familiar or requires the least disruption — miss the question the choice is actually answering. The right model type follows from the strategy: from what the strategy requires of the corporate center, which organizational level needs to be redesigned to execute it, and where value is created in a way the current model cannot support. Organizations that start with those questions choose more durable models. Organizations that start with structure end up redesigning them sooner than they expected.
