How to Decide Which Innovation Projects to Fund, Stop, or Scale

Who this post is for: Chief Innovation Officers, R&D leaders, and innovation portfolio managers who are sitting on more active projects, pilots, and bets than they can fund — and need a defensible way to decide which ones get more resources, which get killed, and which are ready to scale across the organization.

Every innovation leader eventually faces the same budget-season problem: more projects than money, and no clean way to decide between them.

The pilot that's been running for eight months with encouraging-but-not-conclusive results. The scouting engagement that surfaced three promising vendors nobody has capacity to evaluate. The internal tool a team built that works, but that nobody's measured against the alternative. The challenge-campaign winner that everyone loved and no one has moved forward. Each one has a sponsor. Each one has a story. And the honest truth is that the loudest sponsor, not the strongest project, usually wins the next round of funding.

That's not a strategy. It's a popularity contest with a budget attached.

The organizations that consistently get returns from innovation are the ones that replace the popularity contest with a repeatable decision framework — a structured way to look at every project in the portfolio and answer three questions: fund it further, stop it, or scale it. This post lays out that framework.

The Definition

Fund-stop-scale is a portfolio governance discipline: a structured, repeatable process for deciding, at defined decision points, whether each innovation project should receive further investment, be discontinued, or be scaled into broader deployment — based on evidence against predefined criteria rather than on sponsor enthusiasm, sunk cost, or recency.

The critical phrase is at defined decision points. Fund-stop-scale is not a continuous debate. It's a decision made at specific gates — the end of a pilot, a quarterly portfolio review, a budget cycle — using evidence that was defined as decision-relevant before the project began. Everything between gates is execution. The discipline is in the gate.

Why Most Fund-Stop-Scale Decisions Go Wrong

Before the framework, it's worth naming why these decisions are so hard — because the failure modes are predictable and the framework is built to counter each one.

Sunk cost dominates. A project that has consumed eighteen months and a significant budget is psychologically almost impossible to kill, regardless of its current trajectory. The money already spent — which should be irrelevant to the forward-looking decision — becomes the loudest argument for continuing. "We've come too far to stop now" is how portfolios fill up with projects that should have been killed a year ago.

The loudest sponsor wins. In the absence of a common evaluation standard, funding decisions default to organizational politics. The project with the most senior sponsor, or the most persuasive champion, gets the resources — not the project with the strongest evidence. This is invisible when it happens because it always comes wrapped in a plausible business rationale.

No common yardstick. A pilot in manufacturing and a pilot in customer service are evaluated by different teams, against different criteria, in different formats. When they land on the same portfolio review, there's no way to compare them. The decision-maker is comparing a paragraph of narrative enthusiasm against a spreadsheet of metrics, and the narrative usually wins.

Recency bias. The project that presented last week feels more promising than the one reviewed three months ago, regardless of the underlying evidence. Without a persistent, structured record, the portfolio review rewards whoever is freshest in memory.

Nothing ever gets killed. The hardest decision in innovation is the stop decision — and it's the one most organizations avoid entirely. Projects don't get killed; they get quietly defunded, drift into limbo, and consume attention and credibility without ever being formally ended. A portfolio where nothing is ever stopped is a portfolio where everything is slowly starved.

McKinsey's 2026 State of AI survey put hard numbers behind this: only 37% of organizations report any EBIT impact from AI, flat year over year, even as adoption climbs — and the differentiator for the high performers wasn't more projects, it was defined processes for measuring impact and managing what they'd deployed. We covered that finding in detail in McKinsey 2026 AI Survey: Closing the AI ROI Gap With Pilot Governance.

The Fund-Stop-Scale Framework

Here is the structured alternative — a five-part discipline that replaces the popularity contest with an evidence-based decision.

1. Define the decision criteria before the project starts

The single most important move happens at the beginning, not the end. Before a pilot or project begins, define what evidence would justify each of the three outcomes: what result would earn further funding, what result would trigger a stop, and what threshold would indicate readiness to scale.

Criteria set in advance are objective. Criteria set at the decision point are unconsciously shaped to fit the project's actual results — which means the evaluation always confirms whatever the evidence happens to show. A pilot with a predefined success threshold of "reduces processing time by 30%" produces a clean decision. A pilot evaluated against criteria invented after the results are in produces a rationalization.

2. Use a common evaluation format across every project

Every project in the portfolio needs to be assessed in the same structure — the same criteria categories, the same scoring approach, the same output format — so that a manufacturing pilot and a customer-service pilot can sit side by side and be genuinely compared. This is what makes portfolio-level decision-making possible rather than a series of disconnected, incomparable judgments.

The format doesn't need to be complex. It needs to be consistent. Strategic alignment, evidence of impact, cost and resource requirements, risk profile, and readiness — assessed the same way for every project — produce a portfolio view where the strongest projects are visible regardless of who sponsors them.

3. Separate the evidence from the sponsor

At the decision point, lead with the evidence, not the narrative. A structured review looks at what the project actually produced against its predefined criteria before it hears the sponsor's case for continuation. This ordering matters: when the evidence is established first, the sponsor's advocacy is measured against it. When the narrative comes first, the evidence gets interpreted to fit the story.

This is also where institutional memory earns its value. When the portfolio review can see that a similar project was evaluated and stopped eighteen months ago — and why — the current decision is informed by the organization's actual history rather than starting from a blank slate every time.

4. Make the stop decision legitimate

The stop decision has to be culturally survivable, or it will never be made. In most organizations, a stopped project is a failure that reflects on its sponsor — so sponsors fight to keep projects alive long past the point of evidence, and the portfolio clogs.

The fix is to reframe the stop decision as a successful outcome of the process, not a failure of the project. A pilot that reaches a clear stop decision with documented evidence and rationale has done exactly what a pilot is supposed to do: produce a decision efficiently, before more resources were committed. The organizations that get this right celebrate the clean kill as much as the successful scale — because both are the process working. A stop decision that frees budget and attention for a stronger project is a win, and naming it as one is what makes the next stop decision possible.

5. Document every decision as institutional memory

Every fund, stop, or scale decision — with its evidence and rationale — becomes part of the organization's permanent record. This is what makes the portfolio compound rather than reset. The next time a similar project comes up for a decision, the prior decision is available: what was evaluated, what was decided, what happened next. Without this, every budget cycle re-litigates questions the organization already answered, and the same weak projects get re-funded because nobody remembers why they were stopped before. We covered why this matters in Why Innovation Programs Fail: The Structural Problems Nobody Talks About.

What This Looks Like in Practice

In most organizations, this framework lives in spreadsheets and slide decks — which is why it breaks down at exactly the moment it's needed. The criteria live in one team's document, the pilot results in another's, the portfolio view gets rebuilt by hand before each review, and the decision record scatters across email the moment the meeting ends.

A connected system changes that. Traction's Pilot Management tracks every pilot's predefined success criteria, owner, stage, and outcome — so the fund-stop-scale decision at the end of each pilot is made against the criteria set at the start, not reinvented in the room. Portfolio-level dashboards roll every active project into a single scorecard, stage funnel, and owner view — so a portfolio review compares every project on a common yardstick rather than sponsor by sponsor. And every decision is documented as part of the platform's institutional memory, so the portfolio gets smarter with each cycle instead of resetting.

The framework is what turns "too many projects, not enough budget" from an annual political fight into a repeatable, defensible discipline.

This is also the discipline enterprise innovation teams tell us they value most. Traction holds a 4.5-star rating across reviews on G2 and is reviewed by enterprise innovation leaders on Gartner Peer Insights — with customers consistently highlighting the ability to bring every innovation activity onto one platform to collate, review, and assess in one place.

👉 Try Traction AI free · See Pilot Management · View Pricing

Frequently Asked Questions

What is a fund-stop-scale decision in innovation management?

It is a portfolio governance decision made at a defined gate — such as the end of a pilot or a quarterly review — about whether an innovation project should receive further investment (fund), be discontinued (stop), or be expanded into broader deployment (scale). The decision is based on evidence measured against criteria that were defined before the project began, rather than on sponsor enthusiasm, sunk cost, or how recently the project was presented.

How do you decide whether to kill an innovation project?

Compare the project's actual results against the stop criteria that were defined before it started. If the evidence shows the project has not met — and is not on a credible path to meeting — its predefined success threshold, it should be stopped, regardless of how much has already been invested. The money already spent is a sunk cost and is irrelevant to the forward-looking decision. A clean stop decision that frees budget and attention for stronger projects is a successful outcome of the governance process, not a failure.

Why is the stop decision so hard to make?

Three reasons: sunk cost makes it psychologically difficult to abandon a project that has consumed significant time and budget; organizational politics mean a stopped project can reflect poorly on its sponsor, so sponsors fight to keep projects alive; and most organizations lack predefined stop criteria, so there is no objective trigger for the decision. The fix is to define stop criteria in advance and to reframe the stop decision as the governance process working correctly rather than as a project failure.

What criteria should you use to evaluate innovation projects?

A consistent set applied to every project: strategic alignment with current organizational priorities, evidence of impact against a predefined baseline, cost and resource requirements, risk profile, and readiness to scale. The specific criteria matter less than applying the same ones, in the same format, to every project — because that consistency is what makes portfolio-level comparison possible across projects run by different teams in different functions.

How does portfolio-level visibility improve innovation decisions?

It replaces sponsor-by-sponsor advocacy with a common yardstick. When every project is assessed in the same format and rolled into a single portfolio view — a scorecard, a stage funnel, an owner breakdown — the decision-maker can see which projects are strongest on the evidence, regardless of who sponsors them. Without portfolio visibility, funding decisions default to whoever presents most persuasively or most recently, which is how portfolios fill with weak projects that should have been stopped.

How does documenting decisions help future innovation planning?

Every documented fund-stop-scale decision becomes institutional memory the organization can draw on. When a similar project comes up in a later cycle, the prior decision — what was evaluated, what was decided, and what happened — is available to inform it. This prevents the organization from re-litigating questions it already answered and from re-funding weak projects because nobody remembers why they were stopped before. It is what allows an innovation portfolio to compound intelligence over time rather than resetting every budget cycle.

Related Reading

• McKinsey 2026 AI Survey: Closing the AI ROI Gap With Pilot Governance
• Why Pilot Management Software Is the Missing Link in Innovation Execution
• The 10 Biggest Challenges in Innovation Management in 2026 — and How to Actually Fix Them
• How to Evaluate Emerging Technologies: A Practical Guide
• Why Innovation Programs Fail: The Structural Problems Nobody Talks About
• What Is an Innovation Pipeline? A Practical Guide for Enterprise Teams
• What Is the Best Innovation Management Software for Enterprise Teams?

About the Author

Neal Silverman is the co-founder and CEO of Traction Technology. He spent 15 years as a senior executive at IDG — running multiple business units connecting enterprises with emerging technologies through conferences, councils, data services, and professional consulting practices. That firsthand experience watching how enterprises discover, evaluate, and lose track of emerging technology relationships is the origin story of Traction. He works with innovation teams at Armstrong, Bechtel, Ford, GSK, Kyndryl, Merck, and Suntory. Connect on LinkedIn

About Traction Technology

Traction Technology is an AI-powered innovation management software platform trusted by Fortune 500 innovation teams including Armstrong, Bechtel, Ford, GSK, Kyndryl, Merck, and Suntory. Built on Claude (Anthropic) and AWS Bedrock with a RAG architecture, Traction manages the full innovation lifecycle — from technology scouting and open innovation through idea management, RFI management, and pilot management — with AI-generated Trend Reports, AI Company Snapshots, duplication detection, and decision coaching built in.

Traction AI scouts across a database of over 1 million verified companies — retrieving real, current results rather than generating hallucinated names. One annual subscription at $4,000 gives you the full capabilities of an enterprise innovation team — every module, every AI capability, and unlimited View-Only access for every stakeholder at no additional cost. No setup fee. No data migration charges. Featured in the Gartner Market Guide for AI-Enabled Innovation Management Platforms, February 2026. SOC 2 Type II certified.

Try Traction AI Free · View Pricing · Schedule a Demo ·

‍