---
name: yearly-planning-meeting
description: Use when asked to plan or run an annual planning meeting — setting the organization's yearly strategy, budget, and top-level objectives — as the longest-horizon planning cadence in this collection, feeding weekly-planning-meeting's shorter execution cycle and drawing on vision-mission-values and strategic-balanced-scorecard.
---

# Yearly Planning Meeting

A yearly (annual) planning meeting sets an organization's strategic
direction, budget, and top-level objectives for the coming year — the
longest-horizon planning ritual most organizations run regularly, distinct
from [[weekly-planning-meeting]]'s short-cycle execution planning
that operates *within* the boundaries this meeting sets.

## What it typically covers

- **Strategic review** — how the past year performed against its
  objectives, and what that implies for the year ahead (see
  [[agile-reflection]]'s reflection discipline applied at annual
  scale).
- **Vision/mission/values check-in** — confirming the organization's
  foundational statements still hold, or revising them if genuinely
  necessary (see [[vision-mission-values]] — these shouldn't
  change often, but a yearly cadence is a natural checkpoint to ask).
- **Top-level objectives** — the year's [[objectives-and-key-results]]
  or [[north-star]] metric targets, and/or an update to a
  [[strategic-balanced-scorecard]]'s destination statement.
- **Budget allocation** — resourcing decisions across teams/initiatives
  for the year, connecting strategic priority to actual funded capacity
  (see [[portfolio-management]]'s capacity-based sequencing logic).
- **Major initiative selection** — which large bets/programs the
  organization will pursue, and which it will explicitly decline (see
  [[portfolio-management]]'s kill-criteria discipline for the
  "declining" half of this, which is as important as choosing what to
  fund).

## Why the cadence matters

A yearly cycle is long enough to make a real strategic bet meaningful
(a quarter is often too short to judge whether a strategic direction is
working) but short enough to course-correct before too much has been
invested in the wrong direction. Organizations in genuinely fast-moving
markets sometimes shorten this to a rolling or semi-annual cadence
instead — the yearly interval is a common default, not a fixed law.

## Common pitfalls

- **Treating it as a rubber-stamp of leadership's pre-decided plan** —
  if input from across the organization isn't genuinely sought (see
  [[agile-charter]]'s diverse-stakeholder principle applied at
  annual scale), the exercise produces compliance rather than real buy-in.
- **Setting objectives disconnected from actual budget/capacity** — an
  ambitious annual plan with no corresponding resourcing decision is
  aspiration, not a plan; see [[portfolio-management]]'s warning
  about approving more than capacity can actually support.
- **No mechanism to revisit the plan mid-year** — treating annual
  planning as fixed for 12 months regardless of what's learned along the
  way misses the chance to course-correct; most organizations pair this
  with shorter review cadences (quarterly OKR check-ins, or the weekly
  cycle in [[weekly-planning-meeting]]) precisely to catch drift
  early.
- **No connection to the prior year's actual results** — planning the new
  year without a genuine look back at what worked and didn't repeats
  avoidable mistakes.

## Learn more

- [[weekly-planning-meeting]] for the short-cycle execution planning operating within this meeting's yearly boundaries.
- [[vision-mission-values]], [[strategic-balanced-scorecard]] for the strategic inputs this meeting reviews or sets.
- [[portfolio-management]] for the capacity/prioritization discipline behind resourcing decisions made here.