Most OKRs end up forgotten by week three. We share the exact format and review cadence that keeps our team aligned all quarter.
We've done OKRs badly. Very badly. We've written objectives so vague they could mean anything. We've written key results that were actually tasks. We've set them in January and looked at them again in April to find we'd completely forgotten they existed.
After three failed quarters, we got serious. Here's what changed.
The format that works for us
Objective: a qualitative, inspirational direction. It should be uncomfortable to say you didn't achieve it.
Key Results: 2–3 per objective, measurable, binary or numeric. Not "improve NPS" but "raise NPS from 32 to 45." Not "launch onboarding" but "achieve 40% activation rate on new signups."
The cadence that keeps them alive
We review OKRs every two weeks in our all-hands. Not a long review — five minutes, each team lead gives a traffic-light status. Red, yellow, green. If anything is red, we discuss why and what's changing.
The two-week cadence sounds like a lot. But it's what keeps OKRs from becoming January-only artifacts. When you talk about them every two weeks, they become real.
The rule we added
No task gets added to the sprint unless someone can articulate which OKR it moves. This sounds rigid. In practice it takes 30 seconds per task and eliminates a huge amount of busy work that doesn't move the needle.