Builders Camp

Glossary

What Is OKR

An OKR pairs one ambitious Objective, the qualitative answer to where a team wants to go, with a small set of measurable Key Results that show whether it got there. Google's own re:Work guide frames Key Results as outcomes to grade, not a list of activities to complete.

What does an OKR mean?

An OKR, short for Objectives and Key Results, is a goal-setting framework that pairs one ambitious Objective, answering where a team wants to go, with a small number of Key Results, the measurable milestones that show whether the team actually got there. Per Google's re:Work guide, an Objective should be ambitious enough to feel like a real stretch, while Key Results must be quantifiable, gradable, and describe outcomes rather than activities. Google, which introduced the framework to its leadership in early 2000, typically grades Key Results on a 0 to 1.0 scale and keeps OKRs visible across the whole organization rather than hidden inside one team. That visibility is deliberate: a team's OKRs are meant to be checked by anyone else in the company, not filed away in a private document.

Why an OKR matters for product managers

Builders Camp's How to Design OKRs bootcamp opens its practical challenge with a scenario every PM recognizes: inheriting a set of OKRs that are, in the challenge's own words, a mess, with vague objectives and output-based Key Results disguised as outcomes. That opening matters because the most common OKR failure is not choosing the wrong framework; it is writing Key Results that measure activity, such as ship three features, instead of outcomes, such as raise activation from 31 percent to 40 percent, which lets a team feel busy while the actual objective goes unmeasured. A team can hit every activity-based Key Result on a quarterly review and still have made no measurable progress on the objective it was supposed to serve.

OKR example

Builders Camp's practical challenge places a new Senior Product Director at CodeForge, a developer tools company at $1.2M MRR whose activation rate just dropped from 42 percent to 31 percent, with a set of inherited OKRs that read more like a wish list, make CodeForge the best developer tool on the market, than a testable objective. The fix the challenge asks for is rewriting the objective in language a team can act on and pairing it with Key Results genuinely tied to the activation drop, such as a specific KR to increase MRR from 1.2M to 1.5M by June 30, rather than a KR that only counts features shipped regardless of whether they moved the number at all.

How Builders Camp teaches an OKR

How to Design OKRs, a 1 week bootcamp with 1 live session and 6 microlessons taught by Andre Albuquerque, is built entirely around fixing exactly this kind of broken OKR set before it reaches an all-hands. Setting Powerful Objectives covers the same skill from the objective-writing side in more depth, and both bootcamps run live or fully self-paced with the usual graded certification quiz. See the How to Design OKRs bootcamp for the full syllabus.

Bootcamps referred in this Guide

Frequently asked questions

What is the difference between an Objective and a Key Result?

An Objective is the qualitative, ambitious statement of where a team wants to go; a Key Result is a specific, measurable outcome that shows progress toward that Objective, and each Objective typically has two to five Key Results attached.

How many OKRs should a team have at once?

Most guidance, including Google's own practice, favors a small number, often three to five Objectives per team per cycle, since too many OKRs dilute focus and make it harder to tell which goals actually matter most.

What is a common mistake when writing Key Results?

The most common mistake is writing a Key Result that measures an activity, such as launch a feature, instead of an outcome, such as increase a specific metric by a specific amount, which lets a team claim progress without proving real impact.

How are OKRs graded?

Google's own approach grades Key Results on a 0 to 1.0 scale, with a score around 0.7 often considered a strong, appropriately ambitious result, since a consistent 1.0 across every OKR usually signals the goals were set too easily.

Should OKRs be tied to individual performance reviews?

Most practitioners, including Google's own guidance, recommend keeping OKRs separate from performance reviews, since tying them together encourages people to set safer, more easily achievable goals instead of genuinely ambitious ones.

How often should OKRs be set?

Quarterly is the most common cadence for team-level OKRs, often nested under annual company-level Objectives, though the right cadence depends on how fast a specific team's work and market actually change.

Sources

Written by

Andre Albuquerque

Andre Albuquerque

CEO of Builders Camp, SuperOperator, and other companies. Building products.

CEO of Builders Camp, SuperOperator, and other companies. Building products.

LinkedInMore guides by Andre Albuquerque

Last updated 2026-09-16

Researched from Builders Camp's bootcamp, track and masterclass material and the sources listed on this page, drafted with AI, and fact-checked against every source cited.

See the How to Design OKRs bootcamp