Insights
A plain English guide to hoshin kanri: what it is, how catchball and the X matrix work, and a simplified template and planning cycle you can copy.
By Christopher Fagan, Managing Partner, PEF Consulting Partners
Delivered for and alongside
















Hoshin kanri is a strategy deployment method, developed in Japan, that turns a few long term breakthrough objectives into annual goals, projects and measures at every level of an organisation, and reviews them on a regular cycle. In English it is usually called policy deployment or hoshin planning.
The idea is simple: agree the few things that matter most, make sure everyone can see how their work contributes, and check progress often enough to correct course. Doing it well is harder. This guide explains how the method works, how to read an X matrix and the mistakes that make it fail, with a simplified template and planning cycle you can copy.
In this article
Hoshin combines the Japanese characters for direction and needle, as in a compass needle, and is usually translated as direction or policy. Kanri means management or control. Put together, the phrase means something like managing by direction: setting a heading for the whole organisation and steering everyone towards it. The word policy in policy deployment carries that sense of direction and priorities, not rules or procedures.
The method grew up in Japanese manufacturing in the 1960s, as companies that had adopted total quality control looked for a way to connect company wide targets with daily improvement work. It drew on the plan, do, check, act cycle from quality management and on the management by objectives idea Peter Drucker set out in the 1950s. The difference was that it put more weight on how targets are reached, and on agreeing them through discussion rather than handing them down.
Western companies began adopting hoshin planning in the 1980s. An English edition of a book edited by Yoji Akao, published in 1991, helped bring the method to English speaking readers, and Thomas L. Jackson’s 2006 book for lean organisations sets out the X matrix in detail. Both are listed in the sources below.
Versions differ in the detail, but most follow the same sequence. The steps below assume a yearly cycle.
Most versions also separate two kinds of goal. Breakthrough objectives are the few things that must change. Business fundamentals, sometimes called daily management, are the measures that keep the operation healthy, such as safety, quality, cost and delivery. Hoshin effort goes on the first, while the second is run through normal performance management, and confusing the two is one of the quickest ways to overload the plan.
Catchball is the back and forth process by which plans are agreed between levels. Leaders propose an objective and pass it, like a ball, to the next level down. That team replies with what it believes it can achieve, what it would need and what it would change, and the ball goes back and forth until both sides agree a target and a plan they believe in.
It also runs sideways, between departments that depend on each other, so that a sales target is matched by the operational capacity to deliver it. Catchball takes time, especially in the first year, but it is where much of the value lies. People commit to targets they have helped to shape, and the conversations surface constraints a top down plan would miss.
The test of good catchball is whether anything changes. If every proposal comes back exactly as it went down, the organisation is collecting comments, not agreeing a plan.
The X matrix puts a whole year’s plan on a single page. It is built around a large X that divides the centre into four areas, each holding one list, and small grids in the corners show how each item connects to the next. It is read clockwise, starting at the bottom:
The corner grids mark where items are linked, usually with symbols for a strong or weaker relationship. They make gaps obvious: an annual objective with no improvement priority behind it, a project that serves no objective, or a measure that tracks nothing on the plan. That is the matrix’s real value, because it forces the conversation about whether the plan actually adds up.
A full X matrix is hard to show on a web page, so the version below flattens it into rows. Each row traces one thread from a breakthrough objective to the person who owns the work. Copy it into a spreadsheet, add rows as needed and keep the total small.
| Breakthrough objective (3 to 5 years) | Annual objective (this year) | Improvement priority | Measure and target | Lead | Support |
|---|---|---|---|---|---|
| The big change you are committed to | What must be true by year end | The project or initiative that gets you there | One measure, its baseline and this year’s target | One named person | Teams that must contribute |
| Breakthrough 1 | Annual objective 1a | Priority 1a | Measure, baseline, target | Name | Teams |
| Breakthrough 1 | Annual objective 1b | Priority 1b | Measure, baseline, target | Name | Teams |
| Breakthrough 2 | Annual objective 2a | Priority 2a | Measure, baseline, target | Name | Teams |
Two rules keep it honest. Every row needs a single named lead, and every measure needs a baseline before the year starts, because if you cannot measure where you are, you cannot show progress. Track the benefits alongside it with a benefits realisation plan template, so the matrix shows outcomes as well as activity.
This cycle assumes a financial year that starts in April. Shift the months to suit your own year.
| When | What happens | Who is involved |
|---|---|---|
| December to January | Reflect on the current year: what was achieved, what was missed and why. Refresh the three to five year view. | Executive team, with input from senior managers |
| January to February | Confirm breakthrough objectives, draft annual objectives and start catchball with the next level down. | Executive team and senior managers |
| February to March | Catchball down and across: agree improvement priorities, measures, targets and owners, and align the budget. | All management levels and finance |
| April | Publish the matrix and team plans, and start the projects. | Everyone |
| Every month | Review measures at each level, explain misses, agree countermeasures and escalate anything that needs a decision. | Each management team |
| Every quarter | Review the whole portfolio. Change targets or priorities only where the evidence demands it. | Executive team |
This example is hypothetical. Imagine a field services business of around 1,200 people that maintains heating and electrical systems for housing associations and councils. Its leadership team agrees two breakthrough objectives for the next three years: make first time fixes the norm on every contract, and grow planned maintenance until it outweighs reactive repairs.
| Breakthrough objective | Annual objective | Improvement priority | Measure and target | Lead | Support |
|---|---|---|---|---|---|
| First time fixes as the norm | Raise the first time fix rate from 72% to 82% | Better triage at the contact centre so the right engineer is sent | First time fix rate by contract, monthly; 82% by March | Head of Customer Service | Operations, IT |
| First time fixes as the norm | Correct parts on the van for four in five jobs | Parts kits by job type, linked to scheduling | Jobs with correct parts on first visit; 80% by March | Supply Chain Manager | Operations |
| Planned work outweighs reactive | Move two large contracts onto planned schedules | Asset condition surveys on both contracts | Share of contract value from planned work; 35% by March | Commercial Director | Engineering, Finance |
In the first round of catchball, operations managers in the two rural regions pushed back on the parts target, because travel distances made restocking vans much harder there. The leadership team kept the target but agreed to fund a second parts hub. The target stayed ambitious and the plan became believable, which is catchball doing its job.
By month four the first time fix rate was moving, but the parts measure was not. A short root cause analysis found that job codes in the scheduling system were too broad to drive the right kits. The countermeasure, a revised set of job codes, was given an owner in IT and a date, and the review moved on.
Hoshin kanri works best when an organisation has a clear strategy but struggles to turn it into consistent action across functions, when too many priorities compete for the same people, and when leaders can commit to a monthly review rhythm for at least a full year. It also needs a reasonably stable management structure to cascade through.
It is the wrong tool when the strategy itself is not agreed, because it deploys a direction rather than setting one; in that case, start with strategy consulting to make the choices first. It is also a poor fit for an organisation in crisis, where weekly decisions matter more than a yearly cycle, and for leadership teams that will not give time to catchball and reviews. Adding it on top of a planning process that already works usually creates paperwork rather than focus.
Hoshin is one way to run strategy execution, not the only one. Its core principles apply whichever method you use: a few clear priorities, agreed ownership, measures tied to outcomes and a steady review rhythm. Our strategy execution work applies them with as much or as little formal structure as your organisation needs, and our operational excellence team connects the plan to daily improvement on the ground.
Where the projects in the matrix are big enough to need programme disciplines, such as governance, a PMO and independent assurance, our delivery excellence service covers them.
Hoshin kanri is a way of making sure a whole organisation works on a few agreed priorities. Leaders set a small number of long term breakthrough objectives, turn them into annual goals, and agree with each level how it will contribute and how progress will be measured. Progress is reviewed every month, and the whole plan is revisited every year.
The X matrix is a one page planning tool used in hoshin kanri. It shows breakthrough objectives, annual objectives, improvement priorities and measures in four areas arranged around a central X, with grids in the corners showing how each item links to the next. A final section names who leads and supports each priority, so anyone can trace their work back to the strategy.
Catchball is the back and forth discussion used to agree objectives and targets between levels of an organisation. A proposal is passed down, the receiving team replies with what it can achieve and what it needs, and the discussion continues until both sides agree. It also runs across departments that depend on each other. The aim is targets that are ambitious, realistic and genuinely owned.
Both connect goals across an organisation, but they work differently. Hoshin kanri runs on a yearly cycle tied to three to five year breakthrough objectives, agrees targets through catchball and reviews them monthly. OKRs usually run quarterly, are often set partly by teams themselves and are commonly written as stretch goals. Hoshin is more structured and suits organisations that want tight alignment.
Yes. The classic template is the X matrix, which fits a year’s plan on one page. A simpler option is a table where each row traces one thread from a breakthrough objective to an annual objective, an improvement priority, a measure and a named lead. This page includes a copyable version of that table, plus a yearly planning cycle you can adapt.
Related reading: Gap analysis explained, The McKinsey 7S model, Value chain analysis and What a good programme sponsor does.
We help leadership teams turn a few clear priorities into agreed targets, funded projects and a review rhythm that lasts beyond the first quarter. Talk to us about your planning cycle.
Book a confidential conversation
Sources: Yoji Akao (ed.), Hoshin Kanri: Policy Deployment for Successful TQM, Productivity Press, 1991; Thomas L. Jackson, Hoshin Kanri for the Lean Enterprise: Developing Competitive Capabilities and Managing Profit, Productivity Press, 2006; Peter F. Drucker, The Practice of Management, 1954
Written by Christopher Fagan
Managing Partner, PEF Consulting Partners
Christopher has led systems and transformation delivery for 19 years, including the National Grid separation, the £9bn Energy Bills Support Scheme and the BP Pulse EV charging rollout.
Where next