Hoshin Kanri does not end when the annual plan is approved.

A Hoshin review cadence is the recurring management routine used to compare strategic expectations with actual results, understand gaps, and adjust countermeasures.

Without a review cycle, strategy deployment can become a static document.

Review strategy through PDCA

Hoshin Kanri connects long-term direction with annual breakthrough priorities and execution.

The review cadence applies PDCA to that deployment.

Ask:

  • What did we expect by now?
  • What actually happened?
  • Which assumptions were wrong?
  • Which countermeasures are working?
  • What needs support or escalation?
  • What should change next?

The purpose is learning, not explaining away missed targets.

Review outcomes, not only activity

A project can be on schedule while the strategic result remains unchanged.

Avoid reviewing only:

  • task completion;
  • meeting attendance;
  • project milestones;
  • number of workshops.

Instead, connect activity to outcome measures.

If the strategy is to reduce customer lead time, the review should show whether lead time is actually changing.

Keep the breakthrough priorities visible

An X-Matrix can show how long-term direction, annual priorities, measures, initiatives, and ownership connect.

The review should use that alignment rather than create a separate reporting system.

When an initiative no longer supports the strategic priority, the organization should challenge it.

Use Obeya for cross-functional visibility

An Obeya can provide a shared visual environment for strategic review.

It can make visible:

  • target versus actual;
  • major countermeasures;
  • risks;
  • dependencies;
  • unresolved decisions;
  • ownership.

The room or digital environment should support decisions, not presentations.

Escalate barriers

Strategic work often requires resources or decisions that one team cannot provide.

The review cadence should identify:

  • blocked decisions;
  • resource conflicts;
  • cross-functional barriers;
  • changes in assumptions;
  • emerging risks.

Leadership should remove barriers while leaving problem ownership as close to the work as practical.

Use Catchball when assumptions change

Catchball is useful when objectives, feasibility, resources, or dependencies need renewed alignment.

Strategy deployment is not one-way communication.

The dialogue may need to continue during execution.

Common mistakes

Reviewing too many metrics, using the meeting to defend performance, allowing overdue actions to accumulate, changing priorities too frequently, and focusing on project completion instead of strategic outcomes are common mistakes.

Practical sequence

  1. define the strategic measures.
  2. establish a regular review cadence.
  3. compare expected and actual results.
  4. identify the most important gaps.
  5. review current countermeasures.
  6. surface risks and dependencies.
  7. escalate barriers.
  8. adjust actions based on evidence.
  9. confirm ownership.
  10. capture learning for the next planning cycle.

The practical lesson

Hoshin deployment becomes real through repeated review.

The strategy should remain a living management process until the result is achieved or the evidence shows the plan must change.

This topic also connects with Improvement Portfolio Management. Use that method when the improvement requires the related operating or management discipline.