Definition
OKR (Objectives and Key Results)
OKR is a goal-setting framework that pairs a qualitative Objective — what you want to achieve — with three to five measurable Key Results that prove you got there. Set per quarter and scored at the end, OKRs align a team on a small number of outcomes, keeping effort focused on results rather than a list of activities.
Key takeaways
- OKR pairs a qualitative Objective (what you want to achieve) with three to five measurable Key Results that prove you got there.
- Key Results must measure outcomes, not output — 'ship three features' is a task list; 'lift activation from 38% to 50%' is a Key Result.
- OKRs are deliberately few and ambitious: one to three Objectives a quarter forces a team to decide what doesn't matter.
- They only work when kept visible and tied to real work, not set at planning and forgotten until the quarter ends.
An OKR has two halves. The Objective is a short, inspiring statement of intent — 'make onboarding effortless' — that anyone can rally behind. The Key Results are the evidence: specific, numeric outcomes such as 'cut time-to-first-value from 20 minutes to 5' or 'lift activation from 38% to 50%.' If every Key Result is hit, the Objective is, by definition, achieved. The discipline is choosing results that measure outcomes, not output — 'ship three features' is a task list, not a Key Result.
OKRs are deliberately ambitious and deliberately few. Most teams set one to three Objectives per quarter, each with a handful of Key Results, because the framework's value is focus: naming what matters most forces a team to decide what doesn't. Targets are often set as stretch goals where hitting 70% is considered success, which keeps them aspirational rather than sandbagged — though teams vary on whether to grade that way.
The framework only works when OKRs stay visible and connected to daily work. An OKR set at planning and forgotten until the quarter ends is theater. The strongest implementations check in on Key Results regularly and tie the underlying initiatives, projects, and issues back to the Objective they serve, so progress on the goal reflects real execution rather than a separate spreadsheet.
In Planoda, goals connect to the initiatives, projects, and issues that advance them, so an Objective's Key Results track live progress from the work itself instead of a quarterly snapshot reassembled by hand.
Related terms
- North Star MetricA North Star metric is the single measure that best captures the core value a product delivers to customers — and that, when it grows, reliably pulls revenue and retention up with it. It aligns an entire company on one number, cutting through competing departmental metrics so every team can see how its work moves the thing that matters most.
- InitiativeAn initiative is a large, strategic body of work that spans multiple projects, teams, or cycles toward a single outcome. It sits above projects and issues in the planning hierarchy, grouping related efforts under one goal. Initiatives let leadership track progress on big bets without drowning in individual tickets.
- RoadmapA roadmap is a high-level, time-oriented view of what a team or product plans to build and roughly when. It communicates direction and sequencing across initiatives and projects, aligning stakeholders on priorities. Unlike a backlog of granular tasks, a roadmap operates at the altitude of themes, outcomes, and quarters rather than individual issues.
- MilestoneA milestone is a significant checkpoint in a project — a meaningful date or deliverable that marks progress, such as a beta launch, a feature freeze, or a public release. Unlike a task, a milestone has no duration; it is a moment that signals a phase is complete, used to coordinate teams and communicate timing to stakeholders.