Quarterly planning is a 90-day cadence many product organisations use to set priorities, align teams and commit to a small number of outcomes. The quarter is long enough that meaningful work can be shipped within it, but short enough that the plan can adapt to what teams learn before it goes stale.
A quarterly plan typically answers four questions:
- What are we trying to achieve? Usually expressed as outcomes or OKRs, not feature lists.
- Why now, and why these and not others? The trade-offs and what is being deferred.
- Who is doing what? Which teams own which outcomes, and where the dependencies sit.
- How will we know if it is working? The signals teams will watch during the quarter, not just at the end.
The shape of a quarterly cycle
A common rhythm:
- Pre-planning (week before the quarter): Leaders share strategic context. Teams pre-read, draft proposals, surface dependencies.
- Planning week (start of the quarter): Teams converge, negotiate trade-offs, lock the small set of objectives they will commit to.
- Mid-quarter check-in (around week six): Honest assessment of progress. Re-plan if reality has shifted enough to warrant it — don’t wait for the end.
- Quarterly review (last week): Outcomes assessed, learnings captured, signals carried into the next quarter.
Why a quarter
Shorter cycles (monthly) tend to fragment strategic work and reward whatever is closest at hand. Longer cycles (annual) lock teams into plans built on assumptions that are stale by month four. Quarterly planning sits at the boundary where intent and reality stay close enough for the plan to mean something.
Common pitfalls
- Treating the quarter as a delivery commitment instead of a directional one. The plan is a current best understanding, not a contract.
- Loading the quarter to capacity. A plan with no slack can absorb no surprises, and surprises always come.
- Skipping the mid-quarter check-in. Most quarterly plans need adjusting at week six; pretending otherwise just delays the conversation.
- Confusing OKRs with backlogs. OKRs describe outcomes; the backlog describes work. They are not the same.
Further reading
