The Check-In Is Where OKRs Live or Die
Setting OKRs takes a few hours. Executing them takes a quarter. And the difference between the organisations that make OKRs stick and those that abandon them by week six almost always comes down to one thing: the weekly check-in. If your OKR programme is struggling, our OKR Health Check guide can help you diagnose the root cause.
Research across hundreds of teams consistently shows that those with weekly OKR check-ins complete significantly more of their objectives than those without. Data from the 2026 OKR Benchmark Report suggests an improvement of over 40%. That is not a marginal gain — it is transformational.
Yet most teams either skip check-ins entirely, run them as status theatre, or conflate them with sprint ceremonies. This guide gives you a practical, tested structure for check-ins that actually drive progress.
What a Good OKR Check-In Is (And Is Not)
It IS:
- A 15–20 minute, focused conversation about strategic progress.
- A space to score Key Results, identify blockers, and agree on next actions.
- An early warning system that flags risks before they become crises.
- A rhythm that keeps OKRs visible and relevant throughout the quarter.
It IS NOT:
- A status meeting where people read task updates aloud.
- A sprint ceremony (keep your standups and retros separate).
- A performance review or accountability tribunal.
- A monthly or quarterly exercise (weekly is the minimum effective cadence).
The 15-Minute Check-In Structure
This structure works for teams of 4–12 people. Run it weekly, same time, same day. Consistency matters more than duration.
Minutes 1–2: Score Each Key Result
Each Key Result owner gives a confidence score on a simple traffic light:
- Green: On track. No action needed.
- Amber: At risk. Needs attention this week.
- Red: Off track. Needs immediate intervention.
Do not spend time on green items. Move straight to amber and red.
Minutes 3–10: Discuss Amber and Red
For each at-risk Key Result, answer three questions:
- What has changed since last week?
- What is the specific blocker or risk?
- What is the single most important action to move this forward this week?
Be ruthless about staying focused. The goal is to identify the action, not to solve the problem in the meeting. Complex issues get a follow-up conversation outside the check-in.
Minutes 11–14: Cross-Dependencies
Surface any dependencies between OKRs across teams. If your progress is blocked by another team's deliverable, this is where it gets flagged. The OKR owner takes the action to resolve it.
Minute 15: Commitments
Each person states their one commitment for the coming week — the single action that will have the biggest impact on OKR progress. Write it down. Review it next week.
Five Rules That Make Check-Ins Work
- 1. Same time, same day, every week. Consistency creates habit. Sporadic check-ins are worse than none because they signal that OKRs are optional.
- 2. Score before the meeting. Key Result owners should update their scores before the check-in starts. This saves time and ensures the conversation is about action, not catching up.
- 3. Keep it to 15 minutes. If your check-in regularly runs over, you are either discussing too many OKRs (narrow the focus) or solving problems in the meeting (take them offline).
- 4. One owner per Key Result. Shared ownership leads to diffused accountability. One person owns each Key Result. That does not mean they do all the work — it means they are responsible for ensuring progress happens.
- 5. Make it visible. Display OKR scores on a shared board, whether physical or digital. Visibility creates accountability without micromanagement. If your tools are not supporting this, our article on why OKR software is not enough explains what to look for.
What to Do When OKRs Go Off Track
An off-track OKR is not a failure — it is information. When a Key Result goes red, the team has three options:
- Recommit: Double down on the original target. Identify what needs to change in approach and reallocate resources.
- Revise: Adjust the target based on new information. This is not cheating — it is responding to reality. Document why the target changed.
- Retire: In rare cases, an OKR becomes irrelevant mid-quarter because the strategy has shifted. Retire it deliberately and communicate why.
The worst option is to do nothing and let it drift. That is how OKR programmes die.
The Quarterly Rhythm: Check-Ins in Context
Weekly check-ins sit within a broader quarterly cadence:
- Week 0–1: Set and align OKRs. Ensure every team's OKRs connect to the organisation's strategic priorities.
- Weeks 2–12: Weekly check-ins. Score, discuss, act.
- Week 12–13: End-of-cycle review. Score final results, run a retrospective on the OKR process itself, and feed learnings into the next quarter's planning.
Teams that run structured retrospectives at the end of each OKR cycle complete significantly more objectives than those that skip them. The retro is where you improve the system, not just the goals. For more on making OKRs stick beyond the first cycle, see Aaron's OKR Forum talk.
Making Check-Ins Stick
The hardest part of the OKR check-in is not the structure — it is the consistency. Here are three practical tips:
- Start small. If your team has never done OKR check-ins, start with one OKR and build from there.
- Protect the time. Block it in the diary and treat it as unmovable. The moment check-ins become optional, they stop happening.
- Celebrate progress. Acknowledge movement, even partial. OKRs are stretch targets — 60% progress on an ambitious Key Result is worth recognising. If you are looking to integrate check-ins with your existing performance management, our guide on blending OKRs and PDRs covers the practical details.
Ready to put this into practice? Book a free 30-minute consultation with McKenna Agile Consultants. No sales pitch — just a conversation about where you are and what would actually help.
