Business Ecosystem
metaphor
Source: Ecology → Economics, Software Engineering
Categories: biology-and-ecologyeconomics-and-financesoftware-engineering
Transfers
Arthur Tansley coined “ecosystem” in 1935 to name the functional unit of ecology: organisms plus their physical environment, interacting as a system. James Moore imported the term into business strategy in his 1993 Harvard Business Review article “Predators and Prey: A New Ecology of Competition,” arguing that companies do not compete in a vacuum but co-evolve within business ecosystems. The metaphor was then supercharged by the technology industry, where “platform ecosystem” became the dominant frame for describing app stores, API networks, cloud provider dependencies, and developer communities.
Key structural parallels:
- Interdependence is the primitive — in an ecological ecosystem, no organism is self-sufficient. Producers feed consumers, decomposers recycle nutrients, pollinators enable reproduction. The metaphor imports this fundamental interdependence: in a technology ecosystem, the platform needs developers, developers need users, users need content, content creators need distribution. The metaphor insists that you cannot understand any participant in isolation.
- Co-evolution — ecological species adapt to each other, not just to the environment. Flowers evolve to attract specific pollinators; pollinators evolve to exploit specific flowers. The business parallel: iPhone hardware and iOS apps co-evolve. AWS services and the startups built on them co-evolve. The metaphor names why participants in a platform cannot be treated as independent agents with fixed capabilities.
- Keystone species — ecologists identify species whose removal causes disproportionate system collapse (e.g., sea otters in kelp forests). The metaphor transfers directly: removing a platform’s core API, a dominant payment processor, or a critical open-source library can cascade through an entire business ecosystem. The “keystone” concept provides language for risk analysis that “supply chain” does not.
- Niche differentiation — ecological theory explains how multiple species coexist by occupying different niches within the same ecosystem. The business transfer: multiple companies can thrive in the same platform ecosystem by serving different segments, geographies, or use cases. The metaphor warns against direct competition (competitive exclusion principle) and favors differentiation.
- Succession — ecosystems develop through stages (pioneer species, intermediate communities, climax ecosystems). Technology platforms show similar patterns: early adopters build simple tools, mid-stage developers create sophisticated applications, mature ecosystems develop specialized service layers. The metaphor provides a developmental framework for understanding platform maturation.
Limits
- Ecosystems have no owner; platforms do — this is the metaphor’s deepest structural flaw. A forest has no CEO. A coral reef has no board of directors. The organisms in a biological ecosystem interact through evolved relationships with no central governance. Technology “ecosystems” are typically owned, designed, and governed by a platform company whose interests shape the entire system. Apple can change its App Store rules overnight in ways that have no ecological parallel. The metaphor naturalizes what is actually a governed, political arrangement.
- The equilibrium fallacy — ecological language imports the connotation that ecosystems are balanced, self-regulating, and resilient. Ecologists themselves have largely abandoned the “balance of nature” concept, but popular understanding still carries it. When applied to business, this can justify laissez-faire policy: “the ecosystem will self-regulate.” It will not. Markets require regulation, and platform ecosystems are actively shaped by their owners.
- Evolutionary timescales do not transfer — ecological niches, co-evolutionary relationships, and succession patterns develop over thousands to millions of years. Business ecosystems change in months. A single API deprecation can eliminate an entire category of participants. The metaphor’s evolutionary language implies gradual, organic change where the reality is abrupt, designed disruption.
- The “natural” framing obscures power — calling something an “ecosystem” makes it sound organic, inevitable, and apolitical. But platform ecosystems are designed to extract value. The “30% App Store tax” is not a natural phenomenon like nutrient cycling; it is a business decision. The ecological metaphor can function as ideology, naturalizing what is actually a structure of economic power.
- Ecological boundaries are porous; platform boundaries are enforced — in nature, organisms migrate between ecosystems freely. In platform ecosystems, lock-in, proprietary formats, and switching costs are deliberately engineered barriers. The metaphor imports openness and fluidity where the reality is walled gardens.
Expressions
- “The Apple ecosystem” — the canonical technology usage, naming the interdependent network of hardware, software, and services
- “Developer ecosystem” — the community of third-party builders around a platform
- “Ecosystem play” — strategy jargon for building a platform others depend on
- “Ecosystem health” — measuring the vitality of a platform by the diversity and activity of its participants
- “Business ecosystem” — James Moore’s original formulation
- “Ecosystem lock-in” — the difficulty of leaving an ecosystem once you have adapted to it, paralleling ecological specialization
- “Toxic ecosystem” — when the platform’s policies harm participants, borrowing ecological language for pollution
Origin Story
Arthur Tansley introduced “ecosystem” in a 1935 paper in the journal Ecology, arguing against earlier vitalist concepts that treated ecological communities as superorganisms. Tansley wanted a term that included both living organisms and their physical environment as interacting components of a system. The term became foundational in ecology by the 1950s through the work of Eugene Odum, whose textbook Fundamentals of Ecology (1953) organized the entire field around the ecosystem concept.
The metaphorical migration to business began with James Moore’s 1993 article and his 1996 book The Death of Competition. Moore argued that the competitive landscape was better understood as an ecosystem where companies co-evolve than as a battlefield where they fight for territory. The technology industry adopted the term with extraordinary enthusiasm during the 2000s and 2010s, making “ecosystem” perhaps the single most common metaphor in Silicon Valley strategic discourse. Despite its ubiquity, the metaphor continues to do active structural work — co-evolution, keystone species, niche differentiation — shaping how strategists reason about platform dynamics in ways that alternative framings like “supply chain” or “marketplace” cannot.
References
- Tansley, Arthur G. “The Use and Abuse of Vegetational Concepts and Terms,” Ecology 16.3 (1935) — the coining of “ecosystem”
- Moore, James F. “Predators and Prey: A New Ecology of Competition,” Harvard Business Review (May-June 1993) — the business ecosystem concept
- Iansiti, Marco and Levien, Roy. The Keystone Advantage (2004) — keystone species concept applied to business platforms
- Odum, Eugene P. Fundamentals of Ecology (1953) — the textbook that established ecosystem as ecology’s central concept
Related Entries
Structural Neighbors
Entries from different domains that share structural shape. Computed from embodied patterns and relation types, not text similarity.
- Therapeutic Alliance (war/metaphor)
- Guided Participation (education/mental-model)
- Hive Mind Is Collective Intelligence (science-fiction/metaphor)
- Integrate Rather Than Segregate (agriculture/mental-model)
- Sympatheia (philosophy/mental-model)
- Stakeholder (gambling/metaphor)
- Theories Are Cloth (textiles/metaphor)
- Stone Soup (folklore/metaphor)
Structural Tags
Patterns: linkpart-wholeself-organization
Relations: coordinatecompeteenablecause
Structure: networkemergence Level: generic
Contributors: agent:metaphorex-miner