Hoshin Kanri Planning: Annual Cycle, X-Matrix and a Worked Example
8 min read ยท 2026-10-25
Hoshin kanri planning is a strategy method that picks a few breakthrough objectives, turns them into yearly goals and improvement priorities, and deploys them level by level so every team knows which work supports them. Progress is checked monthly and the whole plan is reviewed once a year, following the plan, do, check, act cycle. The name is often translated as policy deployment.
The guide below lays out one full annual cycle in seven phases, from the vision to the annual reflection. It is written for the people who usually run it: the COO, a strategy or transformation lead, a PMO lead or an operational excellence manager, working with the leadership team and department heads. It explains how to build the X-matrix step by step, how catchball works in practice, a filled-in example, who owns what, how to run monthly reviews and how to present the plan.
The roadmap at a glance
Goal: By the end of the year, three breakthrough objectives are deployed to every department, each improvement priority has an owner and a monthly measure, and the annual reflection sets the next cycle. Duration: 12 months (one annual cycle)
Vision and situation review (Weeks 1-3)
Agree where the company must be in three to five years and where it stands today.
- Review last year's results, customer feedback, market changes and internal capability.
- Restate the vision and mission so every leader can explain them in one sentence.
- List the gaps between today and the vision.
- Collect input from department heads before the leadership offsite.
Milestone: A one-page situation review and vision statement approved by the leadership team.
Breakthrough and annual objectives (Weeks 3-5)
Choose the few changes that matter most and set this year's targets.
- Pick three to five breakthrough objectives for the next three to five years.
- For each, set one or two annual objectives that move it forward this year.
- Choose the metrics that show progress, with a baseline and a target.
- Cut or defer everything else that competes for the same people.
Milestone: Three to five breakthrough objectives and their annual objectives approved, with a written list of what the company will stop or defer.
Build the X-matrix (Weeks 5-7)
Put objectives, priorities, metrics and owners on one page and check how they connect.
- Write breakthrough objectives, annual objectives, improvement priorities and metrics in their sections of the matrix.
- Mark correlations between each pair of sections in the corner grids.
- Assign an accountable owner and supporting team for each improvement priority.
- Check for priorities that support no objective and objectives with no priority.
Milestone: A draft X-matrix where every annual objective links to at least one priority and every priority has an owner.
Catchball (Weeks 7-10)
Test the plan with the people who will deliver it and adjust it before it is final.
- Share the draft with department heads and ask what it would take to deliver each priority.
- Collect their feedback on targets, resources and conflicts.
- Adjust targets, priorities or owners, and send the revised draft back.
- Repeat until each department head agrees to their part.
Milestone: Every department head has agreed in writing to the priorities and targets they own.
Deploy to departments and teams (Weeks 10-13)
Turn top-level priorities into team plans with their own measures.
- Each department builds its own matrix or action plan linked to the top-level priorities.
- Teams write their projects and actions with owners, dates and measures.
- Set up bowling charts showing monthly targets and actuals for each measure.
- Publish the plan and explain it at an all-hands or department meetings.
Milestone: Every department has a linked plan, and every measure has a bowling chart with monthly targets.
Execute and review monthly (Months 4-11)
Track progress every month and fix gaps fast.
- Owners update bowling charts before each monthly review.
- Hold a monthly review at each level, focused on measures that are off target.
- Write a short countermeasure for each measure that is off target, with an owner and date.
- Escalate issues that a department cannot solve alone to the leadership review.
Milestone: Monthly reviews held at every level, with a countermeasure recorded for every measure that missed its target.
Annual reflection (Month 12)
Learn from the year and feed the next cycle.
- Compare results with targets for every objective and priority.
- Ask what worked, what did not and why, using the countermeasure history.
- Decide which breakthrough objectives continue, change or close.
- Start the next cycle's situation review with these findings.
Milestone: An annual reflection report approved by the leadership team, and the next cycle's planning dates set.
How the X-matrix works
The X-matrix puts the whole plan on one page. In the most common layout, a large X divides the center into four sections. The bottom holds breakthrough objectives. The left holds annual objectives. The top holds improvement priorities, the projects that will deliver the annual objectives. The right holds the metrics and targets. A column on the far right lists owners and team members for each priority.
The small grids in the corners show how strongly each item links to the items in the next section, often with a filled dot for a strong link and an open dot for a weaker one. These grids are the point of the method. They reveal priorities that support nothing, objectives nobody is working on and people who own too much.
You can build it in Excel with a square of cells rotated in your head, or more simply in PowerPoint or Google Slides with a central square divided by two diagonal lines and four text areas around it. Many teams start with a plain table version, one row per priority with its objective, metric and owner, then move to the matrix once the links are clear.
Catchball in practice
Catchball is the back-and-forth that turns a top-down plan into an agreed one. Leaders throw the draft priorities to the next level. That level throws back what it can deliver, what it needs and what conflicts. The draft goes back and forth until both sides agree.
Run it as a structured process, not as a series of hallway chats. Send the draft with three questions: which priorities can you deliver with your current people, what would you need for the rest, and what would you stop to make room. Set a deadline for answers and a meeting to settle them. Record changes so people see their input was used.
Example: a manufacturer's hoshin plan
Picture a manufacturer of industrial equipment with three plants. Customers complain about late deliveries, and margins are falling. The leadership team runs its first hoshin cycle.
Each priority has one accountable owner and one monthly measure. The COO chairs the monthly leadership review.
- Breakthrough objective 1, Become the most reliable supplier in our market. Annual objective: raise on-time delivery to a set target. Priority: deploy a new sales and operations planning process. Owner: supply chain director. Measure: on-time delivery by plant.
- Breakthrough objective 2, Grow margin through operational excellence. Annual objective: cut scrap at the two worst lines. Priority: run structured problem solving on the top defect causes. Owner: operations excellence manager. Measure: scrap rate per line.
- Breakthrough objective 3, Build a service business. Annual objective: launch a maintenance contract offer in one region. Priority: define the offer and train the field team. Owner: head of service. Measure: contracts signed per month.
- What was stopped: a planned ERP module and a new product variant were moved to next year to free engineering and IT time.
Who owns what
Hoshin kanri fails when it becomes a strategy team's document instead of the leadership team's operating rhythm. Make roles visible in the X-matrix and in the review calendar.
Keep the number of priorities per owner small. Someone who owns five improvement priorities on top of their day job will deliver none of them well.
- CEO and leadership team: set breakthrough objectives, approve the X-matrix and chair the annual reflection.
- COO or strategy lead: owns the planning cycle, the calendar and the monthly leadership review.
- Hoshin facilitator (PMO or operational excellence lead): builds the matrices, runs catchball and keeps bowling charts current.
- Department heads: own department plans and the priorities assigned to them.
- Priority owners: run their projects, update measures and write countermeasures.
- Finance partner: checks targets against the budget and confirms results.
Monthly reviews with bowling charts
A bowling chart is a simple table. Each row is a measure. Each column is a month. For each month, show the target and the actual, and color the actual green when it meets the target and red when it does not. In Excel, build it with Home, then Conditional Formatting, using a rule that compares the actual cell with the target cell.
In the review, skip the green rows. Spend the time on the red ones. For each red measure, the owner explains the cause and the countermeasure, with a date. If a measure is red for several months in a row, escalate it or rethink the priority. Keep each review to about an hour by limiting discussion to measures that missed.
Hoshin kanri vs OKRs vs balanced scorecard
People searching for one of these often compare all three. OKRs set ambitious objectives and key results, usually each quarter, and are often set bottom-up by teams. The balanced scorecard tracks performance across four perspectives: financial, customer, internal process, and learning and growth. Hoshin kanri focuses on a few breakthrough objectives, deploys them level by level through catchball, and runs on monthly reviews within an annual cycle.
They can work together. Some companies use hoshin kanri for the few company-wide breakthroughs and OKRs for team goals inside them. Pick one primary system so people are not tracking the same work in two places.
Common mistakes to avoid
- Picking too many breakthrough objectives spreads people thin, so keep to three to five and write down what you will stop.
- Skipping catchball turns the plan into orders people resist, so let each department test targets and resources before you lock them.
- Filling the X-matrix without checking correlations hides orphan projects, so review every corner grid and cut priorities that support nothing.
- Reviewing only green measures wastes the meeting, so focus monthly reviews on red measures and their countermeasures.
- Giving one manager many priorities overloads them, so cap priorities per owner and check the owner column before approval.
- Treating the annual reflection as a formality repeats last year's mistakes, so compare results with targets and record what you will change.
Frequently asked questions
What is hoshin kanri planning?
It is a strategy deployment method that chooses a few breakthrough objectives, sets annual goals and improvement priorities, and deploys them through every level of the company. Progress is checked monthly and the plan is reviewed yearly. It follows the plan, do, check, act cycle.
What are the steps of hoshin kanri?
Set the vision, choose breakthrough objectives, set annual objectives, deploy them to departments through catchball, carry out the work, review progress monthly and hold an annual review. Many teams use an X-matrix to keep everything on one page.
What is an X-matrix in hoshin kanri?
It is a one-page grid that links breakthrough objectives, annual objectives, improvement priorities, metrics and owners. Corner grids show how strongly each item supports the next. It helps you spot work that supports no objective and objectives with no work behind them.
What is catchball in hoshin kanri?
Catchball is the back-and-forth between management levels to agree on priorities and targets. Leaders share a draft, the next level responds with what is possible and what it needs, and the draft is adjusted until both agree. It builds buy-in and realistic targets.
Is hoshin kanri only for manufacturing?
No. It started in manufacturing but is used in healthcare, services, software and public sector organizations. The method works anywhere leaders need a few clear priorities, deployed to teams and reviewed on a fixed rhythm.