Skip to content
OKR | Part 6 of 10

Aligning OKR Across Teams Without a Cascade

Vertical alignment with the priorities of the plant, horizontal alignment between teams, and dependency agreements written before the quarter starts.

The classic approach to goals is the cascade. The plant manager sets targets, each department breaks them down, each team receives its share. It looks orderly on paper. In practice it is slow, and teams end up executing numbers they do not believe in.

OKR use alignment instead. Leaders share their priorities and their own OKR. Teams draft OKR that contribute, and present them. The leader checks the fit, not the wording.

Vertical alignment

In the running example, a plant with 640 people works on three key results in Q1 2027: on-time delivery from 91 to 97 percent, customer complaints from 14 to 6 per quarter, and order to shipment lead time from 12 to 8 days.

The teams then show how their OKR contribute:

Plant key result Contributing team key results
On-time delivery 91 to 97 percent Logistics on-time shipment, purchasing line stops from missing parts, engineering changeover time
Complaints 14 to 6 per quarter Line 3 first pass yield, logistics picking errors
Lead time 12 to 8 days Engineering changeover time, logistics on-time shipment

A plant key result without any contributing team key result is a gap. Either a team takes it on, or the plant accepts that it will not move.

A healthy plant has roughly half of its team OKR drafted bottom-up. Teams often see opportunities the leadership does not, such as faster onboarding in the warehouse.

Horizontal alignment

Most key results in operations depend on another team. Logistics cannot ship on time if production planning confirms delivery dates late. Line 3 cannot improve first pass yield without the changeover standard from engineering.

These dependencies must be agreed before the quarter, not discovered in week 9. A dependency agreement names what is needed, by when, for which key result, and who confirms it on both sides:

  • Logistics needs delivery dates confirmed every day at 14:00 from production planning.
  • Line 3 needs the changeover standard and quick-release fixtures from engineering by week 6.
  • Engineering needs two changeover trials per week on line 3.
  • Purchasing needs a weekly demand forecast for the 40 A parts from production planning.

The delivering team mirrors the agreement in its own OKR or initiatives. Otherwise it competes with its own priorities and loses.

The alignment meeting

One meeting in the week before the quarter does most of the work. Plant leadership presents its draft and the priorities. Each team presents its draft in five minutes, including what it needs from others. Then the group looks at gaps, conflicts and dependencies.

Conflicts that two teams cannot solve go to the leader both report to, in that meeting. A conflict decided in planning costs ten minutes. The same conflict discovered in week 9 costs a key result.

One view for everybody

Put all OKR of the plant into one list that everybody can read: team, objective, key results, owner, current value. Transparency does more for alignment than any cascade, because people start to look at what their neighbors are working on.

Newsletter

One Lean idea.
Every week.