Your company just crossed 200 people. Eight departments, offices in two time zones, and a leadership team that no longer runs into each other in the hallway. Somewhere in the last year, the OKR process that felt crisp at 60 people started to feel like paperwork. So the instinct kicks in: add a check-in. Then another. Now there is a weekly OKR sync, a biweekly department roll-up, a monthly all-hands scorecard, and a quarterly review that takes two weeks to prepare. Everyone reports status constantly, and leadership still cannot answer a simple question on a Tuesday. Are we on track?
More check-ins did not fix alignment. They rarely do. The problem at 200 people is not that you check in too little. It is that your cadence asks the wrong ritual to do the wrong job.
More reporting is not more alignment
Here is the mistake almost every scaling company makes. When alignment feels shaky, they raise the frequency of status reporting, on the theory that if people talk about the goals more often they will stay closer to them.
But OKRs do not move on a weekly clock. Work moves weekly. A key result that measures activation rate or pipeline coverage barely shifts in seven days, and asking a team to re-score it every Monday produces one of two things: a number that did not change, or a number someone nudged to look like progress. Both are noise. You have added a meeting and subtracted nothing from the confusion.
A working operating cadence at 200 people separates the clock of work from the clock of goals. Work gets reviewed often, because it changes often. Goals get re-scored rarely, because they do not. Collapse the two into one weekly ritual and you get status theater dressed as rigor.
Weekly: the team beat, and it belongs to the team
The weekly beat is for the people doing the work, not for the executive team. Its job is to surface what moved and where a team is blocked, at the team level, in under thirty minutes.
Across time zones, run this async-first. A synchronous standup that forces someone in Berlin to join at 8pm to hear an update they could have read is a tax, not a ritual. Let teams post what moved and where they need a decision. Reserve live time for the blockers that genuinely need a conversation.
The weekly beat should not require anyone to assemble a report by hand. When progress is derived from the real work already living in Jira, Asana, Planner, or HubSpot, the weekly view already exists. The team lead owns this beat. Not the Chief of Staff, not the CEO.
Monthly: where departments reconcile
The monthly beat is where cross-department friction gets resolved. This is the ritual most companies are missing, and its absence is why the quarterly review always contains ugly surprises.
Once a month, department heads and the exec team look at the same picture: which goals have real work behind them, which are running on hope, and where two teams quietly depend on the same over-committed engineer. This is a reconciliation meeting. Capacity gets checked against commitments. A goal that looked green in isolation gets marked red because the team it depends on is underwater.
The monthly beat is owned by whoever owns operational rhythm, usually the COO or Chief of Staff. It is the connective tissue between the fast clock of weekly work and the slow clock of quarterly goals. Ninety minutes once a month saves you the two-week fire drill before every review.
Quarterly: the only ritual that touches the goals
The quarterly beat is the only place the OKRs themselves get set and scored. Nothing else in your cadence should be editing the goals.
At the quarter boundary, the exec team scores the quarter that ended and sets the OKRs for the one beginning, retiring whatever is dead along the way, each new goal with a single named owner and an explicit trade-off. Because you ran the monthly reconciliations, this review is not a discovery exercise. You already know the numbers. The quarterly is for judgment: what did we learn, and where does capacity go next.
The CEO owns the quarterly beat and cannot delegate it. When the CEO stops showing up to score goals personally, the whole cadence loses its teeth. The CEO's role in the operating cadence is the load-bearing wall here.
Who owns what, in one view
Take one thing from this: each ritual has exactly one owner and one job. Team leads own the weekly work review. The COO or Chief of Staff owns the monthly reconciliation. The CEO owns the quarterly goal reset. When ownership blurs, when the CEO starts running the weekly or the Chief of Staff quietly sets the goals, the cadence collapses back into meetings about meetings.
And the count of rituals stays small. Two hundred people can run on three beats. The failure mode is never too few check-ins. It is too many rituals, each doing a fraction of a job, none of them owned.
When progress and risk are derived from the actual work instead of narrated in a meeting, each beat can do its own job without borrowing time from the others. That is the model Vindaris is built around.
FAQ
Should a 200-person company run weekly OKR check-ins? Not on the OKRs themselves. Run a weekly review of the work, what moved and where a team is blocked, and leave the OKR scores alone until the monthly reconciliation and quarterly reset. Weekly re-scoring of goals that move on a quarterly horizon produces noise, not alignment.
Who should own the monthly business review at this size? Whoever owns operational rhythm, typically the COO or Chief of Staff. The monthly is a cross-department reconciliation, so it needs an owner with a horizontal view of the company rather than a single function.
How do time zones change the cadence? They push the weekly beat toward async and protect the quarterly as the one ritual worth getting everyone live for. Do not force a synchronous weekly meeting across a nine-hour gap to read status that could have been posted in writing. Save synchronous time for decisions and the quarterly reset.