Strategy Deployment SoftwareTurn breakthrough goals into daily priorities

Hoshin kanri vs OKRs

Hoshin kanri is the lean approach to strategy deployment. The Lean Enterprise Institute also calls it policy deployment.

OKRs, or objectives and key results, set a few objectives with measurable results. They usually run on a quarterly cycle.

Both aim for focus and alignment. Hoshin kanri ties goals more tightly to daily management and to long-term breakthroughs. The table below compares them.

The X-matrix in one paragraph

The X-matrix is the one-page plan of hoshin kanri. Its four sides hold long-term breakthrough objectives, this year's objectives, the priority projects and the metrics. Dots in the corners show which items support each other.

The X-matrix guide shows how to build one step by step, and the hoshin kanri page covers the full method.

Bowling charts and monthly reviews

A bowling chart lists each metric with its monthly target and actual result, colored red or green. It makes a miss visible within a month, not at year end.

Each red month needs a countermeasure, often worked through with PDCA or an A3. Monthly reviews keep the plan in use. A plan reviewed only once a year becomes a static document.

Linking strategy to daily work

Strategy deployment works when yearly objectives show up on team boards. Daily management software can carry those measures to the floor.

For portfolios of software and product work, lean portfolio management software links funding to the same priorities. The lean management guide covers the wider system.

Common failure modes

The first is setting too many breakthrough objectives. When everything is a priority, focus disappears.

The second is skipping catchball. Targets set without discussion get compliance rather than commitment.

The third is reviews that only report status. A review should end with countermeasures for every miss.