Quarterly planning

Quarterly planning for design and product teams.

Quarterly planning is deciding what your team will actually try to ship over the next thirteen weeks — the horizon above a sprint and below an annual roadmap. For a team of two to ten it isn't an OKR ritual or a planning week; it's a short, honest answer to one question: given the quarter we really have, after holidays and the work that always shows up, what are the few things worth committing to? All Do is a free, web-based planner built for that altitude — the whole quarter on one timeline, a swimlane per teammate, PTO baked in, and a movable cutoff between what's committed and what's still just intention.

What a quarter is for on a small team

A quarter is the planning unit where you protect the important from the urgent. Sprints are great at "what are we doing this week," but a team that only plans in sprints tends to spend thirteen weeks busy, then look up to find the one thing that actually mattered never got a clear run. The quarter is where you decide the thing that matters gets week three, not "eventually."

It's also short enough to be honest. An annual roadmap is mostly fiction by March; a quarter is close enough that you can size it against the people and days you genuinely have. For a small team the job is modest: pick the few themes worth a quarter, place them roughly in time, and leave room for the rest of reality.

Why the enterprise quarterly machinery doesn't fit

Search "quarterly planning" and you'll find OKRs, PI planning, capacity-allocation spreadsheets, a two-day offsite. None of it is wrong — it's built to coordinate many teams who can't see each other's work. On a team of six who share a room (or a Slack channel), that machinery adds ceremony without adding clarity. You spend the planning energy on the process instead of the plan.

Two ideas survive the trip down to a small team, and they're all you need to keep:

Plan the near weeks; leave the far weeks soft

Detail the first few weeks, sketch the rest. Committing all thirteen weeks on day one just guarantees the plan and reality diverge until nobody trusts it. A good quarter plan is explicit about where commitment ends and intention begins.

Plan against the quarter you actually have

Subtract holidays, known PTO, and the standing meeting load before you count the quarter's capacity. A quarter with two people out for a sprint and a company holiday week is meaningfully smaller than thirteen clean weeks — and pretending otherwise is how a confident plan falls apart by week five.

What a small team actually needs to plan a quarter

You can do honest quarterly planning with four things:

• A short, ordered list of themes — the few outcomes worth a quarter, ranked, so when something has to give you cut from the bottom.
• Rough placement in time — which theme lands in which part of the quarter, at the resolution of weeks, not days.
• The real calendar — working weeks minus PTO, holidays, and the recurring load, so the plan is sized against the quarter you have.
• A line between committed and speculative — so leadership reads the near weeks as a promise and the far weeks as a direction, not both as gospel.

Notice what's absent: key results, story-point forecasts, a roadmap tool with dependencies and swimlane permissions. A small team doesn't need to predict the quarter to the day. It needs to see it clearly enough to commit to the right few things and say a calm no to the rest.

Seeing the whole quarter on one timeline

All Do treats the quarter as something you look at, not a document you assemble. The board is one timeline with a swimlane per teammate; one toggle switches between week, month, quarter, and year, so the same plan zooms from "this week" up to "the whole quarter" without re-keying anything.

Concretely:

• Quarter view — thirteen weeks across, one row per person. A glance shows whether the quarter is achievable before you promise it to anyone.
• A movable cutoff — drag a line to mark where the committed plan ends; everything past it reads as speculative, so "planned" and "hoped" never blur together.
• PTO baked in — record time off once and tasks crossing it shorten automatically, so the quarter reflects its smaller weeks without you doing the math.
• Capacity bands — a green / amber / red strip flags a stretch where one person is committed past what the weeks can hold.
• Several quarter tabs — keep this quarter and next quarter side by side, so planning the next one doesn't disturb the current one.
• Memos for context — pin a floating note above the lanes ("hiring freeze through Q-end") so the plan carries its constraints.

Sharing the quarter with leadership

The quarter plan usually has an audience: a founder, a head of product, a client. All Do gives you a read-only, anonymized link to the same board you plan against — so the "here's our quarter" conversation happens over the live picture, not a slide deck that's out of date the moment you export it. Names show as initials on the shared view; the plan stays current because it is the plan, not a copy of it.

A 60-second start

Open alldo.app, sign in with Google, and you land in a sample board. Switch the view to Quarter, add your people, and drop the two or three themes you care about onto the weeks you think they belong in — rough is fine. Mark known time off, then drag the cutoff to where your commitment honestly ends. In a minute you have a quarter you can defend in the next leadership check-in, and adjust in seconds when reality moves.

When you don't need this

To save you the trial:

• You plan one sprint at a time and the quarter takes care of itself — a backlog and a sprint board are enough; you don't need the higher altitude.
• You're a solo founder or a pair — the quarter lives in your head and a shared note; swimlanes are overkill.
• You're coordinating many teams with hard cross-dependencies — that's genuine PI-planning / roadmap-suite territory, and the per-person swimlane stops scaling around ten.
• Your org mandates formal OKRs — keep them; All Do plans the quarter's work, it isn't an objectives-and-key-results system.

Frequently asked questions