Understanding Lean: value, flow, pull, respect, and continuous improvement.

01 · What is Lean?

The definition above fits in a sentence; what truly sets Lean apart is its nature. Contrary to common belief, it is neither a toolbox nor a method to “go faster” or “squeeze costs.” It is a management system that treats the organization as a set of activities to observe, understand, and relentlessly improve.

Its origin goes back to the Toyota Production System — the Toyota Production System — developed after World War II in the automotive industry. It then spread to construction, services, healthcare, and the public sector. Anywhere a work system can be described, Lean offers both a lens and an improvement system.

« Only value-added work counts. Everything else must be eliminated. »

Lean combines two fundamental logics: continuous improvement (kaizen) and respectful involvement of people. The first without the second produces efficient but exhausted organizations. The second without the first produces caring but ineffective organizations. Together they produce organizations capable of learning and improving continuously.

02 · Value-added vs waste

Lean starts by defining value from the customer’s point of view, not the producer’s. This seems obvious but is rarely applied. Most organizations optimize what they can measure (workstation productivity, machine utilization) without asking whether the output is really what the customer expects.

Once value is defined, anything that does not contribute to it is considered waste. Lean classically identifies seven forms, often with an eighth added:

• Overproduction — producing more than actual need
• Waiting — time lost waiting for information, a decision, a handoff
• Transportation — unnecessary movement of materials, people, information
• Overprocessing — steps not valued by the customer, such as excess quality or overly complex operations
• Inventory — early starts, buffers, work-in-process that cost without paying back and hide flow problems
• Motion — unnecessary movements or effort in doing the work
• Defects & rework — fixing poor work — do + undo + redo
• Underutilized talent — ignoring frontline ideas and knowledge

Reducing waste is more profitable than increasing value — it is simpler to grasp, faster to implement, and done by the people who already create value. Those who do the work are best placed to identify and reduce waste.

03 · The value stream

The value stream is the actual sequence of activities — from customer request to delivery — that transforms information and/or material into value. It is Lean’s core analytical lens. We observe it, describe it, measure it, improve it.

Three operations structure this work:

• Observe on the ground (Gemba) what actually happens — not what the procedure says or people report
• Map the stream: steps, times, waits, rework, failure points
• Stabilize before optimizing: you can only improve what is under control

When the stream is visible, problems can be shared. When problems are shareable, improvement becomes collective. Visual management is not a slogan: it is the condition for an honest discussion about the state of the system.

04 · The pull system — start from demand

The pull system (pulled flow) is the opposite of traditional organization. Rather than pushing work downstream to a theoretical plan, activities are triggered by the actual demand of the next step. Each actor produces when and because the downstream needs it.

Pull reduces inventory, waiting, overloading, interruptions, and coordination losses. It also, by contrast, exposes where the system is unstable — because a pull flow does not tolerate approximation.

In construction, the Last Planner System translates the pull principle into project control. In industry, it takes the form of kanban and parts supermarkets. In services, it appears as managed queues and short-cycle commitment loops. The logic is the same: organize work from downstream needs, not an upstream theoretical schedule.

We do what must be done at the right time, not because we can.

05 · Continuous improvement (kaizen)

Continuous improvement is the art of advancing in small steps, relentlessly, with whole-organization engagement and at a high cadence. It runs counter to the logic of “big transformation programs” that mobilize for a quarter and then fizzle out.

It rests on three conditions:

• Problems made visible — visual management, structured problem solving (A3), operating cadence
• A root cause culture — the 5 Whys, critical thinking without blame
• Evolving standards — each improvement becomes the new starting point

Continuous improvement requires that the people who do the work be involved in improving it. You don’t decree this — you design it. Leaders must create the conditions: psychological safety, clear rules of engagement, effective decision processes.

06 · Respect for people

Respect for people is Lean’s most misunderstood principle — often perceived as an HR slogan when it is a system design principle. Respecting people means designing a system in which they can succeed: without wasting their energy, without absurd tasks, without permanent operational contradictions.

Practically, this means:

• Give teams visibility into their performance and their problems
• Give them the means to solve — time, method, coaching
• Build stable standards that simplify work instead of cluttering it
• Practice respectful confrontation on facts, not opinions
• Put learning before blame in managing deviations

Without respect for people, Lean becomes an optimization machine that runs out of steam as soon as pressure eases. With it, it becomes a self-sustaining system of progress.

07 · Indicators to track

Good indicators drive better decisions. Lean indicators are not there to decorate a dashboard; they exist to trigger decisions.

• Cycle time — the actual duration to fulfill a customer request
• Work-in-process (WIP) level — the amount of work in progress that reveals bottlenecks
• First-pass yield — the share of units delivered without rework
• Commitment reliability (PPC) — percentage of commitments kept each week
• Problem-solving cadence — number of root causes addressed per week
• Standard adoption — share of standards used in the field

The goal is not to “compile dashboards” but to put in place the regular conversations that change the system.

08 · Frequently Asked Questions

Go further

This pillar is the starting point. Depending on your context, the following resources will take you further:

A practical way to get started

A Gemba Diagnostic is often the best entry point to move from concept to application. Three to five days on site to identify the real improvement levers.