Annual Planning for Product & Support Ops

Annual planning follows a cascading structure from company to function to team. Phase 1 — Company strategy (typically October for a January fiscal year start): the executive team defines the company-level priorities for the year — top 3 strategic bets, revenue target, growth model emphasis (new business vs. expansion vs. international). These are the inputs that departmental plans must address. Phase 2 — Departmental planning (October–November): each department head (VP of Product, VP of Support, VP of CS) develops a departmental plan: how does their function contribute to each company priority? What resources (headcount, tools, budget) are required? What trade-offs are being made (what is deprioritized to focus on what matters most)? Product Ops supports this phase by providing data: last year's delivery performance vs. plan, the upcoming year's product bet sizing, and the resource modeling. Phase 3 — Integration and negotiation (November): department heads present plans to the executive team, receive feedback, and negotiate the reconciled priorities and budgets. Phase 4 — Cascade (December): approved plans are communicated to teams, OKRs are set at the team and individual level, and tooling and hiring plans are operationalized.

OKR setting for Product Ops must balance ambition with achievability and avoid the most common failure modes. Common OKR failures: Key Results that are activities rather than outcomes ("Launch 3 features" instead of "Increase activation rate to 65%"); Objectives that are so vague they cannot be evaluated at year-end ("Make the product better in 2025"); too many OKRs (three Objectives with three Key Results each = nine measurable targets; more than this creates priority diffusion). Product Ops OKR design principles: each Key Result must be a metric with a current baseline, a target, and an unambiguous measurement method. Example: "KR: Increase the percentage of enterprise accounts with a completed success plan from 44% (current) to 80% (target), measured monthly via Gainsight success plan completion report." "Ambitious but achievable": OKRs calibrated so the team achieves 70% of KRs with excellent execution — if 100% are achieved, the targets were too conservative. OKRs are reviewed monthly (brief), using a simple RAG (Red/Amber/Green) status update, and a mid-year revision is scheduled for Q2 if company priorities have shifted significantly.

Annual headcount requests must survive CFO scrutiny — the presentation must demonstrate that the requested headcount is the minimum needed to achieve the committed business outcomes, and that alternatives to hiring have been genuinely considered. Effective headcount presentation structure: (1) Current state — current team size, current workload metrics (tickets per agent, accounts per CSM, sprint velocity), and current performance against target (are we meeting SLA and CSAT targets with current headcount?). (2) Growth projection — the forecasted increase in demand for the coming year (based on revenue growth plan, product complexity increases, and new market expansion). (3) Efficiency improvement plan — specifically, what non-headcount improvements will offset some of the demand growth (AI tools, process improvements, self-service investments) — and how much demand growth they are projected to absorb. (4) Residual gap — the demand growth that efficiency improvements cannot absorb, requiring headcount. The headcount request is the minimum to cover this gap. (5) Risk of no additional headcount — projected SLA compliance rates, CSAT scores, and churn risk if the headcount request is not approved. This last section is the most persuasive element — connecting headcount denial to specific revenue risk creates the business case that pure efficiency arguments cannot.