Ecosystem Mapping
A map of all the actors in a system and the value that flows between them, used to understand the wider web a problem actually lives in.
Some problems cannot be solved by serving one user, because the problem is not in the user. It is in the web of relationships around them.
What it is
A map of the whole web, not just the user inside it.
An ecosystem map (sometimes called a value network map or actor map) visualizes all the players in a system — the people, organizations, platforms, and institutions — and the relationships and exchanges of value, information, money, or service between them. Where the other Experience & Systems Mapping methods examine a single experience up close, ecosystem mapping pulls back to show the whole web that experience sits inside.
Its power is that it reveals the system, not just the user. Many problems cannot be solved by serving one person in isolation because the problem is embedded in a web of relationships: a marketplace, a platform, a healthcare system, a supply chain, a public service. An ecosystem map exposes where value is created and captured, where the bottlenecks and broken connections are, and where a new entrant could intervene — along with the second-order effects that intervention would trigger across the system.
It is often confused with stakeholder mapping, but the two do different jobs: a stakeholder map identifies who has a stake and how much power or interest they hold; an ecosystem map shows how the whole system is connected and what actually flows between its parts. Stakeholder mapping asks who matters; ecosystem mapping asks how the system is CONNECTED.
One further boundary is worth drawing. An ecosystem map shows STRUCTURE: who is in the system, and what flows between them. It is a picture of an arrangement. It does not explain why the system BEHAVES the way it does over time — why a problem keeps returning after you fix it, why an obvious intervention gets absorbed and produces nothing, or why cause and symptom are separated by months. Those are questions of causality and feedback, and they belong to Systems Mapping, which models loops, delays, and leverage points. Ecosystem mapping asks how the system is connected; systems mapping asks why it keeps doing what it does.
The actor network
See the whole web. Click any actor.
The obvious actors appear in teal. The amber-ringed actors are the non-obvious ones — the players a two-sided-market framing misses. Click any node to see who they are, what flows to and from them, and where their leverage lies.
When to deploy it
A systems tool for problems that resist single-user solutions.
Use Ecosystem Mapping when
- →The challenge involves multiple interdependent actors: a marketplace, a platform business, a healthcare system, a supply chain, a public service.
- →You need to understand where value is created and captured across a system, and where a new entrant could intervene.
- →A problem resists being solved by serving one user — because it is embedded in a web of relationships, not just a user experience.
- →You need to anticipate the second-order effects of an intervention across a system before you make it.
- →You want to find the non-obvious actors — the quiet intermediary, the informal power broker, the emerging complementor — that a simple user framing would miss.
Do not lean on it when
- ×The problem is a simple, self-contained product with a single user and a single transaction — there is no meaningful ecosystem to map.
- ×You only need to know who has a stake and how much power or interest they hold. Use stakeholder mapping, a lighter, faster tool.
- ×You need the felt experience of one user (Journey Mapping), the operational delivery of one service (Service Blueprinting), or a phase-by-phase evaluation of one experience (the 5Es). Ecosystem mapping is the zoom-out companion to all three, not a replacement.
- ×You need primary evidence rather than a structured analysis. The ecosystem map organizes what you know; it does not replace going and finding out.
The honest limit: ecosystems are dynamic and an ecosystem map is a snapshot. Treated as static and complete, it can mislead — because the web shifts, new actors enter, and flows change. It is a tool for understanding a living system at a moment, to be revisited as the system moves.
How it works
Six moves, from the obvious actors to the hidden leverage.
Identify all the actors — including the non-obvious ones.
List the players in the system, and push deliberately past the obvious two or three. The regulators, intermediaries, complementors, competitors, and quiet system-shapers are usually where the insight is. Ask: who regulates this? Who profits without being visible? Who could block it? Who quietly makes it work?
Place them as a network, not a hierarchy.
Position the actors as nodes — with the focal actor or actors at the center and the wider web around them. Resist arranging them in a simple hierarchy or org-chart structure. Ecosystems are webs. The spatial arrangement should show adjacency and connection, not reporting lines.
Draw and label the flows.
Connect the actors and, critically, label what flows along each connection: money, data, goods, services, attention, trust. An unlabeled connection is nearly useless — the value that flows along it is the whole point. Label each connection as you draw it; the discipline of naming forces clarity and exposes connections that are actually empty.
Look for imbalances and leverage points.
Read the web for bottlenecks, broken or missing connections, lopsided value capture, and points of leverage where a small intervention could shift the whole system. The actors with the most connections — or the flows that multiple actors depend on — are usually the leverage points.
Trace second-order effects.
For any potential intervention, follow the ripples: change one flow and see what it does downstream to other actors. The map's real value is anticipating the consequences a single-user view would miss. An intervention that solves a guest problem may trigger a regulatory response via the neighbor-community-regulator chain — the kind of second-order effect that only a systems view reveals.
Treat it as living.
Revisit the map as the ecosystem shifts. Actors enter and leave, flows change, and a map that was accurate a year ago may now mislead. The most useful ecosystem maps are maintained as the system evolves and tested against real changes — not filed as a deliverable and forgotten.
Best practices
What good looks like — and what prevents it.
When it goes well
- ✓The map includes the non-obvious actors — regulators, intermediaries, complementors, competitors — not just the direct users. The hidden system-shapers are where the insight almost always is.
- ✓Every connection is labeled with what actually flows along it, so the map shows value movement rather than just who-knows-whom.
- ✓It surfaces genuine leverage points and reveals the second-order effects an intervention would trigger before the team commits to it.
- ✓It is treated as a living snapshot — revisited as the ecosystem shifts — rather than a one-time deliverable.
- ✓It changes a decision: it redirects a solution toward a leverage point, or surfaces a threat the two-sided framing had missed entirely.
The mistakes, and how to avoid them
Mapping only the direct actors.
Stopping at the obvious players — the "two-sided market" framing — misses the system-shapers, regulators, complementors, and incumbents where the real threats and opportunities live. Build in a specific prompt to hunt for the hidden actors before the session ends.
Unlabeled connections.
Drawing lines between actors without naming what flows along them produces a diagram that looks like insight but is not. Always label the flow. An unlabeled connection is a placeholder, not a finding.
Treating the map as static.
Ecosystems move. A map frozen in time quietly goes wrong as actors and flows change. Set a cadence to revisit it — at minimum, when a significant market event happens or when a new entrant appears.
Confusing it with a stakeholder map.
Listing who has a stake is not the same as showing how the system is connected and where value flows. Ecosystem mapping is about the system's mechanics — what actually flows, not just who is affected.
Mapping for its own sake.
A beautiful, complex web that never informs a decision is decoration. Every ecosystem mapping session should end with a specific implication: a leverage point to pursue, a threat to monitor, or a second-order effect to design around.
Logistics
Assembling the knowledge the map depends on.
No single person usually knows the whole ecosystem. The value of the workshop depends on assembling people with genuinely different vantage points: someone who knows the regulatory landscape, someone who knows the supply side, someone who knows the customer, someone who has operated in the domain. The non-obvious actors surface when the room contains people whose knowledge spans the full system.
Start from a focal question
An ecosystem can be mapped at almost any scope, so anchor it before you begin: whose ecosystem, around what problem? "The ecosystem around a patient's diabetes management" is mappable; "the healthcare ecosystem" is boundless. A clear focal actor and focal question keep the map useful rather than encyclopedic.
Push deliberately for the non-obvious actors
The natural tendency is to map the obvious players and stop. Build in an explicit hunt: after the first round of actors is on the map, ask the group to find the hidden system-shapers. Who regulates this? Who profits without being visible? Who could block a new entrant? Who quietly makes the system work? These prompts are the mechanism that surfaces the insight.
Label flows as you draw them
Do not draw the whole web first and label later. Label each connection as you place it, because the discipline of naming what flows exposes connections that seem important but are actually empty — and forces precision about what is actually exchanged.
Keep it legible
A map with a hundred nodes and no hierarchy of importance is unreadable. Focus on the actors and flows that matter to the focal question. Common tools are whiteboards and digital canvases — Miro, Mural, and Kumu (for network-specific mapping) are examples, not endorsements. The tool is irrelevant; the labeling discipline is everything.
End with specific implications
Every ecosystem mapping session should end with named implications: a leverage point to pursue, a threat to monitor, a second-order effect to design around, a non-obvious actor to research further. "We need to understand the ecosystem better" is not an output. A named actor and a named next step are.
AI and this method
AI draws the visible web fast. The actors that move a system are often the invisible ones.
Toggle between modes to see where AI contributes to building the ecosystem map — and where its mapping goes faint at exactly the actors that most need attention.
In-depth example
The same marketplace, mapped two ways.
A fast-growing short-term rental marketplace wants to understand its world well enough to find growth levers and head off threats. The instinctive framing is a simple two-sided market: hosts and guests. The ecosystem mapping session is commissioned to see if the real system is more complicated than that. The same business is mapped twice: once by a team with diverse domain knowledge running a structured session, once with AI providing the draft map.
Scenario
A fast-growing short-term rental marketplace — mapping the ecosystem to find growth levers and head off threats
The team’s instinctive framing is a two-sided market: hosts on the supply side, guests on the demand side. The ecosystem mapping session is run to find out if the real system is more complicated than that — and where the leverage is.
The actors the map revealed
Hosts
Primary supply-side actors. Listing quality is highly variable — and it becomes clear in the session that what separates high-booking hosts from low-booking hosts is not the properties themselves.
Guests
Primary demand-side actors. Booking behavior and reviews are the visible output, but the map surfaces that what guests actually book on is a specific quality signal — one that leads directly to the photographer finding.
Payment Providers
Standard infrastructure. Mapped and noted. Low insight here, as expected — but worth having explicit in case of a payment-related regulatory action.
Professional Photographers
NON-OBVIOUSThe breakthrough actor. Cross-referencing the map with actual booking data, the team found that listings with professional photography booked dramatically more than those without — a difference the two-sided framing had never surfaced. Photographers were a hidden value-creating actor whose service directly determined host success. This insight led directly to the platform offering professional photography as a service.
Cleaning Services & Co-host Managers
NON-OBVIOUSAn entire supporting operational economy had emerged around the platform. Cleaning services and co-host managers were the operational infrastructure that allowed hosts to scale — and the platform’s supply side could only grow as fast as this layer could. It had never appeared in any product or growth conversation.
Local Regulators & Housing Authorities
NON-OBVIOUSPeripheral on the map but existential in leverage. A local regulator who decided to restrict short-term rentals could effectively close a market. The mapping session forced an explicit conversation about regulatory relationships that had been treated as a legal department problem, not a strategic one.
Neighbors & Residential Communities
NON-OBVIOUSThe most surprising actor: the informal relationship between neighbors, community goodwill, and regulatory behavior. Neighbor hostility → organized community pressure → regulatory action was the causal chain. The trust-based, informal dynamic between neighbors and regulators was the invisible path from a property-level nuisance to a market-level shutdown. A neighbor strategy and a community relations program both followed directly from this finding.
What the ecosystem map produced
The map turned “we match hosts and guests” into an understanding of the actual system the business depended on. Three strategic moves came directly from the hidden actors: a professional photography service (from the photographer actor), a co-host and cleaning ecosystem partnership program (from the service layer actor), and a neighbor and community relations strategy (from the neighbor-to-regulator causal chain). None of these would have emerged from the two-sided-market framing.
Frameworks
Where Ecosystem Mapping shows up.
Ecosystem mapping is a systems-level discovery method. It maps to frameworks at the points where understanding the wider context matters — where the question is “what system is this problem embedded in” before the team narrows to a user or a solution. It is intentionally blank in frameworks that work exclusively at the single-user or single-feature level.
Related methods
What to combine with Ecosystem Mapping.
Sources & further reading
The work behind this method.
Thinking in Systems
Donella Meadows (2008)
The foundational text on seeing and working with systems. Introduces the mental models — stocks, flows, feedback loops, leverage points — that underlie ecosystem mapping. Essential background for anyone who wants to move from drawing actor maps to actually understanding what the map is showing.
This Is Service Design Doing
Marc Stickdorn, Markus Hormess, Adam Lawrence, and Jakob Schneider (2018)
The comprehensive service design toolkit, including system and actor mapping in practice. Covers how ecosystem mapping connects to the methods that surround it — journey mapping, service blueprinting, and stakeholder analysis — and how to run mapping sessions effectively.
Value Proposition Design
Alexander Osterwalder, Yves Pigneur, Greg Bernarda, and Alan Smith (2014)
For value-flow thinking across a system — understanding what is actually exchanged between actors, not just who the actors are. Useful as a companion to ecosystem mapping when the goal is to design new value flows rather than simply understand existing ones.