The most important ritual to incorporate in your OKR program is the weekly OKR Check-in’s. One of the big reasons companies fail to adopt OKRs is that teams simply “set and forget” them. Like any good habit, OKRs must become a deep cultural part of your company DNA.

How often should you meet for a Check-in

This depends on the length of your projects that move the Key results. and also the duration of your key results themselves.

  1. For quarterly goals and key results. the ideal check-in cadence is weekly and at most fortnightly
  2. For goals longer than a quarter. check-in meetings could even be monthly. but no longer.
Who should be in the Check-in

Product managers, Engineering, Design, and leadership stakeholder should participate in the check-in meeting. The leadership team needs to be a part of this to help resolve blockers earlier on and help the team succeed.

Elements of a Check-in

Current OKR Status
Starts with data. What is the current number of that Key Result? Change since the last Check-in.

Initiatives this week
What are the high-impact initiatives or projects that the team will work on to move the key result number?

Updates from last week
Talk about Initiatives or projects from the previous period and call our wins or learning

Risks or Blockers
Call out blockers or risks such as a change in market conditions or blockers from another team.

Sample KR check-in

Current KR Status: On-Track

We’re currently at 30% towards our goal.
This is a 10% increase from the last week

Upcoming Initiatives

Next week, re-design sign up screen
Launch the new Intro video

Updates from last week

We shipped one onboarding Experiment

Risks or Blockers

New video: Our video team has conflicting priorities which need to be resolved

North Features
Org and Team goals
Goal Initiatives
Goal Check-ins
Give Awards
Goal Alignment

Our take on Product
On Product discovery
Communicating well
Metrics for Product teams
Telling stories with data
Data visualisation


Back to Top