Quarterly Roadmap Review Meeting Template

Plan for 90 minutes. If the look-back data is prepared in advance and shared beforehand (which it should be), you can sometimes finish in 60 minutes. Never try to compress it below 45 minutes. The Phase 2 (impact) and Phase 3 (look forward) discussions are where the most valuable conversations happen, and they need space. Use a [Now-Next-Later roadmap format](/roadmap-type/now-next-later-roadmap) if you want a lighter-weight ongoing review cadence between quarterly reviews.

Product leadership, engineering leads, design leads, and 2-3 key stakeholders (typically from Sales, CS, or the executive team). Keep it under 10 people. Larger groups turn the review into a presentation rather than a working session. If you need broader input, gather it asynchronously before the meeting and present a synthesized view. Use the [RICE Calculator](/tools/rice-calculator) to pre-score priorities so the meeting focuses on trade-offs rather than scoring debates.

That is a planning problem, not a performance problem. Use the review to diagnose why. Common causes: unplanned work consumed capacity (too much interrupt-driven work), scope was underestimated (estimation needs calibration), or dependencies were not managed (cross-team coordination gaps). Adjust next quarter's plan by reducing the number of commitments to match actual throughput, not aspirational throughput.

Yes. Monthly check-ins (15-30 minutes) help catch drift early. But the quarterly review is the formal reassessment where you step back, evaluate impact, and potentially change direction. Monthly check-ins are about course corrections within the quarter. Quarterly reviews are about deciding the next quarter's course. The [cross-team sync template](/templates/cross-team-sync-template) works well for the monthly check-in cadence.

Document the request, its expected impact, and its cost (what gets delayed). Present the trade-off transparently: "We can add SSO to Q2, but analytics dashboard moves to Q3. Here is the impact of each option." Let the decision-maker decide with full context. Never quietly absorb scope without surfacing the trade-off. The [stakeholder management guide](/stakeholder-guide) covers techniques for these conversations. ---