In this guide
- Every vendor has an X-matrix
- Test with your matrix, not their demo
- The seven tests for choosing hoshin kanri software
- Beyond the seven: practical fit
- Score it as a gate, not a weighted sum
- Building the shortlist before you run the tests
- A two-week evaluation plan
- Red flags during the demo
- Evaluation mistakes to avoid
- How Profit.co does on the tests
- Questions this article answers
Key Takeaways
- →Every vendor uses the same vocabulary, so a feature-list comparison ends in a tie and the decision falls to price or polish.
- →Send a cut-down version of your own matrix before the demo, including one priority that finished while its KPI stayed flat.
- →Four of the seven tests are must-pass: correlation strength, outcome lag, drill-down, and whether the tool runs the review without an administrator.
- →Gate the result rather than weighting it. Breadth should not rescue a tool that fails a fundamental.
- →Budget about two weeks, keep the same evaluators across every demo, and ask references to name a decision the tool brought forward.
- →Search four categories when you build the shortlist, not one. The same product may be sold as hoshin kanri software, strategy deployment software, strategy execution software or continuous improvement software.
Feature lists won’t separate hoshin kanri tools, because every vendor ticks every box. What separates them is how they behave with your matrix in front of them. These seven tests, with a script for running each one in a demo, do that.
Every vendor has an X-matrix
Put the feature pages of any five hoshin kanri tools side by side and you’ll find the same words: X-matrix, catchball, bowler chart, A3, PDCA, cascading, dashboards. An evaluation built on that list ends in a tie, and the decision falls back on price, interface polish or which salesperson was most persuasive.
The words are the same because they describe the method. The differences are in what the software does with them: whether the X-matrix is a picture or a set of live records, whether catchball is a thread or a form, whether the bowler fills itself or gets filled. Those differences only show up when you watch the tool work on a real plan.
Test with your matrix, not their demo
Vendor demo data is built to look good. Every correlation is sensible, every owner has checked in, every chart has an interesting shape. That tells you how the tool looks at its best, not how it handles your messy reality.
Before the demo, send the vendor a cut-down version of your actual matrix: a few objectives, eight to ten priorities, five or six KPIs, the correlations between them, and two or three months of real or realistic results. Include one priority that finished on time while its KPI stayed flat. Ask them to load it and run the tests below on it. A vendor who can’t or won’t do this for a serious evaluation is telling you something.
The seven tests for choosing hoshin kanri software
| Test | Pass condition | Demo script |
|---|---|---|
| 1. Correlation strength | Each dot carries a grade (primary, secondary, partial), not just presence | “Open the correlation between priority P3 and the services KPI. What does the record show, and who owns each end?” |
| 2. Outcome lag | The tool surfaces priorities that are progressing while their correlated KPIs aren’t | “Our P3 is complete and its KPI is flat. Without building anything, show us where we’d see that.” |
| 3. Catchball record | The negotiation stays attached to the objective it shaped | “The regional lead disagrees with this target. Show us how they push back and where that conversation lives afterwards.” |
| 4. Bowler with comments | Monthly plan, actual and status in one row, with the owner’s explanation alongside | “Show the bowler for the services objective, and the comment explaining September’s red.” |
| 5. Two horizons | Multi-year breakthrough and annual objectives are linked records | “Show this year’s objectives against the three-year breakthrough they serve, then show last year’s.” |
| 6. Drill-down | From a red cell on the matrix to the key results, owners and check-ins beneath it | “Start from this red cell. How many clicks to the person whose work explains it?” |
| 7. Runs the review | Owners check in on a cadence; the tool doesn’t depend on an administrator | “Who enters September’s numbers, and how do they know it’s due?” |
Run each test on your own data. Pass or fail, no partial credit.
Beyond the seven: practical fit
The seven tests decide whether a tool can run hoshin kanri. A second set decides whether it can run it in your organization. These vary more by company, so weigh them against your own situation.
- Cascade depth. How many levels will the matrix need: corporate, division, site, team? Ask to see the deepest level the vendor has running for a real customer.
- Where the rest of your goals live. If teams already use OKRs or a scorecard, ask how hoshin objectives connect to them. Two tools means monthly reconciliation. (See purpose-built hoshin kanri tools vs strategy execution platforms.)
- Permissions. Who can see the corporate matrix, and who can edit a correlation? Site leaders need visibility without the ability to rewrite group targets.
- Languages and time zones, if the program spans regions.
- Integrations for KPIs that already live in an ERP, BI or finance system, so owners aren’t re-keying numbers.
- Admin effort. Ask how many hours a month a customer’s program lead spends maintaining the tool. A large answer means the matrix keeper has moved, not gone.
Score it as a gate, not a weighted sum
Weighted scoring models let a tool that fails a fundamental test win on breadth. Avoid that by treating four of the seven as must-pass.
- Test 2, outcome lag. Without it the tool can’t answer the central question of the monthly review.
- Test 6, drill-down. Without it every red cell becomes an email chain.
- Test 7, runs the review. Without it the matrix keeper comes back within a quarter.
- Test 1, correlation strength. Without it every dot gets the same attention.
Tools that pass all four go on to a weighted comparison of the rest, including practical fit and cost. Tools that fail any of them are X-matrix editors. That can be the right purchase if all you need is a better drafting surface, but it should be a conscious choice.
Building the shortlist before you run the tests
The seven tests assume you already have three or four vendors to point them at. Getting to that shortlist is harder than it looks, because the products that can run hoshin kanri are scattered across four market categories that rarely surface in the same search.
| What the vendor calls itself | Who sits there | What to expect |
|---|---|---|
| Hoshin kanri software | Specialists built around the X-matrix | Strongest on the matrix itself; check tests 6 and 7 closely |
| Strategy deployment software | The same discipline under its English name | Often the identical product; search both terms or you miss half the market |
| Strategy execution software | Platforms running OKRs, scorecards and hoshin on one model | Strongest on check-ins and cadence; confirm correlations are graded |
| Continuous improvement software | Lean and CI suites that added strategy deployment | Strongest where a kaizen program already exists; check test 5 |
Search all four terms. The label tells you where a product came from, not whether it can run your program.
The category a vendor markets in predicts its weaknesses better than its strengths. A continuous improvement suite may pass all seven tests; a product that leads with a beautiful X-matrix may fail test 7 outright. That is why the tests run on behavior rather than on category.
For the record, Profit.co sits in the third row. Hoshin Kanri runs alongside OKRs and Goals, Balanced Scorecard and Strategy Roadmap on one data model, inside the Essentials plan with a 30-day free trial. Put us in the strategy execution column, and run tests 6 and 7 on us as hard as you would on a specialist, because breadth is exactly where that column is supposed to be weak.
Three or four vendors is the right number to carry into demos. Two gives you no real comparison. Six means the demos blur together and the same evaluators stop attending all of them, which is the failure the plan below is built to prevent.
A two-week evaluation plan
| Day | Activity | Output |
|---|---|---|
| 1 | Prepare a cut-down version of your matrix with two or three months of results, including one outcome-lag case | Evaluation dataset |
| 2 | Send the dataset and the seven tests to each shortlisted vendor | Demo dates booked |
| 3 to 8 | Demos on your data, one per vendor, with the same people attending each | Pass/fail per test, per vendor |
| 9 | Reference calls with customers of each vendor that passed the must-pass tests | Notes on adoption and upkeep |
| 10 | Practical-fit and cost comparison for vendors still in the running | Weighted comparison |
Keep the same evaluators across every demo so the comparisons are fair.
A sample scoring sheet
| Test | Must pass? | Vendor A | Vendor B | Vendor C |
|---|---|---|---|---|
| 1. Correlation strength | Yes | Pass | Pass | Fail |
| 2. Outcome lag | Yes | Pass | Fail | Fail |
| 3. Catchball record | No | Pass | Pass | Pass |
| 4. Bowler with comments | No | Pass | Pass | Pass |
| 5. Two horizons | No | Fail | Pass | Pass |
| 6. Drill-down | Yes | Pass | Pass | Pass |
| 7. Runs the review | Yes | Pass | Pass | Fail |
Illustrative. Vendors B and C fail a must-pass test and leave the evaluation, however well they score elsewhere.
Questions for reference customers
- Who updates the matrix each month, and how long does it take them?
- Does your monthly review run from the tool or from slides built from it?
- Name a decision the tool helped you make earlier than you would have otherwise.
- What did you stop doing outside the tool once it was live?
The third question is the most revealing.
A reference who can name a specific decision is describing a working program. One who talks only about visibility and alignment may be describing a well-maintained poster.
Red flags during the demo
- “Let me switch to our demo environment.” The vendor wouldn’t load your data, or couldn’t.
- “That’s on the roadmap.” For one of the four must-pass tests, it means the tool fails it today.
- Numbers typed during the demo. If progress values are being entered by the presenter rather than flowing from check-ins, ask who does that in production.
- A beautiful matrix with no way in. If clicking a dot does nothing, the matrix is a picture.
- No answer on history. Ask what the matrix looked like three months ago. If they can’t show it, neither will you.
Evaluation mistakes to avoid
- Letting the vendor run the agenda. Send your tests and your data first, and run the demo against them. A polished walkthrough of features you didn’t ask about tells you little.
- Different evaluators for different vendors. If the strategy lead sees one demo and the operations lead sees another, the comparison is of the evaluators, not the tools.
- Weighting breadth over the must-pass tests. A tool with fifty features that can’t show outcome lag will lose to one with twenty that can, in every monthly review for years.
- Skipping the people who will check in. Include one or two priority owners in at least one demo. If they find check-ins awkward, adoption will suffer whatever the executive view looks like.
- Ignoring the planning season. Ask how the tool supports next year’s planning cycle, not just this year’s tracking. The planning software page lists six tests for that.
The demo that matters most is the one where your own outcome-lag case is on the screen.
How Profit.co does on the tests
We built Profit.co’s hoshin module around these tests, so it’s fair to say we’d pass them; you should check for yourself.
- Test 1: correlations are graded primary, secondary or partial, each with its expected lag and a strength history of every change.
- Test 2: Profit.co’s exception queue flags each correlation whose hypothesis didn’t hold, and initiative escalation flags delivery problems, so outcome lag reaches the review as a named item rather than something someone has to spot. The four-quadrant chart puts outcome lag in its own quadrant.
- Test 3: catchball runs as a session with a change table, own-number-only counters and agreement from every participant.
- Test 4: the bowler chart shows plan, actual and performance score by month with the owner’s latest comment.
- Test 5: objectives can span multi-year strategy periods, viewed across years on the matrix.
- Test 6: from a red cell, the objective opens to its contributing key results, owners and check-ins, and to any countermeasure A3 on the gap.
- Test 7: check-ins and review cadences come from the same engine that runs Profit.co’s OKR and Balanced Scorecard programs.
The hoshin kanri software overview walks through each one.
Free Product Demo
Run the seven tests on your own 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
Graded correlations on the X-matrix, a way to see priorities progressing while their KPIs don’t, catchball recorded on each objective, a bowler chart with owner comments, linked multi-year and annual objectives, drill-down to key results and owners, and a check-in cadence that runs without an administrator.
Because every vendor’s feature list uses the same vocabulary: X-matrix, catchball, bowler, PDCA. The differences only show when you watch each tool handle your own matrix, including a priority that finished while its KPI stayed flat.
About two weeks: a day to prepare a cut-down version of your matrix, a week of demos on your data with the same evaluators each time, then reference calls and a cost and fit comparison for vendors that passed the must-pass tests.
Who updates the matrix each month and how long it takes, whether the review runs from the tool or from slides, what they stopped doing outside the tool, and a specific decision the tool helped them make earlier.
Usually yes. Strategy deployment is the English name for the same discipline, so the two terms often describe one product. Search both, plus strategy execution software and continuous improvement software, or a shortlist will miss vendors that pass every test.
Most vendors quote rather than publish. Seat count, cascade depth, data migration and whether the same tool runs your OKRs move the number most. In Profit.co, Hoshin Kanri is part of the Essentials plan rather than a separate purchase.
