A hoshin dashboard that averages progress across the plan will usually look reassuring, because averages hide exceptions. The useful dashboard does the opposite: it leads with the few things that need a decision.
In this guide
Key Takeaways
- →A plan can be 64% complete with its most important bet failing. Averages hide exactly that.
- →Lead with five things: outcome lag, persistent reds, trajectory, countermeasures due, stale check-ins.
- →Leave out overall percentage complete, counts of green rows and activity metrics.
- →The bowler is where the full KPI list belongs. The dashboard is for what needs attention.
- →Executives, site leaders and owners need different first screens, not the same one.
- →Nothing on a good executive view is green, and that is intentional.
The reassuring dashboard
A typical hoshin dashboard opens with a summary: the plan is 64% complete, 18 of 24 rows are green, overall status amber. Below that, a grid of charts. It looks thorough, and it answers no question anyone in the review needs answered.
Averages and counts hide exactly what hoshin is meant to surface. A plan can be 64% complete with its most important bet failing, and 18 green rows can include the six priorities whose KPIs aren’t moving.
What to show
| Element | Why |
|---|---|
| Objectives in outcome lag | Work done, results not following: the most important hoshin signal |
| Rows red two months or more | Persistent gaps that need an A3 or a decision |
| Breakthrough trajectory | Cumulative progress against the multi-year path |
| Countermeasures due for checking | Last month’s expected effects, worked or not |
| Stale check-ins | Rows whose data is older than the cadence, so nobody trusts a stale number |
The first row has a chart of its own, and the fourth has a document of its own: The Four-Quadrant Chart: Plotting KPIs Against Initiatives in Hoshin Kanri and Countermeasure Sheets in Hoshin Kanri: Tracking Actions on Off-Track Objectives.
What to leave out
- Overall percentage complete. It averages bets that are working with bets that aren’t.
- Counts of green rows. Green rows need no discussion; counting them invites complacency.
- Every KPI as a chart. The bowler is the place for the full list. The dashboard is for what needs attention.
- Activity metrics such as tasks completed, which say nothing about whether results are moving.
A dashboard that makes everyone comfortable has failed. Its job is to make the right people uncomfortable about the right things.
The third point is a division of labor rather than a dismissal; what the full list should look like is in Bowler Chart Template for Hoshin Kanri: Structure, Formulas, Colors.
Different views for different people
| Audience | Leads with | Detail available |
|---|---|---|
| Executive team | Outcome lag, breakthrough trajectory, escalations | The full X-matrix |
| Site or division leaders | Their objectives’ status, contributions to group priorities | Their bowler rows |
| Owners | Their check-ins due and countermeasures to check | Their objective’s history |
Each of those views feeds a different meeting, and the formats for those meetings are in Hoshin Kanri Review Templates: Monthly and Quarterly Formats.
A worked example: an executive view
Here is a hypothetical executive view with five panels, each a decision or a question:
| Panel | Content in March |
|---|---|
| Outcome lag | Service network: 85% initiative, 20% KPI |
| Persistent reds | Site B on-time delivery (2 months); scope 3 share (3 months) |
| Breakthrough trajectory | Services: 31.8% against a required 32.5% at this point |
| Countermeasures to check | Price discount approval: worked; supplier qualification: pending |
| Stale check-ins | 2 rows not updated this month |
Nothing on this view is green, and that’s intentional. Each panel either needs a decision or tells the room which data to distrust.
In Profit.co, most of these panels already exist as views. The exception queue lists outcome-lag cases and delivery problems; the bowler chart carries check-in comments; the four-quadrant chart sits on each objective; open countermeasure A3s show their phase and, before their check date, “not yet judged” rather than a color; and check-in histories carry dates. See the Hoshin Kanri software page.
What a rebuilt dashboard costs
A dashboard assembled by hand has a monthly bill, and it is the same bill as the review pack: numbers exported, panels rebuilt, charts re-pasted, then circulated. The averages are cheap to produce, which is part of why they survive; percentage complete needs one formula, while outcome lag needs two progress measures per objective on a common period. The panels that cost the most to maintain are precisely the ones worth having.
The stale check-ins panel makes the point sharpest. It can only exist if every row carries a date, which a rebuilt pack usually strips. Without it, the review has no way to tell a green row from an unupdated one, and a plan can look settled because nobody has touched it for six weeks.
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 question decides whether the owner view in the table above can exist at all, because owners are the widest audience and the one a per-seat model prices out first.
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, so the three views draw on one set of records rather than three exports. What drives the cost of hoshin kanri software lists the rest to total, and Digital Tools for Hoshin Kanri: Bringing the X-Matrix Online covers the move off assembled packs. The 30-day free trial spans a full monthly cycle, including the stale-check-in panel filling up.
Free Product Demo
See your plan’s exceptions, not its averages
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
Exceptions: objectives in outcome lag, rows red for two months or more, breakthroughs behind trajectory, countermeasures due for checking and stale check-ins.
Because it averages working and failing bets, so a plan can look healthy while its most important priority isn’t moving its KPI.
No. Executives need exceptions and trajectory; site leaders their objectives and contributions; owners their due check-ins and countermeasures.
Because a row nobody has updated looks the same as a row that is fine. Flagging data older than the cadence tells the review which numbers to distrust.
No. The bowler chart is where the full list belongs. The dashboard is for what needs attention, which is a much shorter list.
No, it is the design. Every panel should either need a decision or tell the room which data to distrust. Rows that are fine do not need the space.
