8 Innovation portfolio mistakes that keep companies funding the wrong projects

Ton van der Linden
Share

Most companies say innovation is a strategic priority. Then 95% of the budget goes to core. After reviewing innovation portfolios at 40+ industrial companies, I keep seeing the same eight mistakes. Not strategy problems. Governance problems. The kind that quietly ensure the wrong projects get funded year after year.

Innovation portfolio management is where strategy meets resource allocation. It is also where most companies quietly ensure the wrong projects get funded, year after year.

I have reviewed innovation portfolios at more than 40 industrial companies over 25 years. Manufacturing companies, chemical processors, equipment makers, B2B enterprises across Europe. The pattern repeats with uncomfortable consistency: leadership says innovation is a strategic priority. The budget says otherwise.

The innovation portfolio mistakes I see are not strategy problems. They are governance problems. The kind that let mediocre projects linger for years while promising ones starve for resources. The kind that no amount of frameworks, software, or innovation labs will fix.

Here are the eight I keep seeing. And what to do instead.


Book a strategy call about your innovation portfolio
Book your Strategy Call

1. Putting 95% of the budget into core while claiming innovation matters

This is the mistake that makes everything else irrelevant.

I ask leadership teams how much of their R&D and innovation budget goes to genuine explore projects: new business models, new markets, unproven technologies. Not product improvements. Not cost reductions. Not line extensions. Actual exploration where the outcome is uncertain.

The answer, consistently, is between 5% and 10%. The other 90-95% funds core improvements that the engineering team was going to do anyway. And leadership still calls it an innovation portfolio.

It is not. It is an optimization portfolio with a thin layer of innovation branding.

This happens because exploit has built-in advocacy. The sales team needs product updates to close this quarter’s deals. Operations needs cost reductions to hit margin targets. Every one of those requests is urgent, measurable, and tied to someone’s bonus. The explore project testing a subscription model for industrial services has none of those advantages. When budgets get tight, explore is the first thing cut.

At one packaging machinery company, I found that their “innovation portfolio” of 23 projects included 21 product improvements and two genuine explore initiatives. Both explore projects had been paused twice in 18 months because their budget was redirected to “urgent” core projects. Leadership genuinely believed they were investing in the future.

What to do instead: Make the allocation visible. Put the actual numbers on the table: what percentage goes to core, what percentage to adjacent, what percentage to transformational. Then protect explore budgets explicitly. Ring-fence a percentage that cannot be raided when quarterly pressure hits. The right number depends on your industry, but if explore gets less than 10%, you are not serious about future growth. Nagji and Tuff’s research in the Harvard Business Review showed that companies who actively managed this allocation outperformed those who let it drift.


2. No kill criteria, so mediocre projects linger for years

This is the second most expensive mistake. Not failed projects. Undead projects.

A project is launched with energy and ambition. Six months in, the initial excitement fades. The market signal is weak. The technology is harder than expected. But nobody kills it. Because nobody agreed upfront what “failure” looks like.

So the project continues. Not with full commitment, just enough resources to keep it alive. One engineer part-time. A quarterly update that says “making progress.” A budget line that is too small to question but too persistent to ignore.

I have seen industrial companies carry zombie projects for three to five years. Not because anyone believed in them. Because nobody had the criteria or the authority to stop them.

In manufacturing, the cost is even higher. A zombie project in software might waste a few developer-months. A zombie project in manufacturing ties up lab equipment, engineering time, and sometimes pilot production capacity that other projects need.

What to do instead: Set kill criteria before a project starts. Not after. Before. “We will stop this project if we cannot find 10 potential customers willing to participate in a pilot within 6 months.” “We will stop if the unit economics do not work at €X per unit by month 9.” The criteria should be specific, measurable, and agreed upon by the project team and the portfolio governance board. When a project hits a kill criterion, the decision is already made. The conversation shifts from “should we kill this?” to “the evidence says stop, do we have a reason to override?”


3. Portfolio reviews based on presentation skills, not evidence

This is the mistake that rewards the wrong behavior.

Most companies run quarterly or annual portfolio reviews. Project leads present their progress. Leadership asks questions. Decisions are made about which projects continue and which get cut.

The problem: decisions are based on who presents best, not on what the evidence shows.

I have sat in dozens of these reviews. The project with the polished deck, the confident presenter, and the exciting narrative always gets funded. The project with messy data, an honest presenter who admits “we do not know yet,” and a request for more time to test assumptions gets questioned or cut.

This is backwards. In innovation, the team that says “we do not know” is often closer to the truth than the team that says “everything is on track.” The messy, honest update usually represents a team that is actually learning. The polished presentation often hides a team that has stopped testing and started selling internally.

What to do instead: Standardize the evidence format. Every project presents the same dashboard: key assumptions tested, results per assumption, next experiments planned, kill criteria status, and budget spent versus learning generated. No narratives. No pitch decks. Just evidence. When every project reports in the same format, the governance board can actually compare them. The decision shifts from “which story do I believe?” to “which project has the strongest evidence?”


4. Pet projects protected by senior sponsors

This is the political version of the kill criteria problem.

Every company has them. The CEO’s favorite project. The board member’s strategic initiative. The SVP’s “baby” that they championed through three budget cycles. These projects are functionally unkillable regardless of what the evidence says.

I worked with a chemical company where one project had consumed over €1.200.000 across four years. The original business case had been disproven twice. Customer interviews showed weak demand. The technology partner had pulled out. But the project continued because the division president had staked his reputation on it in a board presentation two years earlier. Killing the project meant the division president losing face.

The cost is not just the money wasted on the pet project. It is the opportunity cost. Every euro and every engineer-hour going to a protected project is a euro and an hour not going to a project that might actually work. And the rest of the organization notices. When people see that evidence does not matter, that political protection trumps results, they stop bothering with rigorous testing. Why generate evidence nobody will use?

What to do instead: Separate the person from the project. The governance process should evaluate projects based on evidence, not on who sponsored them. One way to do this: anonymous project reviews where the governance board sees the evidence dashboard without knowing who the sponsor is. Another way: mandatory rotation of project sponsors every 12 months, so no single person becomes permanently attached to a project’s survival. The goal is to make killing a project a normal governance outcome, not a political event.


5. Allocating resources by politics, not strategy

This mistake goes beyond pet projects. It is about how the entire portfolio gets funded.

In most companies I work with, the annual innovation budget allocation is a political negotiation. Each business unit argues for its share. The loudest voices, the most persuasive leaders, the divisions with the best quarterly results get the most resources. The allocation reflects internal power dynamics, not strategic priorities.

The result: the division with a strong existing business and little need for exploration gets the most innovation budget because they have the political capital. The division in a disrupted market that desperately needs to explore new business models gets a fraction because they are already under pressure and have less influence.

I saw this at an agricultural equipment company. Their traditional machinery division received 70% of the innovation budget. Their precision agriculture division, which was entering a market growing at 25% annually, received 15%. The remaining 15% was spread across five small projects. The allocation had nothing to do with market opportunity. It was purely a reflection of which division had the stronger VP at the leadership table.

What to do instead: Allocate from strategy, not from politics. Start with the strategic questions: where are the biggest opportunities? Where are the biggest threats? What does the Business Model Canvas show about where value creation is shifting? Then allocate resources to match. This means some divisions will get more than they asked for and some will get less. That is the point. The portfolio should reflect where the company needs to go, not where internal power sits today.


6. Confusing activity with progress (innovation theater)

This is the mistake that feels the best while doing the most damage.

Innovation theater is when a company invests heavily in the appearance of innovation without connecting any of it to portfolio decisions. Hackathons. Innovation labs. Design thinking workshops. Startup accelerator partnerships. Trend reports. Conference attendance. Innovation awards.

All visible. All expensive. None of it connected to the question that matters: what should we fund, what should we kill, and what should we scale?

I worked with a manufacturing company that had an innovation lab, ran quarterly hackathons, sent teams to two conferences a year, and had a partnership with a local startup accelerator. When I asked them to show me which of those activities had produced a project that entered their portfolio, the answer was zero. In three years.

The lab produced prototypes that nobody evaluated. The hackathons produced ideas that nobody followed up on. The accelerator partnerships produced press releases. But the innovation portfolio was still the same list of incremental product improvements it had been before any of those activities started.

What to do instead: Connect every innovation activity to a portfolio decision. A hackathon should produce ideas that enter the portfolio evaluation process. An innovation lab should produce prototypes that get tested against real customer evidence using business experiment methodology. A startup partnership should produce a thesis that gets validated against the portfolio strategy. If an activity does not feed the portfolio, question why you are doing it. Innovation theater is not harmless. It consumes budget and attention that could go to projects that actually move the needle.


7. Ignoring the explore-exploit balance until a disruption forces it

This is the mistake companies only recognize in retrospect.

The explore-exploit balance is the single most important metric in innovation portfolio management. Exploit funds improvements to existing business models. Explore funds the search for new ones. Every company needs both. Almost every company gets the balance wrong and does not realize it until a market shift makes the imbalance painful.

I worked with an industrial sensor company that had spent eight years optimizing their existing product line. Incremental improvements every year. Growing margins. Happy customers. Zero investment in explore.

Then a competitor launched a sensor-as-a-service model that undercut their pricing by 40%. Within 18 months, three of their top 10 customers had switched. The company had no new business model ready because they had never explored one. By the time they started, they were three to four years behind.

The painful part: the signals had been visible for years. Industry publications were writing about servitization. Competitors were experimenting. But because the core business was performing well, nobody felt the urgency to explore. That is how explore-exploit imbalance works. It is invisible when times are good and catastrophic when they change.

What to do instead: Track your explore-exploit balance the same way you track revenue. Make it a board-level metric. Review it quarterly. And do not wait for disruption to start exploring. The time to invest in new business models is when your core business is strong enough to fund them. By the time disruption hits, you have already lost three to five years. For companies with physical products and long development cycles, this is not a theoretical risk. It is an operational reality that requires years of lead time.


8. Managing the innovation portfolio with core business governance

This is the structural mistake that makes all the other mistakes worse.

Most companies manage their innovation portfolio using the same governance system they use for their core business. Same stage-gate process. Same financial metrics. Same review cadence. Same decision criteria. The logic seems reasonable: we already have a governance system that works for projects, so we use it for innovation projects too.

The problem: core business governance is designed for predictability. Stage-gate milestones assume you know what you are building, for whom, and at what cost. Financial metrics like NPV and IRR assume you can forecast revenue and costs. Quarterly reviews assume predictable progress.

Innovation projects, by definition, have none of that. They are searching for a business model, not executing one. They do not know their revenue because they do not know their customer yet. They cannot forecast costs because they have not validated the product yet. And their progress is measured in learning speed, not milestone completion.

When you force explore projects through core governance, you get one of two outcomes. Either the team fabricates the forecasts to pass the gates (which teaches them to lie) or the project gets killed for not meeting milestones that were never realistic in the first place.

I saw this at a packaging company with a promising explore project around sustainable packaging. The project had strong customer interest from early conversations. But it was evaluated quarterly using the same NPV model as line extensions. After two quarters with no revenue projection, the project was deprioritized. The team that had been doing real customer discovery using a Value Proposition Canvas was reassigned. Eighteen months later, a competitor launched a similar product and captured the market.

What to do instead: Build a separate governance track for explore projects. Different metrics: assumptions tested, customer evidence gathered, willingness to pay validated, technical feasibility confirmed. Different cadence: monthly evidence reviews instead of quarterly financial reviews. Different decision criteria: “what did you learn?” instead of “where is the revenue?” The core governance system stays in place for what it is good at: managing execution. The explore governance system manages search. Both feed into portfolio-level reviews where the allocation between explore and exploit gets adjusted based on actual evidence.


Book a strategy call about your innovation portfolio

In 30 minutes, I’ll review how your innovation portfolio is governed and where explore keeps losing to exploit. Or book a leadership workshop where your team builds portfolio governance with real decision criteria.

Book your Strategy Call

The pattern behind all 8 mistakes

Every one of these mistakes shares a root cause: treating innovation as a project management problem instead of a governance problem.

Projects can be managed. You set milestones, allocate resources, track progress. That works for exploit: you know what you are building and you optimize how you build it.

Innovation portfolios need to be governed. You make allocation decisions under uncertainty. You protect future bets from present pressure. You build systems that reward evidence over politics and learning over presentation skills. That requires a fundamentally different operating system.

The companies I work with that get portfolio management right share three characteristics. They protect explore budgets explicitly. They set kill criteria before projects start. And they evaluate projects based on evidence, not on who has the best deck or the most senior sponsor.

None of that requires a new framework. It requires governance discipline. And the willingness to make it stick even when quarterly results are under pressure.

Start there.

If these patterns look familiar from your business model work, read about Business Model Canvas mistakes for the same diagnostic lens applied to individual business models.

Teams that struggle with portfolio governance often struggle with value proposition canvas mistakes too, because unvalidated value propositions are what fill portfolios with the wrong projects.

The testing discipline that portfolio governance depends on breaks down in predictable ways. See business experiment mistakes for the patterns that produce bad evidence.

And if the organization itself is not ready for innovation, no governance system will save the portfolio. See innovation readiness mistakes for the foundational gaps that make portfolio management fail before it starts.

For a practical guide to setting the right allocation between core, adjacent, and transformational, see innovation portfolio allocation.

The kill criteria problem goes deeper than this article covers. See how to kill innovation projects for the full governance and political dynamics.

For a complete governance system including review cadence, dashboards, and decision criteria, see innovation portfolio governance.


Frequently asked questions

What is the most common innovation portfolio mistake?

The most damaging mistake is managing innovation projects with the same governance as core business. Core governance rewards predictability, efficiency, and hitting quarterly targets. Innovation requires uncertainty tolerance, learning speed, and longer time horizons. When you apply core governance to explore projects, you kill them with the wrong metrics before they have a chance to prove anything. Fixing this single mistake often unblocks several of the others.

Why do innovation portfolios fail?

Innovation portfolios fail because of governance, not strategy. Most companies know they should invest in innovation. But without explicit portfolio governance that protects explore budgets, sets kill criteria before projects start, and reviews based on evidence instead of presentations, the present always wins. Quarterly pressure, political dynamics, and sunk cost thinking ensure that the wrong projects get funded and the right projects get starved. An innovation readiness assessment can help identify whether your organization has the conditions to govern a portfolio effectively.

What is innovation theater?

Innovation theater is when companies confuse innovation activity with innovation progress. Running workshops, hosting hackathons, setting up innovation labs, sending teams to conferences. All visible activity, none of it connected to portfolio-level decisions about what to fund, what to kill, and what to scale. The hallmark of innovation theater is a full calendar of innovation events and zero new business models reaching the market.

How do you know if your innovation portfolio is working?

Three signals. First, your portfolio includes projects at different stages of uncertainty, from early exploration to scaling validated models. If everything is either core improvements or moonshots, the portfolio is unbalanced. Second, projects move through stages based on evidence, not opinion or presentation skills. Third, projects actually get killed when evidence says they should. If no project has been terminated in the last 12 months, your governance is not working.

How do you fix an innovation portfolio that is too focused on core?

Start by making the allocation visible. Most leadership teams do not realize how skewed their portfolio is until someone puts the numbers on the table. Then protect explore budgets explicitly: ring-fence a percentage that cannot be raided for core projects, even when quarterly pressure hits. The right percentage depends on your industry and competitive situation, but anything below 10% for explore means you are not serious about future growth. Track the allocation quarterly, report it to the board, and treat it with the same discipline you apply to financial metrics.