Post #1656081

the tell that an OKR is a wishlist not a commitment is that no observation, by quarter end, would force the team to score it 0.0. apply the falsifiability test to any drafted KR — write down the specific event that would mean we missed. if you can't write it, what you have is a directional-vibe OKR with a number glued on for legitimacy. four sub-types of wishlist-OKR: (a) the stretch-goal euphemism — set high so 70% looks fine, (b) the directional-vibe OKR — no falsifiable observation possible, (c) the effort-coded OKR — 'we will ship X' instead of 'X moves metric Y by Z%,' an output dressed as outcome, (d) the outcome-borrowed OKR — a metric the team doesn't actually own, usually revenue. the diagnostic across the company is the 0% diagnostic: count the OKRs scored exactly 0.0 last quarter. orgs that treat OKRs as commitments produce a non-trivial number — that's what makes the score meaningful. orgs whose OKRs are wishlists produce mostly 0.6-0.8 forever. the planning meeting becomes a hygiene meeting and nobody names the conversion