Home/Blog/OKRs/How to Run a Weekly OKR Check In in Fift…
OKRs

How to Run a Weekly OKR Check In in Fifteen Minutes

How to run a weekly OKR check in: fifteen minutes, three questions per key result, and a report of confidence rather than percentages, so trouble shows early.

Cover of the FIKR Space guide: How to Run a Weekly OKR Check In in Fifteen Minutes

To run a weekly OKR check in, spend fifteen minutes going through each key result and ask three things: what is the number now, how confident is its owner of hitting it, and what is in the way. Keep it short, keep it boring and report confidence rather than percentage complete.

This is the smallest habit in the whole method and the one that decides whether the rest does anything. Quarterly goals that are only looked at quarterly cannot influence what people do in between, and in between is where all the behaviour happens.

How to run a weekly OKR check in: the agenda

The meeting has one job, which is to keep the goals in view and to catch trouble early. It needs very little structure.

StepThe questionWho answers
1What is the number now?The key result's owner
2How confident are you of hitting it?The key result's owner
3What is in the way?The owner, then the room
4Who owns the blocker and by when?Agreed before moving on

Run those four steps once for each key result and stop. A company that follows the ceiling in how many OKRs a startup should have will find that the whole set fits comfortably in the time. That is no accident. A short list and a short meeting support each other.

Why confidence beats percentage complete

Percentage complete looks backwards. It tells you how much of the target has been reached, and it moves only when the metric moves. Confidence looks forwards. It is the owner's honest view of whether the result will land, and it moves early.

The guide's observation is that a person's confidence usually drops several weeks before the metric does. That turns the meeting from a reporting session into an early warning system. If an owner who was sure last week now says they are unsure, the room has something real to talk about while there is still time to act.

It also changes the kind of talk. A percentage invites arguments about whether it should be a little higher. A confidence level invites the more useful question of why it fell, and what would have to change for it to rise again.

Free guide, 32 pages: The OKR Playbook. Send me the guide.

What to watch for in the answers

You are listening for movement, not for a pass mark. The guide's checklist for the weekly loop points at the right places.

  • Confidence changes are discussed, especially drops, before the metric moves.
  • Blockers get an owner and a date, in the meeting.
  • The meeting stayed short and nobody prepared slides.

A drop in confidence is the most valuable thing a person can say in this room, so respond to it as news. If it is met with a defensive question, people will learn to keep their confidence artificially high, and you will have rebuilt the problem the meeting was meant to solve. The same instinct is described in how to score OKRs, where a high score everywhere is treated as a warning, not a celebration.

Keep it short and keep it boring

The guide is blunt that the value of this meeting is entirely in its regularity. It gets that value from being a habit, not from being impressive.

The moment it becomes a performance with slides, it stops being useful and starts being avoided. People who have to prepare a presentation will prepare a flattering one, and the flattering version is the opposite of an early warning. So set the rules plainly.

  1. No slides.
  2. No preparation beyond knowing your own number and your own confidence.
  3. A fixed time and a fixed length, in the calendar for the whole quarter.
  4. When a topic needs more than a minute, note it and take it away from the meeting.

The point about the calendar is deliberate. The guide's checklist asks for the weekly check to be booked for the whole quarter, not only for next week. A habit that has to be rescheduled each time is a habit that will lapse.

Where the number comes from

An owner can only report the current number if it is easy to get. The guide's checklist says the measurement source must be agreed and accessible before the quarter starts, and that two people should report the same figure from the same data.

If the owner has to spend an hour assembling the number before the meeting, the meeting will drift towards impressions. Agree the source up front and the number becomes something you read out in a sentence. That is also why the baseline matters at the outset, since a current value has nothing to compare with otherwise. The starting value is the subject of how to set a key result baseline.

What this meeting is not

It is not a status meeting about what everyone did all week. The guide describes the check as a way of making progress visible without surveillance. The conversation is about whether the number is moving and what is in the way, not about how each person spent their days.

It is also not the place to rewrite the goals or to re-argue priorities from scratch. If a goal looks wrong, that is a signal to raise at the mid-quarter checkpoint, not to resolve in fifteen minutes. And it is not a score. Scoring happens at the end, honestly and without adjustment, as a separate act.

FIKR OS, strategy meets execution: OKRs, roadmaps and kanbans in one system. See FIKR OS.

Blockers need an owner and a date

The third question, what is in the way, is where the meeting earns its keep. A blocker that is named but not assigned is just a complaint. The guide's checklist asks that blockers get an owner and a date, in the meeting, before moving on.

That small rule changes the character of the conversation. The owner of a key result is accountable for saying early that something is stuck, but not obliged to fix everything alone. Naming who will unblock it, and by when, turns a worry into a commitment that can be checked at the next check in, a week later. If the same blocker appears twice with the same name against it, you have learned something about the goal, the person or the obstacle, and it is better to learn that in week three than in week twelve.

Setting up the first one

You do not need tooling to start. The guide is explicit that the method can be run with a document, a spreadsheet and real discipline. What you need is a repeatable slot and a short list.

  1. Put the meeting in the calendar for every week of the quarter.
  2. List each key result with its baseline, target and named owner.
  3. Add two columns for each week: the number and the owner's confidence.
  4. Add a third column for what is in the way.
  5. Begin the first meeting by reading the list aloud and checking each owner agrees with it.

That is the whole apparatus. The discipline is the weekly return to it, and the evidence of the discipline is that nothing about the meeting is impressive.

When a goal looks dead

Sometimes the weekly answers keep sinking, and the cause is not an obstacle but the goal itself: the market moved, an assumption was wrong, or something more important arrived. The weekly check is where that first shows up, usually as a confidence that has fallen and stayed fallen.

The guide's advice is to say so early, state why in writing and redirect the effort, rather than carry the goal for weeks out of reluctance to admit error. How to do that as a team is covered in how to run an OKR retrospective, which also describes the longer session at the middle of the quarter.

Free guide, 32 pages: The OKR Playbook. Send me the guide.

If you cannot commit to the weekly check

The guide gives a stark instruction here. If you cannot commit to the weekly check, do not bother with the quarterly document. It will become the thing everyone politely ignores.

That is a useful gate. Before you write a single objective, put the weekly slot in the calendar and ask who will run it. If you cannot name the person and the time, you have found your first real task. Skipping the weekly rhythm is also one of the nine mistakes in the guide, and a diagnosis of the others is in OKR mistakes founders make.

FIKR OS, strategy meets execution: OKRs, roadmaps and kanbans in one system. See FIKR OS.

Frequently asked questions

How long should the meeting be?

Fifteen minutes. If it regularly runs over, either the set has too many key results or discussion is being held in the meeting that belongs elsewhere.

Who should attend?

The owners of the key results, since they are the people who answer the three questions. Each key result has a single named owner, so each one has someone who can speak to it.

Why not track percentage complete as well?

You can read the number, but confidence is the better instrument because it looks forward and moves early. The percentage tells you where you are, not where you are heading.

What if confidence is high every week?

Treat uniform green as a warning rather than a comfort. Either the goals were set inside what was going to happen anyway, or people are managing the report, or bad news is not travelling.

The full method, with the checklists, is in The OKR Playbook, a free 32-page playbook.

LG

Luis Goncalves

// Founder & CEO at FIKR Space

Three-time founder. Built and exited Evolution4All before this. Now building FIKR Space — the operating infrastructure underneath every innovation ecosystem (startups, accelerators, governments, investors). Lisbon-based, works global.

Claim your founding member spot.

Every founding member is hand-reviewed. Tell us who you are and how you want to co-create — we get back inside 48 hours.

Role
Job Title
Country
Cookies

We use cookies.

Essential ones keep the site working. The rest only run if you say so. No dark patterns, no pre-ticked boxes.Privacy policy

Co-create with us. It's about building it together.Co-Create With Us