Skip to content
Hoshin Kanri | Part 1 of 8

Hoshin Kanri Is a System for Saying No

What Hoshin Kanri is, how it differs from management by objectives and OKR, and why its first effect is fewer priorities.

A plant starts the year with twenty-three priority projects. Every department has its own list. By October most projects are half done, the people in them are exhausted, and the three topics that really mattered to the business are among the half-finished ones.

Hoshin Kanri, often translated as policy deployment or strategy deployment, addresses exactly this pattern. Its first effect is not more alignment. It is fewer priorities.

Three ideas behind the method

Few breakthrough objectives. Three to five changes that move the business, each one large enough to need several departments. Everything else is either daily management or stops.

Deployment through dialog. Objectives travel down the organization as a proposal. Each level answers with how it will contribute, what it needs and what it cannot do. The targets are agreed, not dictated.

A monthly rhythm with countermeasures. Progress is reviewed every month against a plan. A red value triggers analysis and a countermeasure, not an explanation.

How it differs from other approaches

Management by objectives assigns individual targets, usually linked to pay. It optimizes each person’s number, often at the expense of the neighbor.

OKR, objectives and key results, works in quarterly cycles with ambitious goals and frequent check-ins. It is lighter and faster to start, and many teams use it successfully. Hoshin Kanri adds a longer horizon, a stronger link between strategy and daily management, and an explicit process for negotiating capacity between levels.

Neither replaces daily management. Keeping the current standard, safety, quality, delivery and cost, runs in the daily and weekly routines. Hoshin is for the few things that must change.

The cost of focus

Saying yes to five breakthroughs means saying no to many good ideas. That is the hard part, and it happens at the top. If the leadership team cannot agree on what stops, the method produces a nicer list of the same twenty-three projects.

A practical test: for each proposed objective, name the project or activity that will be stopped or slowed to make room. If nobody can, the objective is not yet a priority.

Where to start

Start with one site or one business unit and one annual cycle. Use paper or a simple workbook before any software. The value lies in the conversations: between the leadership team when choosing, between levels when deploying, and between owners and reviewers every month.

The remaining parts of this series walk through those conversations, from the long-term direction to the reflection at the end of the year.

Newsletter

One Lean idea.
Every two weeks.