By March, most of the problems a hoshin plan will have this year are visible. Almost all of them were made in planning, months earlier. Here are the ten most common, what each looks like in the first quarter, and where in the planning cycle to fix it.
In this guide
Key Takeaways
- →A plan’s March is decided in its October. Almost nothing you see in Q1 is a performance problem.
- →Ten mistakes, each with a distinct Q1 symptom and a specific planning stage to fix it in.
- →Skipping the reflection costs two years, not one, because the losing bet is re-placed and loses again.
- →Too many priorities and nothing stopped travel together, and they produce the same symptom.
- →Green priorities with flat KPIs is dot inflation, not under-performance. Asking for more effort fixes nothing.
- →Several of these can be partly repaired at the Q1 review rather than waiting a year.
Planning errors have a long fuse
Planning mistakes rarely show up during planning. The matrix looks complete, catchball closes, the plan is signed off. The first monthly reviews are a little rough, which is expected. By the third review, the roughness has a shape, and it traces back to decisions made in October and November.
This list is a diagnostic. If you are in the first quarter and seeing the symptoms, it tells you which stage to fix next cycle. If you are planning now, it tells you what to check.
Ten mistakes, ten symptoms
| Planning mistake | What you see by March | Fix it in |
|---|---|---|
| Skipped the reflection | Last year’s losing bets reappear with new names, and lag again | Hansei |
| Targets set forward from last year | Targets met comfortably while the breakthrough falls behind | Target setting |
| Too many priorities | Several rows nobody discusses, and some nobody checks in on | Vital few |
| Nothing stopped | New priorities slipping because teams are still on old work | Stop-doing |
| No capacity check | The same few people behind on everything | Capacity check |
| Dot inflation | Every priority green, several KPIs flat | Building the matrix |
| Activity KPIs | KPIs on track, business results not | Writing KPIs |
| Linear phasing | Red rows everyone explains away as timing | Phasing |
| Catchball unfinished | Targets still being disputed in reviews | Catchball round |
| No cadence set | Patchy check-ins, review packs built by hand | Locking the plan |
The three that cost most
Skipping the reflection
This one compounds. A bet that lost last year gets reworded and placed again, consumes another year of effort, and loses again. The cost is two years, not one, and it’s invisible unless someone compares the matrices side by side.
Too many priorities, with nothing stopped
These two travel together. The matrix commits to more change than the organization can staff, while all of last year’s work continues. By March the plan is being delivered in an order chosen by whoever shouts loudest, not by the plan.
Dot inflation
When every priority claims a strong link to every KPI it might touch, the review can’t tell which links are failing. The result is the pattern described in Outcome lag: green priorities, flat KPIs and a meeting that ends with a request to accelerate.
A plan’s March is decided in its October. The review can only manage the plan it was given.
If you’re already in March
You don’t have to wait for next year. Most of these can be partly fixed in the first quarterly review: regrade correlations, retire a priority or two, assign a stop-doing list, re-phase plan values, and set a check-in cadence if there isn’t one. See Replanning mid-year for how to do it without restarting the cycle. Then make sure next cycle’s reflection records what you changed and why.
A worked example: a March review, read backwards
| What the March review saw | Traced back to |
|---|---|
| Customer portal lagging again, its second year on the matrix | Reflection skipped; last year’s lost bet re-proposed |
| Eleven of fourteen priorities green; three of six KPIs red | Dot inflation: most priorities claimed strong links to most KPIs |
| Service operations behind on all four of its priorities | No capacity check |
| On-time delivery red since January | Linear phasing on a seasonal KPI |
| North America target disputed in the meeting | Catchball closed by deadline, not agreement |
Illustrative.
Five symptoms, five planning stages. None of them is a performance problem in the usual sense, and asking the owners to try harder would fix none of them. Each needs a change to how the plan was built: two can be repaired at the Q1 review, three need next year’s planning cycle.
Which mistakes the software can catch
Some of the ten are judgment failures that no product prevents. Nobody can stop a room choosing fourteen priorities when it has capacity for seven. But each mistake has a symptom, and a symptom is a query. The difference between a plan that corrects in March and one that limps to December is usually whether anyone could see the symptom without assembling a special analysis.
Worth separating the two. The first group is where a tool can enforce the discipline at planning time; the second is where it can only raise the alarm afterwards.
| Mistake | What the tool can do | How to test it in a demo |
|---|---|---|
| Skipped the reflection | Keep last year’s matrix and verdicts readable beside this year’s | Open a closed year next to an open draft |
| Too many priorities | List rows with no check-in history or no review appearance | Show me priorities nobody updated last quarter |
| No capacity check | Filter for people owning several rows | Show me everyone named against four priorities |
| Dot inflation | Flag green priorities whose correlated KPIs are flat | Show me everything in outcome lag today |
| Activity KPIs | Hold the KPI card, so a measure of work is visible as one | Click a KPI and show me its definition and type |
| Linear phasing | Monthly plan values per row, phased rather than divided | Phase a row unevenly and show the bowler |
| Catchball unfinished | “Closed” means every participant agreed, not that a date passed | Try to close a session with one participant unapproved |
| No cadence set | Check-in cadence as a property of the plan, with dates | Show me when the first check-ins are due |
Eight of the ten leave a trace. Forward targets and an empty stop-doing list are decisions, and they need the room.
Row 7 is the one worth pressing hardest in an evaluation, because “catchball closed” is the check most easily faked. A plan where the deadline passed and the thread stopped looks identical, in a document, to a plan where every participant agreed. Only one of them holds up in a March review. The structure that keeps that distinction is in catchball in software.
Row 4 is the one that saves the most time. Dot inflation produces the single most confusing meeting of the year, green priorities and flat KPIs, and the fix is a report rather than a discussion.
What these mistakes cost in a year
The worked example is five symptoms in one review, and it is worth pricing. The re-proposed portal is a second year of effort on a bet that already lost once. Service operations behind on four priorities is a team working at roughly half the rate the plan assumed. Three KPIs red against eleven green priorities means the executive team cannot tell which of its bets are working, for a quarter. None of that appears as a line item, and all of it is more expensive than any planning tool.
When comparing tools against that, the published figures vary in shape more than size. 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. Rows 2, 3 and 7 of the table above all depend on the delivery teams and the levels below being inside the system, so a per-seat model prices the visibility that catches these mistakes.
Profit.co publishes two plans, Essentials and Enterprise, quoting against modules and scale rather than a public seat rate. Hoshin Kanri sits in Essentials with OKRs and Goals, Balanced Scorecard and Strategy Roadmap, which matters for row 2 in particular: the check-in history that reveals an over-full matrix is generated by teams running their quarters on the same data model as the matrix above them. What drives the cost of hoshin kanri software covers the full list to total before comparing quotes.
The 30-day free trial is long enough to load your current matrix and results and check the first four rows against it, which is the quickest way to find out how many of the ten your plan is carrying.
Spotting the symptoms in Profit.co
Several of these symptoms show up directly in Profit.co: the four-quadrant chart puts green-priority, flat-KPI objectives in the outcome-lag quadrant; the bowler shows rows red against their plan values; owners appear on every row of the X-matrix, so one person carrying too much is visible; and check-in histories show where updates are patchy. More on the planning software page.
That covers four of the ten as reports rather than investigations: dot inflation, phasing, capacity and the over-full matrix. Catchball closing is explicit, since a session closes when every participant agrees, so mistake nine shows as sessions still open rather than as a dispute in the meeting. The two that remain, forward targets and an empty stop-doing list, are choices the room makes, and the place to fix them is target setting and the stop-doing list next October.
Free Product Demo
Find out which mistakes your plan is carrying
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
Skipping the reflection, setting targets from last year, too many priorities, no stop-doing list, no capacity check, inflated correlations, activity-based KPIs, linear phasing, unfinished catchball and no check-in cadence.
Skipping the reflection, because losing bets return with new names and lose again, costing two years rather than one.
Many can, at the first quarterly review: regrade correlations, retire priorities, assign a stop-doing list, re-phase plan values and set a check-in cadence.
That is dot inflation, made at planning. When every priority claims a strong link to every KPI it might touch, the review cannot tell which links are failing. Asking for more effort fixes nothing.
Eight of the ten leave a trace a tool can surface, including dot inflation, over-full matrices, capacity bottlenecks and unfinished catchball. Forward targets and an empty stop-doing list are decisions that need the room.
Ask whether more effort from the owners would fix it. If the answer is no, as with dot inflation, linear phasing or an unresolved capacity overload, it was built into the plan in October.
