OKR Meetings: The Four Meetings a Quarter Actually Needs
OKR Meetings: The Four Meetings a Quarter Actually Needs
Most teams don’t have an OKR meeting problem. They have four different conversations compressed into one recurring forty-minute slot, and none of them now does its job. Planning happens next to progress reporting. Scoring happens next to re-planning. What ends up on the calendar looks like execution discipline and behaves like drift.
A quarter needs four meetings, each producing one kind of decision. Run them separately and the cycle holds. Merge them and the cycle becomes a reporting ritual with a scoring event at the end.
What is an OKR meeting?
An OKR meeting is any recurring meeting where a team sets, updates, reviews or closes its objectives and key results. A standard quarterly cycle contains four of them, and each one exists to produce a different decision.
The generic label is where the trouble starts. When everything from a two-hour planning workshop to a fifteen-minute progress update is called “the OKR meeting”, people stop knowing what they are walking into, and they prepare for all of it or none of it. Naming each meeting for the decision it makes is the cheapest fix available to a rollout
.
Which meetings does an OKR cycle actually need?
Four: a planning meeting before the quarter starts, a weekly check-in inside each team, a review above team level each month, and a retrospective at the close. IBM describes the same shape, with the cycle operating on a quarterly cadence, “monthly reviews at the department or division level” and “weekly or biweekly team check-ins”.
| Meeting | Frequency | Length | Who is in it | The decision it produces |
|---|---|---|---|---|
| OKR planning | Once, before the quarter opens | 60 to 90 minutes | The whole team | Which objectives this team commits to, and who owns each key result |
| Weekly check-in | Every week | 15 to 30 minutes | Only the people who own key results | What each owner will do in the next seven days |
| Monthly review | Months one and two of the quarter | 45 to 60 minutes | Team leads and the stakeholders who control resources | Whether to keep, change or resource an OKR differently |
| Quarterly retrospective | Last week of the quarter | 60 to 90 minutes | The whole team | What changes in how the next quarter’s OKRs are written and run |
The durations here match the cadence Tability publishes for OKR meetings, which puts the quarterly kickoff and the retrospective at “60-90 minutes”, the weekly check-in at “15-30 minutes” with the “team responsible for OKRs”, and the monthly review at “45-60 minutes” with “team leads and stakeholders”.
When should OKR planning start?
Before the quarter opens, not in its first week. What Matters places senior leaders brainstorming top-line company OKRs four to six weeks before the quarter and company OKRs finalised and communicated to everyone two weeks before it starts.
Teams that hold their OKR planning meeting in week one lose the first month. They spend week one drafting, week two waiting for leadership alignment, week three revising, and by the time anything is agreed the quarter is a third gone and nobody wants to admit the set is unfinished. This is the most expensive scheduling mistake in the cycle and it costs nothing to fix.
What happens in the weekly OKR meeting?
Key result owners report where each metric stands, name what is blocking them, and commit to what they will do in the next seven days. It runs fifteen to thirty minutes with the people who own the key results, and updates are written before the meeting rather than read aloud in it.
The weekly meeting is the one that decides whether the other three were worth holding. A quarter’s planning survives contact with reality only if something checks the plan against the work while there is still time to change either. We go deeper on the format in the OKR check-in.
What is an OKR review meeting, and how is it different from a check-in?
A review meeting runs above team level and asks whether the OKRs are still the right ones. A check-in runs inside the team and asks whether the work is moving.
The distinction is about authority, not seniority. A check-in can identify that a key result needs fewer people and a different approach, and then it stops, because the team cannot reallocate what it does not control. The review meeting exists so that finding has somewhere to go. If your monthly review never changes a resourcing decision, you are running a longer check-in with more expensive people in the room.
What belongs on an OKR meeting agenda?
One decision type per meeting, and nothing that belongs to a different meeting in the cycle. Before an item goes on any OKR meeting agenda, the test is simple: which of the four meetings is this for?
Planning covers last quarter’s lessons, this quarter’s objectives, and ownership of each key result. The weekly check-in covers current numbers, confidence, blockers and next week’s commitments. The monthly review covers progress against plan and what leadership will change about it. The retrospective covers final scores and what the team will do differently, which is where most cycles quietly skip half the agenda. Scoring is quick and comfortable. Reflection is neither, and What Matters is right to treat grading and reflecting as “two different yet complementary conversations”.
How do you run an OKR meeting that changes what people do?
End it with named owners and dates instead of a summary. A meeting that changes nobody’s week will not survive its first calendar conflict, and it shouldn’t.
The pattern our coaches see most often is a full set of meetings with no decision rights attached to any of them. Teams report, leaders listen, nothing moves, and within two quarters the cadence is gone. Getting decision rights into the calendar is most of what OKR-Implementierung work actually consists of.
Why do four OKR meetings collapse into one?
Because leadership time is scarce and the four meetings look interchangeable from outside. What separates them is the decision each one is allowed to make, and that separation disappears the moment they share a slot.
The collapse follows a predictable order. The retrospective goes first, absorbed into the scoring conversation. Planning goes next, folded into the first review of the new quarter. What survives is a monthly meeting where teams report numbers to people who then approve them, which is the exact ritual OKRs were supposed to replace. Busyness becomes the proxy for performance again, and the framework gets blamed for a calendar problem.
Who should attend each OKR meeting?
Planning and the retrospective take the whole team, because both are about commitments the team has to own. The weekly check-in takes only key result owners, and the monthly review takes team leads plus whoever can actually move budget or people.
Observers are the quiet killer of the weekly meeting. Every additional person who is present but accountable for nothing raises the cost of saying “this isn’t working”, and candour in week three is the entire point of checking in weekly at all.
Frequently asked questions
What does OKR meeting mean? It refers to any recurring meeting in an OKR cycle where a team sets, updates, reviews or closes its objectives and key results. Four distinct meetings exist in a standard quarter.
How long should an OKR meeting be? It depends which one. Planning and the retrospective run 60 to 90 minutes, the monthly review 45 to 60, and the weekly check-in 15 to 30.
Can we combine the OKR review and the weekly check-in? Only if the same people can make both kinds of decision, which is rare. The check-in commits a team to next week’s work; the review changes what the team is resourced to do.
Do we need an OKR planning meeting every quarter? Yes, though it gets shorter each cycle. Most of the length in a first planning meeting comes from teams learning to write key results, not from choosing objectives.
Who runs the OKR meeting? The team lead for the check-in and the retrospective, and the leader who owns the area for the monthly review. Ownership of the meeting and ownership of the outcomes should sit in the same place.
What if nobody comes to the OKR meeting? Look at what the last four produced. Attendance follows consequence, and a meeting people skip is usually one where nothing was ever decided.
If your OKR meetings have merged into a single reporting slot, that is a calendar and decision-rights problem before it is an OKR problem, and it is fixable inside one quarter. Our coaches rebuild the cadence with teams in the 90-Day Execution Sprint.
About the author
Dirk Schmellenkamp is Founder and CEO of the OKR Institute, which has certified more than 70,000 practitioners and run OKR implementation programmes for over 1,000 organizations across 50+ countries since 2017. The OKR Institute is accredited by the International Coaching Federation, the Association for Coaching and HRD Corp.
CEO des OKR Instituts
Ähnliche Kurse
kürzliche Posts
Stichworte
#OKR
#OKR AI agents
#trends 2026