OKRs

Objectives and Key Results—a goal-setting framework that defines what an organization wants to achieve (Objectives) and how it will measure success (Key Results). OKRs cascade from company strategy to individual execution, creating alignment across departments.

What are OKRs?

OKRs are a goal-setting and accountability system consisting of two parts: Objectives (qualitative, inspirational goals) and Key Results (quantitative, measurable outcomes). An Objective describes the direction—“Become the trusted platform for remote teams.” Key Results measure whether you’ve moved in that direction—“Increase DAU by 40%” and “Improve NPS to 60 or above.”

The framework was popularized by Andy Grove at Intel and adopted by Google, where it remains the primary strategic planning tool. The power of OKRs lies in their simplicity and their ability to create strategic focus. Unlike traditional strategic planning that produces 50-page documents, OKRs force clarity: what matters most, and how will we know we’ve succeeded?

Structure: Cascading Goals Without Dictation

OKRs are typically set in cascades: company-level OKRs, department-level OKRs, and team-level OKRs. The cascade creates vertical alignment—lower-level OKRs should support higher-level ones. But the cascade is not top-down dictation. A team doesn’t receive their OKRs from leadership; they propose OKRs that contribute to company strategy, and leadership approves.

This distinction is critical. In traditional hierarchical planning, leaders dictate what teams must do. In OKRs, teams own how they contribute to strategic outcomes. A marketing team might say: “To support the company OKR of reaching enterprise customers, our OKR is to establish thought leadership in three vertical markets, measured by speaking slots at tier-one conferences and cited mentions in industry research.”

Separating Performance Management from Strategy

A common mistake is treating OKRs as performance evaluations. If you miss your OKRs, you’re fired—which causes teams to set conservative goals they’re certain to hit, defeating the purpose. OKRs should be ambitious. A healthy company sees 70% of OKRs achieved. Anything higher suggests you’re under-ambitioned.

Performance management (promotions, raises, bonuses) should be separate from OKR achievement. You evaluate how someone performs against their full scope of work, not whether they hit a specific numerical goal. This separation allows teams to take bigger swings and report transparently when they miss.

Frequency and Rhythm

OKRs are typically set quarterly in fast-moving environments and annually in mature organizations. Quarterly OKRs create more frequent check-ins and course correction. Annual OKRs provide stable strategic direction but offer less flexibility. Most companies settle on a pattern: annual strategic OKRs (company-level) with quarterly tactical OKRs (department and team-level) that operationalize the annual strategy.

The rhythm also includes mid-quarter check-ins and end-of-quarter scoring. A typical cycle: set OKRs (week 1-2), execute (weeks 3-12), mid-quarter review (week 6-7), end-of-quarter review and scoring (week 13), retrospective on what worked and what didn’t (week 14), then plan next quarter.

OKRs vs. Strategy vs. Roadmap

These are often confused. Strategy is your multi-year direction and competitive positioning. OKRs are the specific, measurable outcomes you’re pursuing in this quarter or year to move toward strategy. Roadmaps are the features and initiatives your teams will build to move OKRs. The logical flow: Strategy → OKRs → Roadmap. If you have OKRs that don’t ladder to strategy, or roadmap initiatives that don’t move OKRs, you have misalignment.

Why It Matters for Product People

For product leaders and enterprise operators, OKRs are the mechanism for creating shared authority without micromanagement. You set the strategic direction, teams set their OKRs, you review quarterly whether the portfolio of OKRs is moving the business forward, and then you get out of the way.

OKRs also make trade-offs defensible. When a team proposes an initiative that doesn’t support company OKRs, you can say “it’s not in our quarterly focus” rather than “I don’t like it.” This is crucial for scaling organizations that need autonomy but also need alignment.

The framework also forces quarterly strategic introspection. If you can’t articulate three to five company OKRs, your strategy isn’t clear enough. If you have 15 company OKRs, you don’t have strategy—you have a prioritized backlog.

Common Implementation Mistakes

Teams often struggle with OKRs because they confuse them with task lists or MBOs (Management by Objectives). Writing “Hire 3 engineers” or “Implement SSO” as a Key Result misses the point—these are initiatives, not outcomes. A proper Key Result measures impact: “Reduce customer onboarding time by 50%” (the SSO is how you might get there).

Another mistake is setting too many OKRs. Three to five company-level OKRs is the target. More than that, you’re not making trade-offs.

OKRs work in concert with North Star Metrics—your company OKRs should move your North Star. They’re also distinct from KPIs, which are ongoing measures of business health, whereas OKRs are time-bound strategic goals. Teams often maintain both: KPIs for sustained health, OKRs for quarterly priorities.