How to Nail Quarterly Planning

Quarterly planning should clarify direction and priorities. Instead, at most companies, it’s a negotiation where teams overcommit to unrealistic goals, then spend the quarter explaining why they’re behind schedule.

I’ve participated in quarterly planning exercises that consumed weeks of the entire company’s time. We’d emerge with detailed roadmaps, capacity models, and dependency charts. Then reality would hit: a key customer emergency, an unexpected competitor launch, a technical blocker, and those perfect plans would become irrelevant by week three. We’d sacrificed agility for the illusion of predictability.

Introduction

Quarterly planning isn’t about predicting the future. It’s about aligning on priorities, understanding constraints, and making resource allocation decisions. The plan itself matters less than the shared understanding that emerges from the planning process.

This matters more now because execution velocity has become a competitive advantage. You can, pretty much, build and release a working complex feature in one day. Companies that plan quickly and adapt easily outmanoeuvre those stuck in rigid planning cycles. Yet many teams treat quarterly planning as something to “get through” rather than a strategic opportunity to align and accelerate.

Traditional planning approaches fail because they optimise for completeness over utility. Teams try to plan every detail for twelve weeks, forgetting that context changes weekly. The result? Plans nobody follows and planning processes nobody trusts.

A Practical Framework

Step-by-Step Planning Approach

Here’s what actually works, refined through many quarters of mistakes:

Week 1: Set the context. Before discussing what to build, align on why. What changed last quarter? What did we learn? What market dynamics shifted? Where did our assumptions prove wrong? Stripe calls this “clearing the cache”, deliberately examining and updating beliefs before making new commitments.

Leadership should communicate business priorities clearly. Not everything, just the 2-3 things that matter most this quarter. Revenue growth? Retention improvement? Specific customer segment expansion? This clarity cascades down. Without it, teams optimise locally without global alignment.

Week 2: Propose and debate. Teams propose their priorities based on the context. Not detailed plans, high-level themes and outcomes. “Improve onboarding completion by 20%” not “Add tooltips, redesign the second screen, implement progress indicators.” This level of abstraction allows debate about whether these are the right priorities before investing in detailed planning.

Encourage tension here. Sales will want more features for deals. Engineering will want to pay down technical debt. Product will want to validate new ideas. These tensions are healthy. Surface them, debate them, make trade-offs explicitly.

Week 3: Commit and allocate. Once priorities are set, map resources. Who’s working on what? Where are the dependencies? What happens if someone leaves or gets pulled onto something urgent? This is where reality meets ambition. You’ll discover you don’t have enough capacity for everything. Good. Better to know now than six weeks in.

Linear uses a simple capacity model: each team commits to one “big bet” that will consume 60-70% of their capacity. The remaining 30-40% absorbs customer issues, technical debt, and unexpected work. This buffer makes plans realistic instead of aspirational.

Week 4: Document and communicate. Write down the plan. Not the process documentation, the decisions. What are we doing? Why? What are we explicitly not doing? Who’s working on what? How will we measure success? Make this accessible to everyone.

Then communicate broadly. All-hands presentations, team syncs, written summaries. Use multiple channels. People absorb information differently. The goal is ensuring everyone knows what matters this quarter and how their work contributes.

Real Examples from Product Teams

Atlassian’s “Health Monitor” approach: Before planning next quarter, they assess current health across multiple dimensions. Team velocity, technical debt, customer satisfaction, competitive position. This grounds planning in reality. If tech debt is critical, that becomes a priority regardless of what new features look tempting.

GitLab’s transparent planning: Their entire planning process happens in the open, even for internal teams. Anyone can see what’s being proposed, what’s being debated, and what’s been decided. This transparency forces discipline (you can’t hide vague plans) and enables better input (more people can spot problems).

Putting It Into Practice

Implementation Tips

Don’t plan at the task level. Tasks are discovered during execution, not planning. Plan at the outcome level. “Improve mobile performance” is a good quarterly goal. “Implement lazy loading on the home screen” is a task you might discover while pursuing that goal. If you’re planning sprints during quarterly planning, you’re going too deep.

Buffer ruthlessly. Things will go wrong. People will get sick. Customers will have emergencies. Competitors will launch things. If your plan assumes everything goes perfectly, it’s not a plan, it’s fan fiction. Reserve 20-30% capacity for the unexpected. Basecamp plans for even more buffer. They assume only 50% of time goes to planned work.

Make trade-offs visible. When you commit to something, you’re saying no to something else. Make that explicit. “We’re prioritising mobile performance over new features because…” This prevents the “can’t we do both?” conversations later.

Plan milestones, not dates. “Complete the redesign by March 15” sets up failure. “Validate the redesign with 20 users before building it fully” creates a clear checkpoint without artificial urgency.

Involve the people doing the work. Don’t let leadership plan in isolation then hand down edicts. The engineers, designers, and PMs closest to the work have critical context about what’s feasible and what’s not. Leadership provides guidance and alignment, not detailed plans.

Measuring Success

How do you know if quarterly planning worked?

Team conviction, not compliance. After planning, do teams believe in their priorities? Or are they grudgingly executing orders? High conviction leads to better work. Survey teams after planning: “Do you believe these are the right priorities?” Track that over time.

Plan adherence (but not blindly). You shouldn’t hit 100% of what you planned, that suggests you weren’t ambitious enough. But you also shouldn’t hit 20%. That suggests planning was disconnected from reality. Somewhere around 60-70% completion is healthy. It means you aimed high but stayed connected to what’s feasible.

Speed to first value. How quickly do teams ship something valuable after planning? If it takes six weeks to ship anything, your plans were too big or vague. Linear targets shipping something meaningful within the first two weeks of the quarter. That forces plans to be concrete and actionable.

Mid-quarter adjustments. The plan will change. How quickly can you recognise that and adjust? Great quarterly planning creates alignment that makes adaptation easier, not harder. If a six-week-old plan prevents you from responding to a critical customer need, your planning process is broken.

Common Pitfalls and How to Avoid Them

Mistakes to Watch For

Planning theatre. Going through motions without genuine decision-making. If you could have predicted the outcome of planning before it started, you didn’t actually plan. You performed planning. Real planning involves debate, discovery, and trade-offs.

The “peanut butter” approach. Spreading resources across too many priorities. Every team gets a bit of everything, nothing gets done well. Better to fully staff three priorities than partially staff eight. Asana explicitly limits company-level priorities to three each quarter. Everything else is local optimisation.

Assuming perfect execution. Plans that assume no blockers, no surprises, no learning are fantasies. Build in learning loops. “We’ll spend two weeks validating this assumption, then decide whether to proceed.” That’s realistic planning.

Ignoring dependencies. Cross-team dependencies kill velocity. If Team A can’t proceed until Team B finishes something, and you didn’t coordinate during planning, you’ll discover this painfully mid-quarter. Map dependencies explicitly. Slack uses a “dependency map” during planning to visualise and discuss cross-team coordination needs.

Prevention Strategies

Start planning earlier than you think. Don’t wait until the last week of the quarter to plan the next one. Start mid-quarter when you still have time to gather context, debate, and iterate. Rushed planning produces poor plans.

Review last quarter honestly. What worked? What didn’t? Why? Teams that skip retrospectives repeat the same mistakes quarterly. Intercom’s planning starts with a thorough retrospective on the previous quarter. Celebrating wins and diagnosing failures.

Separate strategic planning from quarterly planning. Annual or semi-annual strategic planning sets direction. Quarterly planning translates that into concrete actions. Mixing these creates confusion. Is this planning session about where we’re going or how we’re getting there? Keep them distinct.

Accept uncertainty gracefully. The further out you plan, the fuzzier it gets. Week one of the quarter can be relatively concrete. Week twelve is mostly directional. That’s fine. Don’t pretend to have more certainty than you actually have.

Key Takeaways

Essential principles for effective quarterly planning:

• Plan outcomes, not tasks — discover specific tasks during execution as you learn what actually works
• Reserve 20-30% buffer capacity — things will go wrong; plan assuming they will
• Limit company priorities to 3 or fewer — more priorities means no priorities
• Make trade-offs explicit — when you say yes to something, document what you’re saying no to
• Start planning mid-quarter, not at quarter-end — rushed planning produces unrealistic plans

Conclusion

Quarterly planning shouldn’t be painful. If it is, you’re probably doing it wrong—planning too much detail, committing to too much scope, or treating plans as contracts instead of hypotheses.

The best quarterly planning I’ve seen takes about two weeks, involves the right people, and produces alignment around 3-5 key outcomes. The documentation fits on a couple of pages. Everyone knows what matters and why. Then teams execute with autonomy, adjusting as they learn.

Start with less planning, not more. Pick your top three priorities. Align the team around them. Reserve buffer capacity. Document the decisions. Then get out of the way and let teams execute. You can always add more process if needed, but you can’t easily remove it once it’s entrenched.

The goal of planning isn’t perfect prediction. It’s informed commitment with the flexibility to adapt when reality surprises you—which it will.

Have questions or thoughts? Get in touch - I’d love to hear from you!