Skip to content
Information Technology | Part 21 of 40

Networked Organizations, Ecosystems and the Diminishing Firm

Digital coordination allows firms to become more networked, modular and ecosystem-based, but boundary choices still depend on control, capability and risk.

A company no longer has to own every asset it uses or employ everyone contributing to its value proposition. Digital coordination makes networked organizations increasingly viable. But networks do not run themselves.

From an integrated firm to an ecosystem

A vertically integrated company performs many activities internally. A networked organization coordinates capabilities across partners: specialized producers, technology vendors, service providers, logistics firms and distribution channels.

The argument sometimes called the diminishing firm suggests that cheaper information and transaction processing make a smaller internal footprint possible. The organization can retain the orchestration capability while accessing specialist resources externally.

That is only one possible outcome. Digital platforms can also become dominant coordinators of very large ecosystems. Ownership of the transaction infrastructure, standards or customer relationship may be more important than ownership of the physical assets.

Where networked organizations win

They can gain flexibility, specialist knowledge and scalability. A company launching a configurable industrial product may combine in-house product architecture with outsourced manufacturing, specialist software components and regional service partners.

But every external connection introduces interfaces and potential failure modes. Partners may operate to different incentives, use incompatible data definitions or prioritize other customers.

The key capability is orchestration. Someone must define the rules by which participants collaborate, share data, handle exceptions and improve performance.

Operating requirements

Effective ecosystems need common process definitions, transparent responsibilities, interface standards and service agreements. They also need mechanisms for managing dependencies: alternative capacity, continuity planning and conflict resolution.

Measure the full customer outcome rather than isolated partner KPIs. A supplier can meet its shipping commitment while the final customer still experiences a delay because the information arrived too late for the next process.

Management questions

  1. Which capabilities must remain inside the firm?
  2. Which can be obtained competitively?
  3. Where is a relationship-specific dependency developing?
  4. Who owns the end-to-end process across legal boundaries?
  5. How quickly can the network adapt to disruption?

Executive decision lens

Decision to make: Identify the few capabilities the enterprise must control to protect differentiation and resilience, then orchestrate partners around clear performance contracts. A lean asset base is not necessarily a lean operating model. Demand end-to-end accountability, interface standards and recovery options before extending the ecosystem.

Operations Insider takeaway

A networked enterprise replaces some ownership with coordination. Its advantage depends on the quality of that coordination, not merely the number of partners.

Newsletter

One Lean idea.
Every week.