How to Conduct OKR Check-In Meetings and Progress Reviews
This skill teaches you how to run structured OKR check-in meetings at weekly, bi-weekly, and quarterly intervals so your team stays accountable, surfaces problems early, and adjusts course before it is too late.
Run a weekly or bi-weekly OKR check-in meeting by having each key result owner update their current metric, assign a red/yellow/green confidence score, and flag blockers. Spend 80% of the meeting on items scored yellow or red. End with clear owners and deadlines for unblocking actions. Keep the meeting under 30 minutes for teams of 5-8 people.
Outcome: Your team develops a reliable rhythm where progress is visible, blockers are resolved within days instead of weeks, and end-of-quarter OKR scores stop being a surprise.
Prerequisites
- Familiarity with OKR structure (Objectives paired with measurable Key Results)
- A set of active OKRs already written and assigned to owners
- Access to a shared tracking tool or spreadsheet where OKR progress is recorded
- Basic facilitation skills for running a focused meeting
Overview
Setting ambitious OKRs is only the first half of the Objectives and Key Results (OKRs) framework. The second half, the part most teams underinvest in, is the ongoing rhythm of check-ins and reviews that turns static goals into living instruments of execution. Without a regular OKR check-in meeting cadence, objectives drift out of focus within two to three weeks, teams rediscover their OKRs only at scoring time, and the entire framework devolves into a quarterly paperwork exercise rather than a tool for daily prioritization.
An OKR check-in meeting is a short, structured session where key result owners report their current metric value, declare their confidence level in hitting the target by end of quarter, and surface anything blocking progress. The meeting is not a status report where everyone recites what they did last week. It is a problem-solving session. The bulk of time goes to items that are off track, because on-track items need only a quick acknowledgment. This shift in attention, spending 80% of your time on 20% of the OKRs that are struggling, is what separates effective check-in meetings from performative ones.
The skill covers two distinct meeting types. The first is the weekly or bi-weekly check-in, which is a 15-30 minute tactical session focused on current-quarter OKR progress. The second is the quarterly retrospective, which is a longer 60-90 minute session at the end of each cycle where you score and grade OKRs, reflect on what worked and what did not, and feed lessons into the next OKR planning session. Mastering both meeting types produces a concrete artifact each time: an updated OKR tracker with current values, confidence scores, and a dated list of committed unblocking actions with owners and deadlines.
Teams that run disciplined OKR check-in meetings consistently outperform those that set-and-forget. The practice creates a lightweight accountability loop, surfaces misalignment between teams early enough to fix it, and builds the institutional muscle memory that makes each subsequent OKR cycle better than the last.
How It Works
The OKR check-in meeting works by compressing the feedback loop between goal-setting and goal-measurement from quarterly (too slow to course-correct) to weekly (fast enough to act). The underlying mechanism is simple: when you force a confidence prediction at regular intervals, you create a system that identifies problems before they become crises.
The core of the meeting is the confidence score, typically expressed as a red/yellow/green rating or a numerical probability (e.g., 30%, 60%, 90%) of achieving each key result by the end of the quarter. This score is the engine that drives the whole meeting. Green items move fast: the owner states the current metric, says "on track," and the group moves on. Yellow and red items get real airtime, because they represent the places where the team's plan is breaking down and intervention can still change the outcome.
This approach works because of a principle borrowed from exception-based management. Flat status reports treat every item equally, which means a team of eight people with four OKRs each could spend 45 minutes hearing that 28 items are fine before getting to the 4 that actually need discussion. The confidence-first format inverts this. You identify the exceptions immediately, and the meeting becomes a focused problem-solving session rather than a broadcast.
The weekly check-in targets operational problems: a dependency on another team that is not moving, a metric that flatlined because the experiment failed, a resource constraint that was not visible at planning time. These are solvable within the quarter if caught early. The quarterly retrospective targets systemic problems: did we set the right objectives, did our key results actually measure what mattered, is our cadence and cycle structure working.
The confidence scoring mechanism also counteracts two common cognitive biases. The first is optimism bias, where teams overestimate their ability to recover late in the quarter. Forcing a weekly prediction creates a record that makes it harder to hide behind "we will catch up." The second is anchoring, where teams fixate on their original plan and resist adapting. Regular check-ins normalize the idea that plans change and course corrections are a sign of healthy execution, not failure.
One critical nuance: the check-in is not a performance review. The moment people feel their confidence scores will be used to evaluate them, they stop reporting honestly. The meeting must be psychologically safe. Red scores are information, not indictments. The facilitator's job is to respond to a red score with "what do you need?" not "why did you let this happen?" This distinction is what determines whether your OKR check-in meeting produces genuine signal or just noise.
Step-by-Step
Step 1: Prepare the OKR tracker before the meeting
At least 24 hours before the check-in, ask each key result owner to update their current metric value in your shared tracker. This means the actual number, not a qualitative impression. 2%. If data is not yet available for the current period, the owner notes the most recent available figure and the date it was pulled.
The facilitator reviews the tracker before the meeting to identify which items have not been updated, which show stalled progress, and which have moved significantly. This pre-work ensures the meeting is spent discussing implications and actions, not gathering data in real time.
Tip: If owners consistently fail to update before the meeting, add a 5-minute async pre-meeting window in Slack or your project tool where people post their updates. This creates social accountability without adding another meeting.
Step 2: Open the meeting with a 60-second context frame
Start by stating where you are in the quarter. " This framing is important because it calibrates expectations. If you are 54% through the quarter, a key result at 30% of its target should be yellow, not green. Without this temporal context, people default to optimistic interpretations of their progress.
The frame also reminds everyone that this is not a general team meeting. There is no place for unrelated project updates, sprint demos, or announcements. Those belong elsewhere.
Tip: Post a running "quarter progress" percentage in your team channel every Monday. This internalizes the time pressure and improves the accuracy of confidence scores people bring to the meeting.
Step 3: Run through each key result using the confidence-first format
Go through each key result one at a time. The owner states three things in this order: the current metric value, their confidence score (green, yellow, or red), and a one-sentence explanation. " For green items, the facilitator acknowledges and moves on. Do not spend more than 30 seconds on a green item.
For yellow and red items, pause and open a brief discussion, which you will structure in the next step. If you have 12 key results across the team, this initial pass should take 8-12 minutes.
Tip: Have owners declare their confidence score before explaining it. If they explain first, the narrative anchors everyone toward a particular score. Saying "yellow" first and then explaining forces more honest assessment.
Step 4: Discuss yellow and red items with a problem-solving lens
For each yellow or red item, the facilitator asks three questions in sequence. " This identifies whether the problem is new or persistent. " This forces the owner to name a concrete obstacle rather than a vague concern. Common blockers include dependency on another team, insufficient data to make a decision, resource conflicts, or a hypothesis that proved wrong.
" This shifts the conversation from diagnosis to action. The group brainstorms solutions. Timebox each yellow item to 3-4 minutes and each red item to 5-7 minutes. If a problem cannot be solved in the room, assign someone to schedule a separate working session within 48 hours.
Tip: Keep a running "blockers resolved" log visible to the team. Seeing that past blockers actually got fixed builds trust in the process and encourages honest reporting.
Step 5: Capture committed actions with owners and deadlines
Every discussion about a yellow or red item must produce at least one action item with a named owner and a specific deadline. Write these directly in the shared tracker or in your action-tracking system during the meeting. Do not rely on memory or follow-up emails. " Review these action items at the top of the next check-in before moving to new updates.
This creates a closed loop where commitments are visible and follow-through is tracked. If the same action carries over for two consecutive check-ins without progress, escalate it.
Tip: Distinguish between "actions" (things someone will do) and "decisions" (choices the group made). Record both, but only track actions for follow-up. Decisions should be documented so people do not relitigate them next week.
Step 6: Close weekly check-ins with a forward look
" This surfaces risks and opportunities before they materialize. Someone might mention a product launch that could spike a metric, or a team member going on leave that could stall an initiative. Capturing these forward-looking signals lets the team prepare rather than react. End the meeting on time, even if there are remaining items.
If the meeting consistently runs over, that is a signal that you have too many OKRs or your meeting frequency is too low. A well-run weekly check-in for a team of 5-8 people should take 20-30 minutes.
Tip: If you finish early, resist the urge to fill time with other topics. Ending a meeting early reinforces that this meeting is focused, efficient, and worth attending.
Step 7: Run the quarterly retrospective with a different structure
The quarterly retrospective is a longer meeting (60-90 minutes) held at the end of the OKR cycle, after scoring and grading is complete. This meeting has three sections. 0 on a sandbagged target. " Third, identify 2-3 specific process improvements to carry into the next planning cycle.
These might include changes to how you set key results, how often you check in, or how you align OKRs across teams.
Tip: Separate the scoring meeting from the retrospective by at least a day. Scoring while reflecting creates a conflict of interest where people adjust their reflections to justify their scores.
Step 8: Document retrospective findings and feed them forward
Write a one-page retrospective summary that captures the key findings, process changes, and any OKRs that should carry over, roll up, or be retired. Share this document with the team and any stakeholders who depend on your OKRs. The summary becomes an input to the next OKR planning session, ensuring that lessons actually change behavior rather than getting forgotten. Archive past retrospective summaries in a location accessible to the team.
Over 3-4 cycles, these summaries reveal patterns: recurring blockers, types of key results that consistently underperform, or alignment gaps that persist. These systemic patterns are the highest-leverage improvements you can make.
Tip: Start each quarterly planning session by reviewing the previous retrospective summary. This takes 5 minutes and immediately grounds the new cycle in learned experience.
Examples
Example: Small product team weekly check-in (5 people, B2B SaaS)
A product team of five at an early-stage B2B SaaS company is in week 6 of a 13-week quarter. They have one Objective ("Make onboarding self-serve for SMB customers") with four Key Results. The team meets every Monday at 10am for 25 minutes.
Before the Monday meeting, each KR owner updates the tracker. " KR1 (reduce time-to-first-value from 48 hours to 12 hours) is at 22 hours, confidence green. KR2 (increase onboarding completion rate from 35% to 60%) is at 41%, confidence yellow because the new wizard is shipping a week late. KR3 (reduce onboarding support tickets by 50%) is at -20%, confidence red because the new flow introduced a confusing step that increased tickets.
KR4 (achieve NPS of 45+ among new users) is at 38, confidence green. The facilitator spends 1 minute on the two green items and 15 minutes on the yellow and red. For KR3, the team identifies that step 4 of the wizard has a 60% drop-off rate. The designer commits to running three user tests by Wednesday and proposing a fix by Friday.
For KR2, the engineering lead commits to deprioritizing a non-OKR feature to ship the wizard by end of week. Both actions go into the tracker with names and dates. The meeting closes at 10:23am. At next Monday's check-in, these two action items are the first things reviewed.
Example: Cross-functional team bi-weekly check-in (8 people, e-commerce)
A cross-functional team at a mid-size e-commerce company includes members from product, marketing, and analytics. They share one Objective ("Become the #1 search result for our top 20 product categories") with five Key Results spanning SEO, content, and technical performance. The team checks in every other Thursday for 30 minutes because daily work is managed through sprint ceremonies.
The analytics lead pre-populates the tracker with current rankings, organic traffic, and page speed data on Wednesday evening. The meeting opens with the facilitator noting they are at week 8 of 12. KR1 (rank top 3 for 15 of 20 target categories) is at 9 out of 15, confidence yellow because three categories have entrenched competitors. KR2 (increase organic traffic by 40%) is at +28%, confidence green with current trajectory.
KR3 (publish 40 SEO-optimized category pages) is at 26, confidence green. 8 seconds, confidence red because infrastructure changes are blocked by the platform team. KR5 (earn 50 backlinks to category pages) is at 31, confidence yellow. The facilitator allocates 3 minutes to the greens and 20 minutes to the reds and yellows.
For KR4, the team decides the product manager will escalate to the VP of engineering with a specific request and deadline. For KR1, the marketing lead suggests reallocating content resources from already-ranking categories to the three struggling ones. The team agrees and the content calendar is adjusted in the meeting. For KR5, the outreach lead reports that their template is underperforming and commits to A/B testing a new approach by next check-in.
All three actions are logged with owners and deadlines.
Example: Leadership team quarterly retrospective (6 people, Series B startup)
A Series B startup's leadership team of six (CEO, CTO, VP Product, VP Marketing, VP Sales, Head of People) is reviewing company-level OKRs at the end of Q3. They had three company Objectives with a total of 11 Key Results. The retrospective is scheduled for 90 minutes on the first Friday after the quarter ends.
Scores were finalized two days earlier using the scoring and grading process. 9. The first 30 minutes review each OKR score and its story. Objective 2's low score prompts the deepest discussion.
The VP Product notes that two key results assumed a feature that shipped three weeks late, compressing the measurement window. The CTO acknowledges a dependency that was underestimated during planning. The second 30 minutes uses the three retrospective prompts. Under "What helped," the team identifies that weekly check-ins caught the KR4 blocker early enough to partially recover.
Under "What got in our way," two themes emerge: engineering dependencies between teams were not visible during planning, and one KR was unmeasurable because the tracking was never set up. Under "What would we change," the team commits to two process improvements for Q4: include an explicit dependency-mapping step in the next planning session, and require that measurement instrumentation be confirmed before finalizing any key result. The Head of People documents these findings in a one-page summary that will be the first agenda item at the Q4 planning offsite.
Example: Distributed team async-first check-in with sync discussion (10 people, B2C mobile app)
A distributed team spanning three time zones builds a B2C mobile app. They have two Objectives with seven Key Results. Finding a synchronous time that works for everyone is difficult, so they use an async-first format with a short sync window for problem-solving.
Every Monday by noon UTC, each KR owner posts a structured update in a dedicated Slack channel using a template: current metric, confidence (green/yellow/red), one-line explanation, and blockers (if any). The team lead reviews all updates by 2pm UTC and flags items that need synchronous discussion. On Tuesdays at 3pm UTC (the one overlapping window), the team holds a 20-minute sync call that focuses exclusively on flagged items. In a typical week, 4-5 of the 7 KRs are green and require no sync time.
The Tuesday call might address two items: a yellow KR where the growth experiment underperformed and needs a pivot decision, and a red KR where the iOS and Android teams need to coordinate a shared API change. The async updates create a searchable record that the team lead compiles into a weekly summary. At the quarterly retrospective, the team reviews these summaries to identify patterns across the quarter. They discover that KRs involving cross-platform coordination were consistently yellow or red, leading them to create a dedicated coordination ritual for Q4.
Best Practices
Update metrics asynchronously before the meeting so the live session is spent interpreting data and solving problems, not collecting it. When teams gather data during the meeting, they lose 40-60% of the timebox to logistics, and the discussion becomes shallow because people are processing numbers for the first time.
Spend 80% of meeting time on yellow and red items. Green items get a quick acknowledgment and nothing more. If you allocate equal time to every key result, you are implicitly telling your team that problems and progress are equally interesting, which discourages people from flagging issues early.
Timebox the entire meeting and enforce it. A weekly OKR check-in meeting should be 20-30 minutes for a team of 5-8 people. If it regularly exceeds this, you likely have too many OKRs per team. Aim for 3-5 key results per person or team. The constraint forces prioritization.
Keep the meeting psychologically safe by treating red scores as information, not failures. The facilitator should model this by responding to red scores with curiosity ("What do you need?") rather than blame ("Why is this behind?"). If people start sandbagging their confidence scores to avoid difficult conversations, your check-in has become performative.
Rotate the facilitator role every 2-4 weeks. This prevents the check-in from becoming one person's meeting and distributes ownership of the OKR process across the team. It also surfaces facilitation skills and keeps the format from getting stale.
Always close the loop on action items from the previous meeting before opening new discussions. Review the action log at the top of each session. Unresolved items that carry over for two consecutive meetings should be escalated or renegotiated, not silently accepted.
Separate the OKR check-in meeting from other recurring meetings like sprint planning, team standups, or project status updates. Combining them dilutes focus and causes OKR discussions to get squeezed out by more urgent tactical items. A dedicated timeslot signals that OKR progress is a first-class priority.
Common Mistakes
Turning the check-in into a status report where everyone talks about what they did last week
Correction
This happens because teams default to familiar meeting patterns. The symptom is that people describe activities ("I had three customer calls and updated the roadmap") instead of outcomes ("trial-to-paid conversion moved from 10.2% to 10.8%"). To fix this, enforce the three-part format: metric, confidence score, one-sentence explanation. If an owner starts narrating their week, the facilitator redirects: "What is the current number and your confidence level?" The meeting is about trajectory toward the target, not a journal of effort.
Giving equal airtime to every key result regardless of status
Correction
Teams do this because it feels fair and avoids the awkwardness of singling out struggling items. The signal is that meetings consistently run over time, or the team rushes through red items because they spent too long on green ones. Fix this by having owners declare their confidence score first. The facilitator explicitly says, "This is green, so let us move on" for on-track items.
If team members feel slighted by the short acknowledgment, remind them that the lack of airtime is a compliment, it means they are succeeding.
Skipping weeks when things feel like they are going well
Correction
This happens around weeks 3-5 of the quarter when initial momentum is high and everything looks green. The problem is that skipped check-ins create blind spots. A key result can shift from green to red in two weeks if a dependency breaks or an assumption proves wrong. By the time you reconvene, the recovery window has shrunk.
Treat the check-in like a heartbeat monitor. You do not stop monitoring because the patient looks healthy. If the meeting genuinely has nothing to discuss, it will take 10 minutes and end early, which is fine.
Using the check-in to renegotiate or rewrite OKRs mid-quarter
Correction
This surfaces when a key result is consistently red and the team starts debating whether the target was realistic. While mid-quarter adjustments are sometimes necessary, the check-in is not the right venue. The symptom is that check-in meetings balloon to 45-60 minutes as the group wordsmithes key results. Instead, note the concern, assign someone to draft a revised proposal, and bring it to a separate 15-minute decision meeting.
Changes to OKRs should be intentional and documented, not improvised during a progress review.
Not tracking or following up on action items from previous check-ins
Correction
Teams create action items during the meeting and then forget them by the next session. The check-in produces a feeling of progress without actual progress. The fix is structural: open every meeting by reviewing the action log from the previous session. Read each item aloud, ask the owner for a status update, and mark it complete or carry it forward.
If you do not have a visible action log, create one in the same document or tool where you track OKR metrics. The log should be a permanent section, not a set of meeting notes that gets buried.
Having managers dominate the conversation while individual contributors stay silent
Correction
This happens when the meeting culture is top-down or when managers are the ones presenting OKR updates. The signal is that only 2-3 people speak during the entire meeting. The fix is to assign key result ownership to individual contributors and have them present their own updates. The manager's role is to facilitate, ask clarifying questions, and help remove blockers.
If ICs are uncomfortable presenting, start with written updates in a shared document and use the meeting to discuss only flagged items.
Other Skills in This Method
Running OKR Planning and Setting Sessions
How to facilitate collaborative quarterly OKR-setting workshops that generate buy-in, ensure ambition, and produce well-structured goal sets.
Setting OKR Cadence and Planning Cycles
How to determine the right OKR cycle length, manage quarterly vs annual rhythms, and coordinate timing across different organizational levels.
Avoiding Common OKR Mistakes and Anti-Patterns
How to identify and prevent pitfalls like sandbagging goals, confusing tasks with key results, setting too many OKRs, and tying OKRs directly to compensation.
Writing Effective OKR Objectives
How to craft qualitative, inspirational, and actionable objectives that motivate teams and provide clear strategic direction.
Aligning OKRs Across Teams and Organization Levels
How to cascade and align OKRs from company-level down through departments and individual contributors to ensure strategic coherence.
Defining Measurable Key Results
How to create specific, quantifiable key results with clear metrics and targets that accurately measure progress toward an objective.
Scoring and Grading OKRs at End of Cycle
How to evaluate OKR progress using the 0.0-1.0 scoring scale, interpret results, and distinguish between committed and aspirational targets.
Frequently Asked Questions
How long should a weekly OKR check-in meeting take?
For a team of 5-8 people with 3-5 key results each, aim for 20-30 minutes. If your meeting consistently runs longer, you likely have too many OKRs or you are spending too much time on green items. The fix is either reducing the number of tracked key results or enforcing the rule that green items get 30 seconds maximum. If your team is larger than 8 people, consider splitting into sub-team check-ins with a summary roll-up.
Should I run OKR check-ins weekly or bi-weekly?
Start with weekly. A two-week gap between check-ins means a problem can go undetected for nearly a quarter of the cycle. Once your team has run 2-3 quarters of weekly check-ins and consistently has short meetings with mostly green items, you can experiment with bi-weekly. Teams with fast-moving metrics (daily active users, conversion rates) benefit more from weekly cadence. Teams with slower-moving metrics (brand awareness, enterprise deal pipeline) can often work bi-weekly. See [setting OKR cadence and cycles](/skills/setting-okr-cadence-and-cycles) for more on finding the right rhythm.
What tool should I use to track OKR progress for check-ins?
The tool matters less than the discipline. A shared spreadsheet with columns for key result, target value, current value, confidence score, and action items works for most teams. Dedicated OKR tools like Lattice, Weekdone, or Gtmhub add features like automated reminders and visualization, but they do not fix a broken check-in process. Choose whatever tool your team will actually update consistently. The real requirement is that the tracker is visible to everyone and updated before the meeting.
How do I handle a key result that has been red for three consecutive check-ins?
Three consecutive red scores signal a structural problem, not a temporary setback. First, determine if the key result is still achievable with extraordinary effort and whether that effort is worth it relative to other priorities. If yes, escalate for resources or dependency resolution outside the check-in. If no, have an honest conversation about whether to adjust the target, replace the key result, or accept the miss and redirect energy elsewhere. Document the decision and the reasoning. This is not failure, it is responsible portfolio management. Pretending a dead KR is still alive wastes everyone's time and undermines trust in the process.
Should the OKR check-in meeting be separate from our team standup or sprint review?
Yes, keep them separate. Standups focus on daily tasks and immediate blockers. Sprint reviews focus on what was built and demonstrated. OKR check-ins focus on whether what you are building is actually moving the needle on quarterly outcomes. Combining them causes one purpose to crowd out the others, and it is almost always the OKR discussion that gets squeezed. A dedicated 25-minute OKR check-in meeting once a week sends a clear signal that outcome measurement is a distinct, protected priority.
How do I prevent OKR check-ins from feeling like micromanagement?
The key is framing and facilitation. The meeting is about the metrics, not the people. " Ownership of key results should come with autonomy over how to achieve them. The check-in reviews whether the approach is working, not whether the person is working hard enough. If your team reports feeling micromanaged, examine whether you are asking about activities rather than outcomes, and whether confidence scores are being used for judgment rather than problem-solving.
What should I do differently in the quarterly retrospective compared to the weekly check-in?
The weekly check-in is tactical: are we on track, what is blocking us, what action do we take this week. The quarterly retrospective is strategic: did we pursue the right objectives, did our key results measure what mattered, and what systemic changes improve our next cycle. In the retrospective, you zoom out from individual metrics and examine patterns. Did the same type of blocker recur? Were certain key results always green because they were too easy? Did any objective turn out to be irrelevant by mid-quarter? The output is 2-3 concrete process improvements, not action items on specific metrics.