How to run an OKR planning meeting that sets real goals.
Short answer
An OKR planning meeting runs 2–4 hours per quarter and has three stages: reviewing last quarter's results, drafting new objectives (qualitative direction) with 3–5 key results each (measurable outcomes), and aligning across teams on dependencies. Strong key results describe outcomes, not activities — 'grow NPS from 32 to 45' beats 'launch NPS survey program.'
OKRs fail when they become a to-do list with a different name. The planning meeting is where that failure starts — or gets prevented.
Pre-work. Each team lead scores last quarter's OKRs (0.0–1.0) before the meeting. A 0.7 is the target — 1.0 means the goal was too easy. Email the scores and a 3-sentence context note to all participants 48 hours in advance.
Part 1 — Retro on last quarter (30–45 min). Review each objective and its KR scores. For any KR below 0.5 or above 0.9, the facilitator asks: "What happened?" Don't skip this. The pattern of misses tells you whether goals were poorly written, under-resourced, or structurally impossible.
Part 2 — Company OKR draft (45–60 min). Leadership presents 3–5 proposed company-level objectives for the quarter. Each objective should answer: "What inspires us to move in this direction?" Key results should be metrics — numbers, not activities. Common test: can you track it weekly without a meeting? If no, rewrite it.
Formula for a strong KR: [verb] [metric] from [current] to [target]. Example: Increase free-to-paid conversion rate from 4.2% to 7.0%.
Part 3 — Team OKR drafts (45–60 min). Each team drafts their own OKRs aligned to company objectives. Each team should trace at least one KR back to a company KR — this is the alignment check. Teams present drafts in 5 minutes each; others ask one clarifying question.
Part 4 — Dependency mapping (20–30 min). Which team's OKRs depend on another team's output? Map these on a whiteboard: Team A's KR requires Team B's work. Named dependencies need named owners on both sides.
Part 5 — Commit and publish (15 min). Write the final OKRs on the whiteboard in a clean format — Company OKRs at the top, team OKRs below, dependency lines connecting them. Each team lead verbally commits. OKRs should be published (not just emailed) within 24 hours.
Common mistakes: Writing activities as KRs ("Launch X" instead of "Grow Y by Z%"). Setting more than 5 KRs per objective — scope creep by another name. Not scoring last quarter before setting new goals. Letting every team set OKRs that don't connect to company OKRs.
Snap the OKR whiteboard with BoardSnap at the end of the session. The AI reads the nested structure and outputs a clean action list — each KR becomes a trackable item with a defined owner.
Frequently asked
How often should OKR planning meetings happen?
Quarterly. Most companies set OKRs at the start of each quarter (January, April, July, October). Some fast-moving startups run monthly OKRs, but quarterly gives enough time for key results to actually move.
What's the right number of OKRs per team?
3 objectives, 3–5 key results each. More than that and nothing gets focus. If a team has 8 objectives, the real answer is they haven't made any choices.
Should OKRs be top-down or bottom-up?
Both. Company OKRs set direction from the top. Team OKRs are drafted by teams and aligned upward. The best OKR planning meetings have a 60/40 mix: leadership proposes company direction, teams decide how to get there.
See it work in ten seconds.
BoardSnap is free on the App Store. Snap a board — get a summary and action plan.