How to check a key result actually measures its objective
A key result can look specific, numeric, and well written, and still fail to measure its objective. This happens when a key result tracks something that's easy to measure instead of something that reflects whether the objective was actually achieved. The fix isn't better wording, it's a quick check before the key result is approved.
The one-sentence test
Read the objective, then read the key result, and finish this sentence: "If this key result hits its target, that proves the objective was achieved because ___." If you can't finish that sentence without stretching, the key result is measuring something adjacent to the objective, not the objective itself.
Two ways key results drift from their objective
- Too narrow: the key result measures one small, convenient piece of the objective (one specific barrier, one channel) instead of the outcome as a whole. Hitting it wouldn't actually mean the objective was reached.
- Too broad or shared: the key result is written generally enough that it could sit under two different objectives at once. That usually means it isn't specific to either one, and it becomes unclear who owns it.
A worked example
Objective: "New customers get value from the product quickly."
Weak key result: "Reduce support tickets about billing by 50%." This
measures a narrow friction point, not whether new customers are getting value.
Better key result: "Increase the share of new customers who complete
their first key workflow within 7 days from 40% to 70%." This directly reflects the
objective's outcome.
When one key result isn't enough
Some objectives are broad enough that no single number can represent them. In that case, use two or three key results that together cover the ambition, rather than forcing one key result to carry the whole objective. See how to write good key results for guidance on choosing the right number.
Common mistakes to avoid
- Picking a key result because the data already exists, not because it reflects the objective
- Letting one key result satisfy two different objectives to save time
- Approving a key result without asking what achieving it would actually prove
Next step
Run this check during your review round, before key results are finalized. See how to review OKR drafts before they're finalized.