Most teams approach OKR planning the same way: a leader writes the objectives on a Friday afternoon, drops them into a doc, and asks the team for feedback on Monday. By Wednesday everyone has signed off, and within a fortnight nobody can remember what was agreed. The framework is fine. The problem is the meeting. If you already know which framework you are using and how to write good ones, the missing piece is the conversation that turns a draft into a commitment your team owns.
OKRs that are handed down get tolerated. OKRs that are argued through together get owned. The planning meeting is where that switch happens, and it is the part most managers under-invest in.
Prep the room before you book it
The planning meeting fails before it starts when people walk in cold. They cannot debate priorities they have not thought about, so they default to whatever the most senior person says. The fix is half an hour of preparation a week earlier, with three artefacts shared in advance so the meeting is for the hard conversation, not the briefing.
Sent at least 5 days before the meeting
Last quarter review
What we landed, what we missed, what we learnt.
Strategic context
One paragraph: where the company is heading this quarter.
Three or four draft themes
Not full OKRs. Just the directions you are considering.
Ask everyone to come with one objective they would add and one they would cut.
The point of sending draft themes (not finished OKRs) is to invite challenge. If you ship polished objectives, the meeting becomes a rubber stamp. If you ship rough themes, the team has space to push back, combine ideas, or surface the thing you missed. A good signal that you have prepped well is when someone arrives with a counter-proposal, not a question.
A meeting structure that holds up
Two hours is usually enough for a five-to-eight person team. Less than that and you end up rushing the negotiation. More than that and people stop engaging. Split the time so the early phases stay tight and the negotiation phase gets the room it needs.
Two-hour planning meeting
The negotiation block is the biggest. Defend it.
- Ground rulesTwo minutes at the top. Phones away, one person speaks at a time, disagreements get aired in the room rather than after. A weak agreement now is a missed deadline in October.
- Strategic contextWhoever owns the wider strategy gives a fifteen-minute briefing. Where the company is going, what changed since last quarter, the one or two constraints the team needs to know about.
- Walk the themesRead each draft theme aloud. Ask "what is missing" and "what would you cut" before you ask "what would you add". This biases the room toward focus rather than scope creep.
- Lock objectivesYou should land on three to five objectives. Write them on the wall (or screen) so everyone can see them. Resist the urge to wordsmith here; that is for follow-up.
- Draft key resultsFor each objective, generate measurable key results together. Aim for three per objective. If you cannot agree how to measure something, it probably should not be a key result.
- Owners and cadenceEvery objective needs a named owner who will report on it. Agree how often the team will check in (weekly or fortnightly works for most teams) and what format the update takes.
Notice what is not on the list: a long preamble about the OKR framework itself. If half your team are new to OKRs, run a thirty-minute briefing earlier in the week. Do not burn the planning session teaching the format. The meeting is for landing the content.
What happens in the 48 hours after
Most OKR planning fails not because the objectives are wrong, but because nothing happens to them in the two days after the meeting. The notes sit in someone's drafts folder. The owners drift. By the time the first check-in arrives, half the team has reverted to their pre-planning priorities. Two pieces of follow-through stop this.
Within 24 hours
Within 48 hours
In Manager Toolkit each objective becomes a Target, with its key results captured as success criteria. Assign the owner, set the deadline, and the Target shows up everywhere it needs to: the dashboard widget, the owner's profile, and their next Catchup. Actions taken to move each key result Connect back to the Target, so when you check progress you can see not just the number, but the work that drove it.
The two days after the meeting are also when you raise the objectives in your one-to-ones. A two-minute mention in the next Catchup signals to each person that the OKR is real. If you leave it until the first formal check-in three weeks later, people will quietly assume it was theatre. Manager Toolkit's Catchup notes Connect to the relevant Target, so the conversation history sits alongside the goal you agreed.
Common ways the meeting goes sideways
Even with prep and structure, the same three failure modes show up across most teams. None of them are about the OKR framework. They are about the meeting itself. Spotting them early lets you steer back.
- Too many objectivesYou land on eight objectives because nobody wanted to disappoint anyone. By week four, half are forgotten. Cap the list at five and treat the cuts as a feature of the meeting, not a failure of it.
- Vague key resultsA key result like "improve onboarding" is a wish, not a measure. If you cannot tell at a glance whether you hit it, rewrite it. "Onboard 6 new starters with a 9/10 satisfaction score" is something you can actually report on.
- Silent ownersOwners who did not speak up in the meeting will not push the work forward afterwards. If someone has gone quiet, ask them directly whether they have the capacity and conviction to own this. Better to swap owners now than discover the gap in October.
For most teams the difference between OKRs working and OKRs being theatre is two hours of prep and a meeting run with discipline. Get the planning right and the quarter runs itself. Get it wrong and you spend three months chasing a doc nobody believed in.
Frequently asked questions
Land your next OKRs
Turn your planning meeting into Targets your team will actually deliver.