What OKRs are
OKRs (Objectives and Key Results) are a goal-setting framework that pairs a short list of qualitative goals with a few measurable results for each. The Objective says where you want to go; the Key Results are the numbers that prove you got there. Most teams set them quarterly.
Andy Grove developed OKRs at Intel in the 1970s, building on Peter Drucker's management by objectives. John Doerr learned the method at Intel, introduced it to Google in 1999, and later described it in his book Measure What Matters. The idea behind it has not changed: manage by the outcomes you want, not by the tasks you plan to finish.
| Part | What it is | The test | Example |
|---|---|---|---|
| Objective | A qualitative, memorable statement of intent | Would the team remember it without looking it up? | "Make the app feel instant for our busiest customers" |
| Key Result | A measurable outcome with a starting point and a target | Does it have a number, and could you hit it while still failing the Objective? | "Cut median dashboard load time from 2.4 seconds to under 1 second" |
A worked OKR example
An engineering team starts with the goal "improve platform performance." It is a direction, not a goal: nobody can tell at the end of the quarter whether they achieved it. Rewritten as an OKR:
- Objective: Make the app feel instant for our busiest customers.
- Key Result 1: Cut median dashboard load time from 2.4 seconds to under 1 second.
- Key Result 2: Keep uptime at 99.9% or better during peak hours.
- Key Result 3: Halve the number of support tickets tagged "slow."
One line the team first proposed, "migrate to a new caching layer," did not make the list. It is a task: the team could finish it and the app could still be slow. Tasks belong in the plan for hitting the Key Results, not in the Key Results themselves.
OKRs vs. KPIs
KPIs track the health of the business as it runs today: revenue, churn, uptime. OKRs are for the few things you are trying to change this quarter. A KPI becomes a Key Result only when the team decides to move it, not just to watch it. That is why "answer support tickets" is never an OKR, while "halve the tickets tagged slow" can be.
Committed vs. stretch OKRs
Some OKRs are commitments the team expects to hit in full. Others are deliberate stretches, where reaching about 70% of the target counts as a strong result. Say which kind each OKR is when you write it, or a stretch goal that lands at 70% will read as a failure.
The rest of this guide is about the meeting where a team drafts its OKRs, and how to facilitate it so the room leaves with outcomes rather than a to-do list.
The Facilitator's Mindset: The Outcome Enforcer
Your role as an OKR facilitator is to be the relentless "Outcome Enforcer." Teams are deeply conditioned by years of corporate habit to manage by activity. They naturally want to write to-do lists, call them goals, and feel a sense of accomplishment just for being busy. You must push them away from "outputs," what we will do, and toward "outcomes," what impact it will have. Expect to sound repetitive as you constantly stop the room to demand they define the measurable business value of their proposed actions.
When the Framework Actually Works (and When It Fails)
This workshop should be run two to three weeks before the start of a new quarter. It is an essential intervention when a company or team needs to align their focus, or when there is a disconnect between high-level company strategy and the day-to-day work of individual contributors.
It is crucial to remember, and to remind the team, that OKRs are used to manage change and growth, not to track business as usual. OKRs fail when they are used as a comprehensive tracking system for every single task a department does. If a team uses OKRs to track standard, ongoing operations, such as "keep the servers running" or "answer support tickets," the framework loses its power to drive strategic change.
Curating the Room and Setting the Stage
To ensure the session is grounded in reality, you must invite the right people. Department or team leaders must be present as they are the individuals ultimately accountable for the results. You also need key individual contributors to provide a reality check on what is actually achievable; otherwise, leaders might commit to mathematically impossible targets. Crucially, the Executive Sponsor must be present at the very start of the session to clearly state the top-level company strategy before any team-level planning begins.
Before the team attempts to draft their specific OKRs, they must have absolute clarity on the company's high-level strategic priorities. Ensure the company's primary "North Star" Objective for the quarter is highly visible in the room; if this is missing, team-level OKRs will be disjointed and contradictory. Additionally, participants must come prepared with baseline metrics for their current performance. You cannot set a target to increase conversion by a certain percentage if you do not know the current conversion rate.
Navigating the Chaos: The Execution Phase
A standard team-level OKR session requires about 90 to 120 minutes. It begins with a brief alignment on the North Star, followed by brainstorming one to three qualitative, inspiring, and memorable Objectives, such as "Dominate the Mid-Market SaaS Space." The bulk of the session is spent defining three to five Key Results for each Objective. In this phase, you must be firm: if a Key Result does not contain a number, it is invalid. Period.
Toward the end of the session, perform a "70% Rule Check" to ensure the goals are ambitious enough, explaining that hitting 70% of a highly ambitious goal is far more valuable than hitting 100% of a mediocre one. Finally, ensure every single Key Result is assigned to one, and only one, accountable owner. Shared ownership means no ownership.
Engineering the Breakthrough
Throughout the session, challenge the team. Ask if a proposed Key Result is an actual measure of success or merely a task on a to-do list. Ask them if it is mathematically possible to complete all the Key Results and still fail the Objective; if so, their Key Results are insufficient. Force them to articulate what happens to the business if they don't hit a specific number, and call them out if you suspect they are sandbagging a goal out of a fear of failing.
You will need to navigate several common failure modes. The most pervasive is the "Business As Usual" trap, where teams try to include daily operational tasks as OKRs; you must force them to select only initiatives that move the needle, reminding them that if everything is a priority, nothing is a priority. Watch out for output masquerading as outcome, such as "Launch the new website" instead of "Generate 500 new inbound leads from the new website." Finally, prevent the team from creating too many OKRs. Trying to focus on ten Objectives will drown the team in tracking overhead; ruthlessly cut the list down to the top two or three.
Opening the Session
As you start the facilitated session, remind the room that you are not there to list out daily jobs. The goal is to define the exact metrics that will prove the team successfully executed the strategy this quarter. By starting with the Executive North Star, the team can then draft the qualitative Objectives that will guide their most impactful work.
