OKR scorecard
For each OKR: the objective, the key results, the target, and the actual outcome. Rate each KR honestly: 0–1 scale or simple hit/miss/partial. Don't inflate — a partial that's marked as a hit erodes trust in the whole planning system.
Free template
Free quarterly review template — end the quarter on a real whiteboard.
BoardSnap is an iOS app that converts whiteboard photos into clean summaries and action items in about ten seconds. This quarterly review template structures a full-quarter close — OKR outcomes, what worked, what didn't, the key learnings, and next-quarter inputs — on a board you snap and distribute.
Download on the
App Store
Free to start. Pro from $9.99/mo or $69.99/yr.
When to run this
Run this in the last week of the quarter, before setting next quarter's OKRs. The review should inform the planning — if you set Q3 OKRs without reviewing Q2 outcomes honestly, you repeat the same mistakes.
Budget 90 minutes for a team session; 45 minutes for an individual review. Include anyone who owned an OKR or a major initiative this quarter.
The structure
Wins worth celebrating
Write the three to five things that went notably well — not just what hit the OKR, but what created real value, surprised you, or showed the team's capability. Wins that aren't named get forgotten and don't compound.
Misses worth understanding
Write the two to three things that didn't work — missed OKRs, failed experiments, wrong bets. For each: why did it miss? Market, execution, wrong hypothesis, or wrong resourcing? The answer shapes next quarter.
Key learnings
What do you know now that you didn't know three months ago? Write the top three learnings — about the market, the product, the team, or the process. These are the durable outputs of the quarter. Metrics age; learnings compound.
Input for Q+1
Based on the scorecard and learnings: what should the next quarter focus on? Not the full OKR — just the two or three inputs. What did this quarter teach you about what matters most? These inputs go directly into the next quarter's OKR-setting session.
How to run it
- Pull last quarter's OKRs before the session
Write the objectives and key results on the left side of the board before the meeting starts. Everyone should see them before they see the outcomes. This prevents anchoring — where knowing outcomes retroactively adjusts memory of the targets.
- Score the OKRs honestly
Go through each KR and write the actual number next to the target. Calculate the score. Resist the instinct to round up. A 0.7 on a hard objective is genuinely good; a 1.0 on a sandbagged objective is not. Calibrate the ambition first, then the score.
- Write the wins first
Before the misses. Starting with wins sets a fair accounting tone. The team is more honest about misses when they've already named the wins — the review feels balanced rather than a post-mortem.
- Analyze misses with 'because'
For each miss: 'We didn't hit [KR] because [root cause].' The because is the learning. Wrong hypothesis, under-resourced, external blocker, execution gap — each requires a different response next quarter.
- Extract learnings from patterns
Look across wins and misses. What pattern do you see? If every miss was execution-blocked by a dependency on one team, that's an organizational learning, not a project-level miss.
- Write Q+1 inputs, not OKRs
This session ends with direction, not decisions. Write 'Q3 should focus on X because we learned Y.' The formal OKRs get written in the next session, informed by these inputs.
- Snap with BoardSnap
BoardSnap reads the scorecard, wins, misses, learnings, and Q+1 inputs. The output is a clean quarterly summary — wins as completed items, misses as analysis, and next-quarter inputs as action items for the planning session.
Why quarterly reviews on a whiteboard + BoardSnap is better than digital
Quarterly reviews written in Google Docs get shared, skimmed, and filed. A quarterly review drawn on a whiteboard — where every OKR score is visible to the whole team at once — creates shared accountability that a doc never does.
BoardSnap captures the board and produces a structured summary before the conversation ends. Drop it in Slack as the official Q-close record. It takes thirty seconds.
Frequently asked
How long should a quarterly review take?
Team sessions: 60–90 minutes. Individual reviews: 30–45 minutes. If it takes longer, you're doing the next quarter's planning in the same session — that should be a separate meeting with a break in between.
What's the right OKR scoring approach?
The simplest that your team will actually use. A 0–1 numeric score (0 = nothing done, 0.7 = solid progress, 1.0 = fully achieved) is the most common. Google popularized this scale. What matters more than the exact approach is that everyone uses the same approach and is honest about what the numbers mean.
What if we set OKRs that were too vague to score?
That's the most useful output of the quarterly review — identifying that the OKR was set without a measurable key result. Write it as a learning: 'KR 2 was unmeasurable because it had no numeric target.' That informs next quarter's OKR-setting process directly.
Is BoardSnap free?
The free tier includes one project and 30 boards. Pro is $9.99/month or $69.99/year for unlimited boards and AI chat on every board you snap.
Run your next quarterly review and BoardSnap will summarize it.
No exporting, no transcription. Snap the board, get the action plan.
Free · 1 project, 30 boards
Pro $9.99/mo · everything unlimited
Pro $69.99/yr · save 42%