Manufacturing is where lean began and where its daily management is usually strongest. It’s also where the gap between plant-floor improvement and corporate strategy is widest, because plants have their own systems, shifts and histories.
In this guide
Key Takeaways
- →Plant boards already run on SQDC, so express strategic KPIs in the same categories.
- →Shifts mean escalation has to survive handover, not just reach the next huddle.
- →Kaizen is mature in most plants: steering matters more than stimulating.
- →Multiple plants give you a comparison single-site organizations never get.
- →Effort beside result tells you which improvements work and which travel.
- →None of it is visible in a kaizen count or a group on-time delivery figure.
What’s distinctive in manufacturing
Manufacturing rarely has a daily management problem. What it has is five structural features that make the connection to strategy harder than it looks from head office.
The last one is the counter-intuitive one. In most sectors the hard part is getting improvement to happen at all; in a mature plant network it is already happening in volume, and the question is only where it is pointed.
| Feature | Effect on lean strategy |
|---|---|
| Multiple plants | Each with its own boards, systems and improvement habits |
| Shifts | Huddles happen several times a day; escalation must survive handover |
| Strong SQDC tradition | Safety, quality, delivery and cost already organize the boards |
| Operational data systems | Lots of data, often not connected to strategic KPIs |
| Mature kaizen | High improvement volume; steering matters more than stimulating |
Strategic KPIs in SQDC terms
Plant boards are usually organized around safety, quality, delivery and cost. Expressing strategic KPIs in the same categories helps them land: a breakthrough in on-time delivery is a delivery KPI; a services breakthrough may depend on a quality KPI like first-time-fix. The KPI tree connects them to what each line measures.
Two ways of drawing that tree, and what each makes easy to see, are compared in Goal Tree vs X-Matrix: Two Ways to Show Strategy Deployment.
If the strategy can’t be read in SQDC, the plant floor will treat it as head office’s business.
Plants as a natural experiment
Multi-plant manufacturers have something single-site organizations don’t: comparison. When one plant’s kaizen on parts availability moves on-time delivery and another’s doesn’t, the difference is information. Comparing plants on the same strategic KPI, with improvement effort beside it, shows which improvements travel. This is the same comparison used to test outcome lag; see Deploying Hoshin Kanri Across Multiple Sites.
A worked example: four plants, one strategic KPI
Here are four hypothetical plants, with the number of kaizens each ran on delivery and how on-time delivery changed:
| Plant | Kaizens on delivery | On-time delivery change | Note |
|---|---|---|---|
| Plant 1 | 24 | +4 points | Parts pre-check before kitting |
| Plant 2 | 6 | +0.5 points | Little effort on delivery |
| Plant 3 | 18 | +1 point | Effort on changeovers; parts the real issue |
| Plant 4 | 15 | +3 points | Copied plant 1’s parts check in Q2 |
The comparison tells the strategy owner three things: the parts pre-check works and travels; plant 2 needs steering; plant 3’s effort is pointed at the wrong driver. None of this is visible in a kaizen count or a group on-time delivery figure.
Plant 3 is the expensive row. Eighteen kaizens is a real quarter of a real team’s improvement capacity, spent competently on changeovers at a plant whose delivery problem was parts. Nobody did anything wrong; the information simply was not in the room.
What an unsteered plant network costs
Put a number on the table above. Four plants, roughly sixty improvement events in a quarter, and perhaps half of them pointed at a driver that was never going to move the strategic KPI. That is not a software problem and it does not appear in any budget, but it is the largest discretionary spend a plant network makes: the improvement capacity of people who are already doing the work well.
Among published alternatives for connecting the two, OnStrategy lists $200 per month for unlimited users, which is relevant for a plant network because the people who need to see a shared strategic KPI run into the hundreds. i-nexus publishes a free Starter tier for up to five users and $28 per user per month at its Standard tier, which fits a group strategy function more than a shop floor. The capability to test either way is the four-plant table itself: can the system produce it without an export, and does it update itself as the quarter runs?
Profit.co publishes two plans, Essentials and Enterprise, quoting against modules and scale rather than a public seat rate, which is the usual arrangement when plant populations are large and mostly reading. Hoshin Kanri, OKRs and Goals and Balanced Scorecard sit in Essentials, and the 30-day free trial covers a month of real huddles across two plants, which is enough to see whether the comparison assembles itself.
Plants contributing to one group view
In Profit.co, plants’ objectives contribute to group objectives, huddles from daily to quarterly share strategic KPI definitions across plants, improvement ideas link to the KPI they should move, and the exception queue flags plants where effort isn’t moving the result. See the lean strategy software page.
Three consequences matter for a plant network specifically:
- One definition survives the handover. A shared strategic KPI means the night shift flags against the same measure the day shift reviews, which is where most escalation chains break.
- Plant 2 is visible before the quarter ends. Effort by KPI is a running total, so low effort on a focus KPI shows up in weeks rather than in a year-end comparison.
- A travelling improvement can be named. Plant 4 copying plant 1 is only repeatable if the record says what was copied and what it moved.
How the boards and the system divide the work at each tier is set out in Lean Management Systems: What to Digitize and What to Keep on the Board.
Free Product Demo
Compare your plants on a strategic KPI
A 30-minute walkthrough, tailored to your team.
Book a free demoWhat 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 expressing strategic KPIs in SQDC terms, sharing definitions across plants and tiers, escalating problems that affect strategic bets through tiered huddles, and steering a share of kaizen toward weak drivers.
By comparing plants on the same strategic KPI with improvement effort beside it, which shows which improvements move results and travel between plants.
Safety, quality, delivery and cost: the categories most manufacturing daily boards are organized around.
Flag against a shared strategic KPI definition rather than a shift’s own note, so the flag a night shift raises is the one the day shift and the objective’s owner see.
Not by itself. A plant can run eighteen competent kaizens against a driver that was never going to move the strategic KPI. Effort has to be read beside result.