When Your Innovation Pipeline Stalls: The Route to Rapid Recovery in Core and Adjacent Markets

An innovation portfolio connects a company’s strategy with its innovation effort. A well balanced portfolio extends the core and near adjacent businesses while creating options for future growth. When your innovation pipeline stalls, the cause is rarely a shortage of ideas. It is usually too many projects, too little focus, and decisions that are out of sync with the speed at which your markets change.

This article is about the part of the portfolio where results can be achieved in the short term: the core and the near adjacent markets, those that can be reached with the company’s existing core competencies. It describes how to diagnose why momentum has been lost, how to select the bets most likely to produce revenue quickly, how to stop the rest, and how to fund and govern the remaining projects so that they move at speed.

It is not a review of the whole portfolio. Following the distinction between core, adjacent and transformational initiatives described by Nagji and Tuff, transformational options need a different logic and a longer horizon, and they are outside the scope of this article.

What a recovery delivers

A stalled pipeline is usually a compounding of slow decisions, scattered funding and a portfolio that has drifted away from customer needs and what they are willing to pay for. The levers that restore performance are largely internal and can be applied quickly. The approach rests on five moves:

• Diagnose. Run a structured diagnostic over 48 to 72 hours to isolate causes across market, execution, governance and funding.
• Prioritise. Score every opportunity on impact, confidence, time-to-revenue and capability fit, then decide what to accelerate, hold or stop.
• Fund. Move capital from stopped projects to the few bets with the strongest evidence, using time-boxed sprint funding.
• Simplify. Reduce decision layers and give a small, empowered team the authority to act.
• Measure. Track a short set of indicators every week.

A single senior sponsor with cross-functional authority should own the effort, typically the COO, or a Head of Innovation backed directly by the CFO. Diffuse ownership is itself a common reason a pipeline stalls.

Targets for the first six months:

• By day 30: diagnostic complete, portfolio re-scored, stop and accelerate decisions made, sprint funding released to the top three bets.
• By day 90: first paid pilots or paid proofs of concept, and a measurable reduction in the time taken to reach decisions.
• By day 180: material revenue from the accelerated bets, a rebalanced portfolio and a dashboard the executive team trusts.

All of this requires that you are starting from a clear investment hypothesis linked to your strategy about how your innovation efforts contribute to your goals and how resources are ring fenced and distributed across your innovation portfolio.

Why an innovation pipeline stalls: a diagnostic

Before reallocating any budget, the leadership team needs to understand why momentum was lost. The causes cluster into four categories.

Market and customer signals. The most expensive stall is the one nobody noticed: a portfolio still executing against a market that has moved. The test is simple. Which active projects have a named buyer who has confirmed willingness to pay in the last 90 days? Projects that cannot answer this are usually running on historic assumptions.

Execution and resourcing. Capacity spread across too many projects, missing skills and repeatedly deferred validation all lengthen the path to revenue. Portfolios generally progress fastest when validation is built in early rather than left to a late-stage gate. If teams produce activity but not evidence, resourcing is a likely cause.

Governance and decision velocity. When approvals pass through several committees and no single forum can say yes, projects stall between the gates rather than at them. Measure the elapsed time from a request for a decision to the decision itself. If the median is measured in weeks, governance is the constraint, not the ideas.

Funding patterns and incentives. Annual budget cycles deprive promising pilots of timely capital, while sunk-cost thinking keeps weak projects alive. Teams that are rewarded for launching, rather than for proving commercial traction, make the problem worse.

Five diagnostic questions:

• Which projects have a confirmed buyer and willingness-to-pay evidence from the last 90 days?
• What is the median time from request to decision?
• How many projects have no validation milestone in the next 30 days?
• What share of innovation spend is committed to the top three bets?
• Are teams rewarded for launches or for validated commercial learning?

Prioritising core and adjacent bets: adding capability fit

Prioritisation is the highest-leverage action in the first 30 days, because it releases capacity and capital at the same time. Most stalled portfolios carry too many live projects, each short of the focus it needs.

The scoring model rates every project from 1 to 5 on four factors:

1. Impact. Expected revenue or strategic value if the project succeeds.
2. Confidence. Strength of evidence: validated demand, technical feasibility, team capability.
3. Time-to-revenue. Speed to paid traction, scored inversely. A 5 means revenue within 90 days and a 1 means more than 18 months.
4. Capability fit. The extent to which the project draws on the company’s existing core competencies and assets, rather than requiring new ones.

The fourth factor is what makes the model specific to core and adjacent markets. Prahalad and Hamel defined a core competence as a bundle of skills and technologies that gives access to a wide variety of markets, makes a significant contribution to the benefit customers perceive, and is difficult for competitors to imitate. A bet that draws on such a competence can reach the market faster, at lower cost and with a stronger advantage than one that depends on building capability from the beginning. Score a 5 when the project uses existing competencies and assets as they are, and a 1 when it requires capabilities the company does not yet have.

Multiply the four scores for a composite (maximum 625). A multiplicative model is deliberate: a project that is attractive on one dimension but weak on another should not survive on that strength alone. In addition, a project with a capability fit of 1 or 2 cannot be rated green, however well it scores elsewhere. In the short term it is a different kind of investment, and it belongs in a separate conversation.

Rebalancing rules should be agreed in advance (above scoring is for illustration purposes, you may want to have a less or more stricter filter than this one). An amber project that does not reach green after one validation sprint becomes red. A green project that misses two consecutive validation milestones drops to amber. These rules remove emotion from difficult decisions and prevent the sunk-cost drift that allowed the pipeline to stall.

Funding reset: moving capital to the strongest bets

Prioritisation only works if capital follows the decisions. Annual budget cycles are poorly matched to the pace of validation, so the reset needs a central reallocation pool.

• Day 30: create the pool from stopped and amber-held projects, and release time-boxed sprint funding to the top three green bets.
• Day 90: review sprint outcomes, increase investment in projects that show paid traction, and withdraw from those that failed validation.
• Day 180: move proven bets to continuous funding and reset the annual envelope around demonstrated performance.

Faster funding must not mean looser funding. Each tranche should carry one measurable success condition and a pre-defined exit trigger. If the condition is not met, the funding stops automatically and shouldn’t be re-negotiated.

Simplifying governance to speed up decisions

Under pressure the instinct is to add oversight. The better course is usually the opposite: fewer layers, clearer decision rights and faster cycles, with accountability intact.

Establish a single fast-track forum whose members can commit resources on the spot. Set a time-to-decision target, for example five working days from a complete request, publish it and measure against it. Agree the approval and veto rules in advance. A green project with validated demand, below a set funding threshold, should be approvable by the sponsor alone. A project that misses two validation milestones should be reviewed automatically. Clear escalation criteria and exit triggers answer the concern that speed weakens control.

Proving traction in 90 days

In the first 90 days the objective is not a polished product. It is evidence of desirability and commercial traction, produced as cheaply and quickly as possible.

Design the smallest experiment that can move the confidence score. Desirability signals are stronger than opinion. The best evidence is money changing hands: a paid pilot, a letter of intent with commercial terms, or a customer who agrees to co-fund a proof of concept. A customer who contributes budget has shown real willingness to pay.

Repurpose core competencies for fast pilots. Established companies rarely need to build new capability to run a pilot. Manufacturing capacity, distribution relationships, data assets, service teams and brand access can often be redeployed within weeks. The recovery team’s task is to match each prioritised bet to the fastest available internal capability. Running experiments in short, time-boxed cycles, each ending in a decision, keeps projects from returning to the open-ended state that caused the stall.

Measuring the recovery

Progress that cannot be measured cannot be defended. Report the leading indicators weekly and the full set monthly.

• Leading (first 30 to 90 days): decision velocity, the median time from request to decision; the pilot conversion ratio, the share of validation experiments that become paid pilots; and the cost per validated learning, the spend needed to raise a project’s confidence score by one level.
• Lagging (90 to 180 days): pilot revenue from accelerated bets; run-rate growth of contracted revenue in the active portfolio; and funding churn, the share of capital moved from red projects to green ones.

Leading indicators warn early whether we are on track. Lagging indicators confirm that better decisions are producing returns.

A case in practice and patterns to avoid

For a client in the animal feed business we applied this approach and cut about 50% of projects. Most of the projects in the core had been sitting in the pipeline for some time, had no immediate link to a customer need or required new capabilities that were not planned for. The resources that became available were immediately relocated to those projects with high scores. These were revitalized by assigning a team lead and clear timelines and expectations to reach the next milestone.

Three failure patterns recur. The first is a reset that prioritises on paper but never moves the capital, leaving weak projects funded and strong ones short of resources. The second is governance simplified in name, with decisions still passing through the same slow forums. The third is measuring activity, such as demonstrations and workshops, instead of commercial traction. Most resets do not fail because the intention isn’t there but because people are reluctant to follow through when the criteria tells you to stop a project.

A 90-day action plan

1. Name a single executive sponsor and assemble a small, empowered core team.
2. Run the 48 to 72 hour diagnostic.
3. Re-score the portfolio on impact, confidence, time-to-revenue and capability fit.
4. Stop the red projects, pool the released budget and release sprint funding to the green bets.
5. Set up one fast-track forum with a five-day decision target.
6. Run minimum validation experiments and report the leading indicators weekly.
7. Review at day 90, increase investment in projects with traction and move proven bets to continuous funding.

From stall to momentum

Treated as an operating-model reset rather than a strategy exercise, this approach can produce revenue signals within a quarter and sustained performance within two. When your innovation pipeline stalls, the constraint is seldom a lack of ideas. It is diffuse ownership, slow decisions, scattered funding and reluctance to stop projects that no longer earn their place. Companies that concentrate their effort on the bets that fit their core competencies are the ones that regain momentum.

Need Expert Advice?

This article was produced by Global Law Experts. For specialist advice on this topic, contact Michel van Hove at Strategos, a member of the Global Law Experts network.

Sources

1. C.K. Prahalad and Gary Hamel, “The Core Competence of the Corporation“, Harvard Business Review, May-June 1990.
2. Bansi Nagji and Geoff Tuff, “Managing Your Innovation Portfolio“, Harvard Business Review, May 2012.
3. Strategos, Innovation Portfolio Management: Solving the Strategy-Innovation Gap.