Hoshin Kanri review cycles apply plan-do-check-act thinking at monthly and quarterly intervals to catch drift between the X-matrix and actual performance while it is still cheap to correct. Monthly and quarterly reviews using the PDCA cycle inspect progress and adjust plans, which is what separates Hoshin Kanri from a strategic plan that gets built in January and revisited in December, by which point a full year of drift has already accumulated.
Review is not a reporting exercise. It is the check phase of plan-do-check-act applied at the organizational level, and its purpose is the same purpose PDCA serves at the project level: surface a gap between plan and actual early enough that a correction is still cheap, rather than late enough that the year's breakthrough objectives are already unreachable.
This guide covers what each review level checks, how monthly and quarterly cadences differ in scope and attendance, how to keep a review cadence from lapsing under production pressure, and how the annual review closes one Hoshin Kanri cycle and opens the next.
What Hoshin Kanri Review Cycles Check
A Hoshin Kanri review cycle checks two distinct things at every interval: whether the metrics on the bowling chart are tracking to target, and whether the improvement priorities feeding those metrics are actually progressing as planned. These are related but separate questions, and conflating them produces a review that catches missed numbers without ever identifying why they were missed.
Metric Performance Against Target
The bowling chart, tracking the specific targets set in the X-matrix's east quadrant, is the primary artifact for this half of the review. A metric tracking below target is a signal to investigate, not a verdict on the objective itself, since the same shortfall can trace back to a delayed project, an underresourced priority, or a target that was set unrealistically during the original catchball rounds.
Improvement Priority Progress
The second half of the review checks whether the specific projects in the X-matrix's north quadrant are progressing on schedule, since a metric shortfall traced back to a stalled project points to a completely different corrective action than one traced back to an achievable-but-slow initiative.
Key Insight: Hoshin Kanri review checks both whether metrics are hitting target and whether the projects behind them are progressing, since the two questions require different corrective actions.
Monthly Review: Scope and Attendance
The monthly review is the tighter, more operational of the two cadences, focused on catching drift before it compounds across a full quarter.
What Gets Reviewed Monthly
Monthly review typically covers the bowling chart in full detail, project status for every improvement priority currently active, and any newly surfaced obstacles that need escalation before the next quarterly cycle. This is the review level closest to daily management, and in mature implementations it happens inside the same [Obeya Room in Manufacturing: Visual Strategy Management for Cross-Functional Teams] used for daily and weekly management routines.
Who Attends the Monthly Review
Attendance is typically limited to the project owners named in the X-matrix's east quadrant and the department or plant leadership accountable for the annual objectives those projects support. A monthly review that expands attendance beyond the people directly accountable for the numbers on the wall tends to drift toward status theater rather than genuine problem-solving, since the incentive to surface real obstacles honestly weakens as the audience grows.
Key Insight: Monthly review stays tight in both scope and attendance, focused on the people directly accountable for the metrics and projects being examined.
Quarterly Review: Scope and Attendance
The quarterly review steps back from individual project status to ask whether the annual objectives themselves remain on track and whether the strategic assumptions behind them still hold.
What Gets Reviewed Quarterly
Quarterly review examines the trend across three months of bowling chart data rather than a single month's snapshot, checks whether annual objectives are still realistically achievable given the pace of progress so far, and assesses whether external conditions have shifted enough to warrant revising the objectives themselves rather than simply pushing harder on the current plan.
Who Attends the Quarterly Review
This session widens to include the executive sponsors of each breakthrough objective alongside the department leadership who attends monthly review, since a decision to revise an annual objective requires the same level of authority that originally set it through catchball.
Key Insight: Quarterly review widens both its time horizon and its attendance to include the authority needed to revise objectives, not just track them.
Keeping the Review Cadence From Lapsing
The single most common failure in Hoshin Kanri implementation is not a poorly built X-matrix. It is a review cadence that starts strong and quietly lapses under production pressure within the first two or three cycles.
Protecting the Calendar Slot
Monthly and quarterly reviews of hoshin progress are treated as non-negotiable in mature implementations, scheduled with the same fixed calendar priority as a safety audit rather than as a meeting that gets rescheduled whenever a production crisis competes for the same time slot. Once a review gets skipped once without consequence, skipping becomes the default under pressure.
Making Skipped Reviews Visible
Tracking review completion itself as a metric, whether the monthly and quarterly sessions actually happened on schedule, gives leadership a leading indicator of Hoshin Kanri health that surfaces before the bowling chart itself starts showing missed targets.
Key Insight: Protecting the review calendar slot and tracking whether reviews actually happen are what prevent the cadence from lapsing under production pressure.
The Annual Review and Cycle Closure
The annual review closes one full Hoshin Kanri cycle and opens the next, and it carries a different purpose than the monthly and quarterly checkpoints that precede it throughout the year.
Assessing the Full Year
The annual review evaluates performance against every annual objective set at the start of the cycle, captures what was learned about the organization's actual capacity and execution speed, and feeds that learning directly into the following year's breakthrough objective and annual objective development.
Starting the Next Cycle
Carrying learning forward. The single biggest waste in an annual review is treating it purely as a scorecard rather than as the input for the next planning cycle. Objectives missed for structural reasons, chronic underresourcing or an unrealistic original target, should directly shape how the next cycle's catchball rounds are conducted, not simply get restated as next year's goal with the same underlying gap unaddressed.
Key Insight: The annual review closes the current cycle and directly seeds the next one, and skipping the structural learning step repeats the same gaps year over year.
Within the Lean System
Connection to Lean Principles
The review cadence operationalizes the lean principle of continuous improvement at the strategic level, treating the annual plan as a living hypothesis to be checked and corrected rather than a fixed document. This is the mechanism that keeps [Hoshin Kanri: The 7-Step Strategy Deployment Process for Manufacturing] from collapsing into a once-a-year planning exercise.
Connection to Lean Tools
The bowling chart and X-matrix reviewed at each cadence are built through the process covered in [How to Build an X-Matrix: Step-by-Step Hoshin Kanri Guide], and monthly reviews commonly happen inside the same [Obeya Room in Manufacturing: Visual Strategy Management for Cross-Functional Teams] used for daily management, keeping strategic and operational review pointed at the same shared visuals.
Connection to Continuous Improvement
Hoshin Kanri review is a long-cycle plan-do-check-act applied at the organizational level, running in parallel with the short-cycle [PDCA Cycle: The Foundation of Continuous Improvement] that governs individual improvement projects. When a quarterly review reveals an annual objective needs revision, that revision typically runs back through the same [Catchball Process: How Hoshin Kanri Aligns Strategy Across Teams] used to set it originally, rather than being imposed unilaterally.
Frequently Asked Questions
Q: How often should Hoshin Kanri be reviewed?
Monthly for operational drift on the bowling chart and active project status, quarterly for whether annual objectives remain realistically achievable given the pace of progress so far, and annually to formally close the current cycle and feed structural learning directly into the following year's planning process.
Q: What is the difference between monthly and quarterly Hoshin Kanri review?
Monthly review checks the current month's metrics and project status in detail with a tight group of directly accountable owners. Quarterly review steps back to assess a full quarter's trend line and whether annual objectives themselves genuinely need revision, widening attendance to include the relevant executive sponsors as well.
Q: Why do Hoshin Kanri review cadences lapse over time?
Reviews compete directly with production crises for the same calendar slot and get skipped without visible consequence the first few times real pressure hits. Once skipping becomes the accepted default, the cadence erodes quickly, which is exactly why mature implementations treat review scheduling as genuinely non-negotiable.
Q: What happens during the annual Hoshin Kanri review?
The annual review assesses performance against every objective set during the completed cycle, captures what was actually learned about the organization's execution capacity, and feeds that learning directly into the next cycle's breakthrough and annual objective development, rather than functioning purely as a static scorecard.
Q: Where should Hoshin Kanri reviews take place?
Monthly reviews commonly happen inside the obeya room already used for daily management routines, keeping strategic and operational review pointed at the same shared visuals. Quarterly and annual reviews may involve a wider group but should still reference that same bowling chart and X-matrix directly, not a separate deck.
LeanSuite: A complete lean manufacturing software
Schedule Demo
