The Quarterly Planning Process That Doesn't Take a Week
The Quarterly Planning Process That Doesn't Take a Week
Quarterly planning has a size problem. The bigger the team, the more the planning process expands to fill the time available — which, for most companies, is somehow an entire week in which very little actual planning happens and a great deal of slide-making does.
The week usually looks like this: leadership sets the company goals. Each team then creates their own slide deck interpreting those goals in terms of their own roadmap. There are alignment meetings between decks. There are revision cycles. There are cross-team reviews where someone notices that two teams are planning to work on overlapping things and nobody told each other. There are timeline views assembled in spreadsheets that are out of date before the planning week is over.
At the end, the company has a set of plans that are already partially stale, a collection of slide decks that will never be opened again, and a general exhaustion with the whole process.
There's a better version.
The Problem Is the Artifact, Not the Process
Most quarterly planning produces slide decks. A slide deck is the wrong artifact for a plan.
A slide deck is for presenting. A plan is for working from. Those are different documents. A slide deck shows what was decided. A plan is what the team references as the work unfolds — updated when priorities shift, linked to the actual tasks, accessible to anyone who needs to understand what the team is doing and why.
When the plan is in a slide deck, it's immediately disconnected from the work. The team has to maintain two separate systems: the deck that describes the plan, and the boards and docs where the work actually happens. Nobody maintains the deck because updating a slide is disconnected from doing the work. By week six of the quarter, the deck is a historical document, not a current plan.
The artifact that works is a live document in the same workspace as the work — a plan page in Closot that links to the project boards it governs, updated as the quarter evolves, readable by anyone without a presentation being required.
What Planning Actually Requires
Stripped of the presentation layer, quarterly planning requires three conversations:
What are we trying to achieve this quarter? This is the goals conversation. Outcomes, not outputs. What would make this quarter a success? This should produce a small number of clear, specific goals — not a prioritized list of everything the team could possibly work on.
What are we actually going to work on? This is the roadmap conversation. Given the goals and the team's capacity, what projects and initiatives are in the plan for this quarter? What's explicitly not in the plan? This conversation should produce a timeline view — what starts when, what has dependencies, what the sequencing is.
Who is doing what? This is the assignment conversation. Which team owns which initiative? Who are the key contributors? What are the cross-team dependencies and who is accountable for managing them?
Those three conversations, done well, produce a real plan. They don't require a week. They require good preparation, the right people in the room, and a workspace where the outputs are captured in a way that can be used throughout the quarter.
The Preparation That Makes Planning Fast
The quarterly planning meeting is slow when people arrive without preparation. When each team is developing their plan in the room, the meeting is doing two jobs — generating ideas and making decisions — and it does both badly.
The meeting should only make decisions. Ideas, priorities, and rough scope should be developed before the meeting, by the people who know the work best, in writing.
In Closot, the preparation happens in the workspace: each team publishes a draft plan before the planning meeting — what they're proposing to work on, why, and what they'll need from other teams. Cross-team dependencies become visible before the room assembles. Conflicts can be identified and pre-resolved. By the time everyone is together, the meeting is reviewing, adjusting, and deciding — not discovering.
This collapses the planning meeting from a week to a day, or a day to a morning, depending on team size.
The Plan That Lives Through the Quarter
The plan that's written in the first week of the quarter needs to survive contact with the next twelve weeks. Things will change. Priorities will shift. A project will take longer than expected. A new opportunity will emerge.
The plan should reflect those changes. Not as a separate amendment document — as an update to the same page. When a project is descoped in week six, the plan page reflects it. When a new initiative is added in week eight, it appears on the timeline with its context.
This requires the plan to be a living document, not a snapshot. And it requires the living document to be somewhere the team actually looks — in the same workspace as the boards and tasks, not in a slide deck buried in a folder.
When the end-of-quarter review comes, the plan and the actual state of the work are both in the same Closot space. The review doesn't require a data-gathering exercise before it can start. It starts from the current state and works backwards to understand what went well, what didn't, and what the next quarter should look like.
Starting Simpler
If your current quarterly planning process takes a week and produces a deck nobody reads, you don't have to overhaul everything at once.
Start with one team. Instead of a slide deck, write the quarter's plan as a Closot page: the goals, the projects, the timeline. Link it to the relevant project boards. Update it when things change. At the end of the quarter, see if the team has a clearer shared understanding of what they were trying to do and how close they got.
The teams that try this almost always continue. Not because the tool is magic, but because a plan that's connected to the work stays useful through the quarter. A deck never does.
Closot gives teams a live planning workspace — with goals, timelines, and boards in one place — so your quarterly plan actually guides the quarter. Try Closot.