Step 1 of 10
Start here: why don't our OKRs change anything?
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.
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.