OKRs are the bridge between strategy and execution.
1Ambitious but Attainable
OKRs should be 'stretch goals'. If you achieve 100% of your OKRs every quarter, your goals aren't ambitious enough. The 'Sweet Spot' is typically around 70-80% achievement.
2Outcome over Output
Don't list features in your Key Results. Instead of 'Ship Feature X', use 'Increase engagement on Feature X by 20%'. This gives the team the freedom to pivot the solution if the first version doesn't work.
3The Cadence
OKRs are typically set quarterly. This allows for enough time to see real progress but enough frequency to pivot if the market or business needs change.
4Step-by-Step Breakdown
OKRs (Objectives and Key Results) is a goal-setting framework used by companies like Google and Intel to drive alignment and measurable progress.
The Objective is a qualitative, ambitious, and inspiring 'What'. Example: 'Become the most loved payment app in Spain'.
Key Results are quantitative 'Hows' that prove you achieved the objective. They must be measurable and time-bound. Example: 'Achieve a Net Promoter Score of 50+'.
Which of these is a well-written Key Result?
- →Improve the user experience of the checkout page
- →Reduce checkout churn rate from 15% to 10% by the end of Q3
- →Build a new feature for mobile users
- →Make the app faster
What is the primary difference between OKRs and traditional KPIs?
- →OKRs are for tech companies, KPIs are for banks
- →KPIs track business health ('business as usual'); OKRs track strategic change and ambitious growth
- →OKRs are quarterly, KPIs are yearly
- →There is no difference
Level Up 🚀
Advanced cheat sheets, SEO tricks, and interview prep for this topic.
Browser Support
Fully supported.
Fully supported.
Fully supported.
Fully supported.
Accessibility (A11y)
1Readable OKR Documents
OKR trackers and roadmap docs are often screen-reader-only reading for remote stakeholders. Use real heading levels for each Objective and list markup for Key Results instead of colored text or emoji as the only signal of status.
<h3>Objective: Become the most loved payment app</h3>
<ul>
<li>KR1: NPS from 32 to 50+ <span aria-label="on track">🟢</span></li>
</ul>SEO Implications
- 1
Public Roadmap Discoverability
Companies that publish OKRs or quarterly goals publicly (investor updates, public roadmaps) benefit from clear, keyword-rich Objective titles — 'Reduce checkout churn' indexes and reads better than an internal codename like 'Project Falcon'.
Best Practices
Cap Objectives at Three to Five
More than five Objectives per team per quarter signals the list is really a task backlog, not a strategy. Force-rank and cut.
Separate Committed from Aspirational OKRs
Not every Key Result deserves the same risk tolerance. Flag which OKRs are 'must-hit' commitments versus 'stretch' goals so a miss on a stretch KR isn't read the same as missing a promise to the business.
Frequent Bugs
Key Results get written as disguised tasks ('Ship the new onboarding flow') instead of measurable outcomes, so the team can 'complete' the KR without moving any real metric.
Rewrite every Key Result as a before/after number with a deadline — 'Increase onboarding completion from 40% to 60% by end of Q3' — and reject any KR that has no baseline.
Real-World Examples
Rewriting a Vague OKR
A team proposes the Objective 'Improve the mobile app' with the Key Result 'Ship dark mode'. Their manager pushes back because 'ship dark mode' is an output, not a proof of impact.
// Before
Objective: Improve the mobile app
KR: Ship dark mode
// After
Objective: Make the mobile app the preferred way to check out
KR1: Increase mobile checkout completion from 58% to 72%
KR2: Reduce mobile session crash rate from 1.2% to 0.3%