A goal tree and an X-matrix can describe the same plan. The tree is easier to read and hides something important. The matrix shows that something and is harder to read. Knowing which to use, and when, saves a lot of confusion.
In this guide
Key Takeaways
- →A tree is a hierarchy, one parent per item. A matrix is a network, many-to-many.
- →The tree reads like an org chart, which is why people prefer it and why it misleads.
- →What a tree hides is cross-links: a priority driving two objectives, or a KPI fed by several priorities.
- →What a matrix hides is the simple chain of ownership, which is what teams want to see.
- →Plan and grade in the matrix. Communicate and roll up with the tree.
- →If both views come from one set of records, they cannot drift apart.
Two shapes for the same plan
A goal tree, or strategy tree, is a tree diagram applied to objectives. The breakthrough sits at the top, annual objectives branch below it, priorities below those, and measures at the leaves. Each item has one parent. It reads like an organization chart, which is why people like it.
An X-matrix lays the same items around four sides and uses grids to show which relate to which. Any priority can correlate with any KPI. It reads less naturally, and it holds information a tree can’t.
The tree diagram is one of the seven classical planning tools, and the matrix diagram is another; The Seven Management and Planning Tools in Hoshin Kanri covers where each belongs in a planning week.
What each one hides
| Goal tree | X-matrix | |
|---|---|---|
| Structure | Hierarchy: one parent per item | Network: many-to-many correlations |
| Easy to see | Who owns what, and what rolls up to what | Which priorities drive which KPIs, and how strongly |
| Hidden | A priority that drives two objectives; a KPI fed by several priorities | The simple chain of ownership |
| Best for | Communicating the plan; ownership; roll-ups | Planning; grading correlations; testing bets |
A tree tells you who is responsible. A matrix tells you what you are betting on. A plan needs both answers.
The row that does the work here is “how strongly”. Grades only mean something if the room agreed what each one claims, which is the subject of Primary, secondary, partial: grading X-matrix correlations.
When to use each
- Use the X-matrix during planning, when the team is deciding which priorities to bet on and how strongly each one is expected to move each KPI.
- Use a tree to communicate, especially below the leadership team, where people want to see how their work rolls up rather than the full web of correlations.
- Use the matrix in quarterly reviews, where the question is whether correlations held.
- Use the tree in team and site reviews, where the question is whether each contribution is on track.
The second and fourth points are where cascading lands, and the sequence for that is in Cascading the Hoshin Plan From Group to Sites in Planning Season.
A worked example: one plan, both ways
As a tree, an illustrative services objective looks tidy: services at 34% → complete the service network → three centers; and services at 34% → multi-year contracts → legal approval, 40 contracts.
As an X-matrix, the same plan shows two things the tree doesn’t. Multi-year contracts also correlate, as a secondary link, with price realization under the margin objective. And services share depends on a third priority, technician certification, which in the tree sits under a learning objective and appears unrelated.
| Relationship | Visible in the tree? | Visible in the matrix? |
|---|---|---|
| Network → services share | Yes | Yes, graded primary |
| Contracts → price realization | No: contracts sit only under services | Yes, graded secondary |
| Technician certification → services share | No: sits under a different objective | Yes, graded secondary |
Illustrative.
If the certification program slips, the tree suggests it affects only the learning objective. The matrix shows it puts the services target at risk too.
One model or two files, and what that costs
Most organizations end up maintaining both shapes, because both answer questions somebody asks. The cost is not in drawing them. It is in keeping them saying the same thing.
Drawn separately, they drift within a quarter. A priority gets retired in the matrix during the Q1 review and stays on the tree that team leads present from; a KPI definition changes on the matrix tab and the tree keeps the old one. By mid-year the organization has two plans with one name, and the certification example above is exactly the kind of cross-link that gets lost in the gap. The fix is structural rather than disciplinary: both views have to be generated from one set of records, so there is nothing to reconcile.
Among published alternatives, OnStrategy lists $200 per month for unlimited users. i-nexus publishes a free Starter tier for up to five users and $28 per user per month at its Standard tier. The seat model matters for this particular problem, because the tree view is the one the whole organization reads. Pricing per seat prices the audience for the view that exists to be communicated.
Profit.co publishes two plans, Essentials and Enterprise, quoting against modules and scale rather than a public seat rate. Hoshin Kanri sits in Essentials alongside OKRs and Goals, Balanced Scorecard and Strategy Roadmap. What drives the cost of hoshin kanri software lists the rest to total, and the 30-day free trial is long enough to put the same plan into both views and see whether they still agree.
Both views in Profit.co
Profit.co shows both shapes from the same records. The X-matrix shows graded correlations between objectives, priorities and KPIs; each objective also shows its contributing key results with weightings, which gives the roll-up view. Because both come from one model, the tree and the matrix can’t drift apart. More on the Hoshin Kanri software page.
What else changes once the matrix stops being a drawing is covered in What Changes When the X-Matrix Is Live.
Free Product Demo
See your plan as a tree and a matrix
A 30-minute walkthrough, tailored to your team.
Book a free demo
What happens in the call
How your teams set goals, track progress and review results.
Strategy, performance, projects and engagement on one platform, with AI.
A practical path to align teams, execute faster and drive results.
Questions this article answers
A goal tree is a hierarchy where each item has one parent. An X-matrix is a network that shows many-to-many correlations between priorities and KPIs.
Both. Use the X-matrix to plan and test correlations, and a tree to communicate ownership and roll-ups to teams.
Cross-links: a priority that drives more than one objective, or a KPI that depends on priorities in different branches.
The simple chain of ownership. A matrix shows which priorities drive which KPIs, but a tree answers “what does my work roll up to” at a glance.
Yes, and they should. The risk is that maintained separately they drift apart within a quarter, which is why both views are best generated from one set of records.
The matrix, because the question is whether the correlations held. Team and site reviews use the tree, where the question is whether each contribution is on track.
