Free Calendar · 12-Month Cadence
Annual Product
Planning Calendar.
Month-by-month rituals that replace one-quarter thinking. For CPOs and PM leads running multi-team product orgs.
Year: ______
CPO: ______
Org size: ______
CPO: ______
Org size: ______
Why a 12-month rhythm
Most product teams plan in quarters and panic in weeks. A 12-month rhythm absorbs both: it sets the long horizon (strategy, hiring, board cadence) while leaving the short cycle (sprints, releases) untouched. Without it, the org reinvents its own planning ritual every January and burns the first eight weeks figuring out what it’s doing.
The year at a glance
Jan
Annual kickoff
Strategy refresh, 3 themes
Feb
Q1 mid-check
+ Q2 hiring waves
Mar
Q2 plan
Customer council
Apr
Q1 retro
Q2 launch week
May
Mid-year reset
Strategy drift check
Jun
Q3 plan
Leadership offsite
Jul
Focus week
No meetings, no plans
Aug
Hiring review
6-month bar calibration
Sep
Q4 plan
Budget season
Oct
Q3 retro
Q4 launch week
Nov
Annual prep
Board pre-read, capital plan
Dec
Annual close
Q1 commit, reflection
January
Annual kickoff & strategy refresh
- Revisit the strategy one-pager. Question every block, not just the management systems row.
- Set 3 annual themes — not 8, not “a list of priorities.” Three. The forcing function is the constraint.
- Communicate to the team in week 2 via an all-hands + a written memo.
- Confirm the year’s board cadence + customer council dates with leadership and EAs by Jan 15.
February
Q1 mid-quarter checkpoint & Q2 hiring waves
- Run the OKR mid-quarter recalibration in week 6 of Q1. Identify drift early; escalate weak KRs.
- Open Q2 hiring reqs based on Q2 plan. Senior hires take 12–14 weeks; if you wait until Q2 starts, the seat is empty until Q3.
- Capacity check: are the 3 annual themes actually staffed? If two themes have one PM each and the third has six, the “3 themes” framing is theatrical.
March
Q2 planning + customer council
- Q2 OKR mapping meeting in week 1 — 7-column worksheet, 90 minutes.
- Board prep: assemble the Q1 deck (8-slide structure). Send pre-read 48h before.
- Customer council session #1 of the year — 8–12 customers in the target segment, half-day, structured agenda.
- Mid-strategy pulse: one written page from the CPO summarizing what’s on/off track relative to the annual themes.
April
Q1 retro & Q2 launch
- Q1 retro: not the team-by-team retro — that’s a different ritual. The product-org retro asks one question: what changed our thinking this quarter?
- Q2 launch week: first-week war room for the 3 most strategic launches. CPO is in-room, not in calendar slots.
- Hire-quality spot check on Jan/Feb hires: are they ramping? If not, intervene now, not in August.
May
Mid-year strategy reset
- The trap most teams skip. June feels too early to reset; September feels too late. May is when drift is detectable and recoverable.
- Two-day offsite. Day 1: re-read the strategy one-pager out loud. Day 2: name what’s drifted and decide.
- Customer council dataset: theme analysis from the last 6 months of signal data. Are the themes the strategy predicted?
- Output: a written half-page memo — what’s holding, what’s adjusting, what triggers a fuller refresh.
June
Q3 planning + leadership offsite
- Q3 OKR mapping in week 1.
- Leadership offsite (2 days): decide vs. commit. Day 1 is decision-making (irreversible bets). Day 2 is commits (the things we’ll execute against).
- Agenda template: capital allocation review, capability-gap re-score, hiring plan for H2, customer-segment review, the kill list.
- Anything not decidable in the room becomes a memo with an owner and a deadline. No “we’ll discuss later.”
July
Summer focus week
- No planning, no meetings, no all-hands. One full week per team for deep work.
- The rationale: the year has 50 weeks of meetings and 2 weeks of holidays. A focus week is the only structurally protected deep-work surface.
- Output is optional. Not declaring an output is the point — the team picks the work.
- Companies that skip this lose senior engineers and PMs to companies that don’t.
August
Hiring quality review
- Pull the list of hires from the last 6 months. Manager rates each on a 4-point scale: regret hire / below bar / at bar / above bar.
- If any function has >30% “below bar,” the bar isn’t calibrated. Re-train the interviewers.
- Bar calibration session: cross-functional interviewers debrief 3 anonymized recent hires; consensus on score.
- Update the hiring rubric in writing. Hand it to the recruiting team for the H2 reqs.
September
Q4 planning + budget season
- Q4 OKR mapping in week 1.
- Budget season: finance asks for 2-year input. The CPO submits a 2-year capital allocation memo — people, infra, tooling.
- Run a “what would we cut at −20%” exercise. Not because you’re cutting; because the exercise reveals what’s actually load-bearing vs. what’s just there.
October
Q3 retro & Q4 launch
- Q3 retro: same one-question format. What changed our thinking?
- Closing-out conversations — any team member who is being managed out should know by mid-October. December is too late and it’s cruel.
- Q4 launch week. The biggest commercial quarter is now; the war room is non-optional.
November
Annual planning prep
- Board pre-read for the Q3 results meeting (separate from the Q4 board meeting, which lands in late January).
- Capital allocation discussion with finance: what’s the H1 hiring envelope, what’s the infra trajectory, what’s the M&A appetite.
- Leadership council (1 day): each function head presents their 1-page next-year plan. Cross-functional friction surfaced and resolved here, not in February.
- First draft of next year’s strategy one-pager. Circulate to leadership in week 4.
December
Annual close + Q1 commit + reflection
- Q4 retro + annual retro. The annual retro is one written document the CPO publishes to the company — what shipped, what was learned, what was killed, what carries forward.
- Q1 OKR mapping in week 1 of December (so the team has a runway). Don’t plan Q1 in the second week of January.
- Final commit memo: 1 page, the commitments that anchor the new year’s board narrative.
- Reflection: each leader writes 1 page on what they’d do differently. Read by no one but the leader. Filed for next December.
Customer council cadence
Twice yearly (March, September). 8–12 customers from your target segment, half-day, structured. Pre-work: each attendee reads a 2-page brief on what shipped + what’s coming. In-session: 90 minutes of structured feedback on the next 3 priorities, 90 minutes of “what would you spend money on next year that we don’t offer.” Output: a written memo to the company within 7 days — themes, quotes, decisions taken or deferred.
Who to invite. The customers most representative of your strategy — not your highest-paying, not your biggest fans, not your loudest. Pick segment, role, and use case to mirror Where to Play.
Board cadence
Quarterly board meetings + monthly written update. The monthly update is the protective shell around the quarterly meeting — nothing in the quarterly should be news. Monthly format: 1 page, sections are Metric of the Month / What Shipped / What Slipped / Asks. The quarterly meeting then runs the 8-slide structure with no surprises in the room.
Common annual-cadence failures
- Skipping the mid-year reset — the most expensive missed ritual. By September, drift is too embedded to recover this year.
- No summer focus week — the company that doesn’t protect deep-work time becomes the company that loses senior engineers to the one that does.
- Hiring waves disconnected from planning — reqs opened in the same month they’re needed. Senior hires take a quarter; you have to plan a quarter ahead.
- No board pre-read discipline — pre-reads sent the morning of the meeting, or not at all. The board reads it on the train; the meeting recaps the deck. Two hours wasted.
- Retros that don’t change anything — the three-bullet template gets filled out and filed. A retro is only useful if a behavior changes the next quarter; otherwise it’s journaling.