Skip to content
OKR | Part 3 of 10

Writing Objectives That Teams Actually Want

An objective is a short sentence about a change, without numbers. Five tests separate strong objectives from goal lists.

Most first OKR drafts in operations look like this: “Improve logistics KPIs”, “Implement new WMS module”, “Reduce costs by 8 percent”. They are easy to write and they change nothing, because they do not say what should be different.

An objective is a short sentence about a change that the people in the area understand and want. It tells a story in one line.

Weak and strong

Weak Why it is weak Strong
Improve logistics KPIs Says nothing about the change Ship complete and on time without firefighting
Implement new WMS module A task, not a change Make every order traceable from dock to customer
Reduce costs by 8 percent A key result written as an objective Stop paying for our own delays
Continue 5S program Business as usual Make the warehouse a place where new people are productive fast
Be the best warehouse in the group Not in the hands of the team Become the warehouse our production lines never wait for

The strong versions name a change and a reason. A team leader can explain them to a new colleague in one minute.

Five tests

Would the team say it in its own words? If an objective sounds like a slide, rewrite it with the people who do the work. Ownership starts with the wording.

Does it describe a change? “Keep”, “maintain” and “continue” belong to health metrics, the numbers that must stay in range.

Can the team influence it this quarter? “Be the best plant in the group” depends on other plants. “Become the plant our customers can count on” depends on us.

Does it serve a priority of the plant? Write the priority next to the objective. If no priority fits, either the objective or the priority list is wrong.

Is it one of three or fewer? A fourth objective usually means that nothing was decided. Write the rest on a list of things that will not be done this quarter.

Practical rules

Start with a verb of change: make, stop, become, build, cut. Avoid improve, optimize and support, they invite vague results.

Write from the view of the customer of the team. “Our production lines never wait” is stronger than “better line supply”, because it says who notices the change.

Keep numbers out of the objective. An objective with a number usually hides a key result. Move the number down and ask what the change is about.

Two objectives are often better than three for teams that also carry a full daily business. A warehouse that runs two shifts and ships 1,800 order lines a day has limited room for change, and the objectives must fit into it.

How to choose

In a planning workshop, teams usually collect eight to twelve candidates. Let each person place three dots, then discuss the top five. Decide, do not average. The candidates that did not make it are not lost, they are the first input for the next quarter.

A good test at the end: show the objectives to someone from another department. If they understand what will be different in three months, the objectives are ready for key results.

Newsletter

One Lean idea.
Every week.