OKRs
Installation
SKILL.md
Writing the objective (O)
- The O is qualitative and directional: the change in the world if you succeed. "Win the SMB segment" not "grow SMB revenue 20%" (that is a KR). Direction on top, numbers underneath.
- Test the O: if every KR hit and nothing important changed, the O was a restatement. Rewrite around the user or market shift you intend to cause.
- One O per battlefield, not per project. "Make checkout best-in-class" is an O; "ship Apple Pay", "ship one-click", "ship saved cards" are inputs, not three Os.
- Memorable by week 8: if a teammate cannot say the O in one breath without the doc, it is a paragraph, not a direction.
- Inspirational without vagueness: "fastest mobile experience" is directional; "improve things" is vague; "checkout latency under 800ms" is a KR.
- No O overlap: two Os sharing KRs or drivers is one O pretending to be two. Merge.
- Cap at 3-5 Os per level. >5 = wishlist; cutting to 3 is where the real trade-off gets made. The pain of cutting is the signal the list was honest.
- An O should survive the quarter. Wanting to change it mid-quarter means either it was a task (killable) or the strategy genuinely shifted (rare; renegotiate openly, do not silently swap).