Google’s OKR Playbook: 5 Lessons for Writing Better OKRs

Even though I’ve invested significant time into studying OKRs, one thing has become obvious to me – companies don’t fail because they lack goals; rather, they fail because they lack goals telling them what should be changed.

This is what got me hooked when studying how Google implements OKRs.

The OKR Google approach is especially useful because it shows how a simple framework can create much stronger focus and accountability.

The system itself is pretty simple – objectives define your destination, while key results show if you’ve gotten there. But it is precisely the ability of OKRs to make people think about outcomes, priorities, responsibility, and actions that makes this system truly helpful.

These are what I consider the five most valuable lessons learned from Google’s OKR playbook.

1. Measure Results, Not Activities

Characteristics of Good Key Results

One of the most frequent errors that I make when writing Key Results is considering activities as Key Results. Organizing a campaign, carrying out interviews, or releasing new features will give us information about what we have done rather than about changes we have achieved.

A good Key Result measures results. In place of “Launch a customer retention campaign,” we should write “Increase customer retention from 82% to 88%.”

A campaign is an initiative. Improving customer retention is the result.

2. Make Every Key Result Count

The 100% Test

One thing I find particularly useful in the OKR Google framework is this focus on whether Key Results actually prove that the Objective has been achieved. 

This is how I like to check OKRs during the review process: If all Key Results get fully completed, will we definitely achieve the Objective? If not, there must be something missing.

For example, the Objective is “Improving the customer onboarding process.” Improving the process flow, making some video guides, and training the support sales team might do the job, but that does not necessarily mean the onboarding process has been improved.

More meaningful OKRs should check such metrics as success rates, time to value, dropout rate, or customer satisfaction.

3. Know When to Stretch and When to Commit

Committed Objectives vs Aspirational OKRs

OKRs at Google are divided into two categories: committed and aspirational. This classification seems quite helpful because not all goals are equal.

This distinction is one of the most practical lessons from the OKR Google system because it sets the right expectation for different types of goals 

Commits are objectives that need to be achieved, like financial targets, deadlines, or successful launches. On the other hand, aspirational OKRs are meant to stretch teams and make them go beyond their limits.

The trick is in clear definitions: if everything is committed, it means nothing is challenging; if everything is aspirational, it will never be achievable.

The team should understand right away which type of objective it deals with.

4. Good OKRs Make Priority Changes

Don’t Create OKRs that are “Business as Usual”

In evaluating any OKR, my first question is: Will this get done anyway? If the answer is yes, then the work may be considered “business as usual”.

For example, “Complete monthly payroll on time” is a necessary task, but it’s not an OKR. Better would be an Objective based on improvement, like “Reduce hiring times” or “Enhance employee retention”.

OKRs should enable teams to make decisions about what matters when conflicting priorities arise.

This is why I consider OKRs to be more than a method of setting goals – they’re also about making focus and prioritization choices.

5. Tie OKRs to Execution

Objectives → Key Results → Initiatives

OKRs make more sense to me if they are properly split between objectives, key results, and initiatives.

The objective states what you want to achieve. The key result describes how it will be measured, whereas initiatives are things you do to achieve your objective.

Thus, for instance, the objective may be “Building up the enterprise sales engine,” while one of the key results could be “Generating 50 qualified enterprise opportunities up from 30 per quarter.”

The initiatives may comprise more precise targeting, better outreach, an ABM campaign, a referrals programme, and so on.

However, it should be stressed that initiatives may vary over time without altering the desired outcome.

That is why formulating the OKR is just the beginning. It is the review, blockers discussion, and course adjustment that ensure everyday OKR execution.

Conclusion

OKRs Aren’t Only About Performance Metrics. They’re About Driving Performance.

What I take away most from the OKR Google approach is that strong goal-setting depends less on complexity and more on clarity, focus, and consistent execution. 

As I’ve done more research on successful OKR frameworks, it becomes obvious that the complexity does not lie in the framework itself. The difficulty lies in picking the right priorities, determining the desired outcomes, and keeping them visible through execution.

Good OKRs not only set out where you want to get by the end of the quarter but show you what matters now, what slows down the progress, and what needs to be changed.

This is precisely why we came up with the JOP idea: helping teams not just use OKRs but bring them into the performance management process through OKR conversations and execution.

And if OKRs become visible and actionable, they become a true performance management system.