OKR Methodology: Maximise Your Objectives
Actualizado: 2026-05-03
OKRs (Objectives and Key Results) are the goal management system that aligns the entire organisation — from CEO to product team — towards ambitious, measurable goals with periodic review. Google has used them since 1999; Intel invented them in the 1970s. Today they are the de facto standard in the tech world.
Key takeaways
- An OKR has two components: the Objective (what we want to achieve, qualitative and inspiring) and the Key Results (how we will know we achieved it, quantitative and verifiable).
- OKRs are public: the entire organisation sees all teams’ objectives.
- They are reviewed quarterly, not annually — adjustment speed is key.
- A well-defined OKR is ambitious: if you always achieve 100%, it is not ambitious enough.
- OKRs are not task lists or job descriptions: they measure outcomes, not activities.
What OKRs are and how they differ from KPIs
KPIs (Key Performance Indicators) measure the ongoing performance of established processes: conversion rate, NPS, response time. OKRs define where you want to go and how you know you have arrived.
The practical difference:
- KPI: “Keep NPS above 45.”
- OKR — Objective: “Become the reference tool for distributed product teams.”
- OKR — Key Result 1: “Increase 90-day retention from 62% to 78%.”
- OKR — Key Result 2: “Secure 3 public testimonials from companies with more than 50 remote employees.”
- OKR — Key Result 3: “Reduce time to first value (TTV) from 14 days to 5 days.”
KPIs and OKRs coexist: KPIs monitor business health; OKRs drive change.
How to implement OKRs step by step
1. Define the Objective. It must be qualitative, motivating, and clear. A good test: does the team know, unambiguously, what achieving it means? If there is debate, the objective is too vague.
2. Define 2-5 Key Results per Objective. Each KR must be measurable with a concrete figure. “Improve performance” is not a KR; “Reduce homepage load time from 3.2s to 1.5s” is.
3. Set the review cadence. Quarterly for most companies; annual only for company-level strategy. 15-minute weekly check-ins to detect blockers early.
4. Score at the end of the cycle. The 0–1 scale is common: 0.6–0.7 is a good result (ambitious but nearly achieved); repeated 1.0s indicate objectives were not ambitious enough.
5. Iterate. The next quarter’s OKRs must learn from the previous ones: what did we not anticipate? Which key results were hard to measure?
Common mistakes in OKR adoption
Four frequent traps:
- Turning OKRs into task lists. “Launch new feature X” is a task, not a key result. The KR must measure impact, not activity.
- Too many OKRs. More than 3 objectives per team per quarter disperses focus. Less is more.
- OKRs in silos. If the product team and the sales team have OKRs that don’t articulate with each other, the organisation doesn’t align.
- Linking OKRs to individual performance evaluation. When bonuses depend on OKR scores, teams set easy objectives. OKRs are for strategic direction, not individual performance management.
Real OKR examples
Google (1999, Larry Page’s first cycle):
- Objective: become the most popular search engine on the Internet.
- KR1: reach 100 million indexed pages.
- KR2: maintain search latency below 1 second.
SaaS product startup (hypothetical but representative):
- Objective: be the first choice for 5-25 person teams in the Iberian market.
- KR1: reach 500 paying customers in Spain and Portugal.
- KR2: achieve NPS above 50 in the target segment.
- KR3: publish 3 success stories with sector-leading companies.
Conclusion
OKRs work when the organisation adopts them as a thinking system, not as planning bureaucracy. Their value is not in the OKR document but in the conversations they force: what is most important this quarter? How will we know we are making progress? What are we willing to stop doing? Answering those questions quarter after quarter, with honesty and data, is what transforms a good team into an excellent one.
