How to Run an OKR Planning Session That Ends in Commitment

Run an OKR planning session in two hours with a context pack sent in advance, a hard limit of three objectives, and a closing round where each key result gets a named owner and a stated measurement source. The session’s job is not to write beautiful objectives. It is to end disagreement about what the next quarter is for.

This is for whoever facilitates. It assumes you know what an objective and a key result are, and if you do not, the definitions and the pitfalls that sink them are covered separately. What follows is the running order and the two moments where these sessions go wrong.

How to run an OKR planning session

Run it as two blocks: a short framing block for context and constraints, then a longer drafting block where the team writes, cuts and assigns. Two hours is enough for one team. A full day gets spent on adjectives.

1. Send the context pack 48 hours ahead. Strategy, last cycle’s results with the misses shown as plainly as the hits, and any company-level objectives this team must align to. People arriving cold spend the first half hour catching up while the confident ones set the agenda.
2. Open with the constraints, not the ambitions. Cycle length, the maximum number of objectives, and what is already committed: contractual dates, roadmap promises, a hire that will not land until month two.
3. Draft silently first. Ten minutes, everyone writes two or three candidate objectives alone. Sessions that open with discussion converge on whoever spoke first, usually the most senior person rather than the closest to the work.
4. Cluster, then cut to the limit. Force the cut while the wording is still ugly. Once an objective has been polished, someone owns it emotionally and cutting it becomes a personal loss.
5. Write key results against each surviving objective. Aim for three. Each needs a number, a named source for that number, and a starting value.
6. Stress-test every key result out loud. Teams skip this when they are running late, and it is why OKR sets quietly turn into status reports by week four.
7. Assign and schedule. One named person per key result, and a first check-in date in calendars before anyone leaves.

Steps four and seven are where sessions fail. Skip the cut and you leave with a wish list. Skip the scheduling and the document goes unopened until the cycle review.

How many OKRs should a team have?

Three objectives with three key results each is the practical ceiling for one team in one quarter, and two objectives is usually better. The figure most commonly taught is three to five of each, from John Doerr’s writing on the method, but five by five hands a team twenty-five measurable commitments on top of its ordinary work.

Count the key results, not the objectives. Nine is a set a team can recite in week seven. Twenty-five is a spreadsheet somebody maintains.

• One team, one quarter: two or three objectives, three key results each
• Fewer than five people: one objective, given proper key results
• An individual: none of their own. Individual OKRs turn a planning tool into a performance review
• Company level: three to five objectives, with team sets that support them rather than copy them. How those cascade downward is a rollout question, and setup, levels and ownership are covered separately

If the team insists everything on the list is essential, that is your finding. A group that cannot cut to three has not agreed a priority. It has agreed a wish list and distributed the blame for missing it.

OKRs vs KPIs: which of your numbers belong in the session?

Objectives and key results describe a change you intend to cause this cycle. Key performance indicators describe the health of something that runs continuously. Only the first belongs in the OKR set.

	OKR	KPI
What it describes	A change you are trying to cause	A condition you are trying to hold
Time bound	Yes, one cycle	No, it runs indefinitely
Target	Set beyond comfortable, deliberately	Set at a threshold you defend
In the session	Yes, this is the work	On the wall as context, not on the list

The commonest way an OKR set goes stale is a team promoting a metric it already tracks. Uptime at 99.9 percent, churn under two percent: those are thresholds to defend, and dressing them as objectives commits the team to carrying on as before.

A deteriorating KPI can become an objective for one cycle and revert afterwards. For the wider distinction, read the comparison of OKRs, KPIs and north star metrics.

How to stress-test a key result before it goes in the document

Test every key result with four questions, asked out loud while its author is still in the room.

1. Where does the number come from? Name the report, dashboard or query. If nobody can, building the measurement is work that needs its own owner and date.
2. What is it now? “Increase activation to 40 percent” is a different commitment depending on whether you start at 38 or at 12.
3. Who reads it out at the check-in? Not who is responsible in a general sense. Who says the number.
4. If we hit this and the objective still has not happened, what did we get wrong? This flushes out proxy metrics, the ones that measure activity because the outcome is harder to see.

Expect this step to kill drafts, and let it. Watch the verbs while you are at it. Improve, support, increase awareness of, drive engagement with: those describe effort, not result.

How to close the session so the commitment is real

Close by having each owner read their own key result aloud, in their own words, with the date of the first check-in. Agreement that was only nodded at across a table does not survive contact with a busy fortnight.

Everyone should leave with four things:

• The written set, visible to the whole team by end of day
• One named person per key result, a person and not a function
• A check-in cadence in calendars, fortnightly or monthly, with the first one booked
• A note of what the team decided not to do this cycle, which is the part people forget and then relitigate in March

Silence is not agreement. If someone stayed quiet through the cut, ask which of these they think will not happen, and write the answer next to the objective. The cheapest doubt to handle is the one voiced before the cycle starts.

Some teams hand facilitation to software: Projan runs the session as a structured conversation in Slack or Microsoft Teams, pressing on where each key result’s number comes from and who will report it, then writing the agreed set and its follow-up tasks out to Asana or Notion. The tooling matters less than the habit, which is the same one behind this guide to running a project planning workshop.

Frequently asked questions

How many OKRs per team? Two or three objectives per team per quarter, each with three key results. Teams smaller than five people should carry one. The limit is about recall rather than ambition: a team that cannot list its key results from memory in week seven has stopped using them.

Who should attend an OKR planning session? The people who will own the key results, plus whoever can say no for the wider organisation. Keep it under about eight. Observers change the dynamic, because people argue less honestly when their skip level is watching. Absentees send their input as pre-work instead of reopening decisions later.

What do you do if the team cannot agree on an objective? Park it and name the decision that has to be made first. Most deadlocked objectives hide an unmade decision elsewhere, usually about resourcing or about which customer segment matters. Escalate that decision to whoever owns it, with a date, and leave the objective out until it returns.

A good OKR session is mostly subtraction. Cut to a set the team can recite, put a name and a measurable number against every line, and book the first check-in before anyone stands up.