What quarterly planning is (and isn't)
Quarterly planning is deciding, before the quarter starts, the few outcomes your team will commit to over the next 13 weeks and the work that will get you there. Thirteen weeks is a useful length. It's long enough to ship something that changes a number or a behaviour, and short enough that if you've bet wrong, you find out while there's still time to correct.
It isn't a 40-slide deck, a list of every ticket in the backlog, or a promise that nothing will change. A good quarterly plan fits on one page. Anyone on the team should be able to read it in two minutes and tell you what matters this quarter, why, and what they personally are doing about it.
Why most quarterly plans die in week three
Most quarterly plans are written with care and abandoned quietly. The pattern is familiar:
- Too many objectives. Seven objectives means none of them are priorities. By week three the team is optimising for whichever one got mentioned in the last leadership meeting.
- No link from goals to the week's work. The plan describes outcomes; the sprint board describes tickets. Nothing connects them, so the two drift apart and nobody notices until the retro.
- No review ritual. If nobody looks at the plan on a fixed cadence, it stops being a plan and becomes a record of what you hoped for in the first week.
- It lives in a doc nobody opens. A planning doc is closed the day it's approved. The plan has to sit where you look every morning, or it loses to your inbox.
The process below is built to avoid all four.
The quarterly planning process, step by step
Block half a day for the first draft, then spread the conversations over the following week. It gets faster every quarter.
-
Close out last quarter honestly
List last quarter's objectives and mark each one: moved, partly moved, or didn't move. Then write down one learning, the single thing you'd do differently. Be honest in the middle column; “partly” covers a lot of ground, and the gap between plan and reality is the most useful input you have.
-
Pick one to three objectives, each with a why
An objective is the outcome you're aiming for, written as a sentence a new starter would understand. Write one line under each on why it matters now. If you have more than three candidates, write the why for all of them. The weak ones usually give themselves away.
-
Define two or three key results per objective
A key result answers “how will we know?”. It can be a number with a start and a target, or a plain statement of what done looks like if no honest metric exists yet. Don't invent a percentage just to satisfy the format.
New to OKRs? OKRs explained covers objectives, key results and initiatives, with a worked example.
-
Turn each key result into initiatives
Initiatives are the actual work: the bets you'll place to move each key result. Give every initiative one owner, a person rather than a team. If a key result has no initiatives under it, it's a wish. If an initiative serves no key result, ask why you're doing it.
-
Pressure-test capacity
Add up what the initiatives will take against the team you actually have for 13 weeks, after leave, on-call and the support load you always forget. If it doesn't fit, cut. Cutting now is a decision; cutting in week nine is a failure.
-
Bring your manager and team in before it's final
Share the draft while it's still a draft. A 30-minute conversation with your manager beats a polished deck, because it surfaces the context you're missing while it's cheap to change. Then walk the team through it; they'll spot the dependency you didn't, and they'll own the plan instead of receiving it.
-
Set the weekly ritual
Monday: pick the few initiatives that matter this week. Friday: close them out, note what moved and what's next, and decide what carries over. Fifteen minutes each end of the week is what turns a quarterly plan into something you steer by.
-
Run a mid-quarter check at week six or seven
Look at every initiative and make one of three calls: re-tier it, drop it, or double down. Write down the reason for anything you drop. Then tell your manager what changed before they ask.
A quarterly plan example
Here's what a finished plan might look like for a product team at a B2B SaaS company whose free trials aren't converting. The numbers are illustrative; the shape is the point.
ObjectiveNew teams reach their first real result in their first week
Why now: in this team's own funnel, most trials that churn never finish setup, so every improvement here flows straight into conversion.
- KR 1
- Trial teams that invite a colleague within 7 days: 22% → 35%
- KR 2
- Median time from sign-up to first completed workflow: 4 days → under 1 day
- KR 3
- New admins can set up single sign-on without raising a support ticket (qualitative)
| Initiative | Moves | Owner |
|---|---|---|
| Instrument every onboarding step so we can see where teams drop out | KR 1, KR 2 | Eng lead |
| Cut the setup wizard from seven steps to three | KR 2 | Design lead |
| Sample-data workspace, so new teams don't start on an empty page | KR 2 | PM |
| Invite-a-colleague prompt at the moment of first value, not at sign-up | KR 1 | Growth engineer |
| Self-serve SSO setup with in-app connection checks | KR 3 | Platform engineer |
| Watch five recorded onboarding sessions every Friday and log what we learn | All | PM and designer |
Cut at the capacity check: a rebuild of the billing page. Worth doing, doesn't move this objective, parked for next quarter with that reason written down.
Notice what the plan doesn't include: a date for every initiative, a Gantt chart, or a slide per key result. One objective, three ways of knowing, six pieces of owned work, one thing deliberately left out.
Quarterly planning for different setups
OKR teams
The steps above are OKRs with one addition: initiatives. Plain OKRs describe outcomes and stop. Adding the layer of owned work underneath is what lets you answer “how's the quarter going?” from the plan itself, rather than from memory. There's more on this in the Friyay framework.
NCT teams
If you run Narratives, Commitments and Tasks, the process maps cleanly. Steps 1 and 2 produce your narrative, step 3 your commitments, and step 4 your tasks. The capacity check and the weekly ritual matter just as much. See running NCTs for the details.
Agile and scrum teams
A 13-week quarter is roughly six two-week sprints plus a spare week for slippage, planning and the unexpected. Initiatives usually span several sprints. Each sprint goal should name the key result it's moving, and the mid-quarter check lands naturally after the third sprint review. Quarterly planning sets direction; sprint planning sequences the work. Keep them separate and you avoid planning the whole quarter at ticket level.
Common quarterly planning mistakes
- Planning the backlog instead of the outcome. If your plan is a list of features, you've skipped the objective.
- Every key result is a number nobody trusts. A plain statement you can judge honestly beats a metric you made up in week one.
- Initiatives owned by “the team”. Shared ownership means nobody chases it. One name per initiative.
- Skipping the capacity check. The plan that fits on paper and not in the calendar is the one that ruins weekends in week ten.
- Dropping work quietly. Things will fall off; that's fine. Doing it without a recorded reason erodes trust faster than missing the target.
Quarterly planning FAQ
How long should quarterly planning take?
For a single product team, about half a day of focused thinking for the first draft, then one or two short conversations over the following week. If it's taking weeks, the plan is probably too detailed.
How many objectives should a quarterly plan have?
One to three. Three is the most people can hold in their heads on a busy Tuesday. If everything is an objective, nothing is a priority.
What's the difference between quarterly and annual planning?
Annual planning sets direction: the bets and themes for the year. Quarterly planning turns that direction into specific outcomes and owned work for the next 13 weeks. Your quarterly objectives should read as a step toward the annual ones.
What if priorities change mid-quarter?
They often will. Go back to the structure rather than starting over: drop the initiatives that no longer serve a key result, write down why, and tell your manager and team what changed. Adapting in the open builds more trust than following a stale plan.
Do key results need to be numbers?
No. A key result is how you'll know you got there. Use a number when a real one exists with an honest starting point. Otherwise, write a clear statement of what done looks like, and add the metric later if one emerges.
Where Friyay fits
Friyay holds this whole plan on one page: your goals and key results, the initiatives under them, and a weekly list you pick on Monday and close on Friday. It's the habit, with the plan attached, so you can clock off on time. The framework page explains the structure, and how to set your priority areas for next quarter is the companion to this guide.
Plan your quarter in Friyay — free to start