// the weekly loop

OKR check-ins that change confidence, not report status.

The weekly check-in exists to help achieve the goal. The moment it becomes status reporting, it is overhead with a calendar invite.

Here is the test of a check-in worth having: did the goal's chances improve because the meeting happened? A status meeting reports the past. A check-in works the future: what we believe, what the evidence says, what we will do about it this week. Same thirty minutes, entirely different instrument.

Before anyone enters the room

The reporting happens before the meeting, not in it. Each owner updates their Key Result progress, their confidence, High, Medium or Low, and a comment on why. This is deliberately cheap: five minutes at a desk. It means the meeting starts from a shared picture instead of spending its first twenty minutes building one, and it creates the data trail that makes quarter-end retrospectives honest.

The agenda that works

Confidence first, with evidence, per person: not "how do you feel" but "what did you see this week that moved your confidence". Then key learnings. Then issues, and here discipline matters: deep-dive now only if it is quick, otherwise schedule a workshop and protect the check-in's length. Then plan the week's initiatives, process commitments and experiments, because the plans, not the progress bars, are where the goal gets achieved. Capture actions, close.

Occasionally run a ROTI survey on the meeting itself. And if somewhere in the discussion it becomes clear the OKR no longer makes sense, say it out loud. There is a proper route for that, changing or killing an OKR mid-quarter, and taking it is a sign of a healthy system, not a failed one.

The silence tell

The most diagnostic moment in any check-in is when there is nothing to talk about. Little week-to-week discussion is not a sign that things are going smoothly. It is a sign the OKR is either not being worked, is under-resourced, or was never a real bet in the first place. A genuine step-change attempt generates evidence, surprises and decisions every single week. Quiet check-ins are how you find out your OKR is furniture.

How this connects

Philosophically, the weekly cadence is an instance of a deeper principle in our methodology: honing beats transformation. Cheap corrections, made weekly, mean the organisation never needs the expensive reckoning made late. It is the same logic that makes outcome-focused Key Results non-negotiable: the check-in can only steer if the Key Results measure something that can actually move mid-quarter, which is also why leading indicators make better weekly instruments than lagging ones. And the confidence scores are not decoration: graded honestly, they are the earliest warning system a leadership team has, weeks ahead of the metrics themselves.

In practice

If your check-ins have drifted into status theatre, change one thing first: ban progress reporting from the meeting and require it beforehand. The room, freed from reciting the past, has nowhere to go but the future. Most teams find the meeting gets shorter and the goal gets faster in the same fortnight.

From the ZOKRI OKR Handbook, the methodology we install and maintain.

// connected concepts
Key Result → Honing vs Transformation → Explore all 141 notes →
// put it to work

Reading about method is not the same as running it. We install this system and build the capability that stays.

See check-ins run themselves in the AI Business OS →

The log the check-in keeps alive

Every check-in touches the team's Issues and Obstacles Log: new issues added, stale ones aged, each with an owner and a date. The log and confidence discipline each other: a confidence drop must cite an issue, and an issue that survives two consecutive check-ins unresolved escalates by rule, not by mood. The science behind the ritual sits in the pre-mortem and implementation intentions.