How an X-matrix is laid out
Picture a square with an X drawn through it. Each of the four triangles around the X holds a list:
- South (bottom): three to five long-term breakthrough objectives, typically over three to five years.
- West (left): the annual objectives that move those breakthroughs forward this year.
- North (top): the improvement priorities, the projects and initiatives that will deliver the annual objectives.
- East (right): the measures and targets that show whether the priorities are working.
Along the far right edge are the names of the people accountable, and the corners between adjacent lists hold correlation marks: a dot where an annual objective supports a breakthrough, where a priority delivers an annual objective, where a measure tracks a priority, and where a person owns a priority.
How to read one
Start at the bottom and go clockwise. A breakthrough objective leads to the annual objectives that serve it, which lead to the priorities that deliver them, which lead to the measures that prove it, and then to the owners. If a priority has no mark against any annual objective, it does not belong on the plan. If an objective has no priority, nothing is being done about it.
Why hoshin kanri uses it
- It forces the vital few: the lists are short because the page is small.
- It makes the logic visible, so catchball conversations can challenge a specific link rather than the whole plan.
- It is the same at every level: a department X-matrix takes its breakthroughs from the priorities of the level above.
- It gives the monthly review a single page to walk through.
Common mistakes
- Filling every cell so the matrix becomes a list of everything rather than a focus.
- Writing measures that are activities ("hold workshops") rather than results.
- Building it once at planning time and never reviewing it.
- Treating the matrix as the plan, when the plan is the catchball and the projects behind it.
X-matrix or goal tree?
The X-matrix is compact and shows correlations; a goal tree shows the same cascade as parent and child goals with status, which is easier to read for people new to hoshin and easier to keep live in software. Many organisations plan on an X-matrix and manage on a goal tree.