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.