Weekly Check-ins that Work
Weekly check-ins keep OKRs alive. Without regular review, OKRs become stale and teams lose focus. Gallup research on workplace feedback has found that employees who get feedback and recognition on a weekly basis are far more likely to be engaged than those who hear from managers only occasionally. This article shows you how to run effective check-ins that take 15 minutes or less. The difference between successful and failed OKR implementations often comes down to whether teams maintain a consistent weekly rhythm.
What to cover in a weekly check-in
- Progress: What changed this week? Update each key result with current values and show the delta from last week. Focus on actual metrics, not just activity.
- Confidence: Are we on track? Use a simple traffic light system: green (on track), yellow (at risk), red (off track). This makes status immediately visible.
- Blockers: What's in the way? Identify specific obstacles that require action or decisions. Don't just list problems—propose solutions or ask for help.
Keep it lightweight
Check-ins should be fast. Update progress, flag risks, and move on. Don't turn it into a long meeting or a status report. If your check-in takes more than 15 minutes, you're doing too much. The goal is regular pulse-checks, not exhaustive reporting. Teams should spend their time executing, not documenting.
Use a consistent format
Use the same format every week so it becomes routine. This reduces friction and makes it easier for teams to stay current. Google's own guidance on updating OKRs regularly makes the same point: whether it's a shared doc, a tool, or a standup, pick one approach and stick with it. Consistency builds habit, and habit ensures check-ins actually happen every week without debate or calendar juggling.
Make it visible
Share check-ins with the team and leadership. Transparency builds accountability and makes it easier to spot trends and risks early. When everyone can see progress and blockers, help arrives faster and coordination improves naturally. Visibility also creates healthy peer pressure to keep moving forward.
Act on what you learn
Check-ins are worthless if nothing changes. When you spot a blocker, assign an owner and a deadline to resolve it. When confidence drops from green to yellow, adjust plans before it turns red. The point of weekly reviews is to catch problems early while you can still fix them.
A simple example
Imagine a key result to grow signups from 200 to 400 per week. On Monday, the owner updates the number to 240, marks confidence as green, and notes no blockers. Two weeks later, signups stall at 250. Confidence drops to yellow, and the owner flags that the landing page test hasn't launched yet because of a design delay. The team assigns an owner to unblock the design work by Friday. That one line in a weekly check-in likely saves the whole quarter's result.
Who should run the check-in
Each key result should have a single owner who is responsible for updating it every week. The owner doesn't have to do all the work themselves, but they own the number and the story behind it. Without a clear owner, check-ins get skipped or updates come in late, and the whole rhythm falls apart. Assign owners when you set the OKRs, not after the quarter has already started.