Skip to content
OKR | Part 10 of 10

Introducing OKR: From One Area to the Whole Plant

A pilot area, two quarters of learning, a short company guide and waves of new teams: a twelve-month roadmap for OKR in operations.

OKR look simple, and that is the trap. A plant that rolls them out to every team at once usually gets forty goal lists, a few overwhelmed coaches and a quiet return to the old system after two quarters.

Introduce OKR like any other change: pilot, learn, standardize, spread.

Start in one area that wants it

Choose a pilot area with a willing leader and a real change to make. A warehouse with delivery problems, a production line with a quality issue, an engineering group with long changeovers. Ten to eighty people, one leader who can decide about priorities.

Before the first planning, the leader of the next level writes three priorities of the plant for the year. Without them, the pilot team has nothing to align with.

Run two quarters before scaling

The first quarter teaches the form: objectives, key results, check-ins, scoring. The second quarter shows whether the rhythm holds when the novelty is gone. Most problems appear there: check-ins that get skipped, data that is not available on Monday, capacity that is eaten by the daily business.

Score the pilot area with a simple maturity check of 25 statements at the start and after each quarter. In the running example, the warehouse went from 24 to 74 of 100 points in its first quarter.

Write a short company guide

After two quarters, write down what works in your plant in ten rules or fewer. Three objectives at most, key results as outcomes with a data source, health metrics apart, weekly check-ins, one scoring formula, no link to bonuses, retrospectives with carry-over decisions.

Your own rules, based on your own experience, beat any long external method description. New teams read two pages, not a book.

Add teams in waves

Add four to eight teams per quarter. Each new team gets coach support for its first quarter: planning workshop, the first four check-ins and the retrospective. One coach can support about eight teams with 20 percent of their time.

The twelve-month roadmap

Quarter Focus Result
Q1 Pilot in logistics, plant priorities written, coach trained First scores, check-in rhythm holds
Q2 Logistics continues, line 3, engineering and purchasing start Four teams aligned, dependency agreements in use
Q3 All production and support teams, company guide written Plant view of all OKR, mid-quarter reviews by leaders
Q4 Link to the yearly strategy process, check in every area OKR part of the management system

Connect to the strategy

When most areas run OKR, link the plant OKR to the multi-year direction. Plants that need a binding long-term deployment with catchball add Hoshin Kanri on top: breakthrough objectives for several years, OKR for what each team changes this quarter.

Tools come last

Start with a spreadsheet and a board. Buy OKR software only when more than fifteen teams work with OKR and the overview becomes hard to keep. A tool does not create focus, alignment or honest check-ins. It only makes them easier to see once they exist.

Newsletter

One Lean idea.
Every week.