Every guide to hoshin kanri says to focus on the vital few. Few say how few, and the honest answer is that there’s no universal number. There is, though, a way to find yours, and it isn’t a matter of opinion.
In this guide
Key Takeaways
- →There is no universal number. There are two measurable limits, and the tighter one wins.
- →Review capacity: most executive teams can give real attention to eight to fifteen group-level priorities.
- →People capacity is usually tighter, and last year’s reflection gives the real effort figures to use.
- →Link, score, rank, cost, cut. Draw the line where cumulative effort passes capacity.
- →Watch for bundling. Five priorities under one broad name is still five priorities.
- →Work below the line doesn’t have to stop. The matrix is for change you commit to manage, not everything you do.
Why the list keeps growing
The phrase “the vital few” comes from Joseph Juran’s work on quality: a small number of causes usually account for most of the effect. Hoshin kanri borrowed the idea for priorities. A small number of well-chosen, well-staffed priorities will move the plan further than a long list of reasonable ones.
Planning rooms agree with this and then produce long lists anyway. Each proposal is sensible on its own. Each has a sponsor. Cutting one feels like a judgment on the person who proposed it. And there’s no obvious stopping point, so the list stops when the room gets tired.
The way out is to replace the vague question, “is this important?”, with two measurable ones.
Limit 1: review capacity
A priority on the X-matrix is a commitment to look at it every month. If the monthly review has ninety minutes and a priority needs, on average, five minutes of real discussion when it is off track, and about a third of priorities are off track at any time, the review can sustain roughly fifty priorities in theory. In practice, outcome-lag cases and escalations take much longer than five minutes. Most executive teams find they can give real attention to somewhere between eight and fifteen group-level priorities.
Work out your own figure from the review you actually run. It’s the upper limit; going above it means some priorities will be on the matrix but never discussed.
How that review is structured across the month, quarter and year is covered in hoshin review cadence, and why off-track cases eat the clock in Outcome lag.
Limit 2: people capacity
The tighter limit is usually people. Each priority needs an owner with real time and a team that can do the work alongside everything else. The reflection on last year gives you the real figures: how much effort priorities actually consumed compared with what was planned.
Add up the effort this year’s candidate priorities need, using real rather than optimistic estimates, and compare it with the capacity of the people who would do the work after their existing commitments. The point where demand exceeds capacity is the cut line. See the capacity check for the method.
The right number of priorities is the number you can staff and review. Everything above that is a list of intentions.
A method for cutting the list
| Step | What happens |
|---|---|
| 1. Link | Each candidate must serve at least one annual objective. Candidates that don’t are dropped or held. |
| 2. Score | Score each on expected contribution to its objective and confidence in the mechanism, using last year’s verdicts as evidence where relevant. |
| 3. Rank | Force-rank by the two scores together. No ties. |
| 4. Cost | Add each candidate’s real effort in rank order. |
| 5. Cut | Draw the line where cumulative effort exceeds capacity, or where the count exceeds review capacity, whichever comes first. |
| 6. Decide the rest | Below the line: stop, defer, or run as business as usual without a place on the matrix. |
Step 6 matters. Work that doesn’t make the matrix doesn’t have to stop. Much of it is good work that should continue as part of normal operations. The matrix is for the change the organization is committing to manage, not for everything it does.
The bundling trick
One way rooms evade the limit is bundling: merging five priorities into one with a broad name like “operational excellence program” so the count looks short. The matrix then has a few rows with many owners, vague measures and no clear correlation.
- One owner. A priority has one accountable owner who can speak to all of it.
- One mechanism. Its main correlation can be stated in one sentence.
- Measurable change. At least one measure shows the change it causes, not just the activity.
A bundle that fails these is several priorities. Count them as such.
A worked example: from 16 candidates to 7
Sixteen candidates survived the link step. The team ranked them and added up real effort, with a 1.5× multiplier from last year’s reflection, against roughly 60 person-months of capacity for priority work.
| Rank | Candidate | Effort (person-months) | Cumulative |
|---|---|---|---|
| 1 | Complete service network | 12 | 12 |
| 2 | Multi-year service contracts | 8 | 20 |
| 3 | Pricing discipline, wave 2 | 6 | 26 |
| 4 | Low-carbon steel agreements | 9 | 35 |
| 5 | Site maturity, wave 2 | 14 | 49 |
| 6 | Technician certification | 5 | 54 |
| 7 | Dealer quoting tool | 6 | 60 |
| 8 | Customer portal relaunch | 10 | 70: below the line |
| 9 to 16 | Eight further candidates | 46 | — |
Illustrative.
The line falls after rank 7. The customer portal, a popular proposal, misses by ten person-months. Rather than squeezing it in, the team defers it to a second-half start if the service network finishes on time, and records that decision. Four of the remaining eight continue as business as usual; four stop.
What the cut needs from the software
Three of the six steps above are arithmetic over data the organization already has. Step 2 scores candidates partly on confidence in the mechanism, and last year’s verdicts are the evidence. Step 4 adds up real effort, which comes from what priorities actually consumed. Step 6 records what happens to everything below the line.
Where that data sits in a tool, the cut is a two-hour session with numbers on screen. Where it doesn’t, the room falls back on opinion, and opinion is exactly what produced the long list.
| Step | What the tool has to supply | How to test it in a demo |
|---|---|---|
| 1. Link | A candidate cannot be saved without an objective it serves | Try to add a priority that serves nothing |
| 2. Score | Last year’s verdict and outcome-lag position for similar bets | Show me what happened to this priority’s predecessor |
| 4. Cost | Planned versus actual effort per priority from last year | Show me a priority that took double its allocation |
| 5. Cut | Cumulative effort against capacity, visible while ranking | Reorder the list and show the running total move |
| 6. Decide the rest | A place for deferred and stopped work that stays visible | Defer a candidate and show me where it lives now |
| After the cut | Rows with no check-ins, so over-full matrices show themselves | Show me priorities nobody updated last quarter |
The last row is the honest check on limit 1, and it only arrives in March.
Row 6 deserves the weight. Review capacity is a prediction made in October, and the matrix tells you whether the prediction held. Priorities with no check-in history, or that never appear in a review, are the ones that went over the line. That evidence is what makes next year’s number a figure rather than a guess, which is the argument this article opens with.
What an over-full matrix costs
Going three priorities over the line has a price, and it isn’t the software. It is three initiatives staffed at half strength, a review that runs long and skips the quiet rows, and a reflection next October that has to mark several bets “not tested” because the capacity was never there. The expensive mistake happens in the room, not on the invoice.
That said, the invoice shapes the room more than most buyers expect. 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. Step 2 of the method needs last year’s verdicts, and step 4 needs real effort figures, both of which come from the people doing the work rather than the planning team. Per-seat pricing quietly argues for keeping those people out of the system, which is how a room ends up ranking on opinion again.
Profit.co publishes two plans, Essentials and Enterprise, and quotes against modules and scale rather than a public seat rate. The point for this stage is scope: Hoshin Kanri sits in Essentials with OKRs and Goals, Balanced Scorecard and Strategy Roadmap, so a priority that survives the cut carries into the quarter as team OKRs on the same data model, and the check-in history those teams generate is what step 2 and step 4 will read twelve months later. What drives the cost of hoshin kanri software covers the rest of what to total.
The 30-day free trial is enough to load last year’s matrix and run the cut on it as a dry pass, which also tells you how many priorities your review actually discussed.
The vital few in Profit.co
Profit.co helps keep the list honest after planning, too. Every priority on the X-matrix shows its owner and live progress, so a matrix with more priorities than its review can handle becomes visible quickly: rows nobody checks in on and nobody discusses. Last year’s check-in history and outcome-lag data provide the confidence evidence for step 2. More on the planning software page.
The bundling test benefits from the same structure. A priority is a row with one owner, so a bundle with four owners has to be entered as four rows, and the count the room was trying to hide reappears. Where a bundle genuinely is one piece of work, its single correlation can state one mechanism, which is the test in this article’s own list.
Free Product Demo
See how many priorities your plan can really carry
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
As many as your monthly review can discuss and your people can staff, whichever limit comes first. For many executive teams that is eight to fifteen at group level.
A phrase from Joseph Juran’s quality work: a small number of causes usually drive most of the effect. In hoshin kanri it means focusing on a few well-staffed priorities rather than many reasonable ones.
They can stop, be deferred with a date to reconsider, or continue as normal operations without a place on the matrix. The matrix is for change the organization commits to manage.
Apply three tests: one accountable owner who can speak to all of it, one mechanism stateable in a sentence, and at least one measure of the change it causes. A bundle that fails these is several priorities.
It supplies the two inputs the cut needs: last year’s verdicts for scoring confidence, and planned-versus-actual effort for costing candidates. It also shows which priorities were never discussed.
Yes. Look for rows with no check-in history and priorities that never came up in a monthly review. Those are the ones that went over the review capacity line.
