How to Run a Mid-Quarter OKR Review

Run a structured mid-quarter OKR review, surface risks, recalibrate, and keep teams aligned to finish strong.

Time required ~2 hours 60–90 min meeting + prep
Frequency Mid-cycle Week 6 of a 13-week cycle
Who's involved Leadership + managers KR owners present updates
Output Course corrections + revised KRs if needed

Before you start

You need at least 5 weeks of weekly check-in data — without that, this review is just a long status meeting. Update every KR with current numbers at least 24 hours before the review so the meeting can focus on decisions, not data entry.

The 7 steps

7 steps · sequential
1
~5 min·At the start of the cycle

Schedule the review

Build the mid-quarter review into your OKR rhythm. Put it on the calendar at the start of the cycle, or it won't happen.

  • Hold it around week 6 of a 13-week cycle
  • Run reviews at both company and team levels
  • Keep sessions focused: 60–90 minutes is usually enough
  • Treat it as a working session, not just a presentation
2
~60 min·1–2 days before

Collect progress data

Gather accurate, up-to-date information before the review. Walking into the meeting with stale numbers wastes everyone's time.

  • Update all Key Results with the latest metrics
  • Ask owners to provide a confidence rating (High / Medium / Low)
  • Capture notes on blockers, dependencies, or risks
  • Prepare a dashboard or slide deck for visibility
Done whenEvery KR has a current value, a confidence rating, and a one-line context note — visible before the meeting starts.
3
~30 min·First half of the meeting

Review Key Results one by one

Assess progress and identify problem areas. Don't skip the greens — what's working tells you what to do more of.

  • For each KR, review: current progress vs. target
  • Confirm confidence rating
  • Note risks or blockers
  • Use a Red / Yellow / Green status system for clarity
  • Celebrate early wins and recognize contributors
4
~20 min·Mid-meeting

Identify blockers & root causes

Surface what's slowing progress and why. Treating symptoms instead of causes is why most mid-quarter reviews fail to change the trajectory.

  • Ask each KR owner: What's preventing further progress?
  • Separate internal blockers (resourcing, prioritization) from external blockers (market, customer, vendor)
  • Use techniques like the "5 Whys" to dig into root causes
  • Prioritize blockers that affect multiple teams
5
~15 min·Mid-meeting

Adjust Key Results if needed

Refocus effort where it will matter most. Adjusting a KR is not failure — it's focus. The shame is leaving a clearly-impossible KR on the board for 7 more weeks.

  • If a KR is clearly unattainable, decide whether to adjust or replace it
  • Update targets if priorities have shifted significantly
  • Add stretch goals if progress is ahead of schedule
  • Document all changes transparently and communicate them company-wide
DecisionThree options per KR: keep, adjust the target, or replace entirely. Pick one — don't leave it in limbo.
6
~15 min·End of meeting

Reallocate resources

Give teams the support they need to deliver. Identifying blockers is half the work; clearing them is the other half.

  • Shift resources toward high-priority, at-risk KRs
  • Resolve cross-team conflicts or bottlenecks (see Cross-Team Alignment)
  • Assign blocker owners responsible for clearing obstacles
  • Confirm next steps and deadlines before leaving the meeting
Done whenEvery red or yellow KR has either an adjustment, a blocker owner, or both — with a deadline this week.
7
~30 min·Within 24 hours of the meeting

Share outcomes & next steps

Keep everyone aligned after the review. Silence after a mid-quarter review is worse than skipping it — people fill the gap with their own guesses.

  • Send a written recap with: updated OKRs, revised targets, top blockers and resolutions, key decisions
  • Publish updates in your OKR tracking tool or shared workspace
  • Communicate any KR changes broadly — don't quietly edit and hope nobody noticed
What you'll have when you're done

Outputs of this workflow

  • Every KR has a current red / yellow / green status and a confidence rating
  • A documented list of blockers with separated internal vs. external causes
  • A decision per at-risk KR: keep, adjust target, or replace
  • Resource reallocations committed to in the meeting, not after it
  • A written recap shared broadly within 24 hours — no version-control confusion

Run mid-quarter reviews inside OKRs Tool.

Real-time KR data, at-risk alerts, confidence trends, and a clean record of every adjustment — so reviews focus on decisions, not data entry. Free for up to 5 users.

Start free