Quarterly Planning Offsite Agenda
Two-day offsite agenda for quarterly planning, with pre-reads, async inputs, and decision outputs defined upfront.
What this template covers
Offsite planning sessions fail because they start with a blank whiteboard and end with no decisions. This agenda defines the pre-reads (last-quarter retro, customer insight synthesis, competitive scan, data refresh), the async inputs collected from each function, and the decision outputs (themes for next quarter, OKR drafts, investment shifts). Day one is inputs; day two is decisions. Product ops owns logistics, content, and follow-up.
The template
# Quarterly Planning Offsite — Two Day Agenda **Quarter being planned:** Q_ 20__ **Dates:** YYYY-MM-DD to YYYY-MM-DD **Owner:** Product Ops (logistics + facilitation) **Decision-maker(s):** CPO + functional VPs **Attendees:** PMs, design leads, eng leads, data lead, marketing rep, sales rep, support rep --- ## Pre-reads (sent 7 days before) The team must read these before day 1. No catch-up presentations on day 1. 1. **Last-quarter retro** — what shipped, what slipped, what we learned (PO authors) 2. **Customer insight synthesis** — top themes from the past 90 days of interviews and feedback (PM authors) 3. **Competitive scan** — three notable shifts in the market (PMM authors) 4. **Data refresh** — north-star, activation, retention, expansion, churn (Data authors) 5. **Financial guardrails** — the next-quarter budget envelope (Finance authors) 6. **CEO context memo** — strategic priorities for the half (CEO authors, 1 page max) --- ## Day 1 — Inputs (8 hours) | Time | Block | Format | Owner | | --- | --- | --- | --- | | 09:00-09:15 | Welcome, agenda, ground rules | Standing | PO | | 09:15-10:15 | Last-quarter retro discussion | Open table | PO + CPO | | 10:15-10:30 | Break | | | | 10:30-12:00 | Customer insight synthesis — themes ranked | Affinity map on wall | PMs | | 12:00-13:00 | Lunch | | | | 13:00-14:30 | Competitive + financial constraints | Presentation + Q&A | PMM, Finance | | 14:30-15:30 | "What problems are worth solving next quarter?" | Silent brainstorm → group → vote | All | | 15:30-16:30 | Theme drafting in small groups | Breakouts of 3-4 | PMs | | 16:30-17:00 | Theme readout, no decisions yet | Each group reports | All | | 17:00 | Close | | PO | **End-of-day artifact:** A list of 6-12 candidate themes, with sponsors named. --- ## Day 2 — Decisions (6 hours) | Time | Block | Format | Owner | | --- | --- | --- | --- | | 09:00-09:30 | Recap day 1, post candidate themes | Standing | PO | | 09:30-11:00 | Theme prioritization, dot-vote then debate | Forced ranking | CPO | | 11:00-11:15 | Break | | | | 11:15-12:30 | Resource allocation — match teams to themes | Whiteboard | CPO + Eng VP | | 12:30-13:30 | Lunch | | | | 13:30-14:30 | Draft top-line OKRs per theme | Small groups | PMs + their teams | | 14:30-15:00 | Out-of-scope list — what we are explicitly not doing | Group discussion | CPO | | 15:00-15:30 | Risk + dependency review | Round-robin | All | | 15:30-16:00 | Decision log review, follow-up owners assigned | Standing | PO | | 16:00 | Close, handshake on commitments | | CPO | **End-of-day artifact:** Draft OKRs per team, named theme owners, dated decision log. --- ## Decision log (filled live during the offsite) | # | Decision | Owner | Why | Date | | --- | --- | --- | --- | --- | | 1 | | | | | | 2 | | | | | | 3 | | | | | --- ## Follow-ups (PO drives within 5 business days) | # | Follow-up | Owner | Due | Status | | --- | --- | --- | --- | --- | | 1 | Publish written OKRs to the company | PMs | T+5 | | | 2 | Update roadmap doc with Now/Next | PMs | T+5 | | | 3 | Send written summary to absentees | PO | T+2 | | | 4 | Schedule mid-quarter redirect | PO | T+5 | | --- ## Ground rules (read aloud at 09:00) - Phones face down, laptops closed during decision blocks. - No recording — write it down instead. - Disagree-and-commit is fine. Silent dissent is not. - The PO has the floor when the conversation drifts more than 5 minutes off-topic.
When to use it
- Quarterly planning offsite
- Annual planning kickoff
- Post-reorg strategy reset
- New-leadership alignment
How to adapt it
Copy the template above into Google Docs, Sheets, Notion, Airtable, or Confluence. Keep the section order intact, later sections often reference data entered earlier. Replace the example values with your own, then review quarterly and re-circulate to stakeholders.
Related templates
Quarterly OKR worksheet tuned for product operations leaders, outcomes over output, with confidence scoring and mid-quarter check-ins.
Now/Next/Later roadmap format with explicit discovery, delivery, and investment phases, suitable for board and customer-facing reviews.
Templates are drafted from public Product Operations research and reviewed by practicing PO leaders. Free to copy and modify for internal company use.
Frequently Asked Questions
Offsite planning sessions fail because they start with a blank whiteboard and end with no decisions. This agenda defines the pre-reads (last-quarter retro, customer insight synthesis, competitive scan, data refresh), the async inputs collected from each function, and the decision outputs (themes for next quarter, OKR drafts, investment shifts). Day one is inputs; day two is decisions. Product ops owns logistics, content, and follow-up.
This template is written for Product Operations teams at software companies sized 50-500 employees. Common use cases include: Quarterly planning offsite; Annual planning kickoff; Post-reorg strategy reset.
The template is designed as a Google Doc. Copy the structure directly into your own Google Docs, Sheets, Notion, or Airtable workspace. No attribution is required for internal company use.
Start with the section structure exactly as published, then modify field names to match your organization's vocabulary. Most teams complete a first pass in 30 minutes and a polished version within one working week.