Ecosystem Strategy Framework
Ecosystem strategy maps every actor your value proposition actually depends on - suppliers, complementors, platforms, regulators - and sequences your moves around their dependencies, instead of planning as if you compete alone.
Spokes reach out from the firm at the centre to every actor whose choices shape what it can do.
Reach for this when…
- Your product is ready but adoption stalls on something outside your control.
- You're betting on a platform or standard you don't own.
- Growth depends on a channel partner who has no obvious incentive to help you.
How to run it
- Map every actor your value proposition depends on: suppliers, complementors, platforms, regulators, customers.
- Identify the ecosystem's leadership role and where you actually sit - orchestrator, key player, or niche player.
- Find the co-innovation risk: what has to be built by someone else before your part works.
- Find the adoption chain risk: who has to adopt before the next actor in line will.
- Sequence your own moves around those dependencies, not just your own roadmap.
- Build or join the governance that keeps incentives aligned - standards, revenue share, agreements.
A worked example
Situation. Sunita Gurung runs Gurung Sensors, a smart home sensor startup in Kathmandu, Nepal.
Applied. Her hardware was ready, but sales stalled because the hub app only worked well on a rival's platform, and her roadmap had assumed her own app was the only variable that mattered. She mapped the real ecosystem and found the adoption chain risk actually sat with regional installers, who had no incentive to recommend her sensor over the incumbent's.
Result. She redirected effort into installer training and revenue share instead of app features, and installer recommendations became her real growth channel.
The catch
The map looks neat but the real risk is timing - your part can be perfect while a co-innovator's part is still years off, and no framework forces someone else to hit their deadline. It also tempts founders to design for an orchestrator role they don't have the market power to actually hold.
Mapping the ecosystem is not the same as controlling any part of it - know which role you can actually win before you build for it.
Origin: James F. Moore; Ron Adner