What is a hoshin kanri X-matrix?

    Short answer

    A hoshin kanri X-matrix is a one-page planning tool that shows how long-term breakthrough objectives, annual objectives, top improvement priorities, measures and owners connect. Its four sections surround a central X, and correlation grids in the corners show which items support each other, making gaps and overloads visible at a glance.

    Last updated · TeamAssurance

    The layout

    The X-matrix gets its name from the large X in the centre that divides the page into four sections. Each section is read in sequence around the X:

    PositionSectionQuestion it answers
    SouthBreakthrough objectives (3 to 5 years)Where are we going?
    WestAnnual objectivesWhat must we achieve this year?
    NorthTop-level improvement prioritiesWhat will we work on to get there?
    EastTargets to improve (metrics)How will we measure progress?

    Down the right-hand side, a resource grid shows which people or teams own or support each priority. The corner grids use symbols, often filled and open dots, to mark strong or weak correlations between neighbouring sections.

    How to build one

    1. Write the long-term breakthrough objectives in the south section.
    2. Derive annual objectives that move the organisation toward them.
    3. List the few improvement priorities that will deliver the annual objectives.
    4. Define the metrics that will show whether each priority is working.
    5. Mark correlations in each corner, and check every item links to something.
    6. Assign owners and supporting resources on the right.
    7. Use catchball to test the draft with the people who will carry it out.

    What to look for

    • An annual objective with no priority supporting it is a gap.
    • A priority that links to nothing is a distraction.
    • A person marked against many priorities is overloaded.
    • A metric that does not connect to any objective adds noise.

    Common mistakes

    • Treating the matrix as the plan rather than a summary of it. Detail belongs in A3s and project plans.
    • Filling every cell, which defeats the purpose of focus.
    • Building it once and filing it. It should be reviewed with progress data during monthly hoshin reviews.
    • Using it below the level where it adds value. Lower levels often use a simpler cascade or a team-level matrix.

    Where it fits

    The X-matrix is one tool within hoshin kanri. It summarises the plan agreed through catchball; it does not replace catchball, monthly reviews or the A3s that carry each priority forward.

    How TeamAssurance helps

    TeamAssurance's Strategy Deployment capability uses a tree view to structure and cascade goals so each one contributes to its parent, with List, Team and Tree views for different review meetings. Goals can be linked to A3 reports, improvement activities and measures, and a monthly status history highlights at-risk goals, giving teams a live view of the links an X-matrix captures on paper.

    Frequently asked questions

    Do you need an X-matrix to do hoshin kanri?

    No. The X-matrix is a popular summary tool, but hoshin kanri can be run with simpler cascade tables or tree diagrams. What matters is the catchball, the focus on a few objectives and the regular PDCA reviews.

    How often should an X-matrix be updated?

    It is normally created during annual planning and reviewed monthly alongside progress data. The content changes only when objectives or priorities are formally revised.