The weekly review is the heartbeat, but a heartbeat isn't a circulatory system. The week needs somewhere to roll up — a quarterly rhythm that turns thirteen weeks of evidence into the next quarter's priorities, and an annual one that decides what the year is actually for. Miss the upper levels and the weekly cadence executes beautifully toward goals nobody has re-examined since January. Here's the full stack, level by level.
What thirteen weeks of evidence buys you
Walk into quarterly planning without a weekly cadence and the first half-day is archaeology: reconstructing what actually happened from memory, chat scroll, and whoever speaks most confidently. Walk in with one and the evidence is already assembled — thirteen scorecard readings per number, every goal's track record, the issues that kept resurfacing, the meeting ratings themselves. The quarterly review stops being a debate about what happened and becomes a decision about what to do, which is the entire productivity difference between planning days that produce priorities and planning days that produce slides.
The quarterly planning day
One full day, ideally out of the building. The inputs: last quarter's goals (each one done or not done — honestly), the scorecard's thirteen-week story, and the issues list's greatest hits. The output is deliberately small: three to seven priorities for the next ninety days, each specific, finishable, and owned by exactly one name — what EOS calls Rocks, though the doctrine works under any vocabulary. The other quarterly job is recalibration: goals that ran green all quarter get raised or retired, numbers that earned a seat get one, and stale targets get re-derived from what the new plan requires. The free quarterly planning kit is this exact day in spreadsheet form.
The annual layer
Annual planning answers the questions a quarter is too short to hold: what does this year need to be true — revenue, headcount, the two or three bets that define it — and what does that imply for Q1? The output isn't a fifty-page plan; it's a handful of year-level targets, the first quarter's priorities derived from them, and a scorecard revised to measure the year you're actually attempting rather than the one you finished. Annual sets direction once; the quarters steer; the weeks execute. Each level exists so the one below it doesn't have to improvise.
Broadcasting back down
The step most teams skip: the rhythm has to close the loop. After every planning cycle, the whole company hears the output — the priorities, the reasoning, the scoreboard for the quarter — in a short state-of-the-company session. Skip it and the operating system becomes a leadership-team secret: the people doing the work watch priorities shift without explanation and conclude, reasonably, that the goals are theater. Fifteen minutes a quarter of saying it out loud is what makes the cadence a company rhythm instead of a meeting series.
Why rhythm beats resolution
Set-and-forget annual goals fail for the same reason resolutions do: twelve months is too long a feedback loop for a moving business. The stack fixes the loop lengths — the week catches problems in seven days, the quarter re-aims every ninety, the year holds the direction steady enough to compound. None of the levels works alone. The week without the quarter executes toward stale goals; the quarter without the week plans on folklore; the year without both is a memo. Together they're an operating system.