OKR Check-in: How to Run Weekly Reviews That Actually Work
Learn how to run OKR check-ins that take 5 minutes and keep your team accountable. Includes a simple question framework, a reusable template, and tips for remote teams.
Loach Team
Product Team
The weekly OKR check-in is the most important — and most neglected — part of running OKRs successfully.
Most teams hold a quarterly kickoff. Some do a mid-quarter review. Very few maintain a consistent weekly check-in. And that is precisely why their OKRs stop working by week four.
This guide covers why weekly check-ins matter, what they should include, how to keep them short, and what good check-ins look like in practice.
Why Weekly Check-ins Matter
OKRs are a quarterly tool, but execution is weekly. The gap between setting goals and achieving them is filled — or not — by what your team prioritises every week.
Without a weekly check-in:
- Teams drift toward urgent work and away from strategic priorities
- Blockers surface at the monthly review when it is too late to fix them
- OKR progress stalls silently — nobody notices until the end of quarter
- The quarterly retrospective concludes "we need to take OKRs more seriously"
With a weekly check-in:
- Teams stay connected to their OKRs throughout the quarter
- Blockers surface early enough to act on them
- Mid-quarter corrections are small adjustments, not emergency pivots
- The end-of-quarter review has no surprises
The weekly rhythm is the product
The check-in is not an add-on to your OKR process — it is the mechanism that makes OKRs work. Without it, OKRs are just aspirational documents.
The 3-Question Check-in Framework
A good OKR check-in answers three questions per person:
1. What did I accomplish last week toward our OKRs? This connects last week's work to strategic progress. It is not a general task update — it is specifically about OKR-relevant work.
2. What is my focus this week? This is the planning question. What are the 2–3 things this person will work on that move the OKRs forward? This question is the difference between a status meeting and a planning meeting.
3. What is blocking progress? Blockers identified weekly can be resolved weekly. Blockers identified monthly become crises.
That is it. Three questions, 5 minutes per person, same structure every week.
The Check-in Template
Use this format for async check-ins (written) or as the agenda for a synchronous meeting:
Weekly OKR Check-in — [Date]
**Accomplished last week (OKR-relevant):**
- [What moved forward]
**Focus this week:**
- [Priority 1 — tied to which OKR/KR]
- [Priority 2 — tied to which OKR/KR]
**Blockers:**
- [What needs to be resolved — and by whom]
For synchronous check-ins, go around the team. Each person takes 3–5 minutes. A team of 6 completes the check-in in under 30 minutes. A team of 3 does it in under 15 minutes.
Async vs Synchronous Check-ins
When async works best
- Distributed teams across time zones
- Teams with high individual contributor work (engineering, writing, design)
- When the synchronous meeting regularly goes long
How to run async check-ins: Each person posts their 3-question update before a set time (e.g., Monday 10am). The manager reviews the updates and flags blockers for a short synchronous discussion only when needed.
When synchronous works best
- Small teams (under 8 people) where the conversation adds value
- Teams with high interdependency (sales + marketing, product + engineering)
- Early-stage teams still building their OKR habit
How to keep synchronous check-ins short: Use the template above as a strict agenda. No tangents. If a topic requires more than 2 minutes, park it and address it in a separate conversation.
Common Check-in Mistakes
Turning it into a status meeting
A status meeting is a report of what happened. A check-in is a planning touchpoint. The distinction matters: the question "what are you working on this week?" drives planning, while "what did you do this week?" drives reporting.
Keep the emphasis on the second question (focus this week), not just the first (accomplished last week).
Skipping the blocker question
Most people will not volunteer that they are blocked unless explicitly asked. The blocker question has to be part of the format. "I have no blockers" is also a valid answer — but the question must be asked.
Making it monthly
Monthly check-ins are better than nothing, but they are too infrequent to course-correct. Three weeks of off-track progress before a check-in means the quarter may already be lost. Weekly is the right cadence.
Not connecting priorities to OKRs
"I am working on the customer call, the new feature, and catching up on emails" is not an OKR check-in — it is a task update. Each priority should be explicitly connected to an OKR. "I am working on the new onboarding flow to improve our activation rate [KR: increase activation from 40% to 65%]."
What a Good Check-in Looks Like
Bad check-in (status meeting style):
"Last week I worked on the new feature and some customer calls. This week I am continuing the feature and have a few more calls scheduled. No blockers."
Good check-in (planning-first style):
"Last week I completed the first version of the onboarding flow redesign and tested it with 3 users — early signal is positive. This week I am running 5 more user tests and fixing the top 2 issues before handing to engineering. This is directly toward our Q2 OKR to increase activation rate from 40% to 65%. One blocker: I need the updated copy from marketing before I can finalise the flow — flagging this for resolution today."
The good check-in connects work to OKRs, makes the weekly plan explicit, and surfaces a blocker with a clear path to resolution.
Scaling Check-ins as the Team Grows
| Team size | Recommended format | Time |
|---|---|---|
| 1–5 people | Synchronous, full team | 15–25 min |
| 6–15 people | Async updates + 15-min blocker sync | 25–35 min total |
| 15+ people | Async per team + manager-level sync | 45–60 min total |
As the team grows, check-ins should stay short per person even if total time increases. The three-question format scales well because it is consistent and structured.
FAQs
Q: How often should we do OKR check-ins?
Weekly. Not bi-weekly, not monthly. Weekly check-ins are what keep OKRs alive as a planning tool throughout the quarter.
Q: What if someone is not making progress on their OKRs?
The check-in is the right time to surface this. Ask the question: "What is blocking progress?" If the blocker is workload, reprioritise. If it is clarity, resolve it. If it is consistently low priority despite no blockers, have a direct conversation about whether the OKR is still the right goal.
Q: Can check-ins replace all-hands meetings?
No. Check-ins are tactical planning touchpoints. All-hands meetings serve a different purpose: company updates, strategic context, culture. Keep them separate.
Q: What tool should we use for OKR check-ins?
Any tool that surfaces weekly priorities and connects them to key results. A shared document works for small teams. Purpose-built tools like Loach pre-populate weekly priorities from your OKR breakdown and structure check-ins around the three questions automatically.
Conclusion
A consistent weekly check-in is the single most impactful thing you can add to your OKR process. It takes 5 minutes per person. It surfaces blockers early. It keeps the team connected to strategic priorities throughout the quarter.
The format does not need to be complex. Three questions, same time every week, consistent connection to OKRs. That is it.
Related resources:
- Weekly OKR Execution System — The complete weekly planning methodology
- How to Track OKRs Effectively — Planning before tracking
- Why OKRs Fail — The planning gap explained
- OKR Check-ins Use Case — How Loach structures weekly check-ins
Ready to run 5-minute OKR check-ins? Try Loach free →