How do you choose which product investments still deserve funding when assumptions change? The short answer is to set the project status aside for a moment and go back to the reason the investment was approved.
A product initiative can be on schedule, within budget, and executing well while the original investment case underneath it gets weaker.
In this situation, the most useful question is a simple one:
If leadership were approving the next stage today, knowing what it knows now, would the investment still make sense?
We call this investment revalidation.
Most manufacturers already review their funded programs regularly. What they often lack is a way to see when the logic behind an approval has changed, even though the program itself looks healthy.
In this guide, we will show you how to decide which product investments still deserve funding without reopening every decision on the calendar.
Product investments are rarely made against permanent assumptions.
For instance, Flowserve makes this risk explicit in its 2025 annual reporting, noting that product transitions can be unpredictable, product lifecycles can shorten, and investments in new products may not ultimately produce the expected return. The company also describes ongoing product rationalization as part of its portfolio strategy.
None of this means manufacturers should constantly reopen approved work. However, it shows that approval shouldn't freeze the assumptions behind the decision.
Suppose a manufacturer funds a new common controls platform. The case looks strong for four reasons:
Leadership approves the investment. A year later, the program itself looks healthy, but the portfolio around it has changed.
The technical team may be delivering exactly what it committed to. Even so, leadership is no longer evaluating the same investment it originally approved.
This is one way product portfolio planning can break down in manufacturing. Individual programs can look healthy while the assumptions connecting them to the broader portfolio keep moving, especially when a shared platform or module sits underneath several product plans.
If you are looking to revalidate a product investment in your portfolio, follow these steps.
Before deciding whether to continue funding, write down what originally had to be true. For the controls platform, the investment thesis might include five assumptions:
Now compare those statements with what you know today.
Not every assumption has to remain perfectly intact. The real issue is whether enough of them have weakened that the investment is materially different from the one leadership intended to fund.
The lifecycle assumption deserves particular attention, because lifecycle planning in product portfolio management is often where a platform case quietly changes shape.
Pro-Tip: For the broader planning discipline behind these relationships, see What Is Product Portfolio Planning? The Ultimate Guide.
A schedule change doesn't automatically weaken an investment.
Suppose the platform is three months late, but all three future products still intend to adopt it and their timelines can absorb the delay. The original investment thesis may still be sound.
Now reverse the situation.
The platform is perfectly on schedule, but two of the three expected product families no longer intend to use it. The project status looks better while the investment thesis looks worse, and this is exactly the distinction revalidation is meant to surface.
When more than one response is still on the table, scenario planning helps leadership compare the paths before anyone changes the commitment.
You don't need another elaborate scoring model. For each important assumption, ask whether it is:
|
State |
Meaning |
|
Still true |
Current evidence continues to support it |
|
Weaker |
It may still hold, but confidence or expected value has declined |
|
No longer true |
Current evidence contradicts something the investment depended on |
|
Still unknown |
The team does not yet have enough evidence to decide |
Applied to the controls platform, the picture looks like this:
|
Original assumption |
Current state |
|
Three product families will reuse the platform |
Weaker |
|
Platform will be ready before major architecture decisions |
Still true |
|
Existing controller technology needs replacement |
Still true |
|
Common architecture will simplify the future portfolio |
Weaker |
|
Expected reuse justifies the investment |
Needs review |
This produces a far more useful leadership conversation than reporting that the project is green.
A manufacturer may have already invested millions of dollars and years of work, and that history carries real weight. Changing direction can create unfinished transitions, contractual obligations, stranded work, or additional costs.
Prior spending still doesn't prove the next commitment deserves funding. Research on why bad projects are so hard to kill shows how easily sunk effort turns into momentum, so ask one direct question instead:
Would we fund the next stage if this initiative came to us today with its current evidence?
The answer doesn't have to be continued or canceled. Leadership might:
The purpose of revalidation isn't to find reasons to stop work. Its job is to restore confidence that continued investment still makes sense. A clear product portfolio governance model makes these options easier to use without turning every review into a fight over the budget.
Revalidation becomes much easier when the rationale doesn't disappear after the funding meeting. Keep the investment connected to six types of context:
Then, when something changes, leadership doesn't have to reconstruct the original decision from an old business case and months of status decks. Platform bets in particular benefit from this, since products built as platforms only pay off when downstream programs actually adopt them.
This is part of continuous product portfolio planning. The goal isn't to reopen every decision constantly. It's to keep enough context current to recognize when the reason behind an old decision has materially changed, before portfolio drift adds up to a different investment.
Gocious is a strategic product portfolio management platform that supports this planning context.
Our software connects strategic product investments with the products, platforms, roadmaps, lifecycle assumptions, dependencies, and business context behind them. Leadership still makes the call, with the CPO and portfolio leaders working from the same connected picture.
Want to see how our platform keeps the reasoning behind each funding decision in view? Explore Gocious Product Portfolio Planning or book a custom demo to walk through your own portfolio.