The weekly OKR check-in that keeps a quarter on pace

A weekly OKR check-in is a 15-minute ritual where each Key Result owner answers three questions: what’s the number this week, are we on pace, and what’s the next action. Teams that run this every week for all 13 weeks of a quarter catch a slipping goal by week 4 instead of discovering it at the week-13 readout.

OKRs don’t fail at the planning offsite. They fail in the eleven quiet weeks afterward, when nobody looks at them again until the readout. The fix isn’t a better planning template. It’s a small, boring, weekly habit.

Fifteen minutes, three questions

For each Key Result, the owner answers:

1. What’s the number this week? Log the actual. No number is itself a signal.
2. Are we on pace? Compare to where you’d expect to be by now. Behind is fine in week 3; behind in week 10 is a decision.
3. What’s the one thing that moves it? Not a status update, but the next concrete action and who owns it.

That’s it. The discipline is in doing it every week, not in doing it well once.

Surface the stall, don’t bury it

The whole job of the check-in is to make a stall impossible to ignore. A Key Result with no fresh number, or a pace pill that just flipped to “behind,” should be loud. Hespia’s weekly AI digest does exactly this: it emails each owner what moved, what stalled, and what needs a nudge, timezone-aware, every week.

End the quarter with no surprises

Run the check-in for thirteen weeks and the review call writes itself: you already know which Objectives landed, which slipped, and why. The readout becomes a confirmation, not a reveal.