OKRs provide a goal-setting framework that aligns engineering work with business outcomes. Instead of measuring output (features shipped), you measure outcomes (business impact achieved).
Objective: A qualitative, inspirational goal Key Results: 3-5 quantitative metrics that define success
Together, they answer two questions:
Good objectives:
Bad objectives:
Good key results:
Bad key results:
Objective: Improve user retention and engagement
Key Results:
Objective: Build a rock-solid, trustworthy platform
Key Results:
Objective: Make our engineering team the most productive in the industry
Key Results:
Don't create OKRs in a vacuum. They should ladder up to company strategy.
Company Goal → Department OKR → Team OKR → Individual OKR
Output (❌): "Ship 5 new features" Outcome (✅): "Increase user engagement by 30%"
OKRs should be stretch goals. Hitting 70-80% is success.
If you're consistently hitting 100%, you're not ambitious enough.
3-5 OKRs per team per quarter is optimal. More than that dilutes focus.
Every key result needs a number. If you can't measure it, you can't manage it.
At the end of the quarter, score each key result on a scale:
Overall OKR score = Average of all key result scores
Typical targets:
Wrong: "Objective: Implement new payment system" Right: "Objective: Provide a frictionless payment experience"
More than 5 OKRs means you're not focused.
Setting easy goals you know you'll hit defeats the purpose.
OKRs need weekly check-ins and monthly reviews.
OKRs are for stretching, not for evaluating individuals.
Quarterly Cycle:
Engineering teams often struggle with OKRs because:
Solution: Bridge the gap explicitly.
Instead of: "Objective: Build user dashboard"
Try: "Objective: Empower users to understand their data
Objective: [Aspirational outcome you want to achieve]
Key Results:
1. [User/Business metric] from [current] to [target]
2. [Technical metric] from [current] to [target]
3. [Quality metric] from [current] to [target]
Mix user/business metrics with technical/quality metrics for balanced progress.
Ready to try OKRs? Start with one team objective and 3-4 key results for next quarter. Make them ambitious, measurable, and outcome-focused.
Connect features to business goals through user behaviors using this strategic planning technique
Visual framework for quick prioritization decisions based on business value and implementation complexity
Quantify and compare the value of different initiatives using Reach, Impact, Confidence, and Effort