Back to the glossary

Strategy Intelligence

What Are OKRs (Objectives and Key Results)?

Sep 16, 2026·5 min read·Reviewed by Frank Barthélemy

OKRs (Objectives and Key Results) are a goal-setting framework that connects a qualitative goal (Objective) with a few measurable outcomes (Key Results). The Objective describes what is to be achieved; the Key Results define how progress can be measured in concrete terms. Teams usually work with three to five Key Results per Objective and review the status each quarter (Atlassian).

OKRs help organizations translate their strategy into verifiable goals and align teams around shared outcomes. Instead of formulating statements of intent, the framework requires success to be tied to clear figures. This is exactly the core idea: a goal without a measurable outcome remains incomplete under OKRs.

Where OKRs Come From

The method goes back to Andrew Grove, who introduced the approach at Intel in the 1970s and described it in his 1983 book "High Output Management" (Wikipedia). Later, the framework spread further through the investor John Doerr, including at Google. Today, companies of every size use OKRs, from large corporations like Google and LinkedIn to small and medium-sized businesses (Weekdone).

The idea behind it has remained simple: a few clearly formulated goals create focus. When everyone in the company knows what matters in the coming quarter, resources and attention can be concentrated rather than spread across too many initiatives.

Structure: Objective and Key Results

An OKR consists of two parts. The Objective is a meaningful, concrete and clearly defined goal. It is formulated qualitatively and describes a direction meant to inspire (IBM). Example: "We will become the preferred provider for mid-sized businesses in northern Germany."

The Key Results make this goal measurable. They are specific, verifiable and quantify progress. As a rule of thumb, three to five Key Results per Objective apply (Businessmap). For example:

  • Increase the number of qualified initial meetings per quarter from 40 to 70.
  • Reduce the average response time to inquiries to under 4 hours.
  • Increase the closing rate in new customer business from 18% to 24%.

The distinction is important: the Objective states "where to", the Key Results state "how it becomes visible". A Key Result that cannot be expressed in a number is not a Key Result but rather a task.

The OKR Cycle

OKRs are typically used in quarterly cycles. At the start of the quarter, companies, teams and sometimes individuals set their goals, regular check-ins take place during the period, and at the end the degree of goal achievement is assessed (Atlassian). These short cycles make it possible to respond to changes without overturning the annual plan.

A proven practice is the mix of top-down and bottom-up: teams and individuals should formulate a substantial share of their OKRs themselves, often around 40 percent, so that the goals are embraced and do not feel merely imposed (Businessmap). Transparency is equally central: company and team OKRs are published in a shared location so that all participants know the priorities (Synergita).

OKRs and KPIs: Not the Same

OKRs and KPIs are often confused but serve different purposes. OKRs are a goal-setting framework that translates ambitious plans into measurable outcomes. KPIs (Key Performance Indicators) are ongoing metrics that monitor the state of a process or area over longer periods (Businessmap).

One difference lies in the time horizon: OKRs usually work in quarterly cycles, while KPIs often cover longer periods and run continuously (Workpath). In practice, the two complement each other. A KPI can, for example, provide the occasion for an Objective when it points to a problem, and a Key Result can refer to an existing KPI.

OKRs in the Context of AI-Supported Strategy Work

A weak point of many OKR systems is not the formulation of goals but the ongoing gathering of interim results. Sales figures, project progress and metrics are often scattered across different systems. This is exactly where OKR management fits into our Strategy Intelligence field: AI prepares the relevant data for progress and quarterly reporting, while people assess and decide.

For this to work, the data must first be available reliably. In sales, for example, Key Results often depend on well-maintained pipelines, which is difficult without sound lead qualification. For preparing such metrics, AI agents that take over recurring evaluations are an option. An AI employee with a fixed role can compile the interim status of individual Key Results without anyone having to copy the figures manually from several tools. Interpreting these figures and deciding whether a goal needs adjustment remains the team's task.

Frequently asked questions

How many OKRs should a team have?

Less is usually better. A few Objectives per cycle with three to five Key Results each is common (Businessmap). Too many goals dilute attention and undermine the actual purpose of OKRs, which is to create focus. For getting started, a single Objective per team is often enough.

What is the difference between OKRs and KPIs?

OKRs are a framework for setting ambitious goals and tracking their progress. KPIs are ongoing metrics that continuously monitor the state of an area (Businessmap). OKRs usually work on a quarterly basis, while KPIs cover longer periods. The two do not exclude each other but complement one another.

In what cycle are OKRs reviewed?

OKRs are typically set quarterly and accompanied by regular check-ins (Atlassian). At the end of the quarter, the degree of goal achievement is assessed. These short cycles make it possible to adjust goals under changed conditions without redoing the entire plan.

Who are OKRs suitable for?

OKRs are suitable for organizations of any size, from large companies to small and medium-sized businesses (Weekdone). The prerequisite is a willingness to formulate goals measurably and to review progress regularly. Where transparency and open communication are lacking, the framework has little effect.

Sources

  1. Atlassian atlassian.com
  2. Wikipedia en.wikipedia.org
  3. Weekdone blog.weekdone.com
  4. IBM ibm.com
  5. Businessmap businessmap.io
  6. Synergita synergita.com
  7. Businessmap businessmap.io
  8. Workpath workpath.com

This text was generated by AI and reviewed by a human.