How to Run an OKR Planning Meeting

Most teams have a weekly check-in and, if they are disciplined, a retrospective at the end of the cycle. The meeting that gets skipped is the one in between: the planning meeting, where the team decides what the next cycle's OKRs actually are. Without it, new Objectives get written alone in a document, shared in a channel, and never really agreed on. The result is a set of goals nobody feels ownership of.

What the Planning Meeting Is For

A planning meeting has one job: leave the room with an agreed set of Objectives and Key Results, each with an owner and a target. That is it. It is not a strategy workshop, not a brainstorming session, and not a review of last cycle. Those are different conversations, and mixing them into the planning meeting is the fastest way to run out of time before any decision is made.

It helps to think of the meeting as making three decisions about every existing Objective, then writing what is missing. The three decisions are: keep it as it is, close it because it is done or no longer relevant, or change it because the target or the measure was wrong. Everything else in the agenda exists to make those decisions possible.

The Simplified Cadence Model

Classic OKR advice ties everything to the calendar quarter. Quarters start, quarters end, and a whole set of goals is created and retired on those dates. That works for large organizations with a planning department, and it creates a lot of busywork for everyone else.

The simplified model replaces the calendar with a rhythm. It has three parts:

• A cycle length, set once. Three months is the sensible default, but one month suits a young startup and six months suits a slow-moving Organization. It is one setting, not a structure that Objectives belong to.
• Weekly check-ins during the cycle. Short updates on Key Result progress and anything blocking it. These run independently of the cycle length.
• Two meetings at the end of each cycle. First a retrospective, to reflect and learn. Then a planning meeting, to adjust the goals. In that order, always.

The important difference is that your OKRs are not containers tied to a date. An Objective that still matters simply continues into the next cycle, untouched, and keeps its history. The cycle is a prompt to review, not a deadline that forces a reset. This removes most of the administrative weight from OKR planning, which matters because admin weight is the main reason OKR programs quietly die. Research from MIT Sloan Management Review on how organizations are reshaping OKR cycles points the same way: the rhythm should follow how a team actually works rather than a fixed rule.

One more detail makes the model self-correcting. The next review is counted from the last retrospective you completed, not from a date on a plan. If a cycle slips by two weeks, the next one shifts with it instead of leaving you permanently behind schedule.

Before the Meeting

A planning meeting fails on preparation more often than on facilitation. Three things need to be true before people sit down.

The retrospective is finished and written down. This is the single biggest factor. If the team has already agreed on what worked, what did not, and what to change, the planning meeting has something to build on. If not, the first hour turns into an unstructured post-mortem and no goals get set.

Progress is up to date. Every Key Result should have a current value, so the discussion is about real numbers instead of guesses. Chasing updates live in the meeting wastes everyone's time.

Draft ideas are collected in advance. Ask everyone to bring one or two Objective ideas beforehand. Writing from a blank page in a group is slow, and it tends to produce whatever the most senior person in the room said first.

Who Should Be There

Keep it to the people who own the work: the leader accountable for the goals, the owner of every Objective under discussion, and the owners of the Key Results. For a small Organization that is often the whole team, which is fine. For a larger one, run separate planning meetings per team after the leadership team has set its own OKRs, so each team knows the direction it is contributing to.

A 90 Minute Agenda

Ninety minutes is enough for most teams, and a firm time limit does more for meeting quality than almost any other change, a point Harvard Business Review makes in its research on why meetings go wrong. Here is an agenda that fits:

• Recap the retrospective, 10 minutes. Read out what the team decided to change this cycle. No discussion, just a reminder of the conclusions.
• Review the current OKRs, 25 minutes. Go through each Objective and make one of the three decisions: keep, close, or change. Say the decision out loud and record it before moving on.
• Decide the focus, 15 minutes. Given what is being kept, what is the most important new thing for this cycle? Agree on the theme before writing anything.
• Write the new Objectives, 25 minutes. Turn the agreed focus into Objectives, each with two to five Key Results. Write them in the tool during the meeting, not afterwards.
• Assign and confirm, 15 minutes. Every Objective and Key Result gets a named owner who says out loud that they accept it. Set the check-in day, then close the meeting.

If you cannot get through it, the usual cause is too many OKRs in play. Three to five Objectives per team is a ceiling, not a target.

Common Mistakes

Starting from a blank page. Most of your goals from last cycle are probably still the right ones. Continuing them is a legitimate outcome, not a lack of ambition.

Turning the meeting into a retrospective. If the conversation keeps going back to why a target was missed, the retrospective was not actually finished. Note it, and schedule that conversation separately.

Leaving without owners. An Objective with no named owner will not get a single check-in. Assign owners in the room, while everyone is present to object.

Writing Activities as Key Results. Under time pressure, teams reach for what is easy to write down, which is usually a list of work to do. Keep Key Results as outcomes, and put the work underneath them as Activities.

How Easy OKR Supports This

Easy OKR is built around exactly this model. You set one cycle length for your Organization, and the app counts forward from your last published retrospective to work out when the next review is due. As the cycle winds down you get a nudge in the app and an email reminder, so nobody has to remember to schedule the two meetings. The retrospective template asks the same five questions every cycle, and the guidance beside it points you from the retrospective straight into planning: decide which OKRs are still relevant, close the ones that are not, and adjust or create the rest. Because Objectives are not locked to a cycle, keeping one is a single decision rather than a copy-and-recreate exercise.

Start With One

If your team has never held a proper planning meeting, book 90 minutes at the end of this cycle and run the agenda above once. You will probably finish with fewer OKRs than you expected, clearer ownership, and a shorter list of goals the team actually believes in. That is the point.

References

• From Vision to Reality: How OKRs Are Reshaping Team Goals — MIT Sloan Management Review
• Stop the Meeting Madness — Harvard Business Review
• Measure What Matters — John Doerr
• Radical Focus — Christina Wodtke