📆Annual Planning
The single most-leveraged 6 weeks of your year. Most PMs do it badly and pay for 12 months.
Annual planning sets the roadmap, the org structure, the budget, and the OKRs for the year. PMs who run it well shape the company's direction; those who don't get assigned roadmaps they don't believe in.
Annual planning is a 6-8 week process: strategy refresh, opportunity sizing, capacity planning, ruthless prioritization, commitment. The output is annual OKRs, quarterly themes, and a clear understanding of what's NOT being done. The process matters more than the artifact.
The 8-week timeline
Weeks 1-2: Strategy refresh. Read the 10-K (if public), exec updates, customer trends, competitive shifts. Update the strategy doc if anything material has changed.
Weeks 3-4: Opportunity sizing. What are the 10-15 biggest opportunities for the product? Impact-size each. Rough order-of-magnitude estimates, with confidence factors.
Week 5: Capacity planning. Engineering, design, PM capacity for the year. Subtract on-call, hiring time, tech debt. What's the actual discretionary capacity?
Week 6: Bottom-up vs top-down reconciliation. Top-down: what does leadership want shipped? Bottom-up: what does the team think is highest-leverage? Reconcile in writing.
Week 7: Commitment. Annual OKRs drafted, quarterly themes outlined. Each team owns 1-3 bets.
Week 8: Communication. All-hands, written narrative, FAQs. Get the org aligned.
The annual narrative
The single most important artifact: a 3-5 page narrative that tells the story of the year ahead. Not bullet points — a story. "Here's where we are. Here's where the market is moving. Here's the bet we're making and why. Here's what we'll know by Q2. Here's what we're explicitly NOT doing."
This narrative becomes the reference document for the year. Sales pitches reference it. Engineers cite it in PRs. Hiring uses it. If you produce nothing else from annual planning, produce this.
The things that ruin annual planning
- Top-down with no bottom-up. Roadmap dictated; team doesn't believe in it.
- Bottom-up with no top-down. Team prioritizes incremental features; strategic shifts ignored.
- No 'not doing' list. Implicit scope means scope creep all year.
- Annual capacity estimated without subtracting maintenance. You'll be over-committed by 50%.
- Skipping the narrative. OKRs without a story don't motivate.
The mid-year recalibration
Annual planning's biggest weakness: things change in 6 months. The senior move is a mid-year recalibration in July: review the strategy, re-prioritize Q3-Q4 if needed, communicate any changes. Don't pretend the January plan is still right in July.
Real-world examples
Stripe runs annual planning as a memo-driven process. Long-form narratives circulate widely, get debated in writing, and culminate in a published company-wide strategy doc that every team can reference for the year.
Go deeper — recommended reading
Interview questions (1)
Q1How do you handle the conflict between top-down annual goals and what your team thinks is highest-leverage?leadershipsenior▼
Three moves:
- Surface the conflict in writing. Don't smile in the meeting and grumble after. A 2-page memo: 'here's what leadership is asking for; here's the team's bottom-up prioritization; here's where they diverge and the implications.'
- Quantify both. Impact-size the top-down asks vs the bottom-up bets. Often the divergence shrinks when you see actual numbers — sometimes the top-down asks are the right priorities and the team's bottom-up was missing strategic context; sometimes vice versa.
- Negotiate a hybrid. Usually the right answer is 60-70% of top-down + 30-40% bottom-up. Get explicit sign-off from your VP/CPO on the hybrid. If you can't get sign-off, escalate openly — better to have the disagreement now than to under-deliver later.
The PMs who win these conflicts repeatedly do so by being calm, data-driven, and patient. Emotional pushback loses; written analysis wins.