OKR Check-in
A lightweight weekly or bi-weekly ritual where teams briefly review progress on their Key Results, update confidence levels, surface blockers, and decide if course corrections are needed. Check-ins prevent OKRs from becoming a quarterly filing exercise — they make OKRs a living part of how the team works.
How to run it
- 1
Each person/team updates their Key Result progress before the meeting (not during).
- 2
Go through each KR in turn: What's the current status? Is the confidence level (0-100%) going up or down?
- 3
For any KR with declining confidence: What's the blocker? What needs to change? Do we need to revise the KR?
- 4
Quick wins: celebrate meaningful progress, don't skip this.
- 5
Parking lot: any strategic shifts or external changes that affect OKRs? Flag for quarterly review.
- 6
Close in <30 minutes. This is a pulse check, not a planning session.
Tips
Confidence level changes are more informative than raw numbers. A KR at 30% with rising confidence is healthier than one at 80% declining.
If a KR hasn't moved in 2 weeks: it either needs attention or it's a task masquerading as a KR.
Don't use check-ins to add new KRs. Save changes for mid-quarter or quarterly review.
Keep the tone curious, not evaluative. 'What's happening?' not 'Why haven't you hit this?'
Variations
Async check-in: team updates a shared doc Friday afternoon; manager reviews and comments Monday morning. Async-first is faster and creates a written record.
Where it fits
Related methods
Plan your next workshop with AI
Workshop Weaver helps you combine methods like OKR Check-in into a complete, timed agenda in minutes.
Try it freeMethod descriptions on Workshop Weaver are original content written by our team, based on established facilitation practices. This method was inspired by work from Workshop Weaver.