From weekly to quarterly to annual. The full operating system.

Why the room changes — and why it should feel exhausting

The quarterly business review — the QBR — ran three-quarters of a day to a full day, and most of the time we held it offsite, out of the office. That's strategic, not logistical. It sends a message: this is important, this isn't business as usual. And not being in the office meant we could actually focus instead of running to whatever fire started down the hall. Leadership team only, and the attention was 110% on the session — no phones, no Slack, no distractions. Short breaks and lunch, that's it.

That exhaustion is the tell. The weekly meeting runs on rails — same agenda, ninety minutes, in and out. The QBR is a different kind of effort entirely: getting above the business instead of operating inside it, which is precisely the thing that almost never happens in a weekly.

Anatomy of the QBR

The agenda, in roughly the order we ran it. Open with expectations for the day. Then the look back at the previous quarter: what went well and what didn't, by team and by individual. Review and grade the quarter's rocks with a percent completion against each. Work any major IDS issues that need to be resolved before you can honestly look forward. Review the scorecard itself — not just the numbers, but whether they're the right numbers, adding and removing metrics as needed.

Then the strategic core: a section-by-section review and refinement of the entire VTO — the Vision/Traction Organizer, EOS's two-page strategic plan — including the three-year and one-year views and the annual goals that live on it, making any strategic adjustments the quarter's evidence demands. Only then do you look forward: brainstorm ideas for new company rocks and set rocks for each member of the leadership team. (The pitch-and-decide mechanics of that brainstorm are covered in the rocks piece.) Close with a short reflection on the day and grade the meeting — the same ritual that ends the weekly L10, at a different altitude.

What thirteen weeks feed up

Here's what makes the QBR something other than an offsite with better snacks: you don't walk in cold. The weekly cadence delivers the quarter's evidence to the door — your performance against your rocks, a register of issues (hopefully many of them solved), and thirteen weeks of trends on your key metrics. Strategy at the QBR starts from data, not from whoever has the most confident recollection of the quarter.

A red trend on the scorecard doesn't just generate weekly issues — it can become the next quarter. The example I always come back to: we had a trend we didn't like on churn, showing up consistently in our scorecard over the prior quarter. So we made the entire QBR — and the next quarter's rocks — about solving that churn problem, teeing up several projects to address it. That's the continuity working as designed: the week surfaces the signal, the quarter mobilizes against it.

Annual planning — and the horizon beyond the year

Annual planning looked like a QBR, but longer — typically two days. Same skeleton: the look back at what went well and what didn't, for the quarter and for the year, the full VTO review, and then the part that makes it the annual: creating a new set of annual goals or themes. Those goals were super important, because they're what tie together the rocks of the coming year's quarters — each quarter's priorities ladder up to them. The artifacts that came out the other end: an updated VTO, a new or refined scorecard, the new annual goals, and Q1's rocks, ready to run.

Above the annual goals sat the longer horizon, and we actually used it — it wasn't a poster. We maintained a three-year picture and a five-year BHAG, plus a painted picture — the long-form, vivid description of what the company looks like a few years out. They were part of the working process, including setting ARR targets three years ahead. The one layer we never did was the ten-year target: too long in tech. I'll add the honest asterisk from the failures piece: the weakness that crept into our system over time wasn't the planning structure, it was that some rocks came out a bit too generic, too business-as-usual — the machinery was right, and it still deserves your sharpest goals running through it.

The broadcast layer: the State of the Company

Quarterly and annual planning were leadership-only, and that's correct — but a strategic plan the leadership team keeps to itself is barely better than no plan. An essential part of EOS, or any process, is making sure the larger team is involved and understands the company direction. The mechanism is the State of the Company meeting, which followed every QBR and the annual planning session.

These are strategic all-hands: communicate the goals, the rocks, and the priorities to the whole team, and review the VTO in depth — the core values, the target market, the BHAG, all of it. That's the loop closing downward. The weekly cadence feeds evidence up into the quarter; the quarter and the year broadcast direction back down to everyone. Without that last step, you have a leadership team with a strategy and a company without one.

When the year misses — and why the loop beats set-and-forget

What about the year that goes sideways? Our annual plan was never just an ARR number. It carried a set of goals independent of any revenue target — pay down technical debt, improve the product's design and usability — so a revenue miss never derailed the whole year. And when we did fall behind the ARR target, the system responded the way it's supposed to: rocks showed up to attack the gap — testing new customer acquisition channels, for instance. But we never moved the goalposts on the year's ARR forecast. That's the same rule we held at the weekly level, applied at the annual one: the plan stays put, and the work changes to chase it.

So here's what I'd tell a founder running a tight weekly cadence with nothing above it. You need the quarterlies and annuals for three reasons. Strategy — they're the forcing function that lets you and the leadership team get above the business, gain perspective, see where you're going, and set a north star; that almost never happens in a weekly. Accountability — they force a level of accountability on strategic projects that weeklies alone never will. Flexibility — your strategy and direction are a living, breathing organism that should be reviewed on a regular basis, and this rhythm is what supports that. The weekly meeting keeps the company executing. The quarter and the year are what make sure it's executing on something worth doing.