Connecting strategy, team choices and evidence of progress.
All notes

Operational excellence

Hoshin Kanri vs OKRs: turning strategy into what teams do on Monday

Two proven ways to connect strategy to daily work. How Hoshin Kanri cascades a breakthrough objective with catchball and monthly reviews, how OKRs set quarterly stretch goals, one worked example in both, and when to combine them.

A manufacturer wants to halve order-to-delivery lead time. Plant teams need annual targets and resources; their managers also need a way to review shorter trials and adjust the work. The example below follows that same ambition through Hoshin Kanri and OKRs.

Leaders use Hoshin Kanri to connect long-term objectives with annual priorities and team commitments. Teams use objectives and key results (OKRs) to state an aim and measurable results for a chosen period. They can combine the methods, provided the targets and review decisions fit together.

Hoshin Kanri: few things, fully deployed

Hoshin kanri roughly translates as "direction management". It grew in Japanese companies from the 1960s and was brought to Western readers by Yoji Akao's book Hoshin Kanri: Policy Deployment for Successful TQM. Leaders choose a small number of long-term objectives, then agree how each team will contribute.

For this manufacturer, connect four levels:

3 to 5 years Breakthrough objective Halve order-to-delivery lead time This year Annual objectives Cut lead time 20%; on-time delivery to 95% This year Top-level priorities Pull planning in 2 plants; supplier lead-time program Monthly Team targets Plant A: WIP −30% by June; Procurement: 10 suppliers on VMI Catchball:targets go down,reality comes up
A Hoshin cascade for a manufacturer. Each level sets the next one's targets, and catchball arrows run both ways: targets go down, and the reality of what's achievable comes back up.
Level Horizon Example
Breakthrough objective 3 to 5 years Halve order-to-delivery lead time
Annual objectives This year Cut lead time 20%; raise on-time delivery to 95%
Top-level priorities This year Pull planning in two plants; a supplier lead-time program
Targets and measures Monthly, per team Plant A: WIP down 30% by June. Procurement: 10 suppliers on vendor-managed inventory

On paper, many companies show all of this on a single page called an X-matrix: the four levels around the edges and small correlation grids in the corners, showing which priority serves which objective and who owns what. Thomas Jackson's Hoshin Kanri for the Lean Enterprise popularised it. It looks intimidating the first time, but its purpose is simple: to prove that every priority serves an objective, and every objective has someone working on it.

Catchball: agree the target and resources

During catchball, each level proposes how it can contribute and discusses the requirement with the level above. In this example, the plant manager proposes 30% less WIP in Plant A by June, conditional on two extra maintenance technicians. The teams must agree the resources or revise the target before accepting the commitment.

Record the agreed target, resources and conditions so both teams can check the same commitment at the next review.

Monthly reviews and the bowling chart

Hoshin runs on a monthly check: plan versus actual, with red and green, for every target. The usual tool is a bowling chart:

Measure (Plant A) Target by June Jan Feb Mar Apr
Work in process (units) 7,000 9,600 9,100 8,900 8,000
Monthly plan 9,500 9,000 8,500 8,000
Status Red Red Red Green

At the monthly review, investigate a missed target and agree the next action. An A3 can keep the gap, evidence, proposed response and follow-up together. Check that response at the next review.

OKRs: quarterly focus and stretch

Andy Grove developed OKRs at Intel, and John Doerr later introduced them to Google. The team records an objective and the results it will use to assess progress:

  • An objective: qualitative, directional, memorable. What do we want to achieve?
  • Three to five key results: measurable, time-bound. How will we know we got there?

The same lead-time ambition, written as one quarter's OKR for the operations team:

A few conventions matter:

  • Check the operating results alongside delivery milestones. In this example, KR3 records pull-planning rollout; KR1 and KR2 test the lead-time and delivery outcomes. Completing the rollout alone does not show those outcomes improved.
  • Distinguish committed from aspirational targets. In Google's approach, around 0.6 to 0.7 can be an expected score for an aspirational OKR. A committed target has a different expectation; agree which kind the team is setting.
  • Agree how goals relate to performance reviews. A missed aspirational target needs a different discussion from a missed committed obligation. Explain that distinction before setting the goals.
  • They're transparent. Everyone can see everyone's OKRs, which is how alignment happens without a formal cascade.

Side by side

Hoshin Kanri OKRs
Horizon 3 to 5 years, then annual Usually quarterly, sometimes annual
Focus A small number of long-term objectives A few objectives per team, per quarter
Alignment Formal cascade with catchball Transparency and linking, lighter touch
Targets Committed, expected to be met Often stretch; 70% can be success
Review Monthly, plan vs actual, countermeasures Weekly check-ins, quarterly scoring
Visual tools X-matrix, bowling chart, A3 OKR lists, scorecards
Best fit Operational transformation over years Fast-moving teams, product and growth goals
Common failure Heavy paperwork, too many priorities Task lists as key results, goals disconnected from strategy

Using both

The two fit together naturally. Hoshin sets the direction and the annual commitments, which rarely change. OKRs describe how each team will move those numbers this quarter, and can change every three months as teams learn.

In the example, the breakthrough objective and the annual targets come from Hoshin. The operations team's quarterly OKR above is how they plan to deliver their part of the 20% lead-time cut this year. The monthly bowling chart tracks the committed annual numbers; the OKR check-ins track the quarterly bets.

Mistakes that break strategy deployment

  1. Too many priorities. If everything is a breakthrough, nothing is. Three to five objectives at the top is plenty.
  2. Cascading by copy and paste. Each level should translate the target into its own terms and levers, not repeat the level above.
  3. Skipping catchball. Targets set without the people who deliver them become targets nobody believes.
  4. Key results that are task lists. Measure the change, not the activity.
  5. No review rhythm. Without a monthly or weekly check, both methods decay into annual paperwork.
  6. Linking stretch goals to pay. People will protect their bonus by setting safe targets.

For Plant A, check whether the lead-time target has an owner, the required resources and a current review of actual results. Ask the team to show which work it changed after the last review. Knowing the priorities is a starting point; delivery needs those commitments and follow-up.

Strategy needs people to change how they workKotter and ADKAR cover the human side of a transformation, from urgency to reinforcement.

Sources

The manufacturer and its targets are illustrative.

NextHow to read a control chart: common cause, special cause and the rules that matter

Discuss an operations problem

I work with operations and transformation teams on operational excellence, digital transformation programs, supply chains and industrial AI. Send me the problem you’re working on and the result you need.

Abolfazl ShirkavandImage preview unavailable