OKR Goal-Setting System
Define the What (Objectives) and measure the How (Key Results)
OKRs (Objectives and Key Results) are a collaborative goal-setting protocol for companies, teams, and individuals. An Objective is simply WHAT is to be achieved -- significant, concrete, action-oriented, and ideally inspirational. Key Results benchmark and monitor HOW you get to the objective. Effective KRs are specific, time-bound, aggressive yet realistic, and above all measurable and verifiable. You either meet a key result or you don't; there is no gray area.
The system operates on a quarterly cadence (though cycles can be adapted). Each cycle, organizations set 3-5 top-line objectives, each with 3-5 key results. OKRs are public and transparent -- everyone from the CEO down can see everyone else's goals. Roughly half of OKRs should originate bottom-up from contributors, not just cascade top-down from leadership. Critically, OKRs are divorced from compensation to encourage risk-taking rather than sandbagging.
The power of OKRs lies in four superpowers: Focus (choosing what matters most), Align (connecting everyone's work to the mission), Track (monitoring progress with data and check-ins), and Stretch (setting ambitious goals that push beyond comfort zones). Together these superpowers transform vague aspirations into disciplined execution.
- Ideas are easy; execution is everything -- and OKRs bridge the gap between vision and results.
- Less is more: a few extremely well-chosen objectives impart a clear message about what you say yes to and what you say no to.
- What you measure is what you manage -- key results without numbers are not key results at all.
- Goals set from the bottom up foster engagement and innovation; purely top-down mandates corrode motivation.
- OKRs are a tool, not a weapon -- they pace performance rather than punish shortfalls.
- Define 3-5 Objectives for the QuarterSenior leadership brainstorms and selects the most important objectives for the coming quarter. These should be significant, concrete, action-oriented, and inspirational. They answer the question: What is most important for the next three months?Pro tipFind raw material for objectives in your organization's mission statement, strategic plan, or a broad theme chosen by leadership. If an objective doesn't fit on one line, it isn't crisp enough.WarningDon't set more than 5 objectives. As Andy Grove said, if you try to focus on everything, you focus on nothing.
- Craft 3-5 Key Results per ObjectiveFor each objective, define measurable milestones that will indicate achievement. Key results must be specific, time-bound, and verifiable. A mix of quantitative outputs and qualitative inputs creates balance. Completion of all KRs must logically result in attainment of the objective.Pro tipPair quantity and quality key results to prevent one-dimensional goal pursuit. For example, pair 'three new features' with 'fewer than five bugs per feature in QA testing.'WarningIf your KRs use words like 'consult,' 'help,' 'analyze,' or 'participate,' they describe activities, not outcomes. Rewrite them to focus on end-user impact.
- Cascade and Align Across the OrganizationShare company OKRs with all teams. Teams develop their own OKRs that connect to the company's goals. Encourage roughly 50% of OKRs to originate bottom-up from contributors. Make all OKRs public and transparent so everyone can see how their work connects.Pro tipDon't rigidly cascade every goal through every level. Allow objectives to jump levels or emerge from the edges of the organization where innovation often dwells.WarningCompulsive cascading kills agility. If it takes weeks to trickle goals down the hierarchy, you've lost the speed advantage of quarterly cycles.
- Track Progress with Regular Check-insThroughout the quarter, monitor OKR progress through weekly one-on-ones, biweekly staff meetings, and monthly reviews. Use a simple color-coded system: 0.0-0.3 is red (off track), 0.4-0.6 is yellow (needs attention), 0.7-1.0 is green (on track). Course-correct or revise OKRs as conditions change.Pro tipDon't treat OKRs as commandments chiseled in stone. If conditions change mid-cycle, modify or even discard OKRs that are no longer relevant.WarningWithout regular check-ins, OKRs become a set-and-forget exercise. The tracking cadence is what makes the system dynamic.
- Score and Reflect at Cycle EndAt the end of the quarter, score each key result on a 0.0-1.0 scale. Combine objective scores with subjective self-assessments that account for context. Reflect on what contributed to success, what obstacles arose, and what you would change.Pro tipFor aspirational OKRs, an average score of 0.7 is considered success at Google. If you consistently score 1.0, you're not setting ambitious enough goals.WarningNever tie OKR scores directly to bonuses or compensation. This kills risk-taking and encourages sandbagging.
- Reset and RepeatCarry forward unfinished aspirational OKRs if still relevant, or retire them. Celebrate achievements with the team. Apply lessons learned to craft the next quarter's OKRs with greater precision and ambition.Pro tipAn organization may need four or five quarterly cycles to fully embrace OKRs. Build goal muscle gradually and don't expect perfection early on.WarningDon't drop aspirational OKRs just because of lack of progress -- that disguises persistent problems. Either solve the underlying issue or reassign the objective.
In 1999, John Doerr presented OKRs to Google's 30-person team. The company adopted the system for every quarter since. Larry Page personally reviewed OKRs for each engineer, and the leadership team debated top-line objectives each quarter. OKRs became the scaffolding for products like Search, Chrome, Android, Maps, YouTube, Google Play, and Gmail.
In late 1979, Intel faced an existential threat from Motorola's competing microprocessor. Within two weeks of receiving a field report about the crisis, Andy Grove marshaled the entire company behind a single objective: restore Intel's dominance in 16-bit microprocessors. Using cascaded OKRs, the company set an audacious target of 2,000 design wins (triple the prior year). Every division -- sales, marketing, engineering, manufacturing -- aligned their OKRs to this mission.
In 2008, Sundar Pichai's team launched Chrome with a stretch OKR of 20 million seven-day active users, starting from zero. They missed the target. In 2009, they stretched to 50 million and missed again (reaching 38 million). In 2010, they pushed to 111 million, found new distribution strategies, launched on Mac and Linux, and ran their first major TV campaign.
Andy Grove developed OKRs at Intel in the early 1970s, building on Peter Drucker's Management by Objectives (MBOs) but making critical improvements: shifting from annual to quarterly cycles, making goals public rather than siloed, encouraging bottom-up goal setting, divorcing goals from compensation, and emphasizing aggressive aspirational targets. John Doerr learned the system as a young engineer at Intel and later brought it to Google in 1999, presenting it to Larry Page, Sergey Brin, and about 30 employees around a ping-pong table. Google adopted OKRs and has used them for every quarter since, crediting the system with helping build seven products with over a billion users each.