Lean Management is often translated as "lean" – but it doesn't mean "fewer people" or "less budget", it means more value with less waste along the entire value chain. It's a corporate philosophy that consistently aligns processes with customer benefits, reduces waste, and systematically improves quality – not just a collection of individual methods.
Important: Lean is a management system. Tools (5S, Kanban, SMED, A3, etc.) are aids – what matters is how people lead, learn, make problems visible, and develop standards.
The reference point for Lean is the Toyota Production System (TPS). Toyota describes the basic logic of the TPS as a system based on two pillars:
- Just-in-Time (JIT): produce/deliver what is needed, when it is needed, in the right quantity- Jidoka: "built-in quality" or "automation with human sense": deviations are detected, the process stops, causes are resolved, so errors don't continue
Toyota explicitly refers to central designers (including Eiji Toyoda) and the consistent implementation of Jidoka and JIT as the basis for the TPS. The roots of JIT are attributed to Kiichiro Toyoda in Toyota's history (Just-in-Time as a guiding idea in early factory operations).
A common mistake: TPS = "toolkit". The opposite is closer to reality: TPS is a goal and thinking system, in which tools only work when the cultural conditions are met (leadership, standards, problem-solving ability, respect for people). This view is also emphasized in Lean specialist publications: TPS remains effective only when understood as a system – not as a mix of methods.
Toyota summarizes the culture behind TPS in the "Toyota Way": supported by two pillars
- Continuous Improvement (continuous improvement)- Respect for People (respect for people)
Especially "Respect for People" is not a "soft topic", but a prerequisite for performance: people should be able to see, address, and solve problems – with clear goals, responsibility, coaching, and a stable system. (Lean research also explicitly treats this dimension as central to successful Lean implementation.)
While TPS is the historical source, Womack/Jones (from the MIT environment around "Lean Production") have described Lean as a transferable management logic. The Lean Enterprise Institute describes the well-known 5 steps/principles as a thought process for transformation:
- Value (value from the customer's perspective)- Value Stream (understand the value stream)- Flow (create flow)- Pull (control according to demand)- Perfection (perfection as direction: continuously improve)
These 5 principles are particularly helpful because they transfer Lean from production to administration, development, supply chain, or service – always along the same logic: define value → consider end-to-end → stabilize flow/pull → accelerate learning.
Lean addresses waste not only in the sense of "7 types", but systemically:
- Muda: direct waste (e.g., waiting, transport, inventory, rework …)- Mura: unevenness/fluctuation (peak loads, unstable planning, changing priorities)- Muri: overburdening (people/equipment/processes permanently overstrained)
The point is crucial: whoever only reduces Muda but ignores Mura/Muri often builds a "Lean on sand" (more pressure, more hectic, more escalation) – and loses acceptance and quality. In the TPS literature by Taiichi Ohno, Lean is precisely characterized as such thinking: identify waste, understand causes, improve system conditions.
In practice, Lean works not as a Big Bang, but as a build-up logic:
Create stability (prerequisite)- Standards (work processes, parameters, material provision)- Transparency/visualization (make deviations visible)- Basic quality (don't pass on errors)
Create flow- Connect processes so that products/information flow without stop-and-go- Bottlenecks and disruptions become visible (this is intended)
Establish pull- Control from customer demand (takt/demand) instead of push planning- Inventories become a result of uncertainty – not "security feeling"
Accelerate learning- Treat deviations as learning signals (not as blame)- Problem-solving becomes routine (PDCA, A3, root cause analysis)
This creates a system that doesn't "perfectly plan", but learns quickly and robustly.
A modern link between culture ("we improve") and everyday life ("how do we improve concretely?") is Toyota Kata by Mike Rother.
- Improvement Kata: iterative approach towards the target state over obstacles- Coaching Kata: leadership as a daily coaching routine at the place of value creation (Gemba), typically along PDCA questions
The added value: Lean is not understood as a project ("introduce and finish"), but as a skill that is trained and scaled.
Lean tools are sensible when they address a problem in the system:
- 5S / Visual Management: make deviations visible, reduce search times, stabilize standards- SMED: reduce setup times, flexibilize batch sizes, enable flow/pull- Kanban: pull control, WIP limits, stable replenishment logic- Value Stream Analysis/Design: end-to-end transparency, bottlenecks, inventories, interfaces- A3 / 5-Why / Ishikawa: structured problem-solving instead of "firefighting mode"- Heijunka (Leveling): reduce Mura – basis for reliable flow/pull
Rule of thumb: tools without leadership routine result in activism. Leadership routine without system logic results in "meeting Lean". Both together result in effect.
Lean rarely fails due to method knowledge, but due to false assumptions:
- "Lean = Cost Reduction" → leads to pressure, shifting of problems, decreasing motivation- "Lean = Projects" → after the project ends, the system falls back- "Lean = Experts do it" → prevents learning in the line- "Lean = Standardization = Lack of Freedom" → standards are the basis for targeted improvement (not to switch off thinking)
Lean works sustainably when management and employees jointly build a system in which problems can and may be visible and solved.
1. Start with Direction & Customer Benefit: what is "value" – measurable, from the customer's perspective (external or internal)?2. Value Stream First: don't optimize locally, but understand end-to-end (material/info, inventory, waiting times, interfaces).3. Stability Before Speed: standards, transparency, basic quality – only then flow/pull.4. Leadership as a Daily Amplifier: Gemba-oriented, with clear routines (deviation → cause → measure → standard).5. Build Capability Instead of "Tool Rollout": problem-solving and improvement as a trainable routine (Kata/PDCA), so Lean doesn't depend on individual "Lean experts".