In this guide
- The master file
- What Excel does well
- 4 Signs Your Hoshin Spreadsheet Is Breaking
- The real cost is in the lag, not the labor
- A worked example: one quarter of the master file
- A five-minute self-check
- Excel vs hoshin kanri software, side by side
- If you stay on Excel, do these four things
- Signals that it’s time to switch
- What hoshin kanri software adds that Excel can’t
- What hoshin kanri software costs
Key Takeaways
- →Excel is the right tool up to four specific thresholds. The matrix keeper is the clearest sign a program has crossed them, and it is a late sign.
- →The four breaking points: priority and KPI owners differ, the matrix cascades more than one level, more than one person updates results, and you need history.
- →Late discovery is the damage, not the spreadsheet itself. Nothing in Excel compares a priority against the KPI it was meant to move.
- →In the worked example the admin time is countable and the decision delay is not. One of them costs far more.
- →Score the self-check before you shortlist. None or one means tighten the spreadsheet; four or five means hoshin kanri software is already overdue.
- →Price both sides before you decide. The spreadsheet costs hours and late decisions; software costs a license plus setup. Four variables move the second number, and one of them is whether the same tool runs your OKRs.
Excel isn’t the wrong tool for hoshin kanri. It’s the right tool up to four specific thresholds, and most organizations cross them without noticing. The symptom is a person whose job has quietly become keeping the matrix alive.
The master file
Every organization that runs hoshin kanri in a spreadsheet has one. One person, usually a strategy or operational excellence lead, owns it. Before each monthly review they send a reminder, collect numbers from priority owners and KPI owners, paste them in, recolor the cells, export the bowler tabs to slides and circulate the pack.
That person is doing important work, and it’s the wrong work. They have become the matrix keeper: the human integration layer between the plan and the business. When they’re on holiday, the review runs on last month’s numbers. When they leave, the file’s logic leaves with them.
The matrix keeper is the clearest sign that a hoshin program has outgrown its spreadsheet. But it’s a late sign. The thresholds that create the role are crossed earlier, and they can be checked directly.
What Excel does well
It’s worth being fair to the spreadsheet, because the case for software is weaker than vendors suggest in some situations.
Excel is free, flexible and familiar. Every planning participant can open it. It handles the drafting phase of an X-matrix well: moving rows, trying correlations, reworking targets in a room full of people. Many organizations that run hoshin in dedicated software still draft the first version of each year’s matrix in a spreadsheet or on a whiteboard, and that’s sensible.
For a single site, with a handful of priorities and one planning team that reviews the matrix together each month, a well-kept spreadsheet is enough. The problems start when the matrix has to do more than one team can do in one room.
4 Signs Your Hoshin Spreadsheet Is Breaking
1. Priority owners and KPI owners are different people
When the person delivering a priority isn’t the person accountable for the KPI it’s meant to move, the matrix has two sources of truth. Each owner reports their own row; nobody reports the dot between them. The spreadsheet can hold both numbers, but it can’t make anyone compare them, so outcome lag goes unseen. (More in Outcome lag: when priorities are green and KPIs don’t move.)
2. The matrix cascades more than one level
Once a corporate matrix spawns site or functional matrices, the spreadsheet forks. Each level keeps its own file. Links between them are typed by hand and break when a row is renamed. Within a quarter, the site matrices and the corporate matrix describe slightly different plans.
3. More than one person updates results
A shared workbook with many editors becomes fragile: overwritten cells, broken formulas, conflicting copies. So organizations centralize updates through one person, which is how the matrix keeper role is born, and why the review data is always a few days old.
4. You need history
Spreadsheets overwrite. Unless someone snapshots the file monthly, there’s no record of what the plan said in March, who changed a target in June, or why. At the annual reset that history is exactly what the team needs, and it isn’t there.
The real cost is in the lag, not the labor
The matrix keeper’s hours are visible and easy to count. The larger cost is less visible: the time between something going wrong and the review noticing.
In a spreadsheet process, the data in the room is days or weeks old, the comparison between priorities and KPIs is done by eye if at all, and the reasoning behind each target lives in email. A losing bet on the matrix typically surfaces at the quarter or the year end. Every month it isn’t seen, people and budget keep flowing to it.
A spreadsheet doesn’t make hoshin kanri fail. It makes the failures arrive late, which is most of the damage.
A worked example: one quarter of the master file
The costs in the last section are easy to agree with and hard to feel. Here is what one quarter looks like for an illustrative group with one corporate matrix, four site matrices, twelve priorities and nine KPIs.
| Activity, per month | Who | Time |
|---|---|---|
| Chasing and collecting values from owners | Matrix keeper | 6 hours |
| Pasting values, fixing broken links between site and group files | Matrix keeper | 5 hours |
| Recoloring cells and rebuilding the bowler tabs | Matrix keeper | 3 hours |
| Exporting to slides and circulating the pack | Matrix keeper | 2 hours |
| Each owner preparing their own slides for the review | 21 owners at about 1.5 hours | 31 hours |
| Reconciling the group file with finance’s scorecard reports | Finance analyst | 4 hours |
Illustrative. Count your own; most teams undercount the owner preparation line.
That is about fifty hours a month, or roughly a week and a half of one person’s time, spread so thinly that nobody notices it. Over a quarter it’s about 150 hours.
The larger cost is in the timing. In this example the review pack is built from values collected six to ten days before the meeting. In month two, the service network priority reports 70% complete; the services KPI it was meant to move is flat. Both numbers are in the pack, on different slides. Nobody puts them side by side until the quarterly review, by which time the priority is at 88% and another two months of a regional team’s time have gone into a bet that wasn’t paying off.
The fifty hours are the visible cost. The two months are the real one.
A five-minute self-check
Count the statements that are true for your program today.
- Different owners. Most priorities are owned by people who don’t own the KPIs they’re correlated to.
- More than one level. At least one site, region or function keeps its own matrix linked to the corporate one.
- A keeper. One person spends more than a day a month collecting, pasting and formatting matrix data.
- Stale reviews. Review packs are built from data that is more than a week old by the time of the meeting.
- No history. You couldn’t say, from the file alone, which targets changed this year and why.
None or one true: stay on the spreadsheet and tighten it using the four steps below. Two or three: you’re at the threshold, and software will start paying for itself as the program grows. Four or five: the spreadsheet is already costing you the thing hoshin kanri is for, which is finding out early.
Excel vs hoshin kanri software, side by side
| Capability | Well-run spreadsheet | Hoshin kanri software |
|---|---|---|
| Drafting the matrix in a workshop | Excellent: fast, flexible, familiar | Good, if decisions are captured live |
| Graded correlations | Possible as symbols; not records | Records with grades and owners on both ends |
| Priority vs KPI comparison | Manual side-by-side sheet | Built in, often as a chart |
| Multiple editors | Fragile; usually centralized through one person | Each owner checks in on their own rows |
| Cascade across levels | Separate files linked by hand | One model across levels |
| History | Manual monthly snapshots | Kept by default |
| Catchball record | Email and meeting notes | Thread on each objective |
| Cost | Free | License plus implementation |
The spreadsheet wins clearly on the first and last rows. Everything in between is where programs with more than one level and more than one owner start to struggle.
If you stay on Excel, do these four things
Plenty of programs should stay on spreadsheets for now. If yours is one of them, these changes remove most of the risk.
- Add a correlation tab. One row per dot, with its grade, both owners, mechanism, lag window and kill signal. The grid is the picture; the tab is the record.
- Put priority and KPI progress side by side. A simple sheet that lists each primary correlation with the priority’s progress next to the KPI’s progress makes outcome lag visible without any software.
- Snapshot monthly. Save a dated, read-only copy after every review. It’s crude version control, and it’s the history you’ll want at the reset.
- Lock the structure. Protect everything except the cells each owner updates, and give each cell exactly one owner.
Signals that it’s time to switch
Programs rarely cross all four breaking points at once. They tend to show up in a predictable order, and each one is a reasonable moment to reconsider.
| Signal | What usually triggers it | What to do |
|---|---|---|
| A second matrix appears | A site or function wants its own plan linked to the group one | Decide now how levels will connect; this is the first fork |
| A keeper role forms | Updates are centralized to stop broken files | Count the hours; it’s the start of your business case |
| A review discovers a losing bet late | A priority finished and its KPI never moved | Run the self-check above; the comparison is overdue |
| The annual reset starts from scratch | Nobody can reconstruct last year’s target changes | Snapshot now, and plan the move before the next cycle |
The cheapest moment to move is before a planning cycle, because the new tool can hold the reflection on the old year and the plan for the new one. Moving mid-year works too; the guide to migrating your X-matrix from Excel or PowerPoint covers both.
The honest case for staying
If your program passes the self-check with none or one statement true, moving now may cost more attention than it saves. Spend that attention instead on the four spreadsheet improvements above, and revisit at the next planning cycle. Software is worth adopting when it removes a problem you have, not one you might have later.
What hoshin kanri software adds that Excel can’t
A hoshin kanri Excel alternative should remove the keeper role by having owners check in directly, keeps the correlation as a record with both ends live, holds every level of the cascade in one model, and keeps history by default. The seven pass/fail tests for choosing hoshin kanri software turn those requirements into questions you can ask in a demo.
In Profit.co, the X-matrix reads from owners’ check-ins, each objective shows its contributing key results and mapped KPIs, and the bowler chart shows monthly plan against actual with each owner’s latest comment. There’s more on the hoshin kanri software overview.
Catchball captures every exchange so commitments are agreed rather than inherited, and Review Huddles run the monthly and quarterly cycle.
Profit.co is a strategy execution platform rather than standalone X-matrix software, so the annual X-matrix and the quarterly OKRs underneath it draw on the same check-ins. That distinction matters once you start shortlisting: most strategy execution software stops at the goal layer, and most strategic planning software stops at the plan. The overlap between the two is usually what decides whether you buy one tool or run two.
The four breaking points, answered
| Breaking point | What answers it in Profit.co |
|---|---|
| Priority owners and KPI owners are different people | Bowler Chart tracks targets against actuals each period, and KPI Tracking monitors every indicator in real time, so the two sit side by side |
| The matrix cascades more than one level | One X-Matrix links vision, annual objectives, improvement priorities and KPIs in a single view across levels |
| More than one person updates results | Ownership Assignment gives every goal, initiative and KPI a named owner, and each owner checks in on their own rows |
| You need history | The OKR Audit Log records every change to objectives with timestamps, part of the platform’s complete audit history |
What hoshin kanri software costs
Most of the cost question is settled before anyone sees a quote. Four variables move the number:
- Who needs a seat. Priority owners and KPI owners have to check in; everyone else only reads. Pricing that charges for readers costs far more than pricing that doesn’t.
- How many levels you cascade. One corporate matrix is a small deployment. Corporate plus four sites is a different conversation about setup and training.
- What you migrate. Loading this year’s X-matrix takes hours. Loading three years of history, so the annual reset has something to read, takes longer.
- Whether the same tool runs your OKRs. If the quarterly goals under the annual matrix live in the same place, you are consolidating two line items rather than adding one.
That last variable is the one most often mispriced on an evaluation sheet. In Profit.co, Hoshin Kanri sits inside the Essentials plan alongside OKRs & Goals, Balanced Scorecard and Strategy Roadmap rather than being quoted as a separate product, and the plan carries a 30-day free trial. Enterprise is quoted separately for multi-entity deployments that need SSO, data residency and audit logs. Current pricing is published here, and what drives the cost of hoshin kanri software compares both sides in full.
Against that sits the spreadsheet’s bill from the worked example above: roughly 150 hours a quarter of visible admin, plus the months of budget that keep flowing to a priority nobody has put next to its KPI yet.
Free Product Demo
See your spreadsheet matrix running live
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
Yes. A well-kept spreadsheet works for a single site with a short priority list and one planning team that reviews the matrix together each month. It is also a good surface for drafting the X-matrix in a workshop.
When two or more of these are true: priority owners and KPI owners are different people, the matrix cascades to sites or functions, one person spends more than a day a month maintaining it, review data is more than a week old, or you can’t reconstruct why targets changed.
The visible cost is the time spent collecting and formatting data, often tens of hours a month across owners. The larger cost is decision latency: a priority that isn’t moving its KPI keeps its people and budget for months before the review notices.
Add a correlation tab with one row per dot, put priority and KPI progress side by side, save a dated read-only snapshot after every review, and lock everything except the cells each owner updates.
Not always. Excel is enough for one site and one team. Software pays off once two or more breaking points apply: priority and KPI owners differ, the matrix cascades across levels, several people update results, or you need history.
Four variables set the price: how many owners need a seat, how many levels you cascade, how much history you migrate, and whether the same tool runs your OKRs. In Profit.co, Hoshin Kanri is part of the Essentials plan rather than a separate purchase.
