The rhythm you run OKRs on matters more than almost anything else about how you run them, and it is the part teams think about least. They spend weeks agonising over how to word an objective and then give no thought at all to how often they will look at it, who will be in the room, and what each of those meetings is actually for. The result is a calendar full of OKR meetings that all blur into the same vague status update, which is the fastest way I know to make people resent the whole practice.
There are really two cadences in a working OKR system, and they do completely different jobs. Mixing them up is the most common cadence mistake there is.
The weekly check-in is for steering, not scoring
The weekly check-in, sometimes run fortnightly depending on how fast your work moves, exists to keep the quarter on course. Its job is operational. What moved since last week, what is blocked, what does the upcoming week need to look like to stay on track for the quarter’s targets. It is short, it is forward-looking, and it should feel less like a report and more like a team adjusting its aim.
The mistake teams make is treating the weekly check-in as a mini scoring session. They sit and debate whether a key result is at 0.4 or 0.5 this week, which is a waste of everyone’s time, because weekly noise in a metric tells you almost nothing. A key result can dip one week and recover the next for reasons that have nothing to do with your effort. If you score every week, you teach people to either panic at normal variance or to disengage because the number bounces around meaninglessly. The weekly conversation should be about confidence and obstacles, not grades. The honest weekly question is not “what is the number” but “are we still on track to hit it, and if not, what are we changing.”
The quarterly scoring is for learning, not steering
The quarterly scoring session is a different animal entirely. It happens once at the end of the cycle, it is backward-looking, and its job is to extract learning from what just happened. You look at where each key result ended up, you grade it honestly, and crucially you talk about why it landed where it did. A key result that scored 0.3 is not a failure to be glossed over. It is the most informative result in the room, because it is telling you something about either your assumptions or your execution that you did not know twelve weeks ago.
This is the meeting teams most often skip or rush, and skipping it is fatal to the whole system. The quarterly score is where OKRs either build a track record of meaning something or reveal themselves to be theatre. If you never close the loop with honest scoring, every target you set becomes a suggestion, and people treat suggestions accordingly.
Why the two get confused
The confusion between these two cadences comes from a reasonable instinct. People feel that if a metric matters, they should be looking at it constantly and grading it constantly. But constant grading is exactly wrong for a measure that is supposed to capture a quarter’s worth of change. You do not weigh yourself every hour to track a diet, because the hourly number is noise and the noise will either depress you or mislead you. You weigh yourself on a sensible interval and you judge the trend. OKRs work the same way. Watch the leading indicators weekly so you can steer, and grade the outcome at the interval that actually contains a meaningful amount of change.
A cadence that actually holds together
A rhythm I have seen work well across very different kinds of teams looks like this. Weekly, a short team check-in focused on confidence, blockers, and the week ahead. Monthly, a slightly longer review where you step back and look at the trend rather than the week, and where leadership can see across teams. Quarterly, a proper scoring and retrospective, followed immediately by setting the next quarter’s objectives while the lessons are fresh.
The reason most teams cannot hold this rhythm is not that they disagree with it. It is that maintaining three nested cadences manually, chasing updates, assembling the cross-team view, remembering what was committed three months ago, is genuinely tedious, and tedium is where good intentions go to die. This is the practical case for running the whole rhythm inside a proper OKR management platform, because the tool carries the cadence for you, prompts the check-ins, holds the history, and assembles the views, so that the meetings can be about thinking rather than about gathering.
Decide the rhythm before you write a single objective
If you are setting up OKRs, my strong advice is to design the cadence first, before you draft any objectives. Decide who meets weekly and what that meeting is for. Decide how scoring will work and who will be in the room when it happens. Put all of it in the calendar for the whole quarter in advance, so that the discipline does not depend on anyone remembering to schedule it.
Objectives written into a clear rhythm have a real chance of surviving the quarter. Objectives written into an empty calendar are just a document, and documents do not change anything on their own.
