okrslisted

# OKRs OKRs work when the Objective says *where we're going and why it matters*, and the Key Results prove *we actually got there* with movement on a number — not a checklist of shipped work. This skill helps you draft a tight, focused set and then stress-test it against the anti-patterns that quietly kill most OKR cycles. The single hardest discipline: Key Results are **outcomes**, not the tasks you'll do to reach them. **Grounded in:** *Measure What Matters* — John Doerr: outcome objectives with measurable key results (outcomes, not tasks). **Go deeper (The Product Channel):** [OKRs: Secrets of Success](https://sidsaladi.substack.com/p/week-4-week-in-product-series-secrets) ## When to use this - A new quarter or planning cycle is starting and you need to set goals. - You have a strategy or company objective and need to translate it into team/individual OKRs. - Someone hands you a draft and asks "are these good?" — you need to grade and fix them. - Your KRs feel like a project plan and you suspect they're really just a to-do list. - You want to align a goal up the ladder (company → team → individual) so the levels reinforce each other. ## What good looks like - **Objective:** qualitative, ambitious, time-bound, and memorable. A sentence a teammate could repeat from memory and feel pulled toward. No metrics in it. - **Key Result:** a measurable OUTCOME with **baseline → target** and a named data source. It answers "how will we *know* we hit the Objective?" — not "what wil