What Are Objectives and Key Results (OKRs)? How to Write and Use Them
Objectives and Key Results (OKRs) are a goal-setting framework that organizations and teams use to define ambitious goals and connect them to specific, measurable outcomes. The framework was developed at Intel by Andy Grove, popularized at Google in its early years, and has since become one of the most widely adopted goal-setting approaches in the technology industry.
The structure is simple: each Objective (O) — a qualitative, inspiring statement of what you want to achieve — is paired with 2–5 Key Results (KRs) — specific, measurable indicators that define what achieving the objective would actually look like.
The Structure of OKRs
Objectives
An objective is a concise, inspiring statement of a meaningful goal. Effective objectives are:
- Qualitative — Describing a desired state, not a metric
- Ambitious — Challenging enough to require real effort and focus
- Time-bound — Typically set for a quarter or year
- Motivating — Connecting the team’s work to something meaningful
Example objective: “Make our onboarding experience a genuine competitive advantage that drives activation and early retention.”
Key Results
Key results are the specific, measurable outcomes that would indicate the objective has been achieved. Effective key results are:
- Outcome-focused — Measuring impact, not activity (“increase activation rate” not “conduct three onboarding experiments”)
- Quantifiable — Containing a specific number or metric
- Ambitious but achievable — Typically set so that achieving 70% is considered strong performance; 100% suggests the goal wasn’t ambitious enough
Example key results for the onboarding objective:
- Increase new user activation rate from 45% to 65% by end of quarter
- Reduce median time to first meaningful action from 8 days to 3 days
- Achieve Day-30 retention of 55%+ for users who complete the new onboarding flow
How OKRs Work in Product Management
OKRs Align Strategy and Execution
When product OKRs derive from company OKRs, and team OKRs derive from product OKRs, every level of the organization can see how their work connects to the company’s direction. This alignment is one of OKRs’ most powerful organizational benefits.
OKRs Shift Focus from Output to Outcomes
A roadmap of features is an output-oriented plan. OKRs are outcome-oriented — they define what success looks like, not what will be built. This shift helps teams evaluate whether their work is creating value rather than just completing tasks.
OKRs Enable Faster Decision-Making
When a team has clear OKRs, evaluating any proposed initiative is straightforward: will this help us achieve our OKRs? If yes, it’s worth considering. If no, it’s a distraction. This filter accelerates prioritization decisions throughout the quarter.
OKRs Create Accountability
OKRs are typically public within the organization — visible to peers, managers, and leadership. This transparency creates accountability without micromanagement: teams know what they’ve committed to, and the organization can assess whether commitments are being met.
Common OKR Mistakes
Key results that are actually tasks — “Launch new onboarding flow” is a task, not a key result. “Increase activation rate from 45% to 65%” is a key result. OKRs fail when KRs measure activity rather than impact.
Too many OKRs — Organizations often adopt OKRs and immediately set 5 objectives with 5 KRs each. Twenty-five priorities is zero focus. Limit to 3–5 objectives per team per quarter.
OKRs that aren’t ambitious — If a team consistently achieves 100% of its KRs, the goals weren’t challenging enough. OKRs should be aspirational targets, not project plans.
Disconnected cascading — OKRs only create alignment when lower-level OKRs derive meaningfully from higher-level ones. If team OKRs are created independently of company OKRs, the alignment benefit disappears.
Using OKRs for performance evaluation — When employees believe their OKRs will be used directly in performance reviews, they set conservative OKRs they’re confident of achieving rather than ambitious ones. OKRs work best when separated from compensation and performance management.
Key Takeaways
OKRs are one of the most effective tools available for aligning product teams around ambitious, outcome-oriented goals. When written well and used consistently, they shift team focus from output (what we’re building) to outcomes (what we’re achieving) — creating clearer priorities, faster decisions, and more meaningful accountability. The organizations that get the most from OKRs treat them as genuine stretch targets, maintain true alignment from company to team level, and use them as decision tools rather than performance evaluation instruments.