Quarterly planning sounds straightforward. Get the leadership team together, decide what matters most for the next 90 days, and leave aligned.
In practice, most sessions fall short of that in predictable ways. Priorities are defined at the wrong level of abstraction. Nobody is named as the owner, or everyone is. The session runs long on vision and short on specifics. By week three of the new quarter, nobody can agree on what was actually decided.
The issue is usually not intent. Founders and leadership teams want to plan well. The issue is structure. A quarterly planning session is not a strategy retreat and it is not a team brainstorm. It is a specific kind of meeting with a specific job: to convert the company's growth goals into 90-day commitments that are clear enough to execute and specific enough to measure.
This guide walks through how to build one that does that job.
The most important part of a quarterly planning session happens before it starts.
A planning session without pre-work turns the first hour into a data-gathering exercise: what happened last quarter, where are we against annual goals, what are the biggest problems right now. By the time the room has a shared factual baseline, energy is already fading and the actual planning work gets rushed.
Send three things to every attendee at least 48 hours before the session.
First, a summary of last quarter's results against each goal. Not a narrative, not a slide deck, a clean list: goal, metric target, metric result, and one sentence on why. If you ran a proper QBR at the end of the prior quarter, this document already exists.
Second, a current read on annual goals. Where does the company stand against its targets for the year? Which annual goals are on track, which are at risk, and which have already been missed? This gives the planning session its strategic context and prevents the team from setting quarterly priorities that are disconnected from the bigger picture.
Third, one question for each department head to answer before they arrive: given where the company is against its annual goals, what is the single most important thing your department can move this quarter? Not a list of five things. One thing. This pre-work forces early prioritization and surfaces any misalignment between departments before the session begins, which makes the session itself significantly more productive.
A quarterly planning session is a leadership meeting, not a company all-hands.
The right attendees are the people who own departments and will own quarterly goals: the founder or CEO and each department head. If a department does not have a defined leader, that is worth addressing before the session, not during it.
Keep the session small enough for genuine discussion. More than eight people and the room starts to perform alignment rather than produce it. If the company has more departments than that, consider whether every department needs a quarterly goal of its own or whether some can be grouped.
A third-party facilitator changes the dynamic in ways that matter. When the founder runs the session, they are simultaneously trying to lead the conversation, advocate for their own priorities, and read the room. These roles conflict. A facilitator handles the process so the founder can participate as a principal rather than a host, which typically produces better decisions and more honest alignment from the team.
A full quarterly planning session for a leadership team of five to eight people runs three to four hours. That is the minimum to do it properly. Half-day sessions are better when the company has more complex cross-functional dynamics or significant changes to navigate.
The agenda has four parts.
Part one: Grounding (30 minutes)
Open with the facts. Walk through last quarter's results using the pre-work document. This is not a retrospective and it is not a blame session. It is five minutes per goal: what was the target, what was the result, and what is the single most important implication for this quarter. The facilitator's job here is to keep the conversation forward-looking. The point of reviewing last quarter is not to relitigate it. The point is to make sure the decisions in part two are informed by what actually happened rather than what people wish had happened.
Part two: Priority setting (60 to 90 minutes)
This is the core of the session. The question driving this section is: given where we are against annual goals and what we learned last quarter, what are the three to five things that matter most for the next 90 days?
Start by having each department head share the one priority they submitted in their pre-work. The facilitator captures these without evaluation first. Once everything is on the table, the group works through a prioritization conversation: which of these are truly company priorities, which are department priorities that do not need to be on the company list, and which have dependencies on other departments that require coordination?
The output of this section is a shortlist of three to five company-level quarterly priorities. Not ten. Not seven. Three to five. Anything beyond that is not a priority list, it is a wish list, and wish lists do not drive execution.
Part three: Goal architecture (60 minutes)
This is where the shortlist becomes executable. Each priority gets defined with four elements: an outcome statement, a single measurable metric with a numeric target, a single owner, and a deadline.
The outcome statement describes what success looks like in plain language. The metric makes it measurable without ambiguity. One number, not a range. The owner is one person, not a team. If two people share ownership, nobody owns it. The deadline is typically the last day of the quarter, but some goals may have meaningful intermediate milestones worth noting.
Work through each priority one at a time. For each one, the facilitator asks: what is the metric, who owns it, and what would make this goal clear enough that someone outside this room could evaluate whether it was achieved. That last question is the clarity test. If the room cannot answer it in thirty seconds, the goal needs to be refined.
This section often surfaces the most productive tension of the session. Department heads may push back on ownership. The founder may want to keep goals broader than the architecture allows. The facilitator's job is to hold the structure while keeping the conversation moving. The discomfort of naming one owner for each goal is exactly the discomfort that drives accountability.
Part four: Cross-functional alignment and close (30 minutes)
Before the session ends, surface dependencies. Which quarterly goals require input, resources, or coordination from a department that does not own them? Flag these explicitly and assign a conversation owner to resolve each one within the first week of the quarter. Do not try to resolve them in the session. They will take longer than the time allows and they are better handled in a smaller conversation.
Close by reading the full goal list back to the room. Every goal, every metric, every owner. This is not a formality. It is a commitment ceremony. The act of hearing the goals stated aloud with names attached changes the psychological weight of the agreement. Have the room confirm alignment before adjourning.
The session is not done when the meeting ends. It is done when the output is documented and distributed.
Within 24 hours of the session, circulate a goal document containing every quarterly goal in the same four-element format used in the session: outcome, metric, owner, deadline. One page. No narrative, no context, no slides. Just the goals in a format the whole company can reference.
This document becomes the single source of truth for the quarter. It is what gets loaded into the centralized tracking dashboard. It is what the bi-weekly leadership meetings reference. It is what the QBR measures against at quarter end.
If the session ends and this document does not exist, the planning session produced a conversation, not a plan.
Setting goals at the initiative level instead of the outcome level. "Launch the new onboarding flow" is an initiative. "Reduce time to first value from 14 days to 7 days" is an outcome. Goals defined as initiatives tell the team what to do, not what to achieve, which makes it nearly impossible to hold anyone accountable when the initiative happens but the outcome does not.
Assigning goals to teams instead of individuals. Shared ownership is no ownership. When a goal belongs to the marketing team, everyone on the marketing team can plausibly argue they did their part even when the goal is missed. One name on the goal changes the conversation entirely.
Setting too many priorities. Five quarterly goals for a 20-person company is probably too many. Three is more honest. The constraint is uncomfortable, but it is the constraint that makes the priorities real.
Skipping the cross-functional dependency conversation. Goals that require coordination between departments will stall in week four if the coordination was never explicitly planned. Surface the dependencies before the quarter starts.
Letting the session end without a written output. Memory is not a planning tool. The goal document is not optional.
FounderMove runs quarterly planning sessions for founder-led companies, including pre-session preparation, in-session facilitation, and the goal documentation that drives execution all the way to quarter end.
.jpg)
