Operating Models

Operating Model Archetypes: When Coordination, Unification, Diversification, and Replication Actually Work

Cut through the theory and understand which operating model archetype fits your organization's actual constraints, capabilities, and strategic ambitions

8 min read

Here's the uncomfortable truth about operating model selection: most organizations choose their archetype based on what sounds good in boardrooms rather than what actually works given their capabilities, market position, and strategic constraints. The result? Beautifully articulated operating models that crumble under the weight of organizational reality. We've seen global manufacturers attempt Unification models that ignore decades of regional adaptation, and diversified conglomerates force Coordination approaches that strangle business unit agility. The four classic archetypes—Coordination, Unification, Diversification, and Replication—aren't just theoretical constructs. They're proven patterns with specific prerequisites, trade-offs, and failure modes that every business architect must understand.

With digital transformation pressures mounting and hybrid work fundamentally reshaping organizational boundaries, the stakes for getting your operating model right have never been higher. Organizations are simultaneously being asked to move faster, integrate more deeply, and maintain local responsiveness—often contradictory demands that require surgical precision in operating model design.

Key Takeaways

  • Map your current capabilities against archetype prerequisites before designing your target operating model—most failures stem from capability gaps, not design flaws
  • Use heat mapping to identify which business units or geographies are naturally suited for shared services versus autonomous operations
  • Build your operating model transition as a series of capability investments rather than organizational restructuring—structure follows capabilities, not the reverse
  • Test archetype assumptions with small-scale pilots before enterprise-wide rollouts—operating model changes are expensive to reverse
  • Cross-map your value streams to operating model components to identify where standardization creates value versus where it destroys local optimization

The Coordination Archetype: When Business Units Need to Dance, Not March

Coordination operating models work when you need business units to share information and align activities without surrendering their operational autonomy.

Think of Coordination as organized collaboration rather than centralized control. Business units maintain their own P&Ls, operating processes, and decision-making authority, but they share selected capabilities and coordinate on specific value streams. This archetype thrives in organizations where local market knowledge creates competitive advantage, but certain capabilities—like procurement, risk management, or technology infrastructure—benefit from scale. The classic example is a diversified industrial company where each division serves different markets but shares manufacturing capabilities and supplier relationships. The key insight: Coordination requires sophisticated governance mechanisms and shared measurement systems. You're essentially building a federation where business units voluntarily participate because they see clear value. Without those incentives, Coordination devolves into meetings without accountability. Cross-mapping becomes critical here—you need to identify which capabilities truly benefit from sharing versus which ones perform better under local control.

The Unification Archetype: Building the Single-Company Advantage

Unification delivers competitive advantage through standardized processes, shared capabilities, and enterprise-wide optimization—but only when your business model actually supports it.

Unification means one company, one way of operating. Business units share the majority of their capabilities, follow standardized processes, and optimize for enterprise-wide performance rather than local results. This archetype works when customers, products, or markets benefit from consistency and scale. Global banks often use Unification models for risk management, compliance, and customer data—areas where standardization reduces costs and regulatory risk while improving customer experience. But here's where business architects frequently stumble: Unification requires cultural alignment as much as process standardization. You can't simply mandate shared capabilities; you need business units to genuinely believe that enterprise optimization serves their interests. The BIZBOK framework emphasizes this point—capability sharing must be grounded in value stream analysis that shows how standardization improves end-to-end performance. Heat mapping becomes your diagnostic tool: if business units are performing the same capabilities differently without clear market reasons, Unification probably makes sense.

  • Standardize capabilities that directly touch customers first—inconsistent customer experience is immediately visible
  • Build centers of excellence for complex capabilities rather than centralized service organizations
  • Implement enterprise-wide metrics before enterprise-wide processes—shared measurement drives behavioral change
  • Phase Unification by value stream priority, not organizational hierarchy

The Diversification Archetype: When Autonomy Creates Value

Diversification operating models maximize business unit autonomy and local optimization—the right choice when markets, customers, or regulatory environments demand fundamentally different approaches.

Under Diversification, business units operate as largely independent entities with minimal shared capabilities beyond basic corporate functions like treasury and legal. Each unit develops its own operating model optimized for its specific market dynamics, customer requirements, and competitive environment. Private equity portfolio companies often exemplify this archetype—each portfolio company maintains complete operational independence while sharing only capital allocation and governance frameworks. The business architecture challenge: determining which capabilities truly need to remain separate versus which ones you're keeping separate out of organizational inertia. Value stream mapping becomes critical for identifyin