// enterprise okr operating rhythm

The enterprise operating rhythm. Three clocks, one company.

We like a quarterly rhythm. What's changing, with AI especially, is how long a goal takes to stand up and finish. Some now take weeks, not quarters. So the quarter stops being a big planning event and becomes a check-in and, where the evidence says so, a re-set. Here's the rhythm we install so goals move at the speed of the work and the functions don't get raided along the way.

Matt Roberts
By Matt Roberts, co-founder, ZOKRI
Enterprise OKR Implementation Lead
// the three clocks

Set annually. Re-set quarterly. Work continuously.

AnnualStrategy, resource allocation, persistent teams, functional goals, budgetOnce, plus a mid-year check
QuarterlyA check-in, not a planning marathon: progress and confidence reviewed against the metric models, goals continued, closed or re-set, capacity rebalancedFour times, short
ContinuousGoals stood up and closed as the work allows, weekly check-ins, obstacles raised earlyEvery week
// set once a year

Do the expensive trades when they are cheap.

The annual set is the one moment every division is in the room and nobody is committed yet. That makes it the cheapest time in the year to move people and money. Leave a resourcing question for week six and it becomes a raid, and everyone remembers who did the raiding.

Two or three strategic goals: the real bets for the year.
One operational excellence goal per function, each tied to a strategic goal by a logic thread anyone can check.
Persistent cross-functional teams, resourced the day they form.
A metric model for each strategic goal, reviewed at every quarterly check-in as a living model, not an annual artefact.
Five to ten health KPIs, kept deliberately separate from the goals.
Budget and forecast connected, so the money and the goals sit in the same conversation.
// re-set every quarter

The quarter is a check-in, not a big bang.

With AI in the work, a goal can go from idea to done in a few weeks, and waiting for the next quarter to start it is just waiting. So goals start when they're ready and finish when the outcome is reached. The quarter is where everyone stops, looks at the evidence together, and decides what continues, what closes and what gets re-set. Shorter, lighter, and far more useful than a two-day planning marathon.

What flows is the layer beneath the objectives. Annual objectives stay steady; the outcomes and goals beneath them start and finish as evidence and capacity allow. One rule keeps it sane: goals can flow, people mostly can't. A team can pick up a new goal with capacity it already holds. Anything that needs another team's people waits for the quarterly re-set, when trades are cheap.

// the guardrails

Three rules that stop the strategy eating the functions.

01Define what "confidence rose" means

Strategic teams get first call on resource when the evidence moves. Fine, but only if the evidence bar is written down: a validated assumption, a test result at a stated level, a named risk retired. Otherwise priority goes to whoever tells the best story.

02Cut the donor's goal in the same breath

When a function gives up people, its own goal is formally reduced in the same conversation. Skip that and you've quietly raised its bar, guaranteed a miss, and taught every function to sandbag next year.

03Protect a floor

Every function keeps a defended minimum of capacity for its own goal and for keeping the lights on. It's a number agreed at the annual set, not a judgement made later, under pressure, by whoever is having the loudest quarter.

// what to watch

Where this rhythm gets tested.

01People with two homes

Anyone in a persistent cross-functional team has a team and a function. Decide explicitly who owns their development, their review and their career, or it defaults to nobody.

02Annual goals drifting into wishes

The quarterly check-in is the defence. If a strategic goal cannot be discussed against evidence each quarter, it was not measurable enough to set.

03The hidden cost

Health KPIs must include the donor functions. If priority resourcing has a cost, it should show up in the numbers rather than in an exit interview.

// questions to ask

Q&A

Should enterprises run OKRs quarterly? +

Yes, as a rhythm. Keep the quarter as the shared check-in and re-set point, but stop treating it as the only moment goals can start or finish. With AI shortening how long work takes, goals should start when they are ready and close when the outcome is reached.

How often should large companies review OKRs? +

Weekly check-ins inside teams, a quarterly check-in where progress and confidence are reviewed and goals are continued, closed or re-set, and an annual set for strategy and resourcing.

Can OKRs and the annual budget work together? +

Yes, and they should. Do resource allocation at the annual set alongside the budget, so strategic goals, team formation and money are agreed in one conversation rather than reconciled afterwards.

How is AI changing OKR cycles? +

It is shortening how long many goals take to stand up and complete. The quarter remains a useful shared rhythm, but becomes a check-in and possible re-set rather than a big planning event, with goals flowing in between.

// related
Enterprise OKR ImplementationThe full approach, from first look to one way of running.See the approach →
Why Enterprise OKRs Are HardFourteen reasons, and what helpsRead →Enterprise OKR GovernanceSteer the portfolio, not the peopleRead →Converging Goal FrameworksOKRs, KPIs, Hoshin and EOSRead →OKRs for MultinationalsOne rhythm, many marketsRead →Multi-divisional OKRsOne group, one way of runningRead →
// who you'd work withSenior people who've done this at enterprise scale.100+ OKR implementations. 15+ enterprise organisations.Meet the team →

We'll show you how it works and share case studies.

Then you decide.

Book a meeting →OKR Implementation Review