Academy » Lean Foundations
Lean Foundations — Lesson 10: How to sustain a lean program: year one and beyond
Lean Foundations · 4 min read · 10.11.2026

This is the tenth and final lesson of the Lean Basics series. In the previous nine, you learned to see waste, implement 5S, map the value stream, shorten changeovers, and launch small kaizen improvements. Today we tackle what defeats most companies: how to keep the program alive once the initial enthusiasm fades. We'll walk through a quarter-by-quarter plan for year one, three routines that hold results in place, and metrics that reveal decline before your customers notice it.
Why lean programs die after six months
At Foreast, we see the same pattern on projects over and over. January: kick-off, red tags, tidy shelves, photos on the notice board, a 5S audit scoring 85 points. By April, 63 points, kanban cards are disappearing, and the tools are back in the box. By September, 38 points, and on the shop floor the word "lean" means "that thing from last year".
There are usually three causes:
- The program has no owner. When something is everyone's job, it's no one's job.
- Management stopped walking the floor. Once the plant director skips the gemba walk a few times, the team knows the priority has moved elsewhere.
- Improvements were never anchored in standards. As in the lesson on standardized work: anything not written into a standard reverts to its original state within a month.
Whether lean lives isn't decided at the kick-off, but on an ordinary Tuesday at 7:15, when no one is watching.

Year one: four quarters, four goals
Plan the year as a phased project, not as a series of random workshops.
First quarter — pilot. Pick one line or product family, ideally where your value stream mapping showed the worst flow. The goal is one visible number in 90 days: changeover from 45 down to 18 minutes, an intermediate warehouse cut in half.
Second quarter — anchoring. Updated standards, 5S audits with a scoring sheet, maintenance checklists from TPM. The audit score must hold above 80 points for three consecutive months. Without this phase, the pilot dies at the first rush of orders.
Third quarter — replication. A second line, this time without an external consultant. The first kaizen workshops are led by your own supervisors. You're done when a team leader can run a workshop on his own and deliver a measurable result.
Fourth quarter — internalization. Layered audits, internal trainers, lean in the onboarding of new people. And a budget for next year in hours, not just money — a team leader needs 2–3 hours per week for improvement work. If you don't schedule that into his capacity, improvement will lose the battle against daily firefighting.
Routines instead of enthusiasm
Enthusiasm runs out by April. Routine lasts for years. Three are enough:
- Daily: the 5-minute huddle at the board. Yesterday's number, today's risk, who's working on what. Same time, same place. The visual management board from that lesson is exactly for this.
- Weekly: management walk. The plant director spends 30 minutes on the floor. No fixing, no judging — asking questions and taking notes. One question is enough: "What's slowing you down today?"
- Monthly: improvement review. How many ideas did the team actually implement? A realistic target is 1–2 improvements per team per month. Twenty promised means zero completed.
Survival rule: if any level skips its routine three times in a row, the program is dying. Treat the calendar, not the people.
Metrics that reveal decline in time
Outcome indicators — OEE, scrap, changeover time, inventory turnover — tell you something happened. Often with a six-month delay. So watch the leading indicators above all:
- audit score trend — two months of decline means intervene now, not at year-end,
- implemented improvements per 100 employees per year — 3–5 is a decent start, 20 or more is world-class,
- standard currency — what percentage of documents were revised in the last six months.
When ideas stop coming, it's not that people no longer want to help. They've simply stopped believing anyone will listen.
This week's exercise
Pick one method you've already implemented — 5S on a line, a kanban rack, a changeover checklist. Go to the shop floor and answer three questions. Who is the owner (a name, not just a job title)? When was the last audit (a date on paper)? How many improvements were made there in three months (a number)? If any answer takes longer than a minute to find, you've just found your pilot for the first quarter of next year.
Key takeaways
- Lean programs fail because of a missing owner, inattentive management, and unanchored standards — not because of lazy people.
- Year one: pilot, anchoring, replication, internalization. One clear number per quarter.
- Three routines keep the program alive: a daily 5-minute huddle, a weekly management walk, a monthly improvement review.
- Leading metrics (audit trend, number of improvements) reveal decline earlier than outcome metrics. Two months down means intervene.
This closes the Lean Basics series. Ten lessons took you from recognizing waste for the first time to a system that keeps improvement alive for years. Don't start everything at once — pick one method, one line, and the first number you want to change within 90 days. We're preparing new series on an ongoing basis; for an overview, see our e-learning catalogue.