Black Friday & Cyber Monday Sale·50% off·ends in 0d 0h 0m 0s

Claim offer
10 min read ·

Why Lean Strategy Deployment Stalls in Year Two

Bastin Bastin ·
Bastin Gerald, Founder and CEO at Profit.co

Bastin Gerald

Founder & CEO at Profit.co

Bastin Gerald is an entrepreneur, business strategist, and technology leader who pioneers AI-driven strategy execution at Profit.co. A published author, he has mentored over 250 leaders worldwide.

The first year of connecting hoshin to daily management usually goes well: new energy, visible wins, leaders closely involved. Year two is where many programs quietly stall. The causes are predictable, and so are the fixes.

Why does lean strategy deployment stall in year two? Lean strategy deployment often stalls in year two because easy wins are exhausted, the X-matrix is rebuilt without reflection, kaizen counts plateau unsteered, leader standard work lapses, escalations stop getting answers, and focus KPIs never rotate. The fixes are structural: a real reflection, rotated focus KPIs, response times for escalations, and leader routines that are checked.

Key Takeaways

  • →Year one runs on enthusiasm; year two runs on structure, or it doesn’t run.
  • →Six causes recur: easy wins gone, no reflection, unsteered kaizen, lapsed routines, unanswered escalations, stale focus KPIs.
  • →Falling strategic flags are the earliest signal, and the most ignored.
  • →Setting year two’s targets from year one’s results means no reflection happened.
  • →A published escalation response time restores flagging faster than any campaign.
  • →None of the fixes need new tools or new enthusiasm.

Six causes

CauseWhat it looks like
Easy wins exhaustedYear one fixed the obvious problems; year two needs harder ones
No reflectionThe second X-matrix is drafted fresh; year one’s lessons are lost
Unsteered kaizenImprovement volume holds but drifts back to local problems
Leader routines lapseStrategy items quietly drop out of leader standard work
Escalations unansweredFlags reach owners who don’t respond; the front line stops flagging
Stale focus KPIsThe same focus KPI for a year; teams lose interest

Year one runs on enthusiasm. Year two runs on structure, or it doesn’t run.

Read the year-two signals off your own records.

Flag counts, response times and improvement share, already there.

Book a demo →

Signals to watch

SignalSuggests
Strategic flags from huddles fallingFront line has stopped expecting answers
Share of improvement on strategic KPIs drifting downSteering has lapsed
Year-two targets set from year-one resultsNo reflection; forward targets
Monthly reviews shorter and quieterExceptions aren’t reaching them

All four are measurable from records the program already keeps, and all four move a quarter or two before the strategic KPIs do. That is the whole reason to watch them: by the time a breakthrough KPI reports a miss, the year is spent.

Structural fixes

Each fix below replaces something year one got for free. Enthusiasm supplied the reflection, the attention and the answers; year two has to supply them deliberately.

The order matters less than the fact that each one is checkable. A fix that depends on leaders caring more is not a fix, because caring more is exactly the resource that has run out.

Five structural fixes for a lean strategy stalling in year two, from running a real reflection to targeting harder problems with A3s
  • Run a real reflection before year two’s plan; see Hansei: Reviewing Last Year’s X-Matrix Before Planning the Next.
  • Rotate focus KPIs quarterly, by where the KPI tree is weakest.
  • Set a response time for escalations, and report on it.
  • Check leader standard work, peer to peer, monthly.
  • Target harder problems deliberately, with A3s rather than quick kaizens.

A worked example: year two, recovered

Here is a hypothetical year two, quarter by quarter, from the signal that appeared to the fix that followed:

QuarterSignalFix
Q1Strategic flags down 40% from year oneOwners commit to a one-week response; reported monthly
Q2Improvement share on strategic KPIs down to 15%Focus KPIs rotated; two targeted kaizen events per site
Q3Flags back up; share at 30%Leader standard work peer checks introduced
Q4Monthly review dominated by exceptions againReflection held before year-three planning

None of the fixes required new tools or new enthusiasm. Each restored a structure that year one had relied on goodwill to provide.

Worth noting how long the recovery took. The response-time commitment went in during Q1 and flags only returned in Q3, because trust is rebuilt at the speed of the second and third answered flag, not the first announcement. That lag is the argument for watching the signals rather than the outcomes.

What a stalled year two costs

A stalled year two rarely gets recorded as a failure, which is what makes it expensive. The huddles still run, the matrix still exists, the reviews still appear in diaries, and the improvement system still consumes the same hours. What has stopped is the connection between those hours and the strategic bets, so the organization pays the full cost of a deployment system and receives the benefits of an improvement system that happens to be pointed anywhere. A second year at that rate is roughly a second year of the program’s entire cost with none of its premium.

Among published alternatives, OnStrategy lists $200 per month for unlimited users and i-nexus publishes a free Starter tier for up to five users with $28 per user per month at its Standard tier. If you are evaluating a replacement tool in response to a stall, test the diagnosis rather than the dashboard: can the system tell you, from its own records, how many strategic flags were raised last quarter, how long each took to answer, and what share of logged improvement sat against a strategic KPI? A tool that cannot answer those three will not prevent the next stall either.

Profit.co publishes two plans, Essentials and Enterprise, quoting against modules and scale rather than a public seat rate. Hoshin Kanri, OKRs and Goals and Balanced Scorecard sit in Essentials, and the 30-day free trial is enough to load last year’s records and see whether the signals above are already visible in them.

The signals are already in your records

In Profit.co, the signals are visible from the system’s own records: escalations and response times, improvement effort by strategic KPI, huddle and review history, and correlation histories for the reflection. See the lean strategy software page, and Why Hoshin Software Rollouts Fail (It’s Rarely the Software).

Reading the signals off existing records, rather than running a survey, is what makes the check cheap enough to repeat quarterly:

  • Nobody has to be asked how it’s going. Flag counts and response times are by-products of the work, so they cannot be talked up in a steering committee.
  • The reflection has material. Correlation histories mean year two’s plan starts from what year one’s bets actually did, which is the single fix that unlocks three of the six causes.
  • A lapse is visible in weeks. Improvement effort by strategic KPI drifting down is a chart, not an impression, and it moves long before the breakthrough KPI does.

The routines that lapse first are set out in Leader Standard Work and Strategy in Lean Organizations, and the sequence that gets an organization to year two in good shape is in The Lean Transformation Roadmap: Where Strategy Deployment Fits.

Free Product Demo

Check your program for year-two signals

A 30-minute walkthrough, tailored to your team.

Book a free demo
G2, Capterra and Gartner Rated 4.7/5 by 500+ Leaders

What happens in the call

01
Share how you work today

How your teams set goals, track progress and review results.

02
See Profit.co in action

Strategy, performance, projects and engagement on one platform, with AI.

03
Leave with a clear plan

A practical path to align teams, execute faster and drive results.

Questions this article answers

Easy wins run out, plans are rebuilt without reflection, kaizen drifts unsteered, leader routines lapse, escalations go unanswered and focus KPIs go stale.

Fewer strategic flags from huddles, a falling share of improvement on strategic KPIs, targets set from last year’s results and quieter monthly reviews.

Restore structure: a real reflection, rotated focus KPIs, response times for escalations, peer-checked leader routines and deliberate A3s on harder problems.

Expect a lag of a quarter or two. Flagging returns at the speed of the second and third answered flag, not at the announcement of a new response time.

Usually not. Every cause is structural, and the fixes need no new tools. What software decides is whether the signals are visible early enough to act on.

Related Articles

Lean Strategy Software
10 min read · November 16, 2026

Operational Excellence vs Strategy Deployment: Where They Meet

Last updated: Nov 16, 2026 Bastin Gerald Founder & CEO at Profit.co Bastin Gerald is an entrepreneur, business strategist, and…

Bastin Bastin
Lean Strategy Software
11 min read · November 16, 2026

Strategy From the Gemba: Learning Upward From Frontline Improvement

Last updated: Nov 16, 2026 Bastin Gerald Founder & CEO at Profit.co Bastin Gerald is an entrepreneur, business strategist, and…

Bastin Bastin
Lean Strategy Software
10 min read · November 16, 2026

Hoshin Kanri and Daily Management: The Two Engines of Lean

Last updated: Nov 16, 2026 Bastin Gerald Founder & CEO at Profit.co Bastin Gerald is an entrepreneur, business strategist, and…

Bastin Bastin
Lean Strategy Software
10 min read · November 16, 2026

True North in Lean: Setting Direction in a Lean Organization

Last updated: Nov 16, 2026 Bastin Gerald Founder & CEO at Profit.co Bastin Gerald is an entrepreneur, business strategist, and…

Bastin Bastin
Lean Strategy Software
10 min read · November 16, 2026

KPI Trees for Lean Organizations: From Bowler to Daily Board

Last updated: Nov 16, 2026 Bastin Gerald Founder & CEO at Profit.co Bastin Gerald is an entrepreneur, business strategist, and…

Bastin Bastin
Lean Strategy Software
10 min read · November 16, 2026

Tiered Huddles and the Strategy Review Cadence

Last updated: Nov 16, 2026 Bastin Gerald Founder & CEO at Profit.co Bastin Gerald is an entrepreneur, business strategist, and…

Bastin Bastin
Athena

Welcome to Profit.co 👋

How can I help you today?