Measure What Matters: How Google, Bono, and the Gates Foundation Rock the World with OKRs

by John Doerr

Some simple tests to see if your OKRs are good: If you wrote them down in five minutes, they probably aren’t good. Think. If your objective doesn’t fit on one line, it probably isn’t crisp enough. If your KRs are expressed in team-internal terms (“Launch Foo 4.1”), they probably aren’t good. What matters isn’t the launch, but its impact. Why is Foo 4.1 important? Better: “Launch Foo 4.1 to improve sign-ups by 25 percent.” Or simply: “Improve sign-ups by 25 percent.” Use real dates. If every key result happens on the last day of the quarter, you likely don’t have a real plan. Make sure your key results are measurable: It must be possible to objectively assign a grade at the end of the quarter. “Improve sign-ups” isn’t a good key result. Better: “Improve daily sign-ups by 25 percent by May 1.” Make sure the metrics are unambiguous. If you say “1 million users,” is that all-time users or seven-day actives? If there are important activities on your team (or a significant fraction of its effort) that aren’t covered by OKRs, add more. For larger groups, make OKRs hierarchical—have high-level ones for the entire team, more detailed ones for subteams. Make sure that the “horizontal” OKRs (projects that need multiple teams to contribute) have supporting key results in each subteam.