In this guide
- What a bowler chart is
- The color parade
- The countermeasure rule
- A worked example: one objective, six months
- Reading a bowler page in ten minutes
- Getting the plan row right
- Reading the bowler with the matrix
- Escalation rules and leading rows
- What to look for in bowler chart software
- Bowler charts in Profit.co
- Questions this article answers
Key Takeaways
- →A bowler chart and a bowling chart are the same thing: monthly plan against actual for every hoshin objective.
- →The colors are not the value. The rule is: no red cell without a cause, a countermeasure, an owner and a recovery date, written before the review.
- →Two consecutive reds should trigger structured problem-solving, usually an A3, not another one-line comment.
- →Most bowlers fail on the plan row. Twelve equal steps makes rows go red for entirely expected reasons, and the review learns to ignore red.
- →A bowler is not a dashboard. Most KPI dashboard software has no plan row and no owner’s comment, which is the first thing to check when buying.
- →Put leading rows next to lagging ones. Leading rows turn red first, which is the only way a countermeasure gets time to work.
A bowler chart without countermeasures is a color chart. The review spends its time agreeing that red is bad. The discipline that makes the bowler useful is simple: no red cell without a cause, an action and a date.
What a bowler chart is
The bowler chart, also called a bowling chart, is the monthly tracking view of hoshin kanri. Each objective or KPI gets a block of rows: the plan for each month, the actual result for each month, and usually a status color comparing the two. Months run across the columns. Read across a row and you see the year unfold; read down a column and you see the whole plan at one moment.
It’s simple, which is its strength. Anyone can read it. A review can scan a page of bowler rows in a minute and see where the plan is holding and where it isn’t.
That simplicity also invites a failure.
The color parade
In many monthly reviews, the bowler becomes the agenda. The facilitator walks down the rows. Green rows get a nod. Amber rows get a sentence. Red rows get a discussion that sounds substantive but mostly establishes that the owner knows it’s red and intends to improve.
The same rows are red next month. The discussion repeats. After three months, red stops carrying information, because nothing follows from it.
The bowler chart’s job isn’t to show what’s red. It’s to make sure every red has a plan attached before the meeting starts.
The countermeasure rule
Lean practitioners already know the fix: every gap between plan and actual needs a countermeasure. In bowler terms, that becomes one rule for owners, applied before the review rather than in it.
- Cause. What explains the gap, in a sentence. Not “delays”, but which delay and why.
- Countermeasure. What is being done about it, specifically.
- Owner. Who is doing it, if not the row owner.
- Recovery date. When the row is expected to return to plan.
A red row with all four is ready for review. A red row missing any of them isn’t, and the review’s first action is to send it back. That one change shortens meetings and moves the thinking to the person with the most information.
A common escalation rule adds a second layer: a row red for two consecutive months gets a structured problem-solving exercise, often an A3, rather than another one-line countermeasure.
A worked example: one objective, six months
Here is a bowler block for one objective, with the comments that the countermeasure rule requires.
| Apr | May | Jun | Jul | Aug | Sep | |
|---|---|---|---|---|---|---|
| Plan | 33% | 41% | 49% | 58% | 66% | 75% |
| Actual | 33% | 42% | 50% | 50% | 54% | 42% |
| Status | Green | Green | Green | Amber | Amber | Red |
Illustrative: return North America to order growth. Cumulative progress against a phased plan.
| Month | Owner’s check-in comment |
|---|---|
| Jul | Cause: two large orders slipped to August after customer budget freeze. Countermeasure: none needed; both confirmed for August. Recovery: August. |
| Aug | Cause: one of the two orders landed; the other moved to Q4. Countermeasure: pull forward three mid-size quotes in the Midwest pipeline. Owner: regional sales lead. Recovery: October. |
| Sep | Cause: dealer channel orders down 30% after a competitor’s price cut. Countermeasure: pricing review with commercial, decision by 15 Oct; escalating as second consecutive off-plan month. Recovery: Q4 at risk. |
Read top to bottom, the comments tell the story the colors can’t. July was timing and needed nothing. August was a partial recovery with a specific action. September is a different problem altogether, an external force, and the owner has escalated it themselves. The review spends its time on September’s pricing decision, not on whether the row is red.
Reading a bowler page in ten minutes
A full bowler can run to several pages. A disciplined reading order keeps the review on the rows that matter.
| Minute | Look for | Why |
|---|---|---|
| 0 to 2 | Rows red for two or more consecutive months | Persistent gaps need escalation, not another comment |
| 2 to 4 | Rows that turned red this month for the first time | Check the cause and countermeasure are specific |
| 4 to 6 | Red rows without a cause, countermeasure, owner or date | Send back before discussion |
| 6 to 8 | Green priority rows correlated to red KPI rows | Possible outcome lag; switch to the correlation view |
| 8 to 10 | Rows recovering on the date their countermeasure promised | Confirms the discipline is working |
Bowler chart vs dashboard
A dashboard shows the current state of many measures. A bowler shows a planned path, the actual path and the owner’s explanation of the gap, month by month. That makes it a management tool rather than a reporting one: it asks, every month, what will be done about the gap. Teams that replace their bowler with a dashboard often find reviews become more informative and less decisive.
Getting the plan row right
A bowler is only as useful as its plan row, and plan rows are often set lazily: the annual target divided into twelve equal steps. Real results rarely move that way. Sales are seasonal, emissions programs ramp, site improvements land in steps.
If the plan is linear and the business isn’t, rows go red early in the year for reasons that are entirely expected, and the review learns to ignore red. Phase the plan to match how the result is expected to move, and agree that phasing during catchball. It takes an hour per objective and makes every month after that more honest.
Reading the bowler with the matrix
A bowler shows each row on its own terms. It doesn’t show whether a green priority is moving a red KPI. For that, the bowler needs to be read alongside the X-matrix correlations, or alongside a view that plots initiative progress against KPI progress. A row can be green and still be part of a losing bet. (See Outcome lag: when priorities are green and KPIs don’t move.)
The strongest reviews use both: the bowler for “is each row on plan?”, the correlation view for “is the plan working?”
Escalation rules and leading rows
When a red row escalates
| Condition | Response |
|---|---|
| Red for the first time | Cause, countermeasure, owner and recovery date in the check-in |
| Red for two consecutive months | Structured problem-solving, such as an A3, before the next review |
| Red for three months, or recovery date missed twice | Decision at the quarterly review: change the countermeasure, the target or the priority |
| Red because of an external force | Owner flags it; the quarterly review decides whether to reopen the target through catchball |
Put leading rows on the bowler
Many bowlers show only lagging results: revenue, margin, emissions. Those move slowly and confirm problems late. Add a row for the leading measure paired with each lagging KPI, such as contract attach rate alongside services share. Leading rows turn red first, which gives countermeasures time to work before the lagging row confirms the problem. Choosing those pairs is covered in Writing KPIs for the X-matrix.
What to look for in bowler chart software
Most programs build their first bowler in a spreadsheet, and it works until the plan row, the actual values and the owner’s comment stop arriving from the same place. At that point someone assembles the chart the night before the review, and it is stale by the time the meeting opens. The specification for replacing it is short, and almost none of it appears on a feature list.
| What the bowler needs | Why it matters | How to test it in a demo |
|---|---|---|
| Actuals that arrive from owners’ check-ins | A chart one person assembles is out of date the day after the review | Ask whose job it is to enter this month’s actuals |
| A plan row that can be phased by month | Twelve equal steps is the single most common reason bowlers stop being believed | Ask whether the plan can be set month by month or only as an annual target |
| The comment attached to the cell | Cause, countermeasure, owner and date have to live on the red cell, not in separate minutes | Ask to see last March’s countermeasure from this month’s view |
| Consecutive-red detection | The escalation rule is worthless if nobody notices the second red | Ask what the tool does differently on a second consecutive red |
| Leading rows beside lagging rows | Leading rows turn red first, which is the whole point of having them | Ask whether a leading measure sits in the same block as its lagging KPI |
| A correlation view alongside | The bowler cannot show a green priority sitting against a red KPI | Ask to see initiative progress plotted against KPI progress |
Six rows. The first two decide whether the chart is trusted; the rest decide whether it is acted on.
Why a dashboard tool usually isn’t the answer
The distinction drawn above between a bowler and a dashboard has a direct buying consequence. Most KPI dashboard software is bought to answer where are we, and renders a current value beautifully. A bowler is bought to answer what will be done about the gap, which needs three things a dashboard rarely has: a planned path, an owner’s written explanation, and a rule about what happens next. A product can be excellent KPI tracking software and still have no plan row at all, so that is the first thing to check rather than the last.
It is also worth asking where the bowler gets its numbers. If KPI values live in an ERP, finance or BI system, the chart either pulls them through an integration or someone re-keys them every month, and re-keying is how a bowler quietly goes stale again after the tool was bought to stop exactly that.
What the spreadsheet bowler actually costs
The case for buying is rarely made on features, because the spreadsheet bowler does have the features. It is made on what the spreadsheet costs to keep alive, and that number is almost never counted before someone asks for budget.
| Line | Spreadsheet bowler | Bowler chart software |
|---|---|---|
| Who enters this month’s actuals | One person, chasing owners by email in the week before the review | Each owner, at check-in |
| How current the chart is at the meeting | As current as the night it was assembled | Current when the meeting opens |
| Where the countermeasure lives | A comment column, the minutes, or somebody’s inbox | On the cell, readable a year later |
| Noticing a second consecutive red | Someone has to remember last month | Detected and escalated by rule |
| Rebuilding the file each year | A fresh workbook, and last year’s history effectively closed | The same objectives, with history intact |
| The recurring cost | Program lead hours every month, indefinitely | A subscription, and those hours back |
Count the last row at a loaded hourly rate before comparing it with any quote.
Put real numbers in the bottom row before you ask anyone for budget. Twenty hours a month of a program lead’s time, costed properly, is usually larger than the license being argued over, which is the argument what drives the cost of hoshin kanri software makes in full and building the business case for hoshin kanri software turns into a one-page template. The bowler is simply where the cost is easiest to see, because the hours are spent on a visible artifact every single month.
Bowler charts in Profit.co
Profit.co’s bowler chart shows each objective and its key results by month, with plan, actual and a performance score for each, cells colored by status, and the owner’s last check-in comment alongside. Values come from owners’ check-ins, so the chart is current before the meeting without anyone building it.
When a row needs more than a one-line countermeasure, a countermeasure A3 opens straight from the red or amber cell, filled with the row and its gap. The A3 then follows the escalation rules above inside the product rather than in a separate document. More on the hoshin kanri software overview.
The bowler sits in the Essentials plan alongside OKRs and Goals, Balanced Scorecard and Strategy Roadmap, so the same check-in that updates a team key result updates the hoshin row it feeds, and a scorecard perspective reads from the same numbers rather than a second import. The 30-day free trial is long enough to load one objective and run a single monthly cycle on it, which tests the plan row and the comment discipline better than any demo will.
Free Product Demo
See your objectives as a live bowler
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
The monthly tracking view of a hoshin plan: for each objective or KPI, a row of planned values and a row of actual values by month, usually colored to show whether actual is on plan.
None. Both names describe the same monthly plan-versus-actual chart used in hoshin kanri.
The cause in a sentence, the countermeasure being taken, who owns it, and the date the row is expected to return to plan.
Usually because plan rows are split evenly across twelve months when results don’t move that way, so rows go red for expected reasons and the review learns to ignore red, or because red cells carry no countermeasure.
One where actuals arrive from owners’ check-ins, the plan row can be phased month by month, and the cause, countermeasure, owner and recovery date sit on the red cell. Most KPI dashboard software has no plan row at all.
Yes, and most programs start there. It breaks when the plan row, the actuals and the owner’s comment stop arriving from the same place, so the chart gets assembled the night before and is already stale when the review opens.
