Back to BlogOperational Excellence

    What Is Hoshin Kanri? Meaning and the 7-Step Planning Process

    By , CEO and founder, TeamAssurancePublished Last updated

    What Is Hoshin Kanri? Meaning and the 7-Step Planning Process

    Hoshin kanri is a lean strategic planning method that focuses an organisation on three to five breakthrough objectives and aligns every level behind them, from the leadership team to the daily work of frontline teams. Each level agrees its part through "catchball", and progress is reviewed every month through PDCA cycles until the next annual plan.

    At a glance

    • Meaning: "hoshin" means direction or compass and "kanri" means management, so it is often translated as policy deployment or direction management.
    • Origin: Japanese industry in the 1960s, building on Deming's PDCA and management by objectives, later adopted by Toyota and lean organisations worldwide.
    • Cadence: a three to five year vision, an annual plan, monthly reviews and a year-end reflection (hansei).
    • Planning process: 7 steps, from vision to breakthrough objectives, annual objectives, catchball, execution, monthly review and reflection.
    • Main tools: catchball, the X-matrix, A3 reports and bowling charts.
    • Quick reference: the short glossary definition of the term.

    Originally written by Paul Dunlop. Updated in October 2026 by the TeamAssurance team with the 7-step process and how it connects to tiered daily management, and in November 2026 with key facts, sources and a step-by-step guide to the planning process and its yearly calendar.

    What does hoshin kanri mean?

    Hoshin kanri means "direction management": the term is often translated as "policy deployment". The image behind the name is a compass needle: everyone in the organisation pointing the same way. The method emerged in Japanese industry in the 1960s, building on Deming's PDCA cycle and management by objectives, and was adopted by Toyota and later by lean organisations around the world.

    Three ideas set it apart from ordinary annual planning:

    • Focus on the vital few. A hoshin plan has three to five breakthrough objectives, not a long wish list. Everything else is managed through daily management.
    • Plans are built with people, not handed to them. Through catchball, each level proposes how it will contribute and the level above responds, until targets and the means to reach them are agreed.
    • The plan itself runs on PDCA. Progress is checked every month, gaps trigger countermeasures, and an annual reflection feeds the next year's plan.

    A strategy acts as the rudder of the ship: it keeps the organisation on course as conditions change. The hoshin kanri method is how you make sure the whole crew is steering by the same rudder.

    Many organisations summarise the whole plan on one page in an X-matrix, which links long-term strategic goals to annual objectives, improvement priorities, measures and owners.

    The X-matrix shows on one page how each long-term goal turns into this year's work and measures.

    What is the hoshin kanri planning process?

    The hoshin kanri planning process is a 7-step annual cycle that turns a three to five year vision into this year's work. Leaders pick three to five breakthrough objectives, set annual targets, agree them with each level through catchball, then execute, review progress monthly and reflect at year end before planning again.

    The 7 steps of hoshin kanri are: set the long-term vision, pick three to five breakthrough objectives, set this year's objectives, deploy them through catchball, execute, review monthly and reflect at year end. Steps 1 to 4 are the planning phase (Plan), step 5 is Do, and steps 6 and 7 are Check and Act.

    StepWho leads itWhat it produces
    1. Set the long-term visionLeadership teamA three to five year vision statement
    2. Pick 3–5 breakthrough objectivesLeadership teamBreakthrough objectives with long-term measures
    3. Set this year's objectivesLeadership team with department headsAnnual objectives, each with a measure, target and owner
    4. Deploy through catchballEvery level, top to frontlineAgreed improvement priorities, often summarised in an X-matrix
    5. ExecuteOwners and their teamsProjects, A3s and actions tracked in tier meetings
    6. Review monthlyLeaders and goal ownersStatus, trend and countermeasures for goals off track
    7. Reflect annually (hansei)Leadership teamLessons learned that feed next year's plan

    Step 1: Set the long-term vision

    Agree where the organisation must be in three to five years. Keep it concrete enough to test decisions against, for example "the most reliable supplier in our category" rather than "world class".

    Step 2: Pick 3–5 breakthrough objectives

    Choose the few strategic objectives that would transform performance if achieved, such as halving the cost of poor quality or reaching zero lost-time injuries. If an objective can be reached by doing the same things a little better, it belongs in daily management, not in the hoshin plan.

    Step 3: Set this year's objectives

    Decide what must be true by the end of this year to stay on track for each breakthrough objective. Each annual objective needs a measure, a target and an owner.

    Step 4: Deploy through catchball

    Each level of the organisation takes the objectives from the level above and proposes how it will contribute: the improvement priorities, the measures and the resources it needs. The level above responds, and the ball goes back and forth until both agree. Catchball is where commitment is built, and it draws on the consensus-building practice of nemawashi. It is also where unrealistic plans are caught before they fail.

    Step 5: Execute

    Improvement priorities become projects, A3 problem solving and an action plan with owners and dates. The key is to track them where work is already managed, in the daily and weekly tier meetings, rather than in a separate strategy spreadsheet that nobody opens.

    Step 6: Review monthly

    Leaders review each objective against its target, usually with a simple green, amber or red status and a trend, often on a bowling chart. When a goal is off track, the owner brings the cause and a countermeasure, not just a status update.

    Step 7: Reflect annually (hansei)

    At year end, reflect honestly on what worked, what didn't and why. Those lessons are the first input to next year's step 1, so the planning process improves through the same PDCA loop as the work itself.

    What does the hoshin planning process look like in practice?

    In practice, one breakthrough objective is broken down level by level until a frontline team can see it on its board. Here is an illustrative example from a food manufacturer:

    1. Vision: be the most reliable supplier to our retail customers within three years.
    2. Breakthrough objective: halve the cost of poor quality by the end of year three.
    3. This year's objective: cut customer complaints by a third, owned by the operations manager.
    4. Catchball: the packing department proposes fixing labelling errors, its biggest source of complaints, and asks for time to run an A3. The site leadership team agrees and adjusts the target.
    5. Execute: the packing line team tracks label defects per shift on its Tier 1 board and works through the A3 countermeasures.
    6. Review: the monthly hoshin review shows the measure trending to target, so no extra resources are needed.
    7. Reflect: at year end the team notes that complaints fell fastest where operators owned the A3, and builds that into next year's plan.

    When does the hoshin planning cycle happen during the year?

    Hoshin planning usually starts about three months before the new financial year, so catchball is finished and objectives are agreed before the year begins. A typical calendar looks like this:

    TimingActivitySteps
    3 months before year startReflect on the current year and confirm the vision7 and 1
    2–3 months beforeChoose breakthrough objectives and draft annual objectives2 and 3
    1–2 months beforeRun catchball and finish the X-matrix4
    Every month of the yearExecute through tier meetings and hold the monthly hoshin review5 and 6
    Final quarterYear-end reflection (hansei), which starts the next cycle7

    For an Australian organisation on a July to June financial year, that means planning from about April, with catchball finished in May and June. For a calendar year, planning runs from October to December.

    How does hoshin kanri connect to tiered daily management?

    Hoshin kanri connects to tiered daily management by running each breakthrough priority through the same daily and weekly tier meetings that run the business. Most hoshin plans fail in the gap between the annual plan and the shift floor. The objectives are clear in the boardroom, but on Tuesday morning a line team is fighting the same breakdowns as always and can't see how their work connects to the strategy.

    The method was never meant to replace daily management. It depends on it. The breakthrough work runs through the same tiered daily management structure that runs the business every day:

    • Tier 1 (daily, 5–10 minutes, frontline team). The team's hoshin-linked measure, such as label defects per shift, sits on the tier board next to safety and output. New problems are raised and owned the same day.
    • Tier 2 (daily, 15–20 minutes, supervisors). Unresolved Tier 1 issues are escalated, and actions from the A3s behind each priority are checked for progress.
    • Tier 3 (weekly, 30–45 minutes, site leaders). Trends are reviewed and resources are moved to where a goal is at risk.
    • Monthly hoshin review. Goal status comes from the same data the teams discuss every day, so there is no separate strategy report to compile.

    This is what "linking the top to the bottom" means in practice. Strategy travels down through catchball; results, problems and ideas travel back up through the tiers. Each loop runs on plan do check act (PDCA), and each one makes the other more reliable.

    What is the difference between hoshin kanri, OKRs and a balanced scorecard?

    Hoshin kanri deploys a few multi-year breakthrough objectives through catchball and monthly PDCA reviews, OKRs set ambitious objectives with measurable key results on a quarterly cycle, and a balanced scorecard measures strategy across four perspectives.

    Hoshin kanriOKRsBalanced scorecard
    Core ideaDeploy a few breakthrough objectives to every level and review them through PDCASet ambitious objectives with measurable key resultsMeasure strategy across financial, customer, internal process and learning perspectives
    Time horizon3–5 year vision, annual objectives, monthly reviewsUsually quarterlyAnnual, with periodic reviews
    How goals are setCatchball between levelsMix of top-down and team-proposedMostly top-down, often with strategy maps
    Link to daily workStrong: priorities run through A3s and tier meetingsVaries by organisationIndirect, through measures
    Best suited toOperations-heavy organisations running leanFast-moving teams wanting focus and transparencyLeadership teams wanting a balanced view of performance

    The approaches can be combined. Many operations use hoshin for site and department strategy and a balanced set of measures on their tier boards. Hoshin is also the best-known lean form of strategy deployment, the broader term for any structured way of turning strategy into aligned work.

    What are the most common hoshin planning mistakes?

    The most common mistakes are chasing too many objectives, cascading targets without real catchball, loading routine KPIs into the plan, never reviewing it and failing to link it to daily work.

    1. Too many objectives. When everything is a priority, nothing gets real resources. Hold the line at three to five.
    2. Top-down cascading without genuine catchball. Targets that are imposed rather than negotiated get compliance, not commitment.
    3. Loading routine KPIs into the hoshin plan. Keeping the lights on belongs in daily management. Hoshin is for breakthrough change.
    4. Setting the plan and never reviewing it. A plan that isn't reviewed monthly with real data is a poster, not a plan.
    5. No link to daily work. If frontline teams can't see a hoshin-linked measure on their board, the strategy hasn't been deployed, only announced.

    How does TeamAssurance support hoshin planning?

    TeamAssurance's Strategy Deployment capability lets you create goals with clear owners and dates and cascade them in a tree view, so each goal contributes to its parent. Goals can be linked to A3 reports, improvement activities and measures, and a monthly status history highlights goals at risk. Because strategic tasks are tracked through tiered daily management alongside the day-to-day, teams improve the business while running the business.

    Frequently Asked Questions

    What is hoshin kanri?

    Hoshin kanri is a lean strategic planning method, developed in Japan, that focuses an organisation on three to five breakthrough objectives. It deploys them to every level through catchball, links them to daily work through projects, A3s and tier meetings, and reviews progress monthly using PDCA.

    What does hoshin kanri mean?

    "Hoshin" means direction or compass and "kanri" means management or control. The name is often translated as policy deployment or direction management.

    What is the hoshin kanri planning process?

    It is a 7-step annual cycle: set a long-term vision, choose three to five breakthrough objectives, set this year's objectives, agree them with each level through catchball, execute, review monthly and reflect at year end. The reflection feeds the next year's plan.

    When should hoshin planning start?

    Start about three months before the new financial year, so the year-end reflection, objective setting and catchball are finished before the year begins. Monthly reviews then run throughout the year.

    How do you implement hoshin kanri?

    Follow the 7 steps: set a 3–5 year vision, choose 3–5 breakthrough objectives, set annual objectives, deploy them through catchball, execute through projects and A3s tracked in tier meetings, review monthly, and reflect at year end. Start with one site or division for the first cycle.

    What is catchball?

    Catchball is the negotiation between management levels during planning. One level proposes objectives and means, the next responds with what it can deliver and what it needs, and the exchange continues until both agree.

    What is the difference between hoshin kanri and OKRs?

    Both align teams around a small set of goals. Hoshin adds a long-term vision, catchball, a close link to lean problem solving and a monthly PDCA review, while OKRs usually run on quarterly cycles with ambitious key results.

    How long does a hoshin cycle take?

    The main cycle is annual, with monthly reviews in between. Breakthrough objectives usually look three to five years ahead, so most organisations see the full benefit after two or three cycles.

    Sources

    • Yoji Akao (ed.), Hoshin Kanri: Policy Deployment for Successful TQM, Productivity Press, 1991.
    • Thomas L. Jackson, Hoshin Kanri for the Lean Enterprise, Productivity Press, 2006.
    • Pascal Dennis, Getting the Right Things Done: A Leader's Guide to Planning and Execution, Lean Enterprise Institute, 2006.

    Want to see how TeamAssurance connects hoshin goals to daily tier meetings? Book a demo.

    About the author

    Matt Mafrici

    CEO and founder, TeamAssurance

    Operations and continuous improvement practitioner; builds daily management systems with manufacturers, miners, food and pharmaceutical producers in Australia and abroad.

    LinkedIn profile · All articles