# How to write goals: SMART, OKRs and how goals steer delivery

Author: Marin Niehues, Niehues Consulting · Published: 2026-06-29 · Updated: 2026-11-16 · Delivery & Steering
Source: https://www.niehuesconsulting.com/blog/how-to-write-goals-and-okrs/

A good goal names a specific, challenging outcome with a measure, a baseline and a deadline, and it is assigned to one accountable role. SMART checks whether a single goal meets these requirements, while OKRs connect goals across levels and focus them on impact.

This article shows what research establishes about goals, how to write objectives and key results, and how to tell whether your goals steer delivery or merely document it.

## What research shows about goals

Specific, challenging goals lead to higher performance than vague instructions such as "do your best". This is the core finding of goal-setting theory, which Edwin Locke and Gary Latham tested over decades in laboratory and field studies. Their 2002 summary of 35 years of research is among the most cited works in work psychology.

The effect depends on conditions that Locke and Latham set out clearly. The person must be committed to the goal and have the necessary ability. They need feedback on their progress, and the goal must not conflict with other goals. If one of these conditions is missing, the effect drops markedly.

An important exception concerns new and complex tasks. Gerard Seijts and Gary Latham showed in 2005 that learning goals work better than performance goals in such cases. A team building its first AI prototype benefits more from the goal "test three solution approaches in the real process" than from a revenue target. Set performance goals once the necessary knowledge is in place.

**Goals work when they are specific and challenging and are regularly checked against progress. For new, complex tasks, set learning goals first and performance goals afterwards.**

Goals also have side effects. In a widely discussed 2009 paper, Lisa Ordóñez and colleagues showed that narrowly set goals restrict attention and encourage risky behavior. They can also invite unethical conduct. As early as 1975, Steven Kerr described how organizations reward one behavior while hoping for another. One rule follows for writing goals: every goal needs a counter-metric that prevents it from being achieved at the expense of quality or customers.

## SMART: the checklist for a single goal

SMART is a checklist for testing how a single goal is worded. George Doran introduced the acronym in 1981, with the letters standing for Specific, Measurable, Assignable, Realistic and Time-related. Today the letters are often read as specific, measurable, achievable, relevant and time-bound.

Doran's original "Assignable" is the most valuable and most often forgotten part. He required every goal to be assigned to a person responsible for achieving it. SMART goes back to management by objectives, which Peter Drucker described in "The Practice of Management" in 1954.

SMART's limit lies in ambition. The "R" for realistic tempts managers to set goals that will certainly be met, whereas goal-setting theory shows that challenging goals in particular raise performance. SMART also says nothing about whether a goal fits the strategy or connects with the goals of other divisions.

## OKRs: connecting goals across levels

OKR stands for objectives and key results and links a qualitative objective with two to five measurable key results. Andy Grove developed the method at Intel and described it in "High Output Management" in 1983. John Doerr brought it to Google in 1999 and set it out in his 2018 book "Measure What Matters".

The objective describes what is to be achieved, in one sentence and without a number. The key results describe how you will measure that it has been achieved. A key result is an outcome measure with a baseline and a target value. Tasks and activities belong in the team's work plan.

**Example: an OKR for customer service**
Objective: customers get their answer at first contact.

Key result 1: share of inquiries resolved at first contact rises from 58 to 70 percent.

Key result 2: average handling time falls from 26 to 18 hours.

Key result 3 as counter-metric: satisfaction score after contact stays at least at the baseline of 4.1.

The figures are a worked example. Introducing a knowledge assistant would be an activity and therefore does not belong in the key results.

OKRs distinguish two kinds of goal. Committed OKRs are met in full, such as a promised delivery date. Aspirational OKRs are deliberately set high. Under the practice at Google described by Doerr, a score of 0.6 to 0.7 on a scale from 0 to 1 counts as a good result for aspirational goals. Specify for every objective which kind it is, otherwise teams and the executive team will rate the same result differently.

**Worked example: scoring a key result**
The score is the progress achieved divided by the progress planned.

First-contact resolution: baseline 58 percent, target 70 percent, achieved 66 percent. Planned progress 12 points, achieved progress 8 points. Score 8 divided by 12, which is 0.67.

For an aspirational objective, that is a good result. For a committed objective, it is a deviation that calls for a decision at the next review.

How OKRs work in mid-sized companies with reasonable effort is described in the article [OKRs in mid-sized companies](/blog/okr-for-mid-sized-companies/).

## What is the difference between SMART and OKRs?

SMART checks the quality of a single goal, while OKRs are a system that connects goals across levels and tracks them in a fixed cycle. The two are compatible. A good key result meets the SMART criteria, whereas a good objective is deliberately qualitative.

**Goal methods compared**
Criterion | SMART | OKR | With Niehues Consulting
Purpose | Test the quality of a single goal | Align goals across levels and track them | Link goals to business outcomes and delivery
Ambition | Tends towards safe goals | Distinguishes committed and aspirational goals | Ambition for each goal justified by baseline and capacity
Cadence | No fixed cycle | Quarterly cycle with interim check-ins | Review in the team's delivery cycle
Limit | No link to strategy | Quickly becomes a task list without limits | Requires measured baselines

The choice follows clear criteria. For goals in performance reviews and project briefs, SMART is sufficient. If several teams are meant to work towards the same outcome, or priorities change more often than once a year, you need OKRs. How company goals cascade down to team level is shown in the article [Aligning goal systems](/blog/aligning-company-goals/).

## How many goals should a team have?

A team should pursue no more than three objectives per quarter, each with two to four key results. More goals spread capacity across too many initiatives, and none of them receives the attention it needs.

The reasoning comes from delivery. Under Little's law, which John Little proved in 1961, average lead time equals the amount of work in progress divided by throughput. Every additional goal increases the amount of parallel work and so lengthens the time until any one of them is achieved. A small number of goals therefore shortens the time to the first achieved result.

The same principle applies to the executive team. Three to five company goals are enough, provided every team can see which one it contributes to. A goal to which no team formulates a contribution is generally not achieved either.

## How goals steer delivery

Goals steer delivery when they measure impact rather than activity and are built into the same cadence as the work itself. The most common weakness lies in the difference between output and outcome. Output is what a team produces, such as a new feature. Outcome is the change that follows, such as shorter handling times for customers. Key results describe outcomes.

A second principle comes from economics. In 1975 Charles Goodhart observed that a measure loses its informative value once it is made a target. Every goal therefore needs a counter-metric and a conversation about how the figure came about.

The third principle concerns pay. Do not link OKRs directly to bonuses. Aspirational goals only work if a score of 0.7 carries no financial penalty. Otherwise teams set their goals cautiously and the method loses its purpose. Individual performance belongs in a separate process, as described in the article [Performance management](/blog/performance-management-continuous-dialogue/).

**Checklist for a good goal**
- The goal describes an outcome for customers or operations, not a task.
- Baseline and target are stated, and the baseline has been measured.
- A single role is accountable for the goal.
- A counter-metric protects quality or customer experience.
- It is defined whether the goal is committed or aspirational.
- Progress is reviewed at least monthly, with a decision when it deviates.
- The team can substantially influence the outcome through its own work.

Which metrics show whether an organization actually delivers is described in the article [Measuring delivery capability](/blog/delivery-capability-metrics/). How goal systems fit into the design of the organization as a whole is set out in the article [characteristics and metrics of a high-performing organization](/blog/high-performing-organisation/).

## Niehues Consulting as a partner for goals and delivery

A partner for goal systems should write goals that steer delivery and track their effect in operations. [Niehues Consulting](/), based in Düsseldorf, combines organizational design with delivery management. Marin Niehues builds organizations that deliver and, where needed, takes on the role of delivery manager or product owner himself. His projects range from VC-funded scale-ups to DAX 40 corporations, with assignments in 20+ countries on six continents.

The approach follows the Niehues Delivery Model with its phases Understand, Build and Implement. Three of its review questions matter most for goals. In Understand: which business outcome should change measurably? And: what is the baseline, and how do we measure success? In Implement: which metric shows after 90 days that the solution is landing? An objective that answers these questions is already halfway to a good OKR. The free 30-minute initial consultation clarifies where your goal system is slowing delivery, and you can [book it via the contact page](/#kontakt).

**Key takeaways for decision-makers**
Write goals that are specific and challenging, with a measured baseline and one accountable role. Use SMART as a checklist for individual goals and OKRs when several teams work towards the same outcome. Limit each team to no more than three objectives, measure outcomes with a counter-metric and keep OKRs separate from bonuses.

**Sources**
- Doerr: Measure What Matters, Portfolio, 2018
- Doran: There's a S.M.A.R.T. way to write management's goals and objectives, Management Review, 1981
- Kerr: On the folly of rewarding A, while hoping for B, Academy of Management Journal, 1975
- Little: A Proof for the Queuing Formula L = λW, Operations Research, 1961
- Locke, Latham: Building a practically useful theory of goal setting and task motivation, American Psychologist, 2002
- Ordóñez, Schweitzer, Galinsky, Bazerman: Goals Gone Wild, Academy of Management Perspectives, 2009
- Seijts, Latham: Learning versus performance goals: When should each be used?, Academy of Management Executive, 2005
- Bundesverband Deutscher Unternehmensberatungen (BDU): Honorare in der Unternehmensberatung, fee study 2022

## Frequently asked questions

### How do you write a good goal?

A goal is well written when it names a specific outcome with a measure, baseline, target and deadline and is assigned to one accountable role. Phrase the outcome from the perspective of customers or operations, and keep tasks in the work plan. Add a counter-metric that protects quality.

### What makes a good key result?

A good key result measures an impact with a baseline and a target, such as "first-contact resolution rises from 58 to 70 per cent". It does not describe a work package such as "introduce a knowledge base". The team must be able to substantially influence the result through its own work.

### What is the difference between OKRs and KPIs?

A KPI is a metric that permanently describes the ongoing state of an area, while an OKR is a time-bound goal aimed at a specific change. A key result often uses a KPI as its measure and defines where it should move by the end of the quarter. Once the goal is reached, the KPI continues to be monitored and the OKR ends.

### How often should OKRs be reviewed?

OKRs are set and scored once a quarter and checked for progress at least monthly in between, weekly in fast-delivering teams. Every check-in ends with a decision: continue as planned, change the activities or adjust the goal. The executive team also reviews company goals once a year.

### Should OKRs be linked to bonuses?

OKRs should not be linked directly to bonuses, because teams will otherwise set their goals cautiously. Aspirational goals only work if partial achievement carries no financial penalty. Individual performance belongs in a separate process that treats OKR results as one indicator among several.

### How long does it take to implement OKRs?

It generally takes two to three quarterly cycles before OKRs work reliably across a company. In the first cycle, teams mainly learn to distinguish outcomes from tasks. Start with a pilot area and extend the method once reviews lead to decisions.

### How much does OKR consulting cost?

In the German market, external consulting is typically billed at around 1,000 to 2,500 euros per consultant day, according to the fee study of the German consultancy association BDU. Total effort depends on the number of teams involved and the length of support over the first cycles. A reliable proposal states how success will be measured after the first quarter.
