Operational Models: Archetypes and Selection Criteria

What Is an Operating Model

An operating model describes how an organization structures its capabilities, processes, people, and technology to deliver value. It answers questions about where decisions are made, which functions are centralized versus distributed, how resources are allocated across units, and what mechanisms coordinate work that spans organizational boundaries.

Operating model design sits at the intersection of organizational structure, process architecture, and governance. Changes to operating models typically require significant change management effort because they affect reporting structures, accountability, and daily working practices across large portions of an organization.

Process redesign and operating model design are related but distinct disciplines. Process redesign focuses on the logic and sequence of specific workflows; operating model design addresses the structural context in which those workflows occur. In practice, redesign initiatives often surface operating model questions: the redesigned process may require a different allocation of work between headquarters and field units, or a different relationship between IT and operations.

Centralized Model

In a centralized operating model, core functions and decision-making authority are concentrated in a single organizational unit — typically a corporate headquarters or a central function. Business units, regions, or departments operate with limited autonomy and follow standards set at the center.

Centralization offers advantages in areas where standardization and consistency are paramount: compliance and risk management, technology infrastructure, financial control, and brand management. A single center of excellence can develop deep expertise and enforce uniform standards that would be difficult to maintain across multiple independent units.

The limitations of centralization emerge when local conditions require flexibility, speed, or specialized knowledge that the center lacks. Centralized approval processes can create bottlenecks; centrally mandated standards can be misaligned with local market or operational realities; and distance from frontline operations can reduce the quality of centrally made decisions.

Federated Model

A federated operating model distributes authority across business units, regions, or product lines, while maintaining central coordination on a limited set of shared concerns. Each federated unit has meaningful decision-making autonomy within its domain, but operates within frameworks and guardrails established at the center.

Federation is common in organizations with diverse business lines or significant geographic variation. It allows units to adapt processes and structures to their specific context without requiring approval from the center for every decision.

The coordination challenge in federated models is defining the boundaries of autonomy clearly: which decisions belong to the center and which to the units. Ambiguity at this boundary creates conflict and duplication. Effective federated governance requires well-defined policies at the center and genuine respect for unit autonomy within those policies.

Shared Services Model

Shared services involves consolidating common back-office or support functions — finance, HR, IT, procurement, legal — into a single organizational unit that provides those services to the rest of the organization on a standardized basis. The shared services unit typically operates on a cost-recovery or service-level agreement model.

The rationale for shared services is scale efficiency and process standardization. Consolidating repetitive transactional functions reduces duplication and allows investment in specialist capabilities that no single business unit could justify on its own.

The risks of shared services include distance from the business units being served, rigidity in service standards that do not accommodate legitimate variation in business unit needs, and governance complexity when multiple business units have conflicting service requirements.

Platform-Based Model

Platform-based operating models organize around a shared infrastructure — typically a technology platform — that enables multiple business units or external partners to operate. The platform owner defines the architecture, standards, and interfaces; participants build on top of the platform using those interfaces.

Platform models have become increasingly relevant with the proliferation of cloud services, API-based integrations, and marketplace business models. Within enterprises, "internal platform" thinking applies similar logic to shared technical and data infrastructure: a central platform team maintains core capabilities that product and operational teams consume.

The key design challenge in platform models is governance: balancing the platform owner's need for stability and standardization against participants' need for flexibility and rapid iteration. The Digital Tooling guide addresses some of the technology components that underpin platform-based operating models.

Selection Criteria

No operating model archetype is universally superior. Selection depends on organizational characteristics and strategic priorities:

• Degree of business unit diversity. Organizations with highly heterogeneous business units generally require more federated models; homogeneous organizations benefit more from centralization.
• Regulatory environment. Heavily regulated industries may require greater centralization of compliance and risk functions, even if other areas are federated.
• Speed requirements. Markets that require rapid local response favor federation; markets where consistency and risk control dominate favor centralization.
• Economies of scale in common functions. High-volume, standardizable support functions benefit from shared services; highly specialized or variable support functions may not.
• Technology architecture. Organizations with a strong common technology platform are better positioned for centralized or platform-based models; those with fragmented legacy systems may need to federate until technical consolidation is feasible.

Operating model decisions should be revisited periodically — typically as part of strategic planning cycles — as competitive conditions, organizational scale, and technology capabilities evolve.