Quarterly Strategy Review Template

Ninety minutes to two hours. Under 90 minutes means you are skipping the prospective sections (decisions, next quarter goals). Over two hours means you are diving too deep into operational details that belong in team-level reviews. The facilitated agenda in this template targets 90 minutes. The [Product Strategy Handbook](/strategy-guide) covers how to structure the review cadence.

The product leadership team: VP/Head of Product, senior PMs, plus cross-functional leaders who influence strategy (Head of Engineering, Head of Design, Head of Growth/Marketing). Keep it to 6-10 people. Larger groups produce discussion, not decisions. Distribute the review document to the broader team afterward.

Use the metrics dashboard as the starting point and work backward. Ask: "Given these numbers, are we happy with the trajectory?" Set goals for next quarter even if you did not have them for this one. The review itself creates the discipline for future quarters.

Yes. The strategy review evaluates direction: "Are we pursuing the right things?" The roadmap review evaluates execution: "Are we shipping what we planned?" Combining them creates a 3-4 hour meeting that loses focus. Hold the strategy review first, then use its decisions to inform the roadmap review. The [OKR framework](/frameworks) bridges strategy and execution through measurable key results.

Frame disagreements as hypotheses to test, not opinions to debate. If two leaders disagree on whether to invest in AI or international expansion, define a test for each hypothesis that can be resolved with data within 30-60 days. Assign owners and deadlines. Review the data at the next check-in. Strategy reviews should produce decisions, but decisions under uncertainty should be reversible and testable. ---