A cycle in which problems that teams surface during solution discovery (see Discovery (Product Discovery Process)) are routed back to the product leader rather than acted on unilaterally, and become inputs — alongside executive/business input — to the next quarter's or year's Product Strategy. Teams doing discovery work are often the first to see a problem worth solving, but the loop keeps strategy-setting centralized: newly discovered problems are reported upward and folded into the next strategy cycle rather than triggering an on-the-spot pivot in scope.
This loop is what lets an org do independent problem discovery (see Earning the Right to Define Problems) without fragmenting the org's overall bets — new problems change next cycle's strategy, not this cycle's execution.
Strategy should be revisited at minimum quarterly, using the prior quarter's bet outcomes to inform the next quarter's problem selection — in practice it's closer to continuous. "I believe that a product strategy is a living thing. At a minimum, it should be updated quarterly. In reality, I think it's living. It's just constantly updating as you learn." This is what distinguishes strategy from Product Vision: "Visions don't change, but strategies change a lot."
Time horizons for vision and strategy should scale to the maturity of the business — long for an established company, only as long as the runway allows for a startup. Whatever the horizon, the strategy needs to be reviewed at least quarterly, not set once and treated as fixed; a strategy that isn't revisited on a cadence degrades into exactly the kind of stale, unexamined artifact this feedback loop is meant to prevent. See The Decision Stack (Eriksson).
Eriksson frames quarterly as the new floor for strategy review, replacing the older habit of setting vision at a 3–5 year horizon and strategy at 1–3 years, then leaving both untouched until the next planning cycle. Re-test strategic assumptions and direction at least every quarter, reacting sooner when a major shift (his example: AI) demands it.
In Transformed, Cagan frames real product strategy as an ongoing practice on a roughly quarterly cadence, continuously updated as new discovery insight comes in — not a single annual plan. It replaces ad hoc, stakeholder-driven resource allocation (where whoever complains loudest gets staffed) with strategy that is revisited and adjusted as the team learns.