A sheet full of verbs, each with a date

Open any team's OKR sheet in week two of the quarter and count the verbs. Launch. Hold. Build. Analyze. Consult. Each line has a date, so it looks measurable, and each will be ticked off by quarter end. Then someone asks what changed for customers, and the room goes quiet.

That is the most common fault in OKR sets: a task written in key-result clothing. Google's published guidance draws the line in one sentence: key results “must describe outcomes, not activities” 1. The quiz below gives you twelve invented key results, mostly drafts of the kind teams write. For each, you decide whether it is a real result, a task, a KPI in disguise or a line nobody can grade. Every answer explains the rule, so you leave with four questions you can put to any OKR set.

A task proves the work happened. A key result proves the work changed something.

Quiz

Key result or task?

Twelve draft key results, all invented for practice. For most, decide what each one really is. Answers and the reasoning appear at the end.

  1. 1 “Launch the new customer portal by June 30.”
  2. 2 “Consult regional sales leads on the new pricing model.”
  3. 3 “Improve onboarding.”
  4. 4 “Share of new customers who finish setup in their first week: from 40% to 65% by September 30.”
  5. 5 Order accuracy has run between 99.0% and 99.4% for two years. Draft key result: “Keep order accuracy above 99%.”
  6. 6 “Analyze churn drivers in the enterprise segment by the end of Q2.”
  7. 7 “Reach 1 million users by year end.” The team has not said whether it means all-time users or seven-day actives.
  8. 8 “Cut monthly cost to serve a small-business account from $41 to $30 by December 31, with satisfaction scores no lower than today.”
  9. 9 “Help the marketing team launch the spring campaign by March 15.”
  10. 10 Objective: make reordering self-service. Key results: build the reorder page; train the call center on it; announce it in the newsletter. What is the main problem?
  11. 11 A team's committed OKRs score 1.0 every quarter and use about half its people's time. What does Google's guidance infer?
  12. 12 An aspirational key result scores 0.7 at quarter end. How does Google's guidance read that?
Start here

The four ways a key result goes wrong

What it isThe tellThe question that fixes it
A taskA work verb: launch, build, consult, analyze, helpWhat is this work for?
A KPI in disguiseThe number is already there, or “keep,” “maintain”What will we do differently to hit it?
Not gradableNo number, or a number nobody has definedWould two people grade it the same way?
Not sufficientEvery line could hit while the objective missesWhat else would have to be true?

The first three come straight from Google's guidance: activity words mark tasks 1, a goal that requires no change to anyone's activities is business as usual 1, and a key result must allow a grade to be assigned objectively at the end of the quarter 1. The fourth is Google's insufficient-key-results trap 1. Andy Grove's version, from a 1970s teaching clip shown in John Doerr's TED talk, is the shortest: at the end “you can look and without any argument say, ‘Did I do that, or did I not do that?’” 2.

In practice

Why tasks keep winning

Teams do not write tasks because they misunderstand OKRs. They write them because tasks are safe. A task is fully in the team's control; a result depends on customers, other teams and luck. Under any pressure to score well, people drift toward the line they can guarantee. Google's guidance names the same drift for whole OKR sets, which tend to be written around what a team “believes it can achieve without changing anything they're currently doing” 1.

The fix is not to ban tasks. It is to attach each one to the result it is for. Google's own example: “Launch Foo 4.1” is weak, “Launch Foo 4.1 to improve sign-ups by 25 percent” is better, and simpler still is “Improve sign-ups by 25 percent” 1. The launch moves into the plan, where it belongs.

In practice

Reading your score

The bands are our rubric, not a validated test; a twelve-question quiz is a practice set, not an exam. What matters more than the score is the pattern of misses. If you missed tasks, slow down on verbs. If you missed the disguised KPI, ask for the baseline before you judge any target. If you missed the sufficiency question, you are grading lines one at a time; read the set against its objective instead.

Advanced

When a task is the right key result

The honest objection: sometimes the deliverable is the result. A regulatory filing, a plant certification, a contract signed. Nobody needs a downstream metric to know those mattered. Google's guidance agrees in its own way: among its examples of committed OKRs is delivering a defined feature or improvement by a set date 1.

So the test is not “is there a verb?” It is “if this scores 1.0, does anyone outside the team notice?” A certification that unlocks a market passes. A portal nobody uses does not. Keep task-shaped key results for deliverables whose value is not in doubt, and make everyone else say what the work is for.

Where to go next

Draft your own set in the OKR writer, which flags activity words and missing numbers as you type. For the line between key results and KPIs, read OKR vs. KPI. Then take one question into your next review, the one that turns most tasks into results on the spot: what is this work for?

Questions

What is the difference between a key result and a task?
A task describes work the team will do, such as launching, building or analyzing. A key result describes what that work should change, with a number and a date, so it can be graded without argument. Google's guidance says key results must describe outcomes, not activities.
Can a launch ever be a key result?
Yes, when the deliverable's value is not in doubt, such as a certification that unlocks a market. Otherwise attach the launch to its purpose: Google's guidance prefers “Launch Foo 4.1 to improve sign-ups by 25 percent,” or simply the sign-up target.
What are good key results examples?
Good key results name a measure of what customers or the business do, a baseline, a target and a date: the share of new customers who finish setup in week one, from 40% to 65% by September 30. Add a guardrail where the cheapest way to hit the number would do damage.

Sources

  1. Google (n.d.). Google's OKR Playbook. What Matters (whatmatters.com), excerpts reprinted with Google's permission. Key results describe outcomes, not activities, with consult, help, analyze and participate as activity words; measurable key results; “1 million users” as an ambiguous metric; the Launch Foo 4.1 example; the business-as-usual, “Launch X,” sandbagging and insufficient-key-results traps; expected scores of 1.0 (committed) and 0.7 (aspirational); postmortems for missed committed OKRs; not dropping aspirational OKRs for lack of progress; examples of classes of committed OKRs.
  2. Doerr, J. (2018). Why the secret to success is setting the right goals (TED2018 talk transcript). TED. Andy Grove, in a 1970s teaching clip shown in the talk, on key results that can be graded “without any argument.”

More from Stratrix

Strategy Packs
The Liability Reckoning

“What is it worth paying to close an exposure that has no upper bound?”

One decision per pack: the framework, a working model, the sourced cases and the board material.

See the pack — $499 →

All Access

Every Casebook, three Strategy Packs a seat each year and the Analyst, for teams that face these decisions all year.

$1,999 a year · $499 a seatWhat is included →

Weekly email

Stratonomics, every Tuesday

One data story every Tuesday: what happened, what it means, and the figures you can quote. Free.

Confirm from your inbox. Unsubscribe anytime.