OKR are written in a half-day workshop. They succeed or fail in thirteen meetings of thirty minutes. Teams that skip the weekly check-in rediscover their OKR in week 12, when it is too late to change anything.
The agenda
The check-in has a fixed structure and a fixed slot, ideally early in the week when the data of the last week is available.
- Minutes 0 to 10: each owner reads the current value of the key result from the data source and gives a confidence from 0 to 10.
- Minutes 10 to 20: for each key result with a confidence below 7, or one that dropped by two points, the team asks what is in the way.
- Minutes 20 to 27: one action per obstacle, with an owner and a date. Escalations are named.
- Minutes 27 to 30: initiatives done last week and planned for next week.
Health metrics are discussed only when one is out of range. Their place is the daily meeting.
Confidence is a forecast
The current value tells where the team stands. The confidence tells where it will end. 7 means likely with the current plan, 5 means a coin flip, below 5 the plan must change.
Confidence changes are the most useful signal of the meeting. A key result whose value is still on track but whose confidence drops from 8 to 5 is a warning that numbers alone do not show yet.
A worked check-in
Logistics, week 6 of the quarter:
| Key result | Value | Confidence | Comment and action |
|---|---|---|---|
| On-time shipment | 93.8 percent | 6, from 7 | Late confirmations from planning on Fridays. Planning lead joins on Friday at 13:30 from week 7. |
| Expedited freight | EUR 2,600 this week | 7 | Carrier slot booking works. No action. |
| Picking errors | 5.1 per 1,000 lines | 8 | Second scan at packing live since week 4. |
| Multi-zone pickers | 46 percent | 4, from 6 | Training slots canceled twice for volume peaks. Escalation: protect the Tuesday slots. |
Two actions, one escalation, done in 25 minutes. Without the check-in, the training problem would have shown up in the final score, not in week 6.
Rules that keep it short
Values come from the data source, not from memory. If the value is not available on Monday, fixing the data flow is the first action.
No status presentations. Each owner speaks for about a minute. Details go into the action list.
Same time, same place, every week. Put all thirteen dates into the calendar in planning week. A check-in that moves around gets canceled.
Visible to all. Update the team board or the shared list during the meeting, not afterwards.
The mid-quarter review
Once per quarter, around week 7, the leader joins the check-in for 45 minutes. The question is not why a number is behind. The question is which obstacles the team cannot remove alone, and what the leader will do about them. This review is often where capacity is protected and dependencies are enforced.