Most hoshin plans set monthly plan values by dividing the annual target into twelve equal steps. Almost no result moves that way. The bowler then shows red for months for reasons everyone expected, and the review learns to ignore red.
In this guide
Key Takeaways
- →The bowler is only as good as its plan row. A straight line on a result that ramps produces expected reds.
- →A review that sees expected reds month after month stops treating red as a signal.
- →Four shapes cover most results: linear, ramp, step and seasonal.
- →Record the go-live date for a step, so a delay shows as a delay rather than an unexplained miss.
- →Agree cumulative or period per row at planning. Mixing the two confuses every review.
- →The owner agrees the phasing during catchball, not after.
The cost of a straight line
The bowler chart compares plan with actual each month. That comparison is only as good as the plan row. If the plan row is a straight line and the result is seasonal, or ramps slowly, or arrives in a step when a project goes live, the bowler shows red in months where everything is going as expected.
A review that sees expected reds month after month adapts in the worst way: it stops treating red as a signal. By the time a real problem appears, red no longer gets attention. The countermeasure discipline collapses, because owners can rightly say the red was never real.
Four path shapes
| Shape | How the result moves | Typical examples |
|---|---|---|
| Linear | Steadily through the year | Cost run-rates from contracts already signed |
| Ramp | Slowly at first, then faster | Adoption of a new tool or service; new sites maturing |
| Step | Flat, then jumps when something goes live | A new production line; a pricing change on a set date |
| Seasonal | Follows the business’s usual pattern | Sales, order intake, maintenance revenue |
Choosing the shape is part of agreeing the target. The trajectory method already asks how the KPI is expected to move between now and the breakthrough; phasing applies the same question within the year.
How to phase each shape
- Linear: equal steps. Use only when there’s a reason to expect steady movement.
- Ramp: small steps early, larger later. A simple approach is to put about a quarter of the year’s movement in the first half and the rest in the second, then adjust from experience.
- Step: flat until the go-live month, then the step, then any expected growth. Record the go-live date as part of the plan, so a delayed go-live shows up as a delay rather than as an unexplained miss.
- Seasonal: use last year’s monthly pattern as the template, scaled to this year’s target.
| Quarter | Linear plan | Ramp plan | Actual |
|---|---|---|---|
| Q1 | 25% | 10% | 11% |
| Q2 | 50% | 25% | 27% |
| Q3 | 75% | 55% | 53% |
| Q4 | 100% | 100% | — |
Illustrative cumulative progress for an adoption priority. Against the linear plan it is red all year; against the ramp it is on plan.
Cumulative or period values?
Agree at planning whether each plan row shows cumulative progress (year to date) or the value for each month. Mixing the two across objectives is a common source of confusion in reviews. Cumulative values suit objectives measured as progress towards a year-end target; period values suit run-rate KPIs such as monthly on-time delivery.
The plan row is a prediction. If it predicts movement nobody expects, every month it’s wrong teaches the review something false.
The phasing gate
- Shape chosen, with a reason, for every objective and KPI.
- Step dates recorded for anything that goes live on a date.
- Seasonal patterns sourced from actual history.
- Cumulative or period agreed for each row.
- Owner agreed the phasing during catchball, not after.
In Profit.co, each objective takes monthly plan values that appear in the bowler chart alongside actuals and a performance score, and the check-in trend shows actual against plan over the year. Phasing set at lock becomes the plan row the first review runs from. More on the planning software page.
What phasing needs from the software
The gate above is five checks, and four of them are storage questions. A shape with a reason, a go-live date, a seasonal pattern drawn from history, and a per-row choice between cumulative and period all have to live somewhere the review can read them nine months later.
The first question to ask a vendor is blunter than that, though: can a plan row be phased at all? A tool that stores one annual target per objective cannot produce a monthly plan, so the bowler has nothing to compare against and the review falls back on a status color.
| Gate check | What the tool has to hold | How to test it in a demo |
|---|---|---|
| Phasing at all | Twelve monthly plan values per row, editable | Phase one objective unevenly across the year |
| Shape with a reason | A note on the row saying why this shape | Show me why this KPI ramps rather than runs flat |
| Step dates | A go-live date the plan row is built around | Move a go-live by a month and re-phase from there |
| Seasonal from history | Last year’s monthly actuals, available to copy | Build this year’s pattern from last year’s |
| Cumulative or period | A per-row setting, visible in the review | Show me which of these rows is year to date |
| Agreed in catchball | The phasing inside the negotiation, not added later | Show the owner agreeing the monthly values |
| It reaches the bowler | Plan against actual, month by month, with a score | Show January’s review running from this row |
Row 1 is cheap to ask and expensive to discover in January.
Row 4 is the one that makes seasonal phasing practical rather than theoretical. Without last year’s monthly actuals to hand, “use last year’s pattern” means someone reconstructing twelve numbers from a finance export in week twelve, which is when it gets skipped and the straight line goes in instead.
What a false red costs
Take the worked example literally. Against the linear plan that adoption priority is red in Q1, Q2 and Q3 while running almost exactly to its real path. Three quarters of red on a row that is fine. By the fourth review nobody is reading that row carefully, and the review has learned something false about every other red on the page too.
That is the expensive part. The cost is not the one misphased row; it is the credibility of the color across the whole bowler. Once red is discounted, the genuinely failing bets get the same shrug as the timing artifacts.
On the invoice side, the published models vary in shape. 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. For this stage the relevant question is not price but row 1 of the table: a tool that holds only an annual target cannot phase anything, whatever it costs.
Profit.co publishes two plans, Essentials and Enterprise, and quotes against modules and scale rather than a public seat rate. Monthly plan values feed the bowler chart directly, and Hoshin Kanri sits in Essentials with OKRs and Goals, Balanced Scorecard and Strategy Roadmap, so the check-in history that makes seasonal phasing possible is generated by the teams running the year. What drives the cost of hoshin kanri software sets out the rest.
The 30-day free trial is enough to phase one real objective four ways and see which plan row tells the truth.
Phasing in Profit.co
Read against the gate, each check has somewhere to sit. Monthly plan values are a property of the objective rather than a separate sheet, so phasing survives into the year. The bowler reads them as the plan row and scores actual against plan month by month, which is what makes a red mean something.
Seasonal shapes draw on the same place the reflection reads: last year’s check-in history, already in the system rather than reconstructed from a finance export. And because phasing is agreed inside catchball rather than added afterwards, the owner who will be asked about a red month in April is the person who agreed the shape in November.
Free Product Demo
See your plan with phasing that fits
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
By the shape of the path the result is expected to follow: equal steps for steady movement, small then larger steps for adoption, flat then a jump for go-live dates, and last year’s pattern for seasonal results.
Most results don’t move evenly, so linear plans produce expected reds early in the year. Reviews then stop treating red as a signal.
Either, but agree it per row at planning. Cumulative suits progress towards a year-end target; monthly suits run-rate KPIs like on-time delivery.
Linear for steady movement, ramp for adoption that builds, step for results that jump at a go-live date, and seasonal for anything that follows the business’s usual pattern.
So that a delayed go-live shows up as a delay rather than an unexplained miss. Without the date, a step that arrives a month late looks like under-performance.
Hold twelve editable monthly plan values per row, keep the reason for the shape and any go-live date, make last year’s actuals available for seasonal patterns, and feed the bowler chart directly.
