Eleven products come to the quarterly portfolio review, and each is asked the same thing: is it on track? A product six months old, still testing whether early adopters want it, answers with the same kind of evidence as a platform that has run for eight years. Every answer is accurate, and none of them supports a reallocation decision, because the question never changes to match the investment problem each product presents.
In Brief
- Ask each product the question its lifecycle stage makes decisive, rather than a common status question.
- At Introduction, write down what evidence would stop the funding before the funding is approved. At Decline, the product carries the burden of proving it should continue.
- The evidence that decides the question changes with the stage, from Current Value at Introduction to the Cost of Delay of competing work at Decline.
- Persevere and Pivot sit with the Product Manager, Pause and Pull with the portfolio, and a change of lifecycle stage goes to the Board.
Each lifecycle stage carries its own investment problem and its own governance posture (Hodgson, 2026, Chapter 6). The quarterly review applies an investment hypothesis, a diagnostic for absent evidence and four postures to every product (Hodgson, 2026, Chapter 10). Read together, the two give the Product Portfolio Executive a stage-specific question for each product, the evidence that answers it, and a settled answer to who decides when that evidence does not arrive.
One question cannot govern four stages
Table 3 of Evolve names a distinct investment problem for each stage: an unconfirmed value hypothesis at Introduction, a validated hypothesis with growing adoption at Growth, stable value generation at Maturity, and returns below opportunity cost at Decline (Hodgson, 2026, Chapter 6). Each problem carries its own primary risk, from premature commitment to unvalidated scope through to slow drift sustained by approval asymmetry. A review question written for one of those risks is blind to the other three.
Evidence-Based Management supplies the evidence through four Key Value Areas (KVAs): Current Value, Unrealised Value, Time to Market, and Ability to Innovate (Scrum.org, 2024). All four are collected for every product, but the evidence that decides the question changes as the product ages. At Decline, the deciding comparison sits outside the product altogether, in the Cost of Delay of the work competing for its capacity.
| Stage | The review asks | Leading evidence | Investment posture (Table 3) |
|---|---|---|---|
| Introduction | What evidence would stop the funding? | Current Value in the early adopter cohort; Time to Market inside the review cycle | Structured test with go/no-go criteria |
| Growth | Is investment keeping pace with demonstrated demand? | Current Value as adoption widens; Ability to Innovate | Scaled commitment, rolling investment |
| Maturity | What value remains unrealised? | Unrealised Value against the Product Goal | Optimisation-focused investment |
| Decline | What evidence would justify continuing? | Cost of Delay of the work the capacity would otherwise fund | Explicit funding withdrawal decision |
Note. The question and evidence columns are ZXM’s synthesis; the posture column is Table 3 of Evolve (Hodgson, 2026, Chapter 6).
Introduction: what would stop the funding?
A product at Introduction has not yet shown that early adopters find it meets their needs. The funding buys a test, and the test needs go/no-go criteria before money moves (Hodgson, 2026, Chapter 6). The review question follows: what evidence would cause the portfolio to stop? Without a stopping condition written in advance, stopping becomes a fresh political decision taken at the worst possible moment (Hodgson, 2026, Chapter 10).
The investment hypothesis answers the question in advance. Its four sentences state the rationale, the evidence expected within the first review cycle, the threshold that justifies continued funding, and the decision rule when the evidence does not arrive (Hodgson, 2026, Chapter 10). For an onboarding product where 22% of customers abandon before completion because approval takes 11 days, the evidence sentence commits to median approval below 8 days and abandonment below 18% for the early adopter cohort within two Sprints. The stopping condition exists before the review, when nobody has a stake in reinterpreting it.
Current Value in that cohort is the leading evidence, and Time to Market decides whether it arrives in time to matter. If the first working version reaches actual users in six weeks, the review has months of evidence to act on; if it reaches them in fourteen months, the portfolio is governing in the dark (Hodgson, 2026, Chapter 10).
When the evidence stalls, the review diagnoses before it decides. The measures may be wrong, the Product Goal may be wrong, both may be wrong, or the indicators chosen may lag the review window (Hodgson, 2026, Chapter 10). Wrong measures are revised immediately. A wrong Product Goal is revised by the Product Manager against the strategy it is meant to serve. When both are wrong, the investment hypothesis itself is in question and the decision moves to the portfolio. Only lagging indicators justify Pause, and a Pause carries a timebox.
Growth: is investment keeping pace?
At Growth, the product has validated its hypothesis and opened to its wider customer base, and the primary risk reverses: systematic under-investment while alternatives establish their positions (Hodgson, 2026, Chapter 6). The review question is whether investment is keeping pace with the demand the product has already demonstrated. A portfolio still applying the caution appropriate to Introduction rations capacity to a product that has earned more of it.
Current Value remains the test, read across a larger population. The onboarding product’s early adopters were a self-selected cohort. At Growth, the question is whether approval time and abandonment keep trending toward the Product Goal targets of 4 days and 12% as the whole customer base moves onto the new process. Results that hold only for early adopters describe a product promoted out of Introduction too soon.
Ability to Innovate decides how far the commitment can scale. If existing obligations consume most of the team’s capacity, the portfolio is approving work the team cannot absorb, and an AI-augmented team pushed past that point produces volume faster than anyone can diagnose its quality (Hodgson, 2026, Chapter 10). Guardrails are the executive’s instrument for rolling investment: they set the share of allocated capacity a product line may direct to development, technical health and exploration without escalation, so a scaled commitment operates between reviews without every increase returning to the executive’s desk (Hodgson, 2026, Chapter 7).
Maturity: what remains to realise?
A mature product generates stable value, and its primary risk is chronic over-investment beyond its growth ceiling: more features for a solution customers are largely satisfied with (Hodgson, 2026, Chapter 6). The review question moves from Current Value to Unrealised Value, the share of the Product Goal’s target not yet achieved (Hodgson, 2026, Chapter 10).
When the onboarding product’s approval time holds at 4 days and abandonment at 12%, the Product Goal has been met, and further development spending cannot improve on the outcome it was funded to produce. That is a legitimate reason to Pull: the investment ends because the outcome has been achieved and the product has reached maturity (Hodgson, 2026, Chapter 10). The development investment stops, the product keeps running on the optimisation its posture calls for, and the released capacity moves to the highest Cost of Delay elsewhere in the portfolio.
Withdrawing funding is the executive decision most consistently deferred (Hodgson, 2026, Chapter 7), and a mature product that works gives nobody a reason to raise it. Asking for Unrealised Value on every mature product, every quarter, raises it. If the Product Manager proposes a new Product Goal for the same product instead, that proposal is a new investment hypothesis and is tested with the same four sentences as any new investment.
Decline: what would justify continuing?
A product in Decline returns less than the opportunity cost of the capacity it holds. Stage gate governance lets these products drift because the threshold for stopping sits higher than the threshold for continuing, and the product model requires the opposite (Hodgson, 2026, Chapter 6). The review question enacts that reversal by asking what evidence would justify continuing, which places the burden of proof on the product rather than on the executive who wants to stop funding it.
Cost of Delay supplies the comparison. Cost of Delay divided by Duration (CD3) ranks competing uses of the same capacity by the value forgone per unit of time, using only forward-looking inputs, so money already spent on the declining product never enters the calculation (Hodgson, 2026, Appendix C; Reinertsen, 2009). A declining product that argues from its history loses to the work its capacity would otherwise fund. The three questions the quarterly review puts beside every product apply with most force here: whether it still contributes to something the organisation cares about, whether its window is still open, and whether it enables future options or blocks them (Hodgson, 2026, Chapter 7).
Withdrawal is also a delivery obligation. Retiring a product in Decline requires the Product Manager to migrate its customers and, where a successor product exists, help them move to it (Hodgson, 2026, Chapter 6). A funding decision without a migration plan moves the product’s customers from a declining service to an unsupported one.
Who decides when evidence stalls
The investment hypothesis divides the decisions before any evidence arrives. Persevere and Pivot sit with the Product Manager, because they continue or revise the plan inside a hypothesis the portfolio has already approved. Pause and Pull change the hypothesis itself, so the Product Manager triggers them and the Product Portfolio Executive decides them at the quarterly review (Hodgson, 2026, Chapter 10). The Portfolio Product Manager assembles each product’s KVA evidence, lifecycle position and Cost of Delay into the review package, and makes none of the investment decisions (Hodgson, 2026, Chapter 7).
Moving a product from one stage to the next is a decision in its own right. A product crossing a lifecycle stage boundary is one of four conditions that bring technology portfolio governance to the Board, because the strategic case needs reconfirming (Hodgson, 2026, Chapter 7). A portfolio that holds a mature product at Growth, or a declining product at Maturity, keeps asking the wrong question and never triggers the Board conversation the change of stage requires.
What this means for senior leaders: Establish each product’s lifecycle stage before reading any of its evidence, because the stage decides which question that evidence has to answer. Asking every product whether it is on track returns an accurate status report and no basis for moving a dollar.
References
- Hodgson, M. (2026). Evolve: The operating model AI demands. Zen Ex Machina.
- Reinertsen, D. G. (2009). The principles of product development flow: Second generation lean product development. Celeritas Publishing.
- Scrum.org. (2024). The evidence-based management guide: Improving value delivery under conditions of uncertainty. Scrum.org. https://www.scrum.org/resources/evidence-based-management-guide
