Skip to content
  • Official
  • Beginner
  • English
  • 10 steps · 2 quizzes

OKR Workshop: Writing Objectives and Key Results

OKR workshop with practice: rewrite weak objectives, sort outputs from outcomes, make key results measurable and score a quarter from 0.0 to 1.0.

  • Free
  • No account needed
  • Stop any time, pick up where you left off
Workshopy.io

WorkshopyOfficial

78 lessons · used by 2 teachers

For teachers

Teaching this? Run it live with your class.

  • Students join with a code — no accounts
  • See who’s done and who’s stuck, step by step
  • It’s your copy — change anything before class

Sign in to copy it to your workspace. It’s free.

Your path

10 steps · 2 quizzes · open any step, or read it here

  1. Start here: why don't our OKRs change anything?Start hereThis OKR workshop starts with a problem many teams know: every quarter you write objectives and key results, the team works hard, and at the end the numbers that matter have hardly moved.InteractiveHands-on
    Read this step

    This OKR workshop starts with a problem many teams know: every quarter you write objectives and key results, the team works hard, and at the end the numbers that matter have hardly moved. Often the key results counted the team's work, not the change the work was for.

    Interactive · A quarter of work: which key results really moved? — try it in the lesson

    You just watched one quarter: three key results, work done in every lane every week, and only two lines climbing toward their targets. In this lesson you learn to tell those lanes apart while you write them, not thirteen weeks later.

    What you'll do

    • Sort objectives, key results and tasks from a support, a sales and a product team.
    • Rewrite weak objectives and key results until they could be scored.
    • Run a quarter in a simulator and watch a key result that counts work look perfect while nothing changes.
    • Score key results from 0.0 to 1.0 and read what each score means.

    By the end you can

    • Write an objective with three to five measurable key results that track outcomes.
    • Score a quarter and say whether a 0.7 is good news.
    • Run an OKR drafting session with your own team.

    You need a browser. No earlier OKR experience is needed.

  2. What an OKR is: one objective, a few key resultsOKR stands for objectives and key results. The objective says where the team is going, in words: short, qualitative, worth getting up for.InteractiveHands-on
    Read this step

    OKR stands for objectives and key results. The objective says where the team is going, in words: short, qualitative, worth getting up for. The key results say how you will know you got there: a few numbers, each with a starting point and a target, checked at the end of a period, usually a quarter.

    Andy Grove developed the method at Intel in the 1970s, building on Peter Drucker's management by objectives. John Doerr learned it there and brought it to Google in 1999; his book Measure What Matters (2018) made it widely known. The test Grove gave a key result is simple: at the end of the period you can say, without argument, whether you met it.

    What is not in an OKR: the tasks. Hiring, trainings, features and campaigns are how the team plans to move the key results. They belong on the plan, and the plan can change in the middle of a quarter without changing the OKR.

    How many? Few. A common rule, Doerr's included, is three to five key results for each objective, and a team rarely needs more than three objectives in a quarter.

    Try it: each team below has one objective, one key result and one task. Press what each card is.

    Interactive · Objective, key result or task? Sort three teams' cards — try it in the lesson

    Takeaway: the objective is the direction, the key results are the evidence, and the tasks are the plan.

  3. Objectives: where you are going, in wordsA good objective is: Qualitative: no numbers. The numbers go in the key results. A direction, not an activity: it names the change you want, not the work. Ambitious and specific: someone outside the team could tell what you care about this quarter.InteractiveHands-on
    Read this step

    A good objective is:

    • Qualitative: no numbers. The numbers go in the key results.
    • A direction, not an activity: it names the change you want, not the work.
    • Ambitious and specific: someone outside the team could tell what you care about this quarter.
    • Short enough to remember: one line.

    The usual weak objectives are a number dressed up as an objective ("Increase NPS"), an activity ("Make more calls"), a project ("Launch the mobile app") or a heading ("Q3 sales objectives").

    Try it: each team wrote a weak objective. Pick the rewrite that is a real objective. A wrong pick tells you why it falls short.

    Interactive · Rewrite three weak objectives — try it in the lesson

    Takeaway: if your objective already contains a number, you have probably written a key result.

  4. Outputs and outcomes: the work and what it changesAn output is something the team produces: articles published, calls made, a feature shipped. An outcome is a change you can see because of it: fewer tickets, more deals won, users coming back.InteractiveHands-on
    Read this step

    An output is something the team produces: articles published, calls made, a feature shipped. An outcome is a change you can see because of it: fewer tickets, more deals won, users coming back.

    Outputs are tempting key results because the team controls them and they always move. That is the problem: a key result that counts work scores well whether or not the work did anything.

    Try it: run the support team's quarter. Press Next week a few times, then Play the quarter. Then switch key result 3 from Password tickets cut to Help articles published, and look again at its score and at the dotted line. (The numbers are illustrative.)

    Interactive · Run the support team's quarter, one week at a time — try it in the lesson

    The articles were the same in both runs. Only the key result changed, and with it what the team would have learned at the end of the quarter.

    Takeaway: measure the change the work is for, and keep the work itself on the plan.

  5. Sort the drafts: output or outcome?A quick test for each draft key result: could the team do this completely and still see nothing change for customers? If yes, it is an output.InteractiveHands-on
    Read this step

    A quick test for each draft key result: could the team do this completely and still see nothing change for customers? If yes, it is an output.

    Outcomes usually measure behaviour or results ("share of new users who…", "win rate", "tickets a month") and move from a baseline to a target. Outputs usually start with a verb of work: publish, run, ship, send, make.

    Try it: sort four drafts for each team. The team buttons switch between them.

    Interactive · Output or outcome? Sort twelve draft key results — try it in the lesson

    Takeaway: two outputs in every four drafts is normal for a first draft. The skill is spotting them before the quarter starts.

  6. Make it measurable: a measure, a baseline and a targetA key result needs three things before anyone can score it: A measure of an outcome: something you can count that changes when the objective is being met. A baseline: where that number is today, from real data. Without it, "to 60%" says nothing about progress.InteractiveHands-on
    Read this step

    A key result needs three things before anyone can score it:

    1. A measure of an outcome: something you can count that changes when the objective is being met.
    2. A baseline: where that number is today, from real data. Without it, "to 60%" says nothing about progress.
    3. A target: where it should be at the end of the quarter, in the right direction. For some measures, such as reply time or churn, lower is better.

    The pattern is [measure] from [baseline] to [target] by [date], for example: "Median first reply time from 9 hours to 2 hours by 30 June."

    Try it: each tab holds a weak key result and a line of real data. Pick a measure, enter the baseline and a target, and tick every check.

    Interactive · Turn three weak key results into measurable ones — try it in the lesson

    Takeaway: if you cannot write the "from" number today, your first task is to measure it, not to set the target.

  7. Check: objectives and key resultsQuiz · 4 questions
    Read the questions

    Question 1. Which of these is an objective?

    • Publish 12 help articles this quarter
    • Customers get answers fast, the first time they ask
    • Median first reply time from 9 hours to 2 hours
    • Hire two more support agents

    Question 2. A product team writes the key result "Ship dark mode". What is wrong with it?

    • It counts an output: the team could do it completely without anything changing for users
    • It is too short
    • Features may never appear anywhere in an OKR
    • It should be the objective instead

    Question 3. Which key result can be scored at the end of the quarter?

    • Improve the win rate significantly
    • Work on the sales pipeline
    • Win rate on qualified deals from 18% to 25%
    • Do more demos than last quarter

    Question 4. How many key results does a common rule suggest for each objective?

    • One
    • Three to five
    • Ten to fifteen
    • One for every task on the plan
  8. Score the quarter: from 0.0 to 1.0At the end of the quarter each key result gets a score from 0.0 to 1.0. A simple way to compute it: $$\text{score} = \frac{\text{actual} - \text{baseline}}{\text{target} - \text{baseline}}$$ · Round it to one decimal; it never goes above 1.0 or below 0.0.InteractiveHands-on
    Read this step

    At the end of the quarter each key result gets a score from 0.0 to 1.0. A simple way to compute it:

    $$\text{score} = \frac{\text{actual} - \text{baseline}}{\text{target} - \text{baseline}}$$

    Round it to one decimal; it never goes above 1.0 or below 0.0. The same formula works when lower is better: reply time from 9 hours to 2 hours, ending at 4 hours, gives (4 − 9) ÷ (2 − 9) = 5 ÷ 7, a score of 0.7.

    What a score means depends on the kind of OKR. Google's OKR playbook separates two kinds:

    • Committed OKRs are promises: the team expects to score 1.0. Anything less is a miss to explain.
    • Aspirational OKRs, or stretch goals, are set beyond what the team is sure it can reach. They are expected to average around 0.7. On Google's colour scale, 0.7 to 1.0 is green, 0.4 to 0.6 is progress that fell short, and 0.0 to 0.3 means little real progress. A team that scores 1.0 on every stretch goal is probably setting them too low.

    Many organisations pick their own scale; what matters is that everyone knows in advance which key results are promises and which are stretches.

    Try it: move "Where it ended" and watch the score. Then switch between Aspirational and Committed: the same 0.7 means different things.

    Interactive · Score a key result at the end of the quarter — try it in the lesson

    Takeaway: 0.7 on a stretch goal is a good quarter; 0.7 on a committed one is a missed promise.

  9. Score the key resultsScore each key result to one decimal: (actual − baseline) ÷ (target − baseline), never above 1.0 and never below 0.0. A hint costs nothing.Practice · 6 exercises
    Read this step

    Score each key result to one decimal: (actual − baseline) ÷ (target − baseline), never above 1.0 and never below 0.0. A hint costs nothing.

    Sales: qualified meetings booked a month, baseline 20, target 50. The quarter ended at 41. What is the score?

    Support: median first reply time, baseline 9 hours, target 2 hours. The quarter ended at 4 hours. What is the score?

    Support: satisfaction score, baseline 82, target 90. The quarter ended at 86. What is the score?

    Product: teams active every week, baseline 1200, target 1800. The quarter ended at 1950. What is the score?

    Company: monthly churn, baseline 2.0%, target 1.2%. The quarter ended at 2.3%. What is the score?

    A committed key result ended the quarter at 0.7. What does that tell the team?

    • A good result: stretch key results are expected to land around 0.7
    • A miss: committed means the team expected 1.0, so it should find out what happened
    • The target was too easy
    • Nothing: committed key results are not scored
  10. Align and check in: from company OKRs to team OKRsAlignment. A company sets a few OKRs; each team then writes its own OKRs that move one of the company's key results.InteractiveHands-on
    Read this step

    Alignment. A company sets a few OKRs; each team then writes its own OKRs that move one of the company's key results. Avoid pure cascading, where every level copies the level above: the team usually knows best how it can move the company's number, and its key result can be its own measure.

    Check-ins. Once a week or every two weeks, each key result's owner updates the number and says how confident they are of reaching the target. A key result in trouble then shows up in week four, not week thirteen, and the team can change its plan. Changing the key result itself should be rare, and visible to everyone.

    Try it: the company's objective has three key results. Link each team's key result to the one it moves.

    Interactive · Link each team's key result to the company key result it moves — try it in the lesson

    Takeaway: a team key result should move a company key result in a way you can explain in one sentence.

Comments

You’ll sign in with Google before it’s posted.Comments are public — don’t name your students.
0 / 1,500

No comments yet. Be the first to say how it went.

Using it

Workshopy shares this lesson under CC BY 4.0. Anyone may use and change it, with credit to you. Anyone can learn it here, free. A copy in your workspace is yours to change and run live; your students never need an account.

Versions

  1. 1

    Version 1Current

    · First published

Copies are made from the current version. A copy you already have doesn’t change.

More from Workshopy

All 78 lessons
All 14 Business lessons