The quarterly planning process that doesn't waste three weeks

Quarterly planning in most companies is a theatre of prioritisation that produces a roadmap nobody owns and commitments that will be renegotiated in month two. The process that produces genuine quarterly commitment is faster, involves fewer people, and starts from a different input: what did we learn last quarter that changes what we should do next quarter.

Why most quarterly planning fails before it starts.

The standard quarterly planning process goes like this: in week twelve of the current quarter, the founder or PM schedules a series of planning sessions. Each team lead presents their backlog. A prioritisation exercise occurs — usually involving some combination of voting, scoring frameworks, and horse-trading. A roadmap is produced. The roadmap is presented to the company. The quarter begins. By week four, two things have happened: the roadmap has been informally renegotiated to accommodate the things that were not on it, and the things that were on it have not shipped because no one was the single owner of their completion.

The root failure is not prioritisation — it is the starting input. Planning processes that start from "here is our backlog, what should we do this quarter" will always produce a list of things to do. Planning processes that start from "here is what we learned last quarter, what does it change about our strategy" produce a small number of important commitments with a clear causal logic. The second kind of planning is faster, because you are not debating the relative priority of a backlog — you are asking a sharper question.

The learning retrospective as the true start of planning.

The first event in a well-run quarterly planning process is a learning retrospective — a structured review of what you actually learned in the previous quarter, separated from the question of what you shipped. These are different questions. A team can ship everything it planned and learn nothing of strategic value. A team can miss half its planned deliverables and generate insights that completely change the next quarter's direction. The measure of a quarter's value to the company's strategy is the learning, not the output.

The learning retrospective asks three questions of the previous quarter. What did customers do that surprised us? What did we build that had less impact than we expected? What did we assume at the start of the quarter that turned out to be wrong? Each of these questions produces candidates for strategy revision. Each candidate gets a simple evaluation: does this change what we should do next quarter, and if so, how?

The learning retrospective should take two hours, involve the people who were closest to the work and the customers, and produce a one-page document. That document is the primary input to the planning process. A planning process that does not start from this document is a planning process that is not learning from experience — it is a process that is generating work from instinct and backlog inertia.

Commitments, not roadmaps.

The output of quarterly planning should be a set of three to five commitments — not a roadmap, not a list of features, not an OKR spreadsheet with fifteen rows. Commitments are different from plans in a specific way: a plan describes what you intend to do, a commitment describes the outcome that will be true if the quarter is successful, and attaches a named person to making that outcome real.

A simple format for quarterly commitments: Outcome statement (what will be measurably true), Owner (one person, not a team), Success metric (the number or state that would confirm it happened), and Dependencies (the things that would prevent it if they are not resolved). Each commitment is no more than one paragraph. The entire set of quarterly commitments for a twenty-person company fits on one page.

The roadmap is a supporting document, not the primary one. If the commitments are the goals, the roadmap is the current best theory of how to achieve them. The roadmap will change. The commitments should not change except in exceptional circumstances — an external shock, a critical resource constraint, a discovery that makes a commitment fundamentally obsolete. Mid-quarter commitment revision should be treated as an exceptional event requiring explicit acknowledgment, not a routine adjustment.

The planning meeting itself.

If the learning retrospective has been run well and the founder has done the thinking work of translating learning into strategic candidates, the planning meeting is not where the hard decisions happen — it is where they are confirmed and owned. The planning meeting has three purposes: to review the learning and strategic candidates, to agree on the three to five commitments for the quarter, and to ensure that every commitment has one clear owner who accepts the accountability.

The planning meeting should take three hours, not three days. If your planning process takes more than a week, you are using the planning process to do strategy work that should have been done before the planning meeting. Strategy is not a quarterly event — it is a continuous discipline. The quarterly plan is the interface between ongoing strategy work and the team's execution calendar.

The people in the planning meeting should be the people who own the commitments. Not the entire company. Not the board. Not external advisors. The people who will be accountable for delivering the commitments for the next twelve weeks. If you are inviting more than eight people to your core planning meeting, you are treating planning as a communication event. Separate communication from decision-making: decide with a small group, communicate to the full team.

Month two and the inevitable renegotiation.

In almost every company, something happens in the second month of the quarter that creates pressure to revise the plan. A large customer requests something that was not planned. A competitor ships something that changes the landscape. A key engineer leaves. The team discovers that an assumption underlying one of the commitments was wrong. The question is not whether this will happen — it will — but how the organisation responds to it.

Companies that have a roadmap respond to disruption by updating the roadmap. The roadmap changes, the new priorities cascade down, and the original commitments are quietly abandoned. No one is held accountable for the original plan because the plan was never really a commitment — it was a projection of intent that everyone understood was provisional.

Companies that have genuine commitments respond to disruption differently. The commitment stands unless there is an explicit decision to revise it, made by the person who owns it, communicated to the team, with an explanation of what changed. The bar for revising a commitment mid-quarter is high — not impossible, but high enough that it feels like a consequential choice rather than a routine update. That friction is the mechanism that makes the commitment meaningful in the first place.

• 01
  Start with learning, not backlog. The first question in quarterly planning is not "what should we build" — it is "what did we learn last quarter that changes what we should build." A planning process that starts from a backlog is a process that reproduces last quarter's assumptions. A process that starts from learning is one that compounds on it.
• 02
  Three to five commitments, maximum. Quarterly goals beyond five are not goals — they are a list of things the team will feel bad about not doing. The constraint is the strategy. If you cannot pick five things that, if done well, will meaningfully advance the company's annual goals, you have not yet done the strategy work that makes planning possible.
• 03
  One owner per commitment. "The team will" is not a commitment. A commitment requires a name — one person who has accepted responsibility for the outcome. Not responsibility for the project plan, responsibility for the result. If you cannot name a single person, the commitment is not yet scoped correctly, or the ownership structure of the team is too diffuse to produce accountability.
• 04
  Separate the planning meeting from the communication event. Decide with the smallest group that has the full context, then communicate the commitments to the full team in a separate session. When you conflate the two, the planning meeting becomes a performance of inclusive decision-making that slows the decision without actually incorporating the perspectives of everyone in the room.
• 05
  Treat mid-quarter revision as a consequential act. The mechanism that makes quarterly commitments mean something is the friction involved in revising them. If revision requires an explicit conversation, a documented reason, and an acknowledgment from the team, revisions will happen only when they are genuinely necessary. That is the goal. Easy revision is indistinguishable from no commitment.

Frequently asked questions.