When Alex Osterwalder and his co-authors published The Invincible Company in 2020, it introduced something the innovation world needed: a visual way to see an entire innovation portfolio on one page. The invincible company portfolio map gave leadership teams a shared picture. Explore on one side, exploit on the other, every initiative plotted by evidence and expected return.
I have used this portfolio map in a range of industrial companies since the book came out. In packaging machinery, chemical processing, precision manufacturing, industrial automation. Every time, the map creates a moment of clarity. Leadership sees the imbalance they felt but could not articulate.
But clarity is not management. And that is where this book review gets honest. The portfolio map is a strong diagnostic tool. It is not a complete management system. Here is what works, what is missing, and what I have learned to add.
Request a Strategy Call about your innovation portfolio
In 30 minutes, I'll review your portfolio approach and identify where The Invincible Company's tools help and where you need additional frameworks. Or book a workshop where your team builds a portfolio view using the best tools for your situation.
What The Invincible Company proposes
The book’s central argument is that companies become “invincible” by managing a portfolio of business models, not by perfecting a single one. Every company needs both explore activities (searching for new business models) and exploit activities (scaling proven ones). The Business Model Canvas and Value Proposition Canvas handle the individual model level. The portfolio map handles the collection.
Three concepts from the book matter most for practitioners:
The Business Portfolio Map. A two-axis visualization. The horizontal axis shows evidence strength: is this idea a hypothesis, partially tested, or fully proven? The vertical axis shows expected return: incremental improvement or transformational potential. Every initiative in the portfolio gets plotted. The resulting picture shows where the portfolio is heavy and where it is empty.
The explore/exploit distinction. Not new to Osterwalder (it originates from James March’s 1991 research), but the book makes it visual and accessible. Explore vs exploit becomes a portfolio conversation, not an abstract concept. Leadership can point at the map and say “we have 18 initiatives in exploit and 2 in explore” and everyone understands the problem.
Death and disruption risk. The book argues that every company faces two threats: the risk that its current business models die (declining markets, shifting customer needs) and the risk of disruption (new entrants with better business models). This framing helps boards understand why explore investments matter, even when exploit is generating healthy revenue today.
These three elements work together. The risk framework creates urgency. The explore/exploit distinction clarifies the response. The portfolio map makes it visible.
What the book gets right
After using these tools with dozens of leadership teams, three things consistently deliver value.
The visual portfolio concept works
Before The Invincible Company, most innovation portfolio conversations happened in spreadsheets. Lists of projects with budget columns, timeline rows, and RAG status indicators. Red, amber, green. No one could see the shape of the portfolio.
The portfolio map changed that. I see the same reaction regularly: a leadership team plots their innovation initiatives on the map, and within minutes someone says “we have no explore, everything sits in the top-right corner.” That visualization does more in 10 minutes than six months of innovation reports.
The map is genuinely useful because it translates portfolio strategy from a concept into a picture. Pictures create conversations that data tables do not.
The death and disruption risk framework helps boards
Innovation leaders have a persistent problem: justifying explore investments to boards focused on quarterly results. “We need to invest in the future” is too vague. “What is the ROI?” kills the conversation.
The death and disruption risk framework provides better language. Instead of “we need more innovation,” the conversation becomes: “Our core adhesives business faces a 40% revenue risk from sustainability regulations within 5 years. That is death risk. We are not exploring alternatives.” Boards understand risk. They manage risk every day. Framing innovation as risk management, not R&D spending, changes the quality of the conversation.
I now use this framing in almost every portfolio allocation discussion with industrial leadership. It works because it connects innovation to something boards already care about.
The innovation funnel metaphor connects to existing thinking
The book describes the explore side as a funnel: many ideas enter, few survive. This metaphor connects to something most manufacturing leaders already understand from product development. They have run stage-gate processes for decades. The innovation funnel feels familiar, even though the evaluation criteria are different.
This familiarity matters. When I introduce portfolio thinking to companies with no innovation readiness, starting with concepts that connect to existing mental models reduces resistance. The funnel is not a new process. It is a new application of a known concept.
What the book does not address
Here is where the practitioner perspective diverges from the book. These are not criticisms of the book’s quality. They are gaps between mapping a portfolio and managing one. Every company I work with hits these gaps within weeks of building their first portfolio map.
No governance rhythm
The book shows you how to build a portfolio map. It does not show you how to run portfolio review meetings. How often? Who attends? What decisions get made? What happens between reviews?
In practice, governance rhythm is the difference between a map that collects dust and a map that drives decisions. I have seen companies build beautiful portfolio maps in workshops and never look at them again. Not because the map was wrong, but because nobody scheduled the next meeting where the map would be updated and acted on.
What I add: quarterly portfolio reviews with a fixed agenda, defined decision rights, and mandatory evidence updates from every explore team. The map is an input to the meeting. The meeting is where the management happens.
For more on building a governance rhythm, see the innovation portfolio governance guide.
No kill criteria
The Invincible Company explains that explore initiatives should progress based on evidence. But it does not define what “enough evidence” means, when to stop funding, or how to make the kill decision.
This is the hardest part of innovation portfolio management. Not starting projects. Stopping them. In every portfolio review I facilitate, at least one initiative should have been stopped months ago. Everyone knows it, but no one has the criteria or the authority to make the call.
What I add: kill criteria defined before the explore project starts. “If we cannot find 10 potential customers willing to co-develop within 6 months, we stop.” “If the unit economics do not work at 2x our current production cost, we pivot or stop.” Criteria set in advance are easier to enforce than judgments made in the moment.
For practical approaches to stopping projects, see how to kill innovation projects.
No political dynamics
The book presents portfolio management as a rational exercise. Map the initiatives, assess the evidence, allocate resources. In reality, innovation portfolio mistakes are often political, not analytical.
The VP of the core business does not want explore projects competing for engineering resources. The division head whose initiative should be killed sits on the steering committee. The CEO’s pet project has weak evidence but strong protection.
I regularly see portfolio maps that clearly show projects should be stopped. Those projects often run for another year or longer. The map is right. The political dynamics overrule it.
What I add: anonymous evidence scoring, external facilitation for kill decisions, and separating the “review the evidence” meeting from the “make the decision” meeting. These do not eliminate politics. They create structures that make political overrides visible.
No capital-intensive adaptations
The Invincible Company draws heavily from software and digital business model examples. The portfolio map works at the concept level for any industry. But the execution assumptions favor low-cost, fast-iteration explore projects.
In manufacturing, one explore experiment might cost €500.000 before you get meaningful market feedback. A chemical company cannot prototype a new polymer in two weeks. A machinery company cannot build a minimum viable product with sticky notes and customer interviews alone.
What I add: manufacturing-specific explore budgets, longer evidence milestones, and a tiered evidence system that accounts for physical product development timelines. The map stays the same. The evidence criteria and funding rules change to reflect capital intensity.
This is one of the most common patterns I see with companies that read Testing Business Ideas alongside The Invincible Company. The principles translate. The timelines and cost structures do not.
The gap between mapping and managing
This is the fundamental limitation. The portfolio map is a visibility tool. It answers: “What does our portfolio look like right now?” It does not answer: “What should we do about it?”
Managing an innovation portfolio requires decisions. Continue this project or kill it? Increase the explore allocation or hold steady? Merge two similar initiatives or let them compete? Which explore projects get Series A-style funding and which stay at seed stage?
The book implies that visibility leads to good decisions. In my experience, visibility is necessary but not sufficient. You also need decision criteria, decision rights, a governance cadence, and the organizational courage to act on what the map shows you.
I use the portfolio map as the starting point, not the destination. It shows the current state. The management system I build around it handles the decisions that follow.
How I use it in practice
After running portfolio sessions with multiple industrial companies, here is the workflow that works.
Step 1: Map the current state. Use the portfolio map exactly as the book describes. Plot every initiative. Let leadership see the pattern. This step creates the shared understanding that everything else builds on.
Step 2: Score the evidence. For each initiative, document what evidence exists. Customer interviews conducted, prototypes tested, revenue generated, partnerships signed. Not opinions about potential. Actual evidence.
Step 3: Apply decision frameworks. Use the framework comparison to determine which additional tools fit. Three Horizons for time-based planning. The Innovation Ambition Matrix for budget allocation. Zone to Win if disruption is active.
Step 4: Define the governance rhythm. Quarterly reviews minimum. Monthly for explore projects that are burning capital. Each review has three possible outcomes per project: continue (with updated milestones), pivot (change direction, same budget), or kill (stop and reallocate).
Step 5: Build the business model innovation capability. The portfolio map is a tool. The real investment is building the organizational capability to use it. Teams need to know how to fill in a Business Model Canvas, how to run validation experiments, and how to present evidence in portfolio reviews. That capability is what makes the map useful over time, not just in the first workshop.
The portfolio map from The Invincible Company is step 1. Steps 2 through 5 are where portfolio management actually happens.



