OKRs for All

CHAPTER 21FAQs for OKR Check‐Ins

What content should be included in an OKR check‐in?

Your OKR check‐in should contain the data update for each key result and key initiative, alongside a short commentary to add any qualitative context to the data. An example of this update would be “Our product was mentioned in close to 50% of the total press articles about our industry because of our company event. We doubled our goal of 110 articles, and this becomes our new baseline for large‐moment press adoption.”

How should you run an OKR check‐in meeting?

An OKR check‐in meeting should have the expectation set that all check‐ins are made prior to the meeting itself. From there, the meeting conversation should primarily focus on those OKRs that are behind or at‐risk; a dashboard with an OKR list widget that filters for just those statuses can be helpful to facilitate this conversation.

The conversation on the behind or at‐risk OKRs should primarily revolve around a collaborative discussion on how to get those OKRs back on track, and each conversation should conclude with a clear set of next steps and ownership.

Timeboxing the conversation to a predefined amount of time (based on the volume of OKRs on the agenda and meeting duration) can be helpful to ensure that all relevant OKRs are covered.

At the end of the meeting, if time permits, the team can review the other OKRs.

How do you check in on dependencies across an OKR?

Reviewing dependencies should happen asynchronously by the ...