The Quarterly Planning Trap
Quarterly planning feels productive. It's often a ritual that creates false certainty and real organizational drag. Here's how to make it actually useful.
Every quarter, companies go through a ritual that everyone finds painful and nobody thinks is working. Call it QBR prep, OKR planning, or just "Q3 planning" — the form varies but the dysfunction is consistent.
Here's why quarterly planning so often fails, and what to do instead.
The core problem
Quarterly planning fails when it's designed to produce a document rather than alignment.
The artifact of planning — the OKR deck, the roadmap, the financial model — becomes the goal. Teams spend weeks perfecting slides that will be half-forgotten by week three of the quarter. The planning process optimizes for "looking aligned" rather than "being aligned."
Real alignment means:
- Everyone understands why we're prioritizing what we're prioritizing
- Everyone knows what we're not doing, and why
- Teams have enough context to make good local decisions without escalating everything
A slide deck rarely produces this. A process that surfaces tradeoffs and builds shared understanding might.
Three specific traps
1. Planning without pruning
Most planning processes are additive. Teams propose initiatives, leadership adds strategic priorities, the list grows. By the end, there are 12 "top priorities" and everyone knows that's not real.
Good planning is as much about what you're not doing. Force the conversation: if you added this, what comes off?
2. Confusing planning with commitment
Plans are hypotheses. Treating them as commitments produces sandbagging (teams lowball to guarantee hits), gaming (optimizing for metric instead of outcome), and brittleness (teams can't adapt when circumstances change).
Build explicit review points — not to check on commitments, but to ask "is this still the right bet?"
3. Decoupling planning from the people who do the work
Top-down planning without enough bottom-up input produces plans that look clean but don't reflect reality. Individual contributors know where the bodies are buried. If they're not in the room (or the process), their knowledge doesn't make it into the plan.
What actually works
The planning process that I've found most useful has three phases:
Phase 1: Retrospective (~1 week) Before setting new goals, genuinely understand what happened last quarter. Not as a performance review — as a learning exercise. What were our assumptions? Which ones were right? What surprised us?
Phase 2: Strategic context (~1 week) Leadership shares the context that will shape the next quarter: market conditions, company-level priorities, tradeoffs the exec team has made. Not a decree — an explanation. The goal is to give teams enough context to make good local decisions.
Phase 3: Bottoms-up planning with structured negotiation (~2 weeks) Teams draft their own plans given the strategic context. Then there's a structured negotiation process where dependencies get surfaced, tradeoffs get made explicit, and priorities get locked.
The output isn't a perfect plan. It's a team that understood the process well enough to update the plan when reality requires it.
That's the whole point.