The activity is written down as the goal. This is the classic mistake and by far the most common one. "Launch a new website" feels like a goal, because there is work in it and you can tick it off. But it says nothing about what is different afterwards. The matching Key Result from the skill reads: reach 30,000 unique visitors a month on the new site by 30 September. Still the same website, but now with an outcome attached. Every activity you submit gets rewritten into the outcome you are actually after, or it gets pulled out of the set and put where it belongs: your task list.
The Key Result cannot be scored. The test is simple and strict: can you give it a score between 0 and 1 at the end of the period? "Improve customer satisfaction" cannot, because who decides when it has improved. "Raise NPS from 32 to 50" can, because it contains a starting value, a target value and a measurement point. The skill wants to see all three elements in every Key Result.
There are too many goals. One to three Objectives, three to five Key Results per Objective. These are focus defaults; sufficient coverage, not the count alone, determines whether an exception is justified. So anyone who submits ten Objectives does not get ten back. That feels like a loss the first time, until the moment you notice that a team that truly finishes three things gets further than a team that starts ten.
The KPI is sitting inside the OKR set. KPIs measure the health of a running system: revenue, margin, uptime, occupancy. OKRs drive change. Put your standing monitoring numbers in your OKR set and at the end of the quarter you have mainly measured that the shop is still running. So it pulls those numbers out, with one exception: if you want to deliberately influence a KPI this period, it may join the set as a Key Result.
And then there is the question of who writes the set. OKRs are cascadable but not imposed top down. Doerr sums that up as alignment, not assignment: a team OKR may be linked to a Key Result from a higher Objective, but the team formulates it itself. If it lands in your inbox instead, it is an instruction with a new name.
In diff form, examples from the file show outcomes alongside a separately labelled leading activity indicator. These are editorial illustrations, not measured improvements.
--- task-list.txt
+++ key-results.md # this is how the skill rewrites it, shortened examples from the file; activity indicator kept separate
Launch new website
Reach 30,000 unique visitors a month on the new site by 30 September
Improve customer satisfaction
Raise NPS from 32 to 50
Have more sales calls
Leading activity indicator, not a Key Result: 24 sales conversations per quarter, against an explicitly illustrative baseline of 3 per month