Key Takeaways
Make sure your transformation wins the customer’s next game, not yesterday’s.
Kodak did adapt. It invested about $5 billion in digital imaging, built a leading digital-camera business, and became a major player in digital printing. It closed film factories, cut 27,000 jobs, and shifted its business toward printers, ink, and photo paper. The familiar story of a company simply refusing to change misses the point.
The customer moved on. Smartphones made taking, viewing, and sharing images easy without printing them. Kodak had transformed successfully, but the value of printing collapsed as the surrounding system changed. Ecosystem disruption occurs when a change beyond a company’s traditional market boundaries alters the value it provides. The strategic test is not only whether a firm can master a new technology, but whether its transformation still serves a durable customer benefit.
Kodak’s story separates operational adaptation from strategic relevance. A company can execute a difficult transition well and still be optimizing for a shrinking purpose. This distinction is useful well beyond technology: leaders should ask whether their transformation changes how value is delivered or merely changes the machinery used to deliver it. The caution is that durable customer benefits can be hard to define independently of current habits. Kodak’s broad promise of preserving and sharing memories endured, while its assumed role for paper did not. Strategy must keep those two levels separate.
Map the pieces of customer value before you map the technologies.
Start with the benefit. A value proposition describes the benefit intended for the end customer. An ecosystem is the structured set of partners whose distinct contributions combine to deliver that benefit. It is more than a list of stakeholders or a conventional supply chain, because the partners must align around roles and interactions.
Make the value architecture visible. This is a way to break a value proposition into the abstract elements that produce its benefit. Kodak’s imaging promise involved capturing, producing, viewing, and sharing images. Digital cameras changed capture, while smartphones eventually changed viewing and weakened the need for printing. Mapping value elements helps reveal how a shift in one part of the offer can reshape another, even when the technologies seem unrelated.
The value architecture is powerful because it gives teams a level of analysis between the slogan and the operational checklist. It makes assumptions discussable: a team can debate whether discovery is essential to furniture shopping, or whether viewing belongs in the same strategic picture as image capture. That is a benefit and a limitation. The architecture is a chosen model, not an objective map of reality. Different partners may define the customer, the benefit, or the relevant elements differently, so the exercise should expose disagreement rather than create false consensus.
Assume a successful partner can become the substitute that erases you.
Complements can change direction. A complement improves the value of another offer. As it develops, it may keep strengthening that offer, stop adding meaningful value, or begin replacing it. Value inversion names this reversal, when a helpful complement undermines the core value it once supported.
Kodak’s screens crossed the boundary. Better image processors helped people take better pictures, while sensor improvements eventually mattered less to ordinary users. But smartphone screens became good enough to view images instead of printing them. The camera, once a source of more prints, helped eliminate the need for prints. To look for this risk, test what a partner’s technology would do if it became dramatically better and cheaper, then trace the effects across every element of the value architecture.
This view improves on competitor lists that treat partners as permanently helpful or hostile. The same capability can create value in one context and displace it in another, often without any deliberate attack. That makes cross-boundary analysis especially useful for firms dependent on improving technologies. The test is not a prediction, however. A hypothetical breakthrough can produce many plausible futures, and not all are commercially relevant. It works best as a way to identify assumptions worth monitoring, not as a reason to treat every partner’s progress as a threat.
Defend through partners, and specialize where giants cannot copy the whole experience.
Defense is collective. A smaller firm facing an ecosystem giant can change its offer, find partners with aligned interests, or limit ambitions that would damage its coalition. Wayfair responded to Amazon by building distinctive furniture-shopping features: richer visual discovery, tools that helped customers decide how items would fit their homes, and better support for suppliers. Its advantage was not simply a bigger catalog.
Choose allies carefully. TomTom survived Google’s free navigation by serving customers who wanted mapping data without giving Google access to their business information. Spotify, meanwhile, relied on record labels wary of Apple’s dominance. When Spotify tested direct music uploads that threatened the labels’ role, it retreated and pursued podcasts instead. The goal of defense is sustainable value creation alongside rivals, not necessarily their defeat.
These cases show that the best defense may be a change in the basis of competition rather than a stronger version of the old one. They also make partner strategy concrete: a business move can improve customer value while weakening the relationships needed to deliver it. The tension is particularly sharp when a firm’s growth opportunity overlaps with a partner’s livelihood. Coalition building therefore needs more than friendly language. It requires identifying whose contribution is essential, what each partner fears losing, and which areas of expansion can proceed without making allies into opponents.
Build ecosystems one credible partner step at a time.
Begin with a minimum viable ecosystem. This is the smallest arrangement of activities and partners that demonstrates enough value to attract the next participants. It differs from a minimum viable product, which tests customer demand. In Amazon’s early Alexa effort, a basic speaker, Prime Music, and a small group of users generated usage and feedback before Amazon asked developers and device makers to join.
Expand in sequence. Alexa gained skills, opened tools to developers, connected to home devices, and eventually let manufacturers build its voice service directly into their products. Ecosystem carryover means using relationships and capabilities from an existing business to help start another. Oprah brought audience trust into publishing and wellness; ASSA ABLOY carried its access-industry relationships into digital credentials. A compelling vision still needs a workable partner path.
The staged approach treats scale as a coordination problem, not a launch event. Each early participant should make the next participant’s decision easier, whether by proving demand, reducing uncertainty, or providing a credible route to market. This logic also explains why an incumbent’s existing relationships can matter as much as its technology. But a sequence that attracts partners can also entrench the initiator’s control. The strategic question is not only whether each step works, but whether partners see the eventual arrangement as valuable enough to keep participating.
Forecast disruption by tracking system readiness, not just technical performance.
The new offer may be delayed. Ecosystem readiness measures whether the partners, infrastructure, rules, and adoption needed for a new value proposition are in place. Meanwhile, improvements around the old offer can extend its usefulness. Philips developed HDTV well before cameras, broadcasting standards, and production systems were ready, contributing to a $2.5 billion write-down. The promise was real; the timing was not.
Track both sides of the race. New systems may face slow emergence while old systems gain extensions, producing prolonged coexistence or a long lull followed by rapid substitution. Leaders can commit when conditions are ready, wait while naming the milestones they need, shift to a more attainable market, or shape the environment by investing early in relationships and infrastructure. Zebra Technologies, for example, combined bar codes and RFID data systems rather than demanding an abrupt customer transition.
The framework corrects a common forecasting error: treating technical superiority as a timetable. Adoption depends on complements, institutions, and user routines, while established systems can improve using innovations developed around the challenger. This is especially relevant for technologies that require regulation or infrastructure. The model remains a judgment aid, not a clock. Readiness varies across customer segments, and a breakthrough or policy change can alter the pace abruptly. Sound planning therefore pairs a timing hypothesis with observable signals and a willingness to revise it.
Earn leadership through willing followership, or choose a valuable follower role.
Leadership is a role, not a trophy. In an ecosystem, a leader coordinates partners around a value proposition, but partners must choose to follow. Apple Pay struggled in the United States because banks, retailers, mobile operators, and handset companies each had different ambitions. Apple aligned many banks, but retailers and operators pursued competing payment systems, and adoption remained limited.
Followers can win. In China, Alibaba and Tencent built payment systems from existing e-commerce and messaging relationships, giving them a credible starting point. A partner should assess whether the proposed leader’s plan fits its own interests, whether other essential partners will accept the arrangement, and whether each party benefits when the ecosystem succeeds. Leadership efforts that fail to align partners can leave the would-be leader with the largest losses.
The ego-system trap is the assumption that partners naturally accept one company’s leadership because that company is powerful elsewhere. The mobile-payment example shows why authority does not transfer automatically across markets. The distinction between leading an ecosystem and participating in a successful one also broadens the definition of success: a follower can capture value without bearing the full cost of orchestration. Yet followership is not passive. Early partners can shape the rules, negotiate protections, or support a different leader while the structure is still unsettled.
Change leadership style when the ecosystem shifts from alignment to execution.
Different stages demand different work. Emerging ecosystems need leaders who can align independent partners without relying on formal authority. Mature ecosystems need leaders who execute reliably within an accepted structure. Microsoft CEO Steve Ballmer had vision and invested heavily in cloud computing, but struggled to build alignment beyond Microsoft’s established computer ecosystem.
Nadella changed the approach. Satya Nadella made partnership more credible by supporting rival platforms, including bringing Microsoft Office to iOS. He used Office 365 and existing customer relationships to encourage cloud adoption, while changing internal sales and operating practices to support Azure. The difference was not simply a better product or a lack of ambition before. Microsoft had to realign its own departments and partners to make the cloud business work at scale.
The Microsoft comparison resists a simplistic hero story. Ballmer’s execution helped build assets that Nadella could redeploy; the same company needed different leadership priorities as its strategic context changed. This is a useful correction to the idea that one leadership style is universally superior. Alignment work also has a cost: short-term efficiency may be sacrificed to build new relationships and capabilities. Organizations that reward only immediate results can therefore select for the wrong mindset precisely when a new ecosystem requires patient coalition building.
Give strategy a shared vocabulary so teams can act without guessing.
Clarity must travel. A strategy understood only by senior leaders cannot coordinate the many choices required across an ecosystem. A shared account of the customer benefit, value elements, partner roles, and timing gives teams a basis for making consistent decisions. Otherwise, strategy discussions can collapse into budgets and forecasts, or into calls for passion that motivate people without telling them what to do.
Make the model usable. Startups need language that survives team growth. Established firms need to question assumptions that have become invisible inside the core business. Internal pilots also need a path to routine operations: if a project works only because a special team bends the organization around it, the broader organization has not yet aligned to scale it. The same ecosystem logic applies to public and social missions that depend on many institutions.
Shared language acts like coordination infrastructure. It lets people detect when a local decision contradicts the broader value proposition and makes disagreement more specific than a clash of intuitions. This is particularly important in complex organizations, where no single leader sees every dependency. The risk is turning a useful vocabulary into a ritual: diagrams and labels can create an appearance of alignment while incentives remain unchanged. Strategic fluency matters only when it affects resource allocation, partner commitments, and the choices people make under pressure.
Analysis
The book’s central contribution is a change in the unit of strategic attention. Instead of asking only which firm or technology will win inside an industry, it asks how a network of partners creates a customer benefit, and whether changes elsewhere in that network will alter the benefit itself. This explains why Kodak could adapt and still fail, why Amazon could build Alexa through a sequence of partner commitments, and why Apple’s reputation did not guarantee leadership in mobile payments.
The frameworks are most valuable as disciplined prompts. A value architecture surfaces hidden dependencies; value inversion makes the changing effects of complements visible; and the timing framework distinguishes technical readiness from system readiness. Their practical force comes less from prediction than from making assumptions explicit enough to test. The same applies to leadership: the distinction between alignment and execution clarifies why a successful operator may struggle when roles are unsettled, and why a follower can be better positioned than an unsuccessful would-be leader.
A necessary qualification is that alignment is not automatically fair or mutually beneficial. A powerful orchestrator can set terms that shift risk onto weaker partners, and a coalition’s success for firms may not equal social benefit for customers or workers. The book recognizes broader stakeholder concerns, but its central tools chiefly explain how organizations create and capture value. Applying them responsibly requires asking who bears the costs, who controls data and rules, and whether partners can leave or negotiate. Even with that caveat, the book offers a compelling practical lesson: strategy must describe not only the destination, but the structure of cooperation that makes the destination attainable.
People Also Read
Glossary
Ecosystem
Partner structure for shared valueAn ecosystem is the structure through which specific partners interact to deliver a value proposition to an end consumer. The concept emphasizes defined roles, positions, and flows among partners, rather than a loose list of stakeholders or a chain of separate supplier and buyer relationships.
Value proposition
Benefit promised to customersA value proposition states the benefit that a collective effort is intended to provide to an end consumer. It anchors ecosystem analysis in the customer outcome rather than a particular firm, technology, or industry, and it helps determine which partners and activities are needed.
Value architecture
Elements composing customer valueA value architecture is the set of abstract elements brought together to create a value proposition. It is distinct from a list of technologies, operational activities, or product features. By making the building blocks of value explicit, it helps reveal how a change in one element can affect others.
Value inversion
A complement becomes a threatValue inversion occurs when an improving complement stops strengthening a focal offer and begins to undermine it. The complement may not intend to compete. Its development can still replace an element of value elsewhere in the architecture, as smartphone screens reduced the need for printed photographs.
Ecosystem cycle
Alignment emerges, then destabilizesThe ecosystem cycle describes how interdependent partners move from unsettled collaboration toward stable, routinized roles and exchanges, which can become recognizable as industries. When those arrangements break down, participants must establish a new structure of alignment, returning competition to an ecosystem phase.
Minimum viable ecosystem
Smallest partner setup that attracts othersA minimum viable ecosystem is the smallest configuration of activities and partners that creates enough evidence of value to attract additional partners. Unlike a minimum viable product, which tests customer demand, it is designed to help align participants and build the structure required to deliver a fuller value proposition.
Staged expansion
Add partners in useful sequenceStaged expansion is the deliberate sequencing of partners and activities beyond an initial minimum viable ecosystem. Each addition should improve the value proposition while also making it easier to attract the next participant. The approach avoids demanding that every partner commit to a fully formed ecosystem at the outset.
Ecosystem carryover
Reuse relationships in a new ecosystemEcosystem carryover uses relationships, capabilities, or partners developed in one ecosystem to help establish a position in another. It can give an established firm or entrepreneur an early foothold, but partners still need a reason to participate in the new structure and value proposition.
Ego-system trap
Assuming others accept your leadershipThe ego-system trap occurs when an organization treats itself as the natural center and leader of an ecosystem. This presumption can obscure partners’ own leadership ambitions and interests. If key participants do not accept the proposed roles, the ecosystem may fail to align and cannot scale.
Ecosystem readiness
System prepared to deliver new valueEcosystem readiness refers to whether the partners, infrastructure, regulations, procedures, and adoption needed for a new value proposition are sufficiently developed. A technology can work well while the broader system remains unprepared, delaying the point at which customers can receive the promised value.
Extension opportunities
Ways to improve the old offerExtension opportunities are improvements to an established value proposition that arise through its technology or surrounding ecosystem. They can raise the performance customers expect from a challenger and delay substitution, even when the old core technology itself changes little.
Time compression diseconomies
Rushed development costs moreTime compression diseconomies describe how some resources become more costly or less effective to build when development is rushed. Trust, reputation, and partner relationships often require time to mature. Investing early in these resources can be advantageous when they are essential to future ecosystem alignment.
Download PDF
Download EPUB
.epub digital book format is ideal for reading ebooks on phones, tablets, and e-readers.