Skip to article
Bridge

How to run an OKR planning meeting that sets a real quarter

An OKR planning meeting sets a team's objectives and key results for the next quarter. It works when it starts from last quarter's grades and the organization's goals, cuts to three to five objectives, and ends with an owner and a check-in date for every key result.

What the meeting is for

OKRs pair an objective, what you want to achieve, with key results that show you got there. Google's re:Work guide describes objectives as ambitious and key results as measurable and easy to grade with a number.

The planning meeting turns that into a short list for one quarter. It is not where the team lists every project. As re:Work puts it, OKRs are not a master task list.

Who should attend

Keep it small enough to debate. If many people need a say, hold a draft round with owners first.

  • The team lead, who owns the final list and its link to company goals.
  • The people who will own key results, since they know what is measurable.
  • One person from each team you depend on, if a key result needs their work.
  • A facilitator, who can be the team lead in a small team.

Prepare before the meeting

  • Grade last quarter's key results, so the meeting starts from data.
  • Share the organization's objectives for the coming quarter.
  • Ask each owner to bring one or two draft objectives, each with its key results.
  • List known commitments, such as launches or contracts, that the quarter must absorb.

A 90-minute agenda

TimeBlockOutput
0–15Review last quarter's gradesWhat to carry over, drop or rewrite
15–25Restate the organization's objectivesWhich ones this team supports
25–55Debate draft objectivesThree to five objectives
55–80Sharpen key resultsAbout three measurable results per objective
80–90Assign owners and check-insAn owner and a mid-quarter date for each key result

Test each draft before you keep it

Use these questions on every objective and key result. They come from the re:Work guide's tips and common mistakes.

  • Is it one of only three to five objectives? More spreads the team thin.
  • Does it connect to at least one organizational key result?
  • Is each key result an outcome, not an activity? Words like "help", "analyze" or "participate" signal an activity.
  • Would an observer know whether it was achieved?
  • Is it committed or aspirational? Say which, so other teams know what to rely on.

Example: rewriting an activity into a result

This example is illustrative. A support team drafts "Help the product team analyze ticket trends." That is an activity, and nobody can grade it.

In the meeting, the team rewrites it: "Cut median first response time on billing tickets from 9 hours to 4." It now has a number and a baseline. Dana owns it, with a check-in at week six.

Set expectations for grading

Agree on how you will grade before the quarter starts. Google grades key results from 0.0 to 1.0 and treats 0.6 to 0.7 as the sweet spot for ambitious goals.

A team that always scores 1.0 is probably aiming too low. Low grades are data for the next round, not a verdict on people.

Follow up so the OKRs stay alive

Publish the final list where every team can see it, with each key result's owner. Then put the check-ins on the calendar before the meeting ends.

re:Work suggests a mid-quarter check-in and an end-of-quarter check-in before final grading. Keep the planning discussion recorded, so the check-in can revisit why a target was set.

  • Week 1: final OKRs shared, owners confirmed.
  • Mid-quarter: each owner reports progress and risks.
  • End of quarter: grade, then bring the grades to the next planning meeting.

Keep the reasoning, not just the list

The list of OKRs survives in a doc. The reasons behind each target usually don't. If you hold the meeting on Bridge, you get a speaker-labeled transcript, notes and a recording afterwards.

Before the mid-quarter check-in, open that recap and ask the Assistant why a target was set. It answers from that meeting's notes and transcript.

Sources & further reading