Quarterly Roadmap Planning: A Step-by-Step Process
6 min read ยท 2026-10-08
Quarterly roadmap planning is a recurring process where a product team reviews last quarter's results, sets measurable outcomes for the next quarter, gathers and prioritizes candidate initiatives, checks them against real capacity, and commits to a plan stakeholders understand. Done well, it takes a few weeks of preparation spread across the end of one quarter, not a frantic week of meetings.
This guide lays out the full process as a six-week roadmap, explains how to size capacity and prioritize, walks through a worked example, and covers how to run the planning session itself.
The roadmap at a glance
Goal: Run a structured quarterly planning process that produces a capacity-checked, outcome-driven product roadmap for the next quarter. Duration: 6 weeks before quarter start
Review Last Quarter (Week 1)
Learn from what happened before planning what comes next.
- Score each outcome from last quarter against its target metric.
- Compare planned initiatives to what actually shipped and note the reasons for gaps.
- Review unplanned work that consumed capacity, such as incidents and urgent requests.
- Run a short retrospective with the team on what helped and hurt delivery.
- Summarize the learnings in a one-page review document.
Milestone: A one-page quarter review with scored outcomes and delivery learnings is shared.
Set Quarterly Outcomes (Week 2)
Define the few measurable results the team will pursue next quarter.
- Revisit company goals or OKRs and the product strategy for context.
- Draft two or three product outcomes with a clear metric and target each.
- Check each outcome is within the team's influence within one quarter.
- Align outcomes with leadership before moving to initiatives.
Milestone: Leadership approves two or three measurable product outcomes for the quarter.
Gather Candidate Initiatives (Weeks 2-3)
Collect options that could move each outcome.
- Pull themes from customer feedback, support tickets and sales requests.
- Review product analytics for drop-off points and underused features.
- Collect technical needs and tech debt from engineering leads.
- Brainstorm initiatives per outcome with product, design and engineering.
- Write a short brief for each candidate: problem, expected impact and rough size.
Milestone: A list of candidate initiatives with short briefs is mapped to each outcome.
Size Capacity (Week 4)
Know exactly how much the team can take on.
- Calculate available person-weeks after holidays, time off and on-call duty.
- Subtract recurring support, maintenance and meetings based on last quarter's actuals.
- Reserve a buffer for unplanned work based on what last quarter consumed.
- Set a target split between outcome work, tech debt and discovery.
Milestone: A capacity sheet shows available person-weeks by team with buffer and allocation split.
Prioritize and Sequence (Week 5)
Choose the initiatives that best move outcomes within capacity.
- Score candidates with a simple model like RICE or impact versus effort.
- Fill capacity from the top of the ranked list, stopping at the limit.
- Map dependencies between initiatives and other teams.
- Sequence work so risky or blocking items start early in the quarter.
- Move remaining candidates to Next or Later with a reason recorded.
Milestone: A draft roadmap fits within capacity with sequencing and dependencies mapped.
Commit and Communicate (Week 6)
Lock the plan and make sure everyone understands it.
- Hold a planning session with leads to review and confirm the draft roadmap.
- Get explicit commitment from engineering on scope and from leadership on trade-offs.
- Publish the roadmap with outcomes, initiatives, owners and confidence levels.
- Brief sales, support and marketing on what changed and what was deferred.
- Schedule monthly check-ins to track progress during the quarter.
Milestone: The quarterly roadmap is published, committed by leads and briefed to go-to-market teams.
Start From Outcomes, Not Features
The single biggest improvement to quarterly planning is setting outcomes before choosing initiatives. An outcome is a measurable change, such as raising activation for new workspaces or reducing time to first report. When outcomes come first, initiatives compete on how well they move a shared goal rather than on who asked loudest.
Keep the number small. Two or three outcomes per team is enough to focus without leaving people idle. Each should have a metric, a baseline and a target, and the team should be able to influence it within the quarter. If your company uses OKRs, the product outcomes can map to key results directly.
How to Size Capacity Honestly
Most quarterly plans fail on capacity, not priorities. Start with the number of people on each team and the number of working weeks in the quarter, then subtract holidays, planned time off, on-call rotations and recurring meetings. Use last quarter's actuals to estimate how much went to support, bugs and urgent requests, and reserve that as a buffer.
What remains is your real capacity for planned work. Split it intentionally between outcome-driven initiatives, tech debt and discovery work for future quarters. Writing the split down prevents tech debt from being cut every time a new request arrives, and gives engineering a defensible share of the quarter.
- Gross capacity: people times working weeks.
- Minus: holidays, time off, on-call, meetings.
- Minus buffer: based on last quarter's unplanned work.
- Allocate: outcome work, tech debt and discovery.
Worked Example: Planning a Quarter
A product team of five engineers, one designer and one PM reviews last quarter: activation rose but missed its target, and two of six initiatives slipped because of an infrastructure migration. For next quarter, they set two outcomes: improve week-one activation and reduce support tickets about billing.
Candidates include a guided setup checklist, sample data for new workspaces, a self-serve invoice page, a billing FAQ redesign and a reporting export. Capacity math leaves about two thirds of the quarter for planned work after buffer and debt. RICE scoring ranks the checklist, invoice page and sample data highest; together they fit. The export moves to Next with a note. The final roadmap has three committed initiatives, one stretch item and a clear explanation of what was deferred.
Running the Planning Session
The planning session should confirm decisions, not create them from scratch. Send the quarter review, outcomes, capacity sheet and draft roadmap in advance so participants arrive with questions. In the session, walk through each outcome, the initiatives supporting it, and the items deliberately left out.
Focus discussion on risks and dependencies: what could block delivery, which other teams are involved, and where confidence is low. End with explicit commitments from engineering, design and product leads, and a list of open questions with owners. A two-hour session is usually enough when preparation is done well.
- Pre-read sent at least a few days before.
- Walk through outcomes, initiatives and exclusions.
- Discuss risks, dependencies and confidence.
- Close with commitments and owners for open questions.
Common mistakes to avoid
- Planning the next quarter without reviewing the last repeats the same errors, so score outcomes and delivery first.
- Picking initiatives before setting outcomes invites feature lobbying, so agree on measurable outcomes first.
- Planning to full capacity guarantees slips, so reserve a buffer based on last quarter's unplanned work.
- Cramming all planning into one long meeting produces rushed decisions, so spread preparation over several weeks.
- Leaving deferred items unexplained frustrates requesters, so communicate what moved to Next and why.
- Treating the plan as fixed for the whole quarter ignores new evidence, so hold monthly check-ins to adjust.
Frequently asked questions
How long should quarterly roadmap planning take?
Preparation typically spans several weeks at the end of the current quarter, with a few hours of focused work each week: reviewing results, setting outcomes, gathering candidates, sizing capacity and prioritizing. The actual planning session can be around two hours if preparation is solid. Starting about six weeks before the new quarter avoids a last-minute scramble.
Who should be involved in quarterly planning?
The core group is the product manager, engineering lead and design lead for each team, with leadership approving outcomes and trade-offs. Sales, support and customer success should contribute input during the gathering phase and be briefed afterward. Including the whole team in the retrospective improves the quality of capacity estimates and risk spotting.
How many initiatives should be planned per quarter?
Plan only what fits within measured capacity after buffer and tech debt allocation. For one product team, that often means a small number of meaningful initiatives rather than a long list of small features. If an initiative cannot be clearly linked to one of the quarter's outcomes, it probably should not be on the plan.
What is the difference between quarterly planning and sprint planning?
Quarterly planning sets outcomes, chooses initiatives and allocates capacity for roughly three months. Sprint planning breaks the current initiatives into tasks the team can complete in one or two weeks. Quarterly planning decides what and why; sprint planning decides how and in what order for the immediate term.
How do OKRs fit into quarterly roadmap planning?
OKRs provide the objectives and key results the roadmap should serve. Product outcomes can map directly to key results, and each roadmap initiative should show which key result it targets. This keeps the roadmap tied to company goals and makes the end-of-quarter review straightforward, since outcomes are already defined and measurable.