What to prepare beforehand
The most common failure is spending the first two hours presenting information. Circulate it 48 hours ahead so the session can start with a discussion rather than a readout.
| Prepared in advance | Who owns it |
|---|---|
| Last quarter's goals and what actually happened | Whoever set them |
| The core numbers, with the previous two quarters for comparison | Whoever owns them |
| What customers said, including the uncomfortable parts | Sales or support |
| What did not get done, and why | Team leads |
| Anything that changed externally | Whoever noticed |
Send it as a document, not slides. Slides get presented; documents get read. This is the same principle that makes a board or investor update work.
Ask everyone to arrive with one thing they think the company should stop doing. It is a small ask that reliably surfaces the accumulated work nobody has questioned.
The agenda
Half a day. Four blocks.
Review last quarter honestly, 60 minutes
What we said we would do, what happened, and why the gaps happened. Not a presentation, a discussion of the causes.
The temptation when a quarter went badly is to move quickly on to the new plan. That is exactly when this block matters most, because the cause will otherwise repeat.
60 minutesLonger if the quarter was badWhat we are hearing, 30 minutes
Customers, prospects, the market, and the team. Concrete examples rather than summaries.
This block is what stops planning becoming an internal exercise disconnected from anything outside the building.
30 minutesSpecifics onlyChoose the priorities, 90 minutes
Written-first: everyone lists what they think the top three should be, silently, before any discussion. Then compare.
The overlap is usually striking and the disagreements are the interesting part. Going straight to open discussion means the first confident voice sets the frame.
90 minutesWrite before you talkName owners, measures, and what you are dropping, 45 minutes
Each priority gets one owner, a way to tell whether it worked, and a first step with a date.
Then list what is being deferred to make room. Without this the plan is additive, and everything continues alongside three new things.
45 minutesThe dropping matters most
Choosing three priorities
Three, not eleven. Every small company overestimates quarterly capacity, because the estimate ignores the normal work that consumes most of the time. A quarter has roughly twelve working weeks, minus holidays, minus support, minus everything unplanned.
Each one needs an owner who is not everyone. Priorities owned by the team are owned by nobody.
Each needs a way to tell whether it worked that does not require a debate. If assessing it needs a meeting, it is not measurable enough. The distinction between an outcome and a task is covered in our guide to OKRs for small teams.
At least one should be defensive. Something that reduces risk or fixes accumulated problems rather than adding. Teams that only ever plan new work accumulate a maintenance debt that eventually consumes a whole quarter.
Write down the trade-off. "We are prioritising onboarding, which means the reporting work waits until next quarter." Naming the cost is what turns a wish list into a plan, and it prevents the argument in week six about why nobody worked on reporting.
Making it survive week three
Most quarterly plans are undone by week three, not because they were wrong but because nothing connects them to daily work.
Put the three priorities where the team sees them weekly. Not in a document opened once a quarter. They belong in the same place as the weekly priorities, which is the connection point described in our guide to a weekly operating rhythm.
Check them in the weekly review, in two minutes. On track, at risk, off track, per owner. Any plan that is not looked at weekly is a plan that gets rediscovered in month three.
Allow one to die mid-quarter. If a priority is clearly not going to happen, kill it in week six and say so. Carrying a dead priority to the quarter end so it can be marked incomplete wastes the attention it keeps taking.
Send the summary within a day. What was decided, who owns what, what was dropped and why. The same discipline as meeting notes that turn into action items, and it matters more here because people will refer back to this document for three months.
One thing worth protecting: do not fill the whole session with the plan. The review block at the start is where the useful thinking happens, and it is the block that gets cut when the day runs late. Planning that never examines the last quarter honestly produces the same plan with new dates on it.
Frequently asked questions
- How long should a quarterly planning session be?
- Half a day for a team under twenty, with the data circulated beforehand. Full-day sessions usually mean the first half is spent presenting information people could have read.
- Who should attend quarterly planning?
- Everyone in a team under about fifteen. Above that, leads attend and then run a shorter version with their own teams within the week. Excluding people from planning and then expecting ownership of the plan does not work.
- How many priorities should come out of it?
- Three. Possibly four. The number of things a small team can genuinely finish in a quarter alongside normal work is much lower than the number it can list.
- Should quarterly planning happen offsite?
- Away from the usual desks helps, but the location matters far less than the preparation. A well-prepared session in a meeting room beats an unprepared one in a nice venue.
- What if the quarter went badly?
- Spend more time on why, not less. The instinct is to move quickly to the new plan, which guarantees repeating the cause. A bad quarter examined honestly is more valuable than a good one glossed over.