OKR Builder (1 Objetivo + 3 KR)

OKR: Objectives and Key Results, the goal-setting framework

OKR stands for Objectives and Key Results, a goal-setting framework codified by Andy Grove at Intel in the 1970s as a descendant of Peter Drucker's Management by Objectives (1954). John Doerr — a young Intel employee who later joined Kleiner Perkins — carried the practice to Google in 1999, where it became the operating system of the company. His 2018 book Measure What Matters codified the modern version. Since then OKRs have been adopted by LinkedIn, Twitter/X, Spotify, Sequoia Capital portfolio companies, Allbirds, Slack and tens of thousands of startups and enterprises worldwide. In Brazil, Nubank, RD Station, iFood and Stone are public users.

An OKR has two parts. The Objective is qualitative, ambitious and inspirational — a short sentence anyone in the team can recite, such as "Become the most loved customer experience in the category". Key Results, typically 3 to 5 per Objective, are quantitative and measurable — the evidence that the Objective is being achieved. Good KRs answer "how would we know?", not "what should we do?". Example: NPS from 30 to 50, support response time from 8 h to 2 h, second-purchase rate from 18% to 30%. Cadence is usually quarterly for team and individual OKRs and annual for company-wide ones. They cascade in alignment — company → team → individual — without becoming a literal tree, because each level should also contribute lateral commitments.

Scoring: 0.0 to 1.0 and the 70% target

OKRs use a 0.0 to 1.0 scoring scale, often expressed as 0% to 100%. The expected average score for ambitious OKRs is around 0.7, not 1.0. If teams routinely score 1.0 the objectives were sandbagged; if they routinely score below 0.3 the bets were unrealistic. Google calls the ambitious version "moonshot OKRs", while easier "committed OKRs" are expected to hit 1.0. The crucial anti-pattern is tying compensation to OKR scores: it destroys honesty, because nobody volunteers an ambitious target if missing it cuts the bonus. OKRs are a transparency and alignment tool, not a performance-review weapon.

OKR vs KPI, MBO, V2MOM and Hoshin Kanri

OKRs are often confused with KPIs but the two coexist. KPIs are ongoing health metrics — uptime, churn, gross margin — that a business monitors continuously. OKRs are time-boxed change targets — what we will push this quarter. A KPI becomes a KR when it stops being baseline and starts being a destination. Related frameworks include Salesforce's V2MOM (Vision, Values, Methods, Obstacles, Measures), Stephen Covey's 4DX (4 Disciplines of Execution) and Toyota's Japanese Hoshin Kanri, all addressing the same problem: aligning hundreds of people behind a small number of priorities.

Tools, cadence and check-ins

Dedicated platforms include Lattice, 15Five, Workboard, Ally.io (acquired by Microsoft and folded into Viva Goals), Mooncamp, Perdoo and Gtmhub. A robust cadence is: quarter kickoff (set OKRs), weekly check-ins (update confidence and blockers), mid-quarter review (adjust ambition if reality shifted), quarter close (score and retro). Many tech companies now employ OKR coaches to facilitate the process and to write objectives that are inspiring rather than bureaucratic, the single most common failure mode.

FAQ

Do OKRs replace KPIs? No — they complement them. KPIs monitor the steady state; OKRs drive the change. Most companies report both side by side, with the KPI dashboard for operations and the OKR review for strategy.

Is it OK to miss an OKR? Yes, and that is the point of moonshot OKRs. Scoring 0.7 is success; scoring 1.0 routinely is a sign objectives were too soft. Missing a committed OKR, however, is a problem worth a candid retrospective.

How many OKRs per person or team? The widely cited cap is 3 Objectives with up to 5 KRs each. Past that, focus disintegrates and weekly check-ins become impossible to staff. Many teams set just 1 or 2 Objectives a quarter.

Should OKRs be public inside the company? Yes — that is one of John Doerr's "F.A.C.T.S." (focus, alignment, commitment, tracking, stretching). At Google every engineer can read every other team's OKRs. Public OKRs make dependencies and conflicts visible early, before they ship.