Hoshin kanri is often described as PDCA applied to strategy. That’s true, but it’s not one cycle. It’s several, running at different speeds and levels, and the plan works only when each level’s act step becomes the next level’s plan.
In this guide
Key Takeaways
- →Hoshin is not one PDCA cycle. It is four, nested, running at different speeds.
- →Each level’s act step is another level’s plan. That handover is the whole mechanism.
- →Annual planning starts with check, not plan. Reflect, act on the lessons, then plan.
- →A review that notes the reds and moves on is PDC, not PDCA.
- →With no quarterly cycle, a losing bet runs the whole year.
- →Cycles in separate tools cannot hand over, so neither act step reaches the other.
Where PDCA comes from
The plan, do, check, act cycle traces back to Walter Shewhart’s work on quality control and was popularized by W. Edwards Deming, who later preferred “study” to “check” to emphasize learning over inspection. Japanese quality management built it into daily work, and hoshin kanri applied it to strategy.
Its planning-side relatives, the seven classical tools, are covered in The Seven Management and Planning Tools in Hoshin Kanri.
Four cycles, four speeds
| Cycle | Plan | Do | Check | Act |
|---|---|---|---|---|
| Annual | Breakthroughs and X-matrix | Run the year | Reflection on every correlation | Next year’s plan |
| Quarterly | The current set of bets | Three months of execution | A3 findings, outcome lag, kill signals | Regrade, retire, retarget |
| Monthly | Phased plan values | The month’s work | Bowler and four-quadrant review | Countermeasures, A3s |
| Weekly or team | Key results and tasks | The work itself | Team check-ins | Adjust the next week |
The cycles are nested. The monthly act step (a countermeasure) changes what teams do next week. The quarterly act step (a retired priority) changes the monthly plan. The annual act step changes everything.
The monthly row has two tools behind it: Bowler Chart Template for Hoshin Kanri: Structure, Formulas, Colors and The Four-Quadrant Chart: Plotting KPIs Against Initiatives in Hoshin Kanri.
Starting with check
Hoshin practitioners often describe annual planning as starting with check rather than plan: reflect on what happened, act on the lessons, then plan. The sequence is sometimes written CAP-Do. It’s the logic behind the reflection that opens the planning cycle; see Hansei: Reviewing Last Year’s X-Matrix Before Planning the Next.
A plan that starts with plan has nothing to learn from. A plan that starts with check begins with evidence.
Where the cycles break
- Monthly check without act. Reviews note the reds and move on. The cycle is PDC.
- Quarterly cycle missing. The plan changes only annually, so a losing bet runs all year.
- Cycles not connected. Team cycles run on OKRs in one tool, the monthly cycle on a bowler in another, and neither’s act step reaches the other.
The first failure has a format fix: an agenda that ends in a decision log rather than a status walk. See Hoshin Kanri Review Templates: Monthly and Quarterly Formats.
A worked example: one issue through three cycles
| Cycle | What happened |
|---|---|
| Weekly (service sales team) | Check-in shows attach rate stuck in two territories; team adjusts call scripts |
| Monthly | Bowler red for the second month; countermeasure (retraining) failed; A3 assigned |
| Quarterly | A3 finds routing cause; priority’s measure changed; correlation kept |
| Annual | Reflection records the lesson: measure network priorities by calls served locally |
Illustrative.
Each cycle handled the part of the problem it could. The team couldn’t change routing; the monthly review couldn’t change the measure; the quarterly review could. The annual cycle made sure the lesson outlived the year.
Profit.co runs PDCA cycles alongside monthly and quarterly huddles, with team key results contributing to hoshin objectives, so the act step at one level reaches the plan at the next. The countermeasure A3 is a PDCA cycle in its own right: its phase moves from Plan to Do, Check and Act, and its Act decisions on correlations are written to each correlation’s strength history. More on the Hoshin Kanri software page.
What a disconnected cycle costs
The third failure above is the expensive one, and it is almost always a tooling artifact rather than a discipline problem. Team cycles live in whatever the teams use; the monthly cycle lives in the bowler workbook; the quarterly lives in a slide pack. Each runs competently. None of them hands over.
Trace the worked example through a disconnected setup and the arithmetic is visible. The weekly team adjusts scripts, which nobody at the monthly sees. The monthly assigns an A3, which the quarterly reads as a summary line. The quarterly changes the measure, which the teams learn about in the next planning season. The same issue takes a year instead of a quarter, and the annual reflection has no record of why.
Among published alternatives, OnStrategy lists $200 per month for unlimited users. i-nexus publishes a free Starter tier for up to five users and $28 per user per month at its Standard tier. The seat model is the deciding factor for the weekly row specifically, since team cycles involve the most people and are the first thing a per-seat budget cuts.
Profit.co publishes two plans, Essentials and Enterprise, quoting against modules and scale rather than a public seat rate. Hoshin Kanri sits in Essentials alongside OKRs and Goals, Balanced Scorecard and Strategy Roadmap, which is what lets the weekly and monthly cycles share a data model instead of two tools. Hoshin Kanri and OKRs on One Platform: Where Each Belongs covers that boundary, What drives the cost of hoshin kanri software lists the rest to total, and the 30-day free trial spans a monthly cycle and the weekly cycles inside it.
Free Product Demo
Connect your PDCA cycles
A 30-minute walkthrough, tailored to your team.
Book a free demo
What happens in the call
How your teams set goals, track progress and review results.
Strategy, performance, projects and engagement on one platform, with AI.
A practical path to align teams, execute faster and drive results.
Questions this article answers
As nested cycles: annual for the plan and breakthroughs, quarterly for changing bets, monthly for tracking and countermeasures, and weekly for team work, each feeding the others.
A way of describing annual planning that starts with check and act, reflecting on last year and acting on lessons, before making the new plan.
Deming preferred “study” to “check” to emphasize learning from results rather than inspecting them. The cycle is otherwise the same.
The plan can only change annually, so a bet that is clearly losing by March still runs until December. The quarterly cycle is where priorities get retired, correlations regraded and targets reopened.
A monthly review that notes which rows are red and moves on. Checking without acting is the most common way the cycle breaks, and it looks like diligence.
Through the act step. A monthly countermeasure changes what teams do next week; a quarterly retirement changes the monthly plan; the annual act step changes the matrix itself.
