5.3Lean & continuous improvement in supply chain
The essentials in 30 seconds
- Hunt the 7 wastes: over-ordering, inventory, transport, motion, waiting, over-quality, defects.
- Simple tooling: 5S to see, kanban to pull, VSM to map, kaizen in small steps.
- JIT to make reliable: low inventory reveals problems; keep buffers where risk requires it.
Mini-case thread — Nadia hunts waiting time on her dock
Nadia sees cartons stagnating on the dock of her agrifood SME in Algiers: parcels waiting for decision, pickers walking too much, returns dragging on. This section shows how she lists wastes in one hour on the floor, tidies her dock in 5S and launches a kaizen ritual of one problem a month.
Sequel to cases 5.1-5.2 — Nadia moves from figures to flows, with the same products and suppliers.
1. The 7 wastes in your flow
Lean (Toyota) hunts muda: overproduction/over-ordering (the root waste), excess inventory, unnecessary transport (zigzags 4.1), unnecessary motion (picker kilometres 4.2), waiting (truck at the dock), over-quality (triple packaging), defects (disputes, returns).
This entire guide was lean without the name: just need (1.1), direct flows, reliability.
Mapping often reveals that goods spend 95 % of the time waiting.
2. Tools: 5S, kanban, VSM, kaizen
5S: clear out, organise, clean, standardise, sustain — makes abnormal visible (the systematised zero-budget audit). Kanban: visual signal that pulls the order (empty bin → replenishment, reserve bin for C items).
VSM (Value Stream Mapping): map the flow with its times to see waiting. Kaizen: continuous improvement in small steps driven by those who do the work, one concrete problem at a time, rather than the yearly big-bang project.
One hour of floor observation is enough to list the costliest muda.
3. Just-in-time and balance with resilience
JIT (flows pulled by real demand) is first a reliability machine: low inventory reveals breakdowns/defects/unstable suppliers that you fix — inventory reduction is the result, never the starting point.
Demanding conditions: reliable nearby suppliers, frequent deliveries, controlled quality, levelled demand. A fully tightened chain is fragile under shocks — modern doctrine: tight lean where it is reliable, accepted buffers where risk justifies them.
Safety stock protecting against a real risk is not waste; stock with no function is (3.1).
🔎 Concrete example — Kaizen of the congested dock
Congested dock full of parcels awaiting decision: team gathered for 45 min, 5 whys → root cause: no sorting rule at receipt. Countermeasure: immediate-decision bins (new/refurbished/after-sales) + 5S of the dock.
Before/after measure: dock → stock crossing time divided by 3, returns handled within 48 h.
Lesson: one concrete problem per month, measured, standardised: that is kaizen.
Section vocabulary
- Muda (waste)
- Anything consuming resources with no value for the customer: overproduction, excess stock, unnecessary transport and motion, waiting, over-quality, defects.
Simple example: Nadia lists cartons waiting for decision and the picker's round trips on her dock.
What it is not: calling every dormant inventory "necessary" without ever questioning it.
Reflex: where does the product wait without moving, at my place?
- 5S
- Clear out, organise, clean, standardise, sustain: the workspace discipline that makes abnormal visible — the foundation of any high-performing warehouse.
Simple example: Nadia clears the dock, marks zones, posts the sorting rule at receipt.
What it is not: a big yearly tidy-up with no posted rule and no follow-through.
Reflex: can abnormal be seen in 30 seconds on entering?
- Kanban
- Visual pull replenishment signal (the empty bin, the card triggering the order): simple, robust, self-regulated.
Simple example: Nadia sets a reserve bin for wrapping films: empty bin means reorder.
What it is not: recomputing each routine need by hand in a never-updated spreadsheet.
Reflex: what visual signal could order in my place?
- Just-in-time (JIT)
- Supply/produce what is requested, when and in requested quantities; a reliability machine (low stock reveals problems) — demanding and to balance with resilience.
Simple example: Nadia tightens the flow on a reliable nearby supplier, with frequent deliveries.
What it is not: removing all safety on an imported item with long variable lead time.
Reflex: is this flow reliable enough to be tightened?
- Kaizen
- Continuous improvement in small steps, driven by those who do the work: one concrete problem at a time, measured, fixed, standardised — then repeat.
Simple example: Nadia handles one irritant a month with the dock team, measuring before and after.
What it is not: announcing a big yearly plan nobody follows after the meeting.
Reflex: what is my single problem of the month, measured?
In practice — Launch your continuous improvement approach
- Hunt the 7 wastes in one hour on the floor: dormant stock, double movements, waiting, redundant checks, recurring errors.
- Pick ONE recurring irritant and apply the 5 whys with those who live with it down to the root cause.
- Test a simple countermeasure, measure before/after (KPIs 5.1), standardise if it works.
- Set the kaizen ritual: 45 min per month, one problem at a time + 5S of the critical area.
Ready-to-say script — launch the kaizen of the month (1 min)
"45 minutes together on a single irritant: we describe, look for the cause with 5 whys, decide a simple countermeasure. We measure before and after, and if it works we write it as a rule. Which irritant slows you most right now?"
Say in front of the floor team, then note root cause and before/after measure.
Copy-paste template — express kaizen sheet
IRRITANT (where, when, who): _______________
ROOT CAUSE (5 whys): _______________
SIMPLE COUNTERMEASURE: _______________
MEASURE BEFORE: _______________ / AFTER: _______________
WRITTEN RULE IF IT WORKS: _______________
NEXT PROBLEM (next month): _______________Small business / tight budget
One hour on the floor is enough: Nadia handles a single irritant with available means, no consultant or investment.
Algeria SME
Start with 5S of the dock and receipt area: visuals make waiting and errors obvious.
Agrifood import
Target waiting at receipt and redundant checks on time-sensitive products.
Small team
45-minute ritual a month kept even with short staff: one problem at a time keeps momentum.
✓ Best practices
- Start with 5S in the most critical area: visuals make abnormal obvious.
- The kanban bin is the best P2P for C items: simple, self-regulated, with no calculation.
- Display the trend of the targeted KPI: visible improvement keeps momentum.
✗ Common pitfalls
- Trying to lean everything at once: the big-bang exhausts, kaizen embeds.
- Tightening flows without making them reliable: you create fragility, not performance.
- Automating disorder: lean first, investment after.
Key takeaways
- 7 wastes: this whole guide was its application — just need, direct flows, reliability.
- Tools: 5S (visible), kanban (visual pull), VSM (95 % waiting), kaizen (small steps).
- JIT = RELIABILITY machine; inventory reduction = result, never starting point.
- Lean/resilience balance: tight on reliable, costed buffers on risky.
48h challenge — apply tomorrow
Spend one hour on the floor listing the 7 wastes, pick one irritant and apply the 5 whys with those who live it. Write the simple countermeasure and how you will measure before and after.
- I can cite the 7 wastes without hesitating.
- I found my root cause with the 5 whys.
- My countermeasure is tested and measured.
Frequently asked questions
Does lean apply outside industry / in small firms?
Yes: in trading (over-ordering, dormant stock, unnecessary touches), in admin (re-entries, dormant approvals — VSM reveals 99 % waiting) and in small firms (short loop, versatility, accessible owner to decide fast). Translate the 7 muda into your context.
Are JIT and safety stock not contradictory?
No: JIT fights stock with no function, safety stock funds an identified risk (demand/lead-time variability, critical item). Segment: tight flows on reliable/stable, accepted buffers on risky — and work to shift the boundary by making flows reliable.
What does VSM reveal in most flows?