Skip to content
OKR | Part 1 of 10

OKR for Operations Teams: Few Goals That Change Something

Why plants, warehouses and engineering teams need a short quarterly goal list next to their KPIs, and how OKR provide it.

A logistics manager opens the monthly review with fifteen KPIs on one slide. Inventory accuracy, dock to stock time, overtime, picking errors, freight cost, on-time shipment. All of them matter. None of them tells the team what must be different three months from now.

Operations teams are measured all day. That is exactly why they need a second, much shorter list: the few things that must change this quarter.

What OKR are

OKR stands for objectives and key results. An objective is a short sentence about a change the team wants, without numbers. Key results are three or four measured outcomes that prove the change, each from a start value to a target value.

A warehouse example for one quarter:

  • Objective: ship complete and on time without firefighting.
  • Key result: on-time shipment rate from 91 to 98 percent.
  • Key result: expedited freight cost per week from EUR 3,540 to EUR 1,150.
  • Key result: picking errors per 1,000 order lines from 8 to 2.

The team adds a second objective, at most a third. Everything else keeps running and is watched on the board, but it is not an OKR.

What OKR add in operations

Focus. A plant can improve everything a little or a few things a lot. OKR force the choice and make it visible.

A time box. Improvement topics that used to run for a year get a result or a decision after thirteen weeks.

A weekly look. Yearly targets are set in January and checked in December. OKR are checked in a thirty-minute meeting every week.

Connection. Teams write their objectives against the priorities of the plant, and they agree what they need from each other before the quarter starts.

What OKR are not

They are not the yearly target agreement with a new name. They are not a list of everything the team does. They are not a basis for bonuses. And they do not replace daily shop floor management, which keeps the normal business stable.

In operations, OKR fail most often because the three lists get mixed: the numbers that must stay in range, the numbers that must change, and the tasks that make them change.

What a first quarter delivers

In the example, the warehouse of a plant with 640 people ran its first OKR quarter from January to April. On-time shipment reached 96.5 percent, picking errors dropped to 3 per 1,000 lines, and new pickers worked independently after 8 days instead of 15.

Not every target was reached, and that was intended. The overall score was 0.76, a very good result for ambitious key results. More important than the score: the team knew every week where it stood and what it would do next.

This series shows how to get there: how to write objectives and key results, how to keep health metrics apart, how to align teams, how to run the weekly check-in and how to scale from one area to the whole plant.

Newsletter

One Lean idea.
Every week.