How to Do Quarterly Planning: A Step-by-Step Process

Most quarterly planning sessions fail before they start. The meeting is scheduled too late (the quarter has already begun), the retrospective is skipped (too uncomfortable), and the output is a list of ambitious projects with no weekly milestones attached. The plan is technically complete. It just doesn’t work.

This guide walks through the sequence that actually produces a functioning quarterly plan—one that holds up past week four.

Step 1: Block the Time Before You Do Anything Else

Schedule your planning session in the last week of the outgoing quarter. Not the first week of the new one.

This matters because starting a quarter without a plan means you spend the first seven to ten days operating on inertia—doing what feels most urgent rather than what you decided was most important. By the time you finish planning, you have already lost 8% of the quarter.

For solo practitioners: block 2 hours, undistracted, with your calendar and project history open.

For teams: block a half-day offsite or a focused block with an explicit agenda sent 48 hours in advance.

Step 2: Run an Honest Retrospective

Before you plan forward, you have to look back. Most planners rush this step. It is the most important one.

Pull up your prior quarter’s plan and answer four questions:

1. Which objectives did you complete, fully or substantially?
2. Which did you start but not finish—and what caused the stoppage?
3. Which did you not meaningfully touch at all?
4. What consumed time that wasn’t in the plan?

The last question is often the most illuminating. If you planned for deep work but spent two weeks managing an unexpected personnel issue, that is not a planning failure—it is information about the actual nature of your work. Your next plan should account for it.

Write your answers in one page or less. Bullet points are fine here. The goal is honest accounting, not narrative polish.

Step 3: State the Destination Clearly

Quarterly planning starts with a single question: What does good look like at the end of these 13 weeks?

Write a three-to-five sentence description of the state you want to be in on the last day of the quarter. Not a list of tasks. A state.

For example: “At the end of Q1, we have closed three enterprise pilots, our onboarding drop-off rate is below 30%, and the engineering team has shipped the new API layer into production with no critical incidents.”

This description becomes the filter for everything that follows. If a proposed objective does not clearly advance this state, it belongs in a backlog, not the quarterly plan.

Step 4: Select Your Objectives

From the destination description, identify the two to four initiatives that are most critical to reaching it. These are your quarterly objectives.

Each objective should meet three criteria:

Specific enough to be unambiguous. “Improve sales process” is not an objective. “Reduce the sales cycle from 45 days to 30 days for mid-market accounts” is.

Achievable within the quarter. An objective that requires six months of work creates drift by definition. If something is six months away, break it into two quarterly chunks.

Within your control, at least 80%. Dependencies on external decisions, partnerships, or approvals that aren’t yours to make create high-variance objectives. These can still be valid quarterly priorities—but they need contingency milestones so the quarter isn’t stranded if the dependency doesn’t resolve.

Step 5: Define Success for Each Objective

For every objective, define what “done” looks like in measurable terms. This is where the OKR framework’s concept of Key Results is genuinely useful, even if you are not running a full OKR system.

Write one to three measurable outcomes per objective. These become your scorecard. At the end of the quarter, you are not asking “did we work on this?”—you are asking “did the needle move?”

If you cannot define a measurable outcome, that is a signal that the objective is either too vague or too activity-based. “Hold weekly sales calls” is an activity. “Generate 20 qualified pipeline opportunities” is an outcome.

Step 6: Break Each Objective Into Weekly Milestones

This is the step most quarterly plans skip. It is the reason most quarterly plans fail.

For each objective, map out what needs to happen in each of the 13 weeks. The milestones do not need to be elaborate—a single deliverable or decision point per week is sufficient.

A useful structure:

• Weeks 1–4: Foundation work. Research, setup, initial outreach, early builds.
• Weeks 5–9: Core execution. The primary work of the objective happens here.
• Weeks 10–12: Completion and review. Closing loops, incorporating feedback, finalizing.
• Week 13: Buffer. Something will slip. This week catches it.

Once you have milestones, put them in your calendar. An objective without calendar time is a wish, not a plan.

Step 7: Identify the One Dependency That Could Break Everything

For each objective, ask: “What is the single most important thing outside my direct control that this depends on?”

Name it explicitly. Assign it a risk level: high (the dependency could fail and the objective would stall), medium (a workaround exists), or low (the dependency is likely to resolve on schedule).

For high-risk dependencies, decide now whether to build a contingency path or to accept the risk. Making that decision explicitly at the start of the quarter is far better than discovering the gap at week seven.

Step 8: Schedule the Mid-Quarter Review

Before the quarter begins, put a two-hour mid-quarter review on the calendar for week six or seven.

At that review, you will ask: Are we on track? Where have we drifted? What adjustments are needed? Is any objective no longer the right priority given what we have learned?

The mid-quarter review is not a failure event. It is an intended decision point. Quarters are long enough that the right priorities in January may not be the right priorities in February. The review is where you make that call deliberately rather than letting drift make it for you.

Step 9: Share the Plan

A plan that exists only in your own head (or your own notes) lacks the accountability structure that research on goal commitment shows matters. Gollwitzer’s work on implementation intentions demonstrates that stating a plan—specifying when, where, and how—significantly increases follow-through compared to stating only a goal.

Sharing with even one other person creates the minimum viable accountability structure. For team plans, the sharing step is how the plan becomes an operating agreement rather than a management document.

What a Functioning Quarterly Plan Actually Looks Like

After this process, your quarterly plan should fit on one page. It contains:

• A three-to-five sentence destination statement
• Two to four objectives, each with one to three measurable outcomes
• A 13-week milestone map, at minimum in outline form
• Named dependencies and their risk levels
• A mid-quarter review date

If it is longer than one page, you have too many priorities. If it is shorter, you probably skipped one of the steps above.

Start your next quarterly plan by booking two hours this week—even if the quarter hasn’t ended yet. The retrospective alone is worth the time.

Related:

• The Complete Guide to Quarterly Planning Frameworks
• Why Quarterly Planning Drifts by Week 4
• 5 AI Prompts for Quarterly Planning
• Weekly Review Systems

Tags: quarterly planning, how to plan, goal setting, OKRs, execution