Winning the Right Game

Ecosystem Disruption: How to Compete When Boundaries Collapse

The basis of competition is changing. Rivalry is leaving well-defined industries and moving into ecosystems, where the map of who threatens whom no longer follows the old category lines. Automakers now compete with mobility platforms, banks with fintechs, broadcasters with streamers. The rival that ends you may never have been in your industry at all.

An ecosystem here has a precise meaning: the structure through which a set of partners interact to deliver a single value proposition to an end customer. Three things define it. A value proposition anchors the whole system. Specific partners agree to collaborate. And a structure of roles and positions keeps everyone aligned on who does what.

That definition matters because the classic strategy toolkit, five forces and industry analysis, only sees rivals inside the industry box. It is blind to a partner two steps away whose improvement quietly rewrites the rules. The book's whole project is to give leaders a way to see, and then shape, that larger map of connections.

What losing the wrong game means

The greatest danger is not losing a fair fight. It is pouring everything into winning, executing flawlessly, and only then realizing the game itself moved. That is what winning the wrong game means, and it is the failure the rest of the book is built to prevent.

For a product manager, the takeaway is a habit, not a tactic. Define your product by the value proposition and the partners who co-deliver it, not by the category on the pitch deck. The competitor spreadsheet lists the rivals you already know. The ecosystem map is where the ones that will actually hurt you first show up.

Winning the Wrong Game Means Losing

Kodak is the anchoring case, and the usual telling is wrong. Kodak did not miss digital. It became the number one seller of digital cameras in America and a leader in digital printing. It won the technology transition everyone said it would lose, and it still went bankrupt.

Value architecture

Take a value proposition, relive and share memories through images, and break it into its constituent value elements. For Kodak these were Capture, Produce, View, and Share. This sits a level above technologies or supply chains: it describes the benefits themselves, and it reveals how a change in one element can wreck another.

Value inversion

A complement, something that makes your value proposition more valuable, can improve along three paths. It can keep helping you. It can plateau and stop mattering. Or it can improve so far that it inverts, and the thing that helped you now substitutes for you.

Smartphone screens ran that third path. Better screens first improved Capture, making phones better cameras. Then the same screens became where people View photos, and the reason to print anything vanished. Kodak's partner, the screen, never attacked. It just got too good, and print demand disintegrated underneath a company that was still winning at printing.

The unsettling point: this happened with no rival strategy aimed at Kodak. The pie did not get sliced differently. The pie itself disintegrated.

What this means for a product roadmap: map which adjacent products are complements to yours today, then ask which could invert. An integration or platform that lifts a metric this quarter can, at higher performance, quietly remove the reason your product exists. Watching only your named competitors would never surface that.

Ecosystem Defense Is Collective

Once a partner or a giant threatens your value architecture, the instinct is to defend alone and head-on. That instinct loses. Defense in an ecosystem is collective: you survive by mobilizing partners, not by out-muscling the attacker. Three principles make it work, and they reinforce each other.

Modify your value architecture

Recruit and redeploy partners to add value elements the giant cannot match. Wayfair, facing Amazon, did not try to out-scale the everything store. It added Discovery and Deliberation, inspiration, visualization, and curation for a category where people browse before they buy, which a generalist could not replicate.

Find defensible ground with like-minded partners

When Google Maps threatened TomTom's core, TomTom and Garmin shifted to being a neutral supplier of map data to partners, automakers, Apple, and ride-hail firms, who did not want to depend on Google. The defensible ground was chosen precisely because partners preferred an ally who would not dominate them.

Discipline your ambition

Spotify needs the record labels, so it restrains itself from competing with them, even when it could. A coalition survives only if you do not become the threat your partners feared. Overreach dissolves the very alliance defending you.

The connective idea: acknowledge the offense is real, act before it matures, and organize to preserve your ability to create value rather than to score a direct win.

For a PM under platform pressure: when a large platform enters your space, resist the reflex to match it feature for feature. Instead, ask which partners share your interest in the giant not winning, and build the coalition on ground those partners will actively defend with you. Chapter 3 flips the lens from defending an ecosystem to constructing one.

Ecosystem Offense: From Adding Competition to Changing Competition

An ecosystem disruptor does not add another competitor to an existing game. It changes the game, redrawing what value is and who delivers it. Building that new structure has its own discipline, and three construction principles carry it.

Minimum viable ecosystem

The minimum viable ecosystem is the smallest configuration of partners and activities that generates enough evidence of value creation to attract the next partner. This is not a minimum viable product, which is a thing you ship. It is the minimum set of relationships that makes the value proposition real enough to pull the next participant in.

Staged expansion

Be explicit about the order in which you add partners and activities beyond the MVE. Each stage's proof of value is what recruits the next stage. Amazon built Alexa this way, standing up basic voice commands first, then letting demonstrated usage draw in device makers and skill developers in sequence.

Ecosystem carryover

Reuse elements built for one ecosystem to construct a second. Amazon carried its customers, reviews, and cloud into Alexa. Oprah Winfrey carried audience trust earned on television into a magazine, a book club, and wellness ventures, a relational asset a fresh entrant could not assemble. ASSA ABLOY carried a lock business into digital access.

The strategic shift: sequencing beats the grand unveiling. You do not need every partner on day one. You need the minimum that proves value, then a deliberate order for the rest.

For product builders: treat a new platform or marketplace as an MVE problem. Find the smallest partner configuration that proves value to one side, use it to recruit the other, and inventory the assets you already own, users, data, and trust, that carry over so you are not building the ecosystem from zero.

Timing Ecosystem Disruption: Too Early Can Be Worse Than Too Late

Being first is often a trap. Two forces, not your technology alone, decide when an ecosystem disruption actually lands, and misreading them burns pioneers who were technically right.

Emergence challenges

These are the bottlenecks inside your own new ecosystem that must be resolved before your value proposition can function. Autonomous vehicles do not just need a better car. They need regulation, high-definition mapping, insurance norms, and infrastructure, and none of that moves at the speed of your engineering.

Extension opportunities

This is how much life the incumbent solution still has. Every time the old technology improves, it pushes the disruption further out. When emergence challenges are high and the incumbent can still extend, disruption arrives years, sometimes decades, later than a pure technology comparison predicts.

Seize, wait, shift, or shape

Crossing those two forces yields four responses. Seize when both point your way and you sprint. Wait when emergence challenges are unresolved and racing ahead only strands you. Shift when you redirect the innovation toward a market with lower barriers. Shape when you proactively fix the bottleneck yourself so the ecosystem can catch up. Tesla, 23andMe, and Zebra Technologies each illustrate a different read of the same clock.

The core caution: early entry into an ecosystem that cannot yet support you does not make you a visionary. It makes you the company that spent its runway waiting for partners who were not ready.

For a PM setting launch timing: stop timing the release off your own tech readiness. Map the ecosystem bottlenecks blocking adoption, honestly estimate how long the incumbent can keep improving, and choose seize, wait, shift, or shape deliberately. A "we were just too early" post-mortem is usually a timing-framework failure, not bad luck.

The Ego-System Trap

The most seductive mistake in ecosystem strategy is assuming the ecosystem revolves around you and that you are its natural leader. Adner calls this the ego-system trap, and it kills coordination. If everyone believes they are the leader, then no one is, and the whole system stalls.

United States mobile payments is the cautionary case. Apple, Google, the carriers, the banks, and the retailers each wanted to sit at the center and capture the most value. Every player had the means to lead and none would follow, so for years a technically ready product went nowhere. The bottleneck was not technology. It was too many would-be kings.

The leadership litmus test

Ask whether other players will actually accept a structure where you lead and capture the most value. If the honest answer is no, you do not have a leadership position, you have a wish. The hierarchy of winners makes the harder point: not everyone can lead, and that is fine, because followers can still win handsomely.

Microsoft and Intel are the proof. IBM led the PC but ceded the operating system and the chip. The disciplined followers, Microsoft and Intel, captured the enduring value. Choosing to follow well beat fighting an unwinnable leadership battle.

For a PM eyeing a platform play: run the litmus test before you declare yourself the hub. Ask, honestly, whether partners will line up behind you or whether every one of them is planning the same move. If leadership is not realistically yours, a disciplined follower position in someone else's ecosystem can pay far better than losing a war for the center.

Mindsets Matter: Establishing Leadership Is Different from Exercising Leadership

Leading a new ecosystem and leading a mature one demand opposite skills, and confusing them wastes good leaders in the wrong phase.

Establishing leadership

This happens in an emerging ecosystem, where partners are independent and you have no authority over them. It needs an alignment mindset: persuasion, credibility, and a willingness to cede value to get partners to occupy the roles you need. Nothing is settled, so the job is to convince, not to command.

Exercising leadership

This happens once the ecosystem matures and roles are known. It needs an execution mindset: optimize the structure, drive efficiency, and run the machine. The persuasion is done; now it is about operating well.

The ecosystem cycle

Ecosystems mature into industries as alignment hardens into predictable structure, shifting the work from alignment to execution. And industries revert to ecosystems when disruption breaks that structure, throwing everyone back to alignment. The cycle is why the same leader rarely fits both phases, and why a company can have exactly the wrong kind of leader for the moment it is in.

Microsoft Azure is the modern example. Success required moving from an execution mindset built to defend Windows toward an alignment mindset willing to partner with former enemies and cede ground to build a cloud ecosystem.

For product organizations: match the leader, and the PM, to the ecosystem's phase. The evangelist who recruits partners and gives away value to stand up a new platform is not automatically the operator who should scale it, and the reverse holds too. Naming which phase you are in tells you which mindset the role actually requires.

Strategic Clarity Is Collective

A strategy that lives only in the founder's head is not a strategy, it is a secret. Ecosystem strategy is executed by many independent hands, your own teams and your partners, so it works only when the clarity is shared across all of them.

Everyone in the coalition needs the same answers: what value architecture are we building, who leads and who follows, which game are we actually playing, and, just as important, which tempting moves we are deliberately not making. When that understanding is collective, partners self-align. When it is not, each player optimizes locally and the structure drifts apart.

This reframes communication as a strategic act, not an afterthought. The clearest ecosystem plan fails if the people delivering it cannot articulate it back to you.

For a PM: treat shared understanding as part of the deliverable. Communicate the value architecture and the explicit reasons you are not doing something to your team and partners as rigorously as you communicate the roadmap. Alignment you cannot see repeated back to you is alignment you do not actually have.

Confronting Ecosystem Disruption beyond the Private Sector

The same frameworks reach past companies. Governments, healthcare systems, education, and smart-city efforts are all ecosystems, value co-delivered by many parties who answer to no single boss. Value architecture, collective defense, minimum viable ecosystems with staged expansion, and the ego-system trap all apply wherever no one player can command the rest into place.

The reader's takeaway: the ecosystem lens is not a tech-industry trick. Anywhere multiple independent parties must align to deliver value, from a public-health rollout to an internal platform team serving other teams, the same questions decide who wins and whether the right game is even being played.

The Entire Book in One Framework

The whole book runs on one move: stop defining your game by your industry, and define it by your value architecture, the elements of customer value and the partners who deliver each. Once you see the game that way, four decisions follow.

Offense: build a new ecosystem through a minimum viable ecosystem, staged expansion, and carryover. Defense: modify your architecture, find defensible ground with aligned partners, and discipline your ambition. Timing: read emergence challenges against extension opportunities before you commit. Leadership: know whether you are establishing or exercising, and never assume the ego-system centers on you.

Everyone is playing to win. Winning the right game means first making sure the game you are pouring everything into is the one that still decides who creates value, and not a contest the world has already moved past.

10 Most Important Takeaways

• Competition has left the industry box; your real rivals may be partners or firms from an adjacent ecosystem.
• Define your product by its value architecture, the distinct value elements and who delivers each, not by its category.
• A complement can invert: the partner improving your product may keep improving until it replaces you, as smartphone screens did to Kodak.
• Kodak did not miss digital. It won the technology and still lost, because it was winning the wrong game.
• Defense is collective. You survive a giant by mobilizing a coalition, not by matching it feature for feature.
• The three defense principles work together: modify your architecture, find defensible ground with aligned partners, and discipline your ambition.
• Build ecosystems in stages: land a minimum viable ecosystem, prove value, recruit the next partner, and reuse assets that carry over.
• Time disruption off ecosystem readiness, weighing emergence challenges against how long the incumbent can still improve; too early can beat you worse than too late.
• Beware the ego-system trap: if everyone insists on leading, no one does, and a disciplined follower can win more than a failed leader.
• Establishing a new ecosystem needs an alignment mindset; running a mature one needs an execution mindset, and the same leader rarely does both.

The deepest idea worth keeping: strategy is no longer about beating the rivals in your industry. It is about seeing the whole map of who creates value with you, and making sure that when you finally win, you have won the game that still matters.