What Is the Hoshin Kanri X-Matrix?

The hoshin kanri X-matrix is a one-page planning form that arranges long-term breakthrough objectives, annual objectives, improvement priorities, and metrics around a central X, with correlation marks linking each quadrant. It originated in the Quality Function Deployment (QFD) community, not at Toyota. Toyota does not use it.

That second fact surprises many people, because the X-matrix has become the visual shorthand for hoshin kanri in Western practice. This article explains what the X-matrix is, where it actually came from, why Toyota’s own hoshin kanri runs without it, and what to watch for if your organization uses one.

The X-matrix is a legitimate planning form from the QFD community, developed by Yoji Akao and popularized in the United States by GOAL/QPC
It is not part of Toyota’s hoshin kanri practice, past or present
The tool and the management system are separate things: organizations can run hoshin kanri well without an X-matrix, and can fill out X-matrices while failing at hoshin kanri

What are the four quadrants of the X-matrix?

The X-matrix takes its name from the large X drawn in the center of the page, which divides the sheet into four fields. Labels vary by template, but the standard arrangement is:

Position	Content	Typical horizon
South (bottom)	Breakthrough objectives	3–5 years
West (left)	Annual objectives	This year
North (top)	Improvement priorities or projects	This year
East (right)	Metrics and targets to improve	This year

At each corner of the X, a correlation matrix of marks (often filled and open circles) indicates which items in one quadrant support which items in the next. A section along the right edge typically assigns responsibility, marking which people or teams own each improvement priority.

Read clockwise, the form tells a story: long-term breakthroughs drive this year’s objectives, which drive specific improvement projects, which are tracked by specific metrics, which are owned by specific people. The whole strategy fits on one page.

Where did the X-matrix come from?

The X-matrix originated in the Quality Function Deployment (QFD) community. QFD is a product development methodology built around matrix diagrams that translate customer requirements into engineering characteristics. Yoji Akao, the central figure in QFD, developed the matrix-based approach, and the consulting and training organization GOAL/QPC popularized the X-matrix format in the United States as part of its hoshin planning material.

This lineage explains the form itself. The X-matrix is a QFD-style relationship matrix applied to strategy: rows and columns of items with correlation symbols at the intersections. That is the QFD signature, carried over from product development into planning.

The important point is what this lineage means. The X-matrix entered Western hoshin practice through the QFD and consulting route. It did not come out of Toyota, and it was never part of the hoshin kanri system that Toyota built from 1963 onward.

Does Toyota use the X-matrix?

No. Toyota does not use the X-matrix in its hoshin kanri practice.

Mark Reich managed the hoshin kanri process at Toyota North America for 23 years, including six years in Japan. In Managing on Purpose (Lean Enterprise Institute, 2025), he describes encountering the X-matrix only after leaving Toyota, when working with other companies: “Some were familiar with the X-matrix — which I had never encountered at Toyota — and believed that if they filled out the form correctly they would have aligned goals. However, what they really had was management by objectives: ‘Here is what I need from you. Please get it for me.’”

The historical record agrees. Mikio Sugiura was the responsible manager for hoshin kanri in Toyota’s Corporate Planning Department during the late 1970s, and his firsthand account (Toyota Global 10, published in Japanese in 2017) describes Toyota’s hoshin documents, cascade, and review mechanisms in detail. No X-matrix appears anywhere in the system he describes.

For a fuller answer to this question, see Does Toyota Use Hoshin Kanri?

What does Toyota use instead of the X-matrix?

Toyota’s hoshin kanri runs on a written document, a dialogue process, a cross-functional structure, and a review mechanism. None of them is a matrix.

A written Company Hoshin in three layers. From its first version in January 1963, Toyota’s hoshin document had three nested layers: Basic Hoshin (the permanent foundational direction, barely changed over fifty years), Long-term Hoshin (targets and countermeasures over three to five years), and Annual Hoshin (this year’s goals and measures). By 1967 the document had grown to six categories, organized by function.

Catchball between management levels. Hoshin items are negotiated up and down the hierarchy, with targets and methods both on the table, until each level genuinely owns its piece. The documented cascade stops at the section manager level; below that, hoshin content changes form and carries to the supervisor level through FMDS floor management boards and daily management, not personal hoshin documents.

Function Meetings for horizontal coordination. Standing management forums organized by function (Quality, Cost, Production, Technology, Sales/HR) coordinate hoshin across departmental boundaries. Major objectives like Global 10, Eiji Toyoda’s 1978 challenge to raise Toyota’s global production share from 7% to 10%, required Product Development, Production Engineering, Manufacturing, and Sales to move together. The Function Meetings were where those interdependencies were worked.

A review layer with real consequences. Toyota reviews hoshin through the year, and in the period Sugiura documents it also ran operational audits reporting to the president: four to six themes per year, presented on a double-sided A3 report in ten minutes with five minutes of questions, with the president’s written feedback in his own words. This documented mechanism is covered in depth in Operational Audits: The Missing Feedback Loop in Hoshin Kanri.

Notice what carries the alignment load in Toyota’s system: dialogue, standing cross-functional forums, and executive review with real consequences. A one-page form does not appear in that list. In principle a matrix could sit alongside all of those behaviors; what it cannot do is substitute for them.

How do you build an X-matrix?

If your organization has decided to use an X-matrix, the standard build sequence runs counterclockwise from the bottom:

Enter breakthrough objectives (south): the three to five multi-year changes that matter most.
Derive annual objectives (west): what portion of each breakthrough must be achieved this year.
Define improvement priorities (north): the concrete projects and initiatives that will deliver the annual objectives.
Set metrics and targets (east): how progress on each priority will be measured.
Mark correlations and assign owners: fill in the corner matrices showing which items support which, and assign accountability for each priority.

Done honestly, the exercise forces useful questions: Do our projects actually connect to our strategy? Do we have too many priorities? Does anyone own this? Those questions have value regardless of the form used to ask them.

What are the limits of the X-matrix?

The accurate frame is category, not quality: the X-matrix is a tool, and hoshin kanri is a management system. A tool records and displays. A system is the set of ongoing behaviors that produce what the tool records.

What the matrix genuinely does: it compresses long-term objectives, annual objectives, improvement priorities, metrics, and ownership onto one page with the relationships marked. That is useful work. It creates visibility, forces a choice of few priorities, and keeps a standing record of who owns what.

What the matrix does not contain is the rest of the system, so an organization using one still has to build the following alongside it, in whatever form fits its culture and capability:

The negotiation. Catchball on targets and methods. Teams using an X-matrix can and do run catchball; the corner marks then record what was negotiated. The mark is the record of a dialogue, not a substitute for one.
The horizontal coordination. Standing cross-functional forums, which at Toyota are the Function Meetings, where interdependencies between departments are worked through the year. The matrix marks that two items relate; a forum is where the relationship gets managed.
The review leg. The format has no equivalent of the review layer Sugiura documents at Toyota: executive examination of actual execution, with feedback that had consequences. An organization can build that review rhythm alongside the matrix. The form does not ask for one.
The permanent and long-term layers as operating layers. The breakthrough quadrant carries a three-to-five-year horizon, but the form treats those objectives as input to the current cycle’s sheet. Toyota’s Basic Hoshin (permanent, barely changed over fifty years) and Long-term Hoshin (with its own targets and countermeasures) are managed in their own right. The matrix has no place for the permanent layer at all.

The failure mode Mark Reich describes is what happens when the tool is mistaken for the system: teams believe a correctly completed matrix means aligned goals, when what they have is management by objectives with better graphics. The trap is not using the matrix. It is stopping there.

The practical conclusion is not that the X-matrix must be abandoned. Organizations that find the one-page visibility useful have reason to keep it. The conclusion is that the matrix is one tool within a larger system, and a hoshin effort that centers on completing the form has skipped the parts that make the system work.

Frequently asked questions

Did the X-matrix come from Toyota? No. The X-matrix originated in the Quality Function Deployment (QFD) community, developed by Yoji Akao and popularized in the United States by GOAL/QPC. It is not part of Toyota’s hoshin kanri practice. Mark Reich, who managed hoshin kanri at Toyota North America for 23 years, has stated he never encountered it at Toyota.

Is the X-matrix required for hoshin kanri? No. Toyota, the best-known practitioner of hoshin kanri, has run the system since 1963 without an X-matrix. Toyota’s written hoshin is a document organized in three layers (Basic, Long-term, Annual), aligned through catchball dialogue and cross-functional Function Meetings, and reviewed through disciplined A3-based executive review.

What are the four quadrants of the X-matrix? In the most common Western format: long-term breakthrough objectives (typically 3-5 years), annual objectives, improvement priorities or projects, and metrics or targets to improve. Correlation marks at the corners link the items in adjacent quadrants, and a side section assigns accountability for each priority.

Is the X-matrix a bad tool? Not inherently. It compresses objectives, projects, metrics, and owners onto one page, which some organizations find useful for visibility. The risk is treating the completed form as the management system. Filling out the matrix correctly does not create the dialogue, cross-functional coordination, or review discipline that make hoshin kanri work.

What does Toyota use instead of the X-matrix? A written Company Hoshin in three layers (Basic, Long-term, Annual), catchball negotiation between management levels, Function Meetings for cross-functional coordination, and disciplined executive review, documented in the Sugiura era as operational audits where managers presented on a double-sided A3 in ten minutes and the president provided written feedback in his own words.

Hoshin Kanri: How Direction Becomes Daily Work — the full guide to Toyota’s system
Does Toyota Use Hoshin Kanri? — the direct question, answered
Operational Audits: The Missing Feedback Loop in Hoshin Kanri — the review leg the X-matrix lacks
Hoshin Kanri — encyclopedia entry
Hoshin Kanri Topics — structured knowledge claims

Art Smalley is president of Art of Lean, Inc. This article draws on Mikio Sugiura’s firsthand Japanese-language account of Toyota’s hoshin kanri system (Toyota Global 10) and Mark Reich’s Managing on Purpose. AI was used in the editing of this article.