A plain-English glossary of the terms that come up when teams set, run, and review OKRs — written for operators, not consultants.
The state where every team's goals roll up to a shared company priority — so people aren't working hard in the wrong direction. The 2026 OKR Benchmark Report found 65% of teams admit their goals aren't clearly linked to company strategy. OKR alignment is the structural fix: every team Key Result connects to a company Objective before the cycle starts.
Read the alignment guideA single visual view of every OKR across the company — from company-level Objective down to team Key Results. Each line shows how a goal cascades up to the one above it. Makes the 65% misalignment problem visible in one view rather than requiring a status meeting. In OKRs Tool, this is the default planning view.
See the Alignment MapOKRs where 70% completion is considered a strong result — the bar is deliberately set beyond what feels achievable. Used to push teams beyond the safe range. Pair carefully: aspirational OKRs work when teams understand they won't fully hit them. Misused, they erode trust in the scoring system fast.
How OKR scoring worksA timestamped record of every change made inside the platform — who edited a Key Result, when a goal was deleted, when permissions changed. Required for enterprise compliance and useful when something gets accidentally overwritten. Available on the Expand plan.
See Expand featuresThe current value of a metric before the OKR cycle begins — the starting point from which progress is measured. No baseline means no way to know if the metric actually moved. Every Key Result should have a specific baseline before the cycle goes live. Without it, the OKR can't be scored honestly at cycle end.
How to write Key ResultsAn approach where teams propose their own OKRs, which leadership reviews and integrates into the company plan. The opposite of top-down. Most effective organizations combine both: leadership sets strategic direction top-down; teams contribute the tactical specifics bottom-up. Produces more buy-in than pure top-down, more coherence than pure bottom-up.
How the OKR process worksThe rhythm at which a team updates progress on their OKRs. Weekly is the standard — and the data is precise: teams that check in weekly complete 43% more OKRs than those who don't. Monthly and quarterly check-in cadences are the most common reason OKR programmes fail after a strong start.
Weekly check-in guideThe practice of connecting team OKRs to a parent company OKR — so every goal contributes to a larger strategic priority. Cascading isn't a slide in the kickoff deck — it's a structural requirement. Teams that complete the full cascade before the cycle starts see up to 50% higher completion rates.
Cascading OKRs guideA management practice introduced alongside OKRs in John Doerr's Measure What Matters — the human layer that reinforces the quantitative OKR layer. Conversations are structured manager–employee discussions on progress and development. Feedback is continuous rather than annual. Recognition acknowledges contributions in real time.
Measure What Matters guideA short async update where the Key Result owner records progress, sets a status (on track, at risk, behind), and flags blockers — typically weekly. Replaces status meetings. The platform sends an automated nudge via Slack or Teams so owners don't need to be chased. The cadence is the mechanism; the check-in is how it runs.
Run automated check-insAn owner's subjective probability estimate that a KR will be achieved by cycle end — updated alongside the progress score at each check-in. Useful when progress looks fine but blockers are emerging: a KR at 60% complete in week 8 might have low confidence if the remaining 40% depends on external factors.
OKRs that are expected to be fully delivered — the opposite of aspirational OKRs. Reaching 100% is the goal, not 70%. Used for must-ship work where missing the target has real business consequences: a contractual deliverable, a compliance deadline, a product launch date.
Committed vs aspirational OKRsThe time window an OKR runs for — most commonly a quarter (12–13 weeks). Some teams run 6-week cycles for faster-moving work. The maturity data is striking: first-cycle teams average 51% completion. Teams in cycle five average 79%. The improvement compounds — but only if the full cycle runs, including the retrospective.
OKR cycle guideA centralized, live view of all Objectives and Key Results — including progress, ownership, status, and alignment. The mechanism that keeps goals visible between the planning session and cycle end. The benchmark data found that 7% of off-track Key Results are quietly abandoned mid-cycle — a dashboard with at-risk flagging prevents that.
What a good dashboard needsOKRs set between company and team level — e.g., the Engineering department's OKR for the quarter, which then cascades to individual squad OKRs. Useful once you cross 50+ people with multiple sub-teams per function. Not every organization needs a department layer — adding it before the foundation is solid creates overhead without clarity.
Cascading OKRs guideWhen goals quietly stop being referenced during the cycle — priorities shift, no one updates the OKR, and by week six nobody mentions it in meetings. The leading cause of dead OKRs — and the OKR Intelligence Report found it affects 7% of all active Key Results. Weekly check-ins surface drift before it becomes abandonment.
The level of active participation a team shows in OKRs — measured by check-in completion rate, Key Results with at least one update, and active logins. OKRs Tool's 60% adoption guarantee is built on this signal: if engagement drops below 60% in 30 days, you get a refund. Most tools don't measure it. We do.
See the adoption guaranteeThe distance between what an organization decides to do and what actually happens. OKRs close this gap by making strategy visible, ownership explicit, and progress trackable weekly. The execution gap is where strategy goes to die. The check-in cadence is what keeps it closed.
OKR methodology guideThe primary mechanism of the OKR framework — forcing teams to choose what matters most this quarter, and by implication, what they won't do. Teams running 1–2 Objectives are twice as likely to achieve them as those running three or more. The constraint isn't a limitation: it's the point.
Right number of Key ResultsA predicted end-of-cycle outcome based on current progress and pace. Useful for catching at-risk goals weeks before they miss — instead of waiting for the retrospective to explain why they did. Status is owner-set; forecast is data-computed.
The category of structured approaches for setting and tracking organizational goals — including OKRs, SMART goals, MBO (Management by Objectives), Balanced Scorecard, and BHAG. OKRs are the dominant framework for growing companies because they combine alignment (cascade), measurement (Key Results), and rhythm (weekly check-ins) in a single system.
The OKR framework explainedThe practice of scoring each Key Result at cycle end on a 0.0–1.0 scale. 0.6–0.8 is the healthy range for aspirational OKRs — consistent 1.0s mean targets weren't ambitious enough; consistent 0.0s signal structural problems. Grading is the feedback loop that improves the next cycle.
OKR scoring guideA composite metric showing how well an OKR or team is tracking — combining check-in cadence, progress velocity, and time remaining in the cycle. Surfaces problems before they become misses. Different from owner-set status (which reflects intention) — health is computed from actual behavior and progress data.
OKRs set at the individual contributor level — connecting a person's quarterly priorities to their team's Key Results. Most OKR experts recommend against individual OKRs in cycle one: the overhead of writing, cascading, and reviewing them before the team habit is established creates more friction than value. Start at company and team level, add individual OKRs from cycle three onwards.
OKR adoption guideA specific project or workstream that contributes to a Key Result. Sits below the KR in the hierarchy: Objective → Key Result → Initiative. The distinction matters: campaigns, features, and experiments are initiatives — not Key Results. Initiatives are the bets on how to move the metric; Key Results measure whether it moved. Initiatives often map to Jira epics or Asana projects.
Input: what you put in (hours, budget, headcount). Output: what you produce (features shipped, calls made, posts published). Outcome: what changes in the world as a result (revenue, retention, NPS). Strong Key Results measure outcomes. Weak ones count outputs. Our analysis of 7,857 Key Results found 52% were outputs or inputs in disguise.
The vanity metrics problemA measurable outcome that signals whether an Objective is being achieved. Each Objective typically has 2–4 KRs. The best KRs measure change — a business metric moving from a baseline to a target — not the work that caused it. Our platform data across 12,000 Objectives found high-performing teams average 2.9 KRs per Objective. Overloading past five correlates with worse outcomes.
Key Results: full definitionAn ongoing metric a team monitors continuously — monthly recurring revenue, churn rate, NPS. KPIs are health metrics; OKRs are change metrics. A KPI tells you how things are; an OKR tells you what you're committed to changing this quarter. The confusion between the two is one of the most common reasons teams write weak Key Results.
KPI vs OKR explainedThe practice of monitoring ongoing business health metrics alongside OKRs — not instead of them. OKRs and KPI tracking complement each other: KPIs show whether the business is healthy; OKRs define what you're actively trying to change. Most mature OKR platforms support both in the same view.
OKR metrics guideA Key Result with only two possible scores — 0.0 (not done) or 1.0 (done). Used for outcomes that are genuinely all-or-nothing: a contract signed, a certification achieved, a feature shipped to production. Use sparingly. Most outcomes have meaningful intermediate states — if yours doesn't, a binary KR is the honest format. Avoid using it to disguise a task as a Key Result.
OKR scoring guideA Key Result structured as a series of discrete milestones rather than a single metric — scored by how many milestones were reached by cycle end. The risk: milestone KRs slide into output-tracking if milestones describe deliverables rather than outcomes. Each milestone should represent a real business change, not a step completed.
How to write Key ResultsA category of OKRs designed to test a hypothesis or explore a new approach — one of three types alongside committed and aspirational. Used when the team doesn't yet know whether an approach works. Scored on whether the learning objective was achieved, not whether the hypothesis was confirmed.
OKR examples by teamA metric that confirms a trend after it has already occurred — quarterly revenue, annual retention, end-of-cycle NPS. Useful for measuring outcomes, but slow to react. Most OKR outcomes are lagging. Pair with leading indicators to understand what's actually driving the change in real time during the cycle.
The structural mechanism that ensures senior leaders are held to the same OKR standards as the rest of the organization — named ownership per Key Result, weekly check-in discipline, and honest scoring at cycle end. The OKR Intelligence Report found 50% of all Key Results have no named owner. Leadership accountability starts by fixing that at the top.
Leadership accountability guideA metric that predicts where you're heading — pipeline volume, weekly active users, demos booked. Faster signal than lagging indicators. Good Key Results often combine both: a lagging outcome (ARR growth) alongside the leading indicators that drive it (qualified pipeline, trial conversion rate). The leading indicator is what you manage week to week; the lagging indicator is what you're ultimately trying to move.
A goal-setting framework developed by Peter Drucker in the 1950s — the predecessor to OKRs. Andy Grove adapted MBO at Intel by adding the Key Results layer and the quarterly check-in cadence, creating what became OKRs. The key difference: MBOs are often annual and tied to compensation; OKRs are quarterly, not compensation-linked, and designed for ambitious stretch targets.
How well-established an organization's OKR practice is — measured by check-in consistency, cascade completeness, scoring honesty, and retrospective quality. The maturity curve is real: first-cycle teams average 51% completion; teams in cycle five average 79%. Maturity compounds when the full five-step cycle runs consistently, including the retrospective.
OKR adoption guideA planned checkpoint at approximately week six of a cycle to assess what's on track, what's slipping, and where to refocus. The intervention point — not a status report. Every Key Result below 0.5 at week six needs an explicit decision: revise the target, escalate the blocker, or formally close it. The OKR Intelligence Report found 7% of KRs are simply abandoned without this decision.
Mid-cycle review guideA statement of why an organization exists — the most stable layer above strategy and OKRs. Doesn't change quarterly. The standard hierarchy: Mission → Vision → Strategy → OKRs. A strategy without OKRs stays aspirational. OKRs without a mission lack the "why" that makes goals meaningful to the people executing them.
A performance management framework that plots employees on a 3×3 grid: performance on one axis, potential on the other. Used for talent reviews, succession planning, and identifying high-potential team members. When connected to OKR delivery data, the performance axis becomes objective rather than impressionistic. Available on the Expand plan.
See Expand featuresA single metric that best captures the core value a product delivers to customers — weekly active users, annual recurring revenue, or transactions per month. If only one number can move this quarter, it should be this one. Most company-level OKRs cascade down from the North Star, and most team Key Results should ultimately connect back up to it.
A qualitative, directional statement of what a team wants to achieve in a cycle. The “O” in OKR. Should be ambitious, time-bound, and meaningful — not a metric, not a task list. No numbers in the Objective itself; those live in the Key Results. Each Objective should be answerable in one sentence: “This quarter we will [do X] so that [Y happens].”
What makes a great ObjectiveShort for Objectives and Key Results. A goal-setting framework developed at Intel by Andy Grove and popularized by John Doerr at Google. An OKR is one Objective (where you're going) plus the 2–4 Key Results (how you'll know you got there). Not a performance review tool, not a task manager — a system for focus, alignment, and measurable progress.
How OKRs Tool worksThe designated person inside an organization responsible for driving OKR adoption — running planning sessions, coaching team leads on Key Result quality, facilitating retrospectives, and ensuring the weekly check-in rhythm holds. Most successful OKR rollouts have one. Without a champion, accountability for the process diffuses across the leadership team until nobody owns it.
OKR Champion role explainedA practitioner who helps organizations implement and improve their OKR programme — facilitating planning sessions, coaching on Key Result quality, and diagnosing adoption problems. Distinct from an OKR Champion: a Coach is often external, whereas a Champion is an existing team member with OKR accountability added to their brief.
OKR Champion vs CoachPurpose-built platforms for setting, cascading, tracking, and reviewing OKRs — replacing spreadsheets with structured ownership, automated check-ins, and live alignment maps. The ROI difference is significant: organizations using purpose-built OKR software generate a 1:88 return on investment versus 1:25 on spreadsheets. The tool isn't the framework — but it is the infrastructure that makes the framework stick past cycle two.
Best OKR software comparedThe standard method for evaluating Key Result progress at cycle end — expressed as a number between 0.0 (not started) and 1.0 (fully achieved). 0.6–0.8 is the healthy range for well-calibrated OKRs. The score drives the retrospective: each KR that scored below 0.5 should have a structural explanation, not just "it was a hard quarter."
OKR scoring guideOutput: the work produced — features shipped, calls made, articles published. Outcome: the change that resulted — revenue earned, users retained, deals closed. Good Key Results measure outcomes; weak ones count outputs. Our analysis of 7,857 Key Results found output verbs (launch, complete, deliver) in 52% of all KRs. The teams that rewrote them as outcomes saw measurably higher completion rates.
Vanity metrics in OKRsThe single accountable person for an Objective or Key Result — one person, not a team. The OKR Intelligence Report found 50% of all Key Results have no named owner. Teams with required single ownership see 26% higher completion rates. Other people can contribute, but only one person checks in, reports progress, and is responsible for the score at cycle end.
OKR ownership guideThe higher-level OKR that a team or department OKR rolls up to. In OKRs Tool, every team OKR requires a parent — you can't set a team goal without picking which company priority it contributes to. This structural requirement closes the 65% misalignment gap before the cycle even starts.
Cascading OKRs guideA structured assessment of an individual's performance over a defined period. OKRs make reviews better: KR completion rates, check-in consistency, and at-risk history are already in the platform — no manual data pull. The 2026 OKR Intelligence Report found 75% of organizations formally link OKR outcomes to performance decisions. Available on the Expand plan.
See Expand featuresThe structured session at the start of each cycle where company Objectives are set, Key Results are written, and the cascade is completed. Should be done in under a week. Teams that complete planning and launch in under seven days see up to 50% higher completion rates than those taking three to four weeks. Planning complexity is a direct predictor of execution outcomes.
OKR planning guideThe current completion percentage of a Key Result — typically expressed as a number between 0% and 100%, or 0.0 and 1.0. Updated by the owner at each weekly check-in. Progress is the signal that drives everything else: at-risk flagging, health scores, forecast projections, and mid-cycle interventions all depend on progress being updated honestly and on time.
OKR tracking guideA structured review at the end of each quarter where leadership examines what was committed, what was delivered, and what changes for the next cycle. The retrospective that closes one OKR cycle and opens the next. Teams that run structured QBRs complete 30–45% more OKRs the following cycle — not from writing better goals, but from understanding why the previous cycle produced the results it did.
Free QBR templateThe standard OKR operating rhythm — one cycle every 13 weeks, with weekly check-ins and a mid-cycle review at week six. Quarterly is the right cycle length for most 50–200 person organizations: long enough to achieve meaningful outcomes, short enough to course-correct before the miss is final. Annual OKRs are too slow; monthly are too tactical.
Quarterly OKRs guideA structured look-back at what worked, what didn't, and what specific structural changes will improve next cycle — run at the end of each OKR cycle. The highest-leverage practice for compounding OKR quality. Teams that run honest retros and commit to two to four structural changes see completion climb consistently cycle over cycle. Without the retro, each cycle restarts from scratch.
End-of-cycle reflection guideThe measurable return generated by an OKR programme. The 2026 Benchmark Report across 330 organizations found purpose-built OKR software generates a 1:88 return on investment — compared to 1:25 on spreadsheets and 1:16 on enterprise blended platforms. The difference isn't the software cost: it's the weekly visibility, required ownership, and cascade alignment that makes accountability structural.
ROI of OKRs reportAutomatic calculation of higher-level OKR progress from the team and individual OKRs underneath it. Leadership opens one dashboard and sees how the whole company is tracking — no spreadsheet stitching, no status meeting required. Roll-up accuracy depends entirely on owners updating their Key Results at the correct cadence.
The practice of deliberately setting easy OKR targets to guarantee hitting 1.0 — protecting the team from accountability rather than committing to genuine progress. The most corrosive anti-pattern in OKR programmes because it looks like success while delivering none. The fix is separating OKR scores from performance reviews: when hitting 1.0 has career consequences, teams sandbag. When 0.7 on a stretch goal is celebrated, they don't.
How OKR scoring worksOKRs that are co-owned by two or more teams — typically because the outcome requires contributions from multiple functions (e.g., a product launch that needs engineering, marketing, and sales to execute). Use the single named owner rule: even with shared contribution, one team or person should hold the primary accountability. Shared OKRs with no clear primary owner drift faster than team-level OKRs.
OKR alignment guideAn older goal-setting framework (Specific, Measurable, Achievable, Relevant, Time-bound). OKRs extend SMART in two critical ways: they add a cascade layer (alignment) and a check-in rhythm (cadence). Individual SMART criteria handle goal quality; OKRs add the structural layer for organizations. Most well-written Key Results satisfy the SMART criteria as a baseline, not a ceiling.
The owner-set health signal of a Key Result — typically On Track, At Risk, or Behind. Set during the weekly check-in based on the owner's assessment. Drives the leadership dashboard: at-risk KRs surface automatically so leadership can intervene before the miss. Different from Health Score, which is computed from progress data rather than set by the owner.
The set of choices that determines where an organization competes and how it will win. Sits above OKRs in the hierarchy: Mission → Vision → Strategy → OKRs. A strategy that doesn't translate into OKRs is a document. OKRs are the mechanism that turns strategic intent into weekly action.
OKR strategy execution guideSee Aspirational OKRs. A Key Result set deliberately beyond comfortable reach — where 70% completion signals a strong quarter, not a failure. The concept comes from Andy Grove's original OKR work at Intel: if you always hit 100%, the targets weren't ambitious enough. Use sparingly and explain the convention to your team before the first cycle.
A structured performance feedback process that collects input from multiple sources — manager, peers, direct reports, and self — rather than just from the direct line manager. When connected to OKR delivery data, 360 reviews produce more complete and objective performance pictures: the quantitative KR score combines with qualitative peer and manager feedback. Available on the Expand plan.
See Expand featuresOKRs set at the team level — the Marketing team's OKRs, the Engineering squad's OKRs, the Customer Success team's OKRs. Should always cascade up to a department or company OKR. The most operationally meaningful layer for most organizations, since it's where week-to-week execution happens and where alignment breakdowns first become visible.
Team OKRs guideTwo approaches to setting OKRs. Top-down: leadership sets company OKRs and teams cascade beneath. Bottom-up: teams propose OKRs that leadership filters and integrates. Most healthy organizations do both simultaneously — top-down for strategic direction, bottom-up for buy-in and ground-level insight. Pure top-down produces compliance; pure bottom-up produces drift.
OKR process guideThe practice of monitoring Key Result progress throughout the cycle — via weekly check-ins, automated nudges, and live dashboards. Tracking is the habit that makes OKRs a management system rather than a planning exercise. Our benchmark data found that 71% of Key Results that ever moved off their starting value did so because of structured tracking. The 29% that never moved were almost universally un-tracked.
OKR tracking guideA metric that can increase while the business gets worse — page views, app downloads, social followers, emails sent, features shipped. The most common Key Result quality problem in fast-moving teams. Our analysis of 7,857 Key Results found 52% were vanity metrics or tasks in disguise. The diagnostic: can this number go up while the business gets worse? If yes, it's vanity.
Vanity metrics in OKRsA long-term statement of what an organization is trying to become — the picture of the world if it succeeds. Sits between Mission (why we exist) and Strategy (how we'll compete). Doesn't change quarterly. Vision gives OKRs their “why” at the organizational level — without it, quarterly goals feel like arbitrary targets rather than stepping stones to something larger.
The cadence that makes or breaks an OKR programme. The single biggest predictor of OKR completion: teams with weekly check-ins complete 43% more OKRs than those without. Automated nudges via Slack or MS Teams remove the coordination overhead — the nudge goes out at the same time every week whether the owner remembers or not. Five minutes per Key Result. No meeting required.
Weekly check-in guideA repeatable process tied to the OKR cycle — planning, weekly check-ins, mid-cycle reviews, end-of-cycle retrospectives. Strong OKR teams treat these as recurring structural commitments, not one-off events. The difference between teams that compound from 51% to 79% completion across cycles and teams that stay flat is almost always whether the workflows run consistently or get deprioritized when the quarter gets busy.
OKR workflowsReading definitions only gets you so far. Set up your first OKR cycle in OKRs Tool — it takes about two minutes, no credit card required. Free for up to 5 users, forever.