A product’s move from one lifecycle stage to the next is an investment decision, and an executive who does not take it keeps funding the product for the stage it has left. Figure 7 of Matthew Hodgson’s Evolve: The Operating Model AI Demands, the book’s product lifecycle curve, carries the subtitle “Stage transition is a governance decision, not a milestone-driven event” (Hodgson, 2026, Chapter 6). The sections below set out the evidence that signals each lifecycle stage transition, what changes in the product’s funding when it happens, and who makes the call at the quarterly portfolio review.
In Brief
- A product moves to its next lifecycle stage by a decision taken on evidence at the quarterly portfolio review, not by reaching a date in a plan.
- Each move changes the investment posture, the primary risk to manage and the evidence the product reports.
- The Product Manager brings the transition evidence, the Product Portfolio Executive decides, and the Board reconfirms the strategic case.
- Decline is the transition most often deferred: under stage gate governance, stopping a product needs a higher approval threshold than continuing it.
What changes at a stage boundary
Table 3 of Evolve gives each lifecycle stage a different primary risk: premature commitment to unvalidated scope at Introduction, systematic under-investment at Growth, chronic over-investment beyond the growth ceiling at Maturity, and slow drift at Decline (Hodgson, 2026, Chapter 6). An executive who misses a crossing keeps guarding against the old risk and leaves the new one unmanaged.
At each crossing the investment posture changes to the one Table 3 sets for the new stage, the product starts reporting against a different measure, and the Board reconfirms the strategic case. The measures are the four Key Value Areas (KVAs) of Evidence-Based Management (EBM), and Chapter 15 assigns them by stage: Time to Market and Ability to Innovate at Introduction, the Current Value threshold in the investment hypothesis at Growth, Unrealised Value at Maturity, and the cost of migrating customers at Decline (Hodgson, 2026, Chapter 15; Scrum.org, 2024). The investment hypothesis is the four-sentence investment case Evolve asks for before money is approved: why the product is funded, what evidence is due in the first review cycle, what threshold keeps the funding, and what happens when the evidence does not arrive (Hodgson, 2026, Chapter 10). The Board (in a government agency, its equivalent governing body) is involved because a product crossing a lifecycle stage boundary is one of the four conditions that bring technology portfolio governance to the Board (Hodgson, 2026, Chapter 7).
| Transition | Evidence that signals it | What changes | Primary risk after the crossing |
|---|---|---|---|
| Introduction to Growth | Threshold in the investment hypothesis met; results hold beyond the early adopter cohort | Structured test becomes scaled commitment with rolling investment; reporting moves to the Current Value threshold | Systematic under-investment while alternatives establish their positions |
| Growth to Maturity | Adoption flat across two or more quarterly reviews; Unrealised Value approaching zero | Optimisation-focused investment; reporting moves to Unrealised Value | Chronic over-investment beyond the product’s growth ceiling |
| Maturity to Decline | Returns below the opportunity cost of the capacity the product holds; users migrating to a successor | Explicit decision to withdraw funding; reporting moves to the cost of migrating customers | Slow drift, sustained because stopping needs a higher approval threshold than continuing |
Note. In every row the Product Manager triggers the change, the Product Portfolio Executive decides it at the quarterly review, and the Board reconfirms the strategic case. The evidence column is ZXM practice; the other columns follow Evolve (Hodgson, 2026, Chapters 6, 7 and 15).
Evolve applies the same four stages to the operating model itself (Hodgson, 2026, Chapter 6). In one Australian federal government agency, the product operating model ran in the Introduction Stage for two years, cutting decision latency from several months to one day, and moved into Growth in year three. When the coaching investment was withdrawn, the agency reverted to project-based investment and milestone reporting within six months, because nothing was checking whether the conditions that made the model work were still in place (Hodgson, 2026, Chapter 13).
The question to ask a product within each lifecycle stage has its own companion page; the sections below cover the move between stages.
Introduction to Growth: the hypothesis holds
An Introduction Stage product is ready for Growth when the team has data showing that early adopter customers find the solution meets their needs (Hodgson, 2026, Chapter 6). The investment hypothesis supplies the measures: its evidence sentence states what must be measurable within the first review cycle, and its threshold sentence states what justifies continued funding (Hodgson, 2026, Chapter 10).
In ZXM’s practice, the Product Manager brings the move to the quarterly review once the threshold has been met and three signals are all present: results that hold beyond the early adopter cohort, working increments released to users at a steady cadence over at least three Sprints, and a cost of serving each user that can be measured even if it is not yet optimised.
After the crossing the posture is scaled commitment with rolling investment, and the primary risk is systematic under-investment while alternatives establish their positions (Hodgson, 2026, Chapter 6). The Product Manager stops reporting mainly against Time to Market and Ability to Innovate and starts reporting spend against the Current Value threshold in the investment hypothesis (Hodgson, 2026, Chapter 15). An executive who keeps funding the product in Introduction-stage tranches after this point slows it while alternatives compete for the same users.
A citizen-facing service built to replace a paper application process is funded for a six-month structured test, with go/no-go criteria written into its investment hypothesis. At the quarterly review the Product Manager reports 800 pilot users with a 92% task completion rate, fortnightly releases sustained for three months, and a cost per application 40% below the paper process. The Product Portfolio Executive, who allocates investment across the portfolio, moves the product to Growth and sets the rolling investment and the Current Value threshold it will report against, and the strategic case goes to the Board for reconfirmation.
Growth to Maturity: demand stops rising
A Growth Stage product is entering Maturity when adoption stops rising and each additional unit of investment buys less improvement than the last. In ZXM’s practice the signals are growth in active users or transactions that has been flat across two or more consecutive quarterly reviews, a cost of bringing each additional user onto the product that has risen over three or more reporting periods, and Unrealised Value against the Product Goal approaching zero. The three signals tend to arrive together because they come from the same change in demand, and an executive who waits for all three to be unambiguous starts Maturity governance late.
After the crossing the posture is optimisation-focused investment, and the primary risk is chronic over-investment beyond the product’s growth ceiling: more features for a solution customers are largely satisfied with (Hodgson, 2026, Chapter 6). The Product Manager reports whether Unrealised Value, the distance between Current Value and the Product Goal’s target, still justifies development investment or whether the portfolio should redirect the funding (Hodgson, 2026, Chapters 10 and 15). When the Product Goal has been met, Pull is the right posture for the development investment: of the four postures Evolve‘s quarterly review applies (Persevere, Pivot, Pause and Pull), Pull ends an investment because its outcome has been achieved and the product has reached maturity (Hodgson, 2026, Chapter 10). The product keeps running on optimisation-focused investment, and the portfolio reallocates the development capacity it releases.
In ZXM’s practice the technical measures change at the same boundary, from speed and scale (throughput, time to deploy, infrastructure elasticity) to durability: time between failures, the share of critical dependencies on supported versions, and security posture. An executive reading Growth measures for a Maturity product receives answers to a question that no longer needs asking.
An internal developer platform reaches 30 teams and then stops growing: for three quarters the number of teams onboarding has been flat, the support cost per team has stopped falling, and the platform’s Product Goal of self-service provisioning for every team has been met. The Product Manager triggers Pull on further development investment, the Product Portfolio Executive decides it at the quarterly review, the platform team’s remaining capacity goes to reliability and dependency currency, and the strategic case for the platform goes to the Board.
Maturity to Decline: alternatives return more
A Maturity Stage product is entering Decline when its returns fall below the opportunity cost of the capacity it holds (Hodgson, 2026, Chapter 6). The economic test is what the next dollar invested in the product returns compared with the best available alternative. Cost of Delay divided by Duration (CD3), which ranks competing uses of the same capacity by the value lost for each period the work waits, uses forward-looking inputs only, so money already spent on the product never enters the calculation (Hodgson, 2026, Chapter 7 and Appendix C; Reinertsen, 2009).
In ZXM’s practice, four observations signal the crossing: a viable successor or alternative exists and users are measurably migrating to it; maintenance cost per active user is rising as the user base shrinks; a critical upstream vendor has published an end-of-support date within 18 months, or the skills to maintain the technology are getting harder to find; and each enhancement now costs more than the value it returns. When three of these current-state observations are present, the transition plan should already be under way.
Evolve explains why the Decline crossing is deferred: stage gate governance sets the approval threshold for stopping higher than the threshold for continuing, which produces slow drift, and the product model requires the opposite (Hodgson, 2026, Chapter 6). Chapter 7 calls withdrawing funding the hardest of the executive’s three portfolio decisions and the most consistently deferred, and the decision where the evidence and the institutional instinct reliably point in opposite directions (Hodgson, 2026, Chapter 7). At Decline the Product Manager reports the cost of migrating customers to whatever replaces the product, and is accountable for migrating them and, where a successor exists, helping them move (Hodgson, 2026, Chapters 6 and 15).
ZXM’s practice is to fund the declining product from a run-off envelope limited to security patches and break-fix support, with an end date set before migration begins, and to fund the migration separately. Where the asset is legacy core infrastructure whose replacement risk exceeds what one Sprint cycle can absorb, Evolve treats the migration as a parallel strand of investment governed as a product in its own right (Hodgson, 2026, Chapter 6). When both come from one budget line, maintenance and migration compete for the same money, and an executive who extends the end date each time migration slips removes the urgency the end date was set to create.
A legacy customer relationship management system is being replaced over 12 months. The Product Portfolio Executive funds the legacy system for security patches and break-fix support only, funds the migration as its own product, and ends the run-off envelope at month 12. If the migration cannot finish in 12 months, the Product Manager revises the migration plan and the portfolio funds the revision; the legacy end date stays.
Who decides a stage change
The Product Manager triggers a stage change and the Product Portfolio Executive decides it at the quarterly portfolio review. The investment hypothesis already settles this split: the Product Manager holds the decisions inside the hypothesis, and the portfolio holds the decisions that change the hypothesis itself (Hodgson, 2026, Chapter 10). Moving a product to a new stage rewrites its posture and threshold, so the decision sits with the portfolio.
The Portfolio Product Manager assembles each product’s EBM measures, lifecycle position, current investment and Cost of Delay into the quarterly review package, and makes none of the investment decisions. Evolve places the authority to reallocate, reduce or divest with the executive, and the Board sets the envelope within which the Product Portfolio Executive decides; at a crossing, the Board’s role is to reconfirm the strategic case (Hodgson, 2026, Chapter 7).
Five changes to the quarterly review
- Record a lifecycle stage for every product in the quarterly review package, and confirm or change it at every review.
- Write the signals for the next transition into each investment hypothesis when it is approved, so the crossing is triggered by evidence the portfolio agreed in advance.
- Change the posture, the reporting Key Value Area and the guardrail shares together when a product changes stage; Evolve sets guardrail proportions partly by the portfolio’s lifecycle distribution (Hodgson, 2026, Chapter 7).
- Take every crossing to the Board to reconfirm the strategic case.
- Set the Decline end date and the migration funding before migration begins, and fund a slipping migration with a revised plan while the declining product’s end date stays in place.
In ZXM’s experience, a portfolio in which most products are classified as Growth has either not reclassified them recently or has no mechanism to do so.
What this means for senior leaders: Ask, at each quarterly review, which products have crossed a stage boundary since the last one and what changed in their funding as a result. When the review names none, quarter after quarter, the portfolio is renewing last year’s funding logic for every product.
Zen Ex Machina works with portfolio executives to set up lifecycle classification, investment hypotheses and the quarterly review that acts on them. Request a conversation to test how your portfolio review handles stage changes.
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
