Everything else - waiting, rework, interruptions, overproduction, unnecessary movement, excessive approvals, or incomplete information - is waste that slows the system down and degrades overall performance.
One of Lean's fundamental objectives is therefore to distinguish clearly between:
- what creates value,
- and what consumes time, energy, or resources without improving the final result.
Simple definition
What is value-added?
An activity creates value when it:
- actually transforms the product, service, or information,
- answers a concrete need,
- and contributes directly to the outcome expected by the customer or user.
Examples:
- installing a functional piece of equipment,
- producing a conforming part,
- solving a critical problem,
- finalizing a useful decision,
- delivering usable information.
What is waste?
Waste is an activity that consumes resources without creating real value.
Waste can take several forms:
- lost time,
- unnecessary movement,
- waiting,
- errors,
- rework,
- unproductive meetings,
- information overload,
- multitasking,
- delayed decisions,
- redundant tasks.
In many organizations, a large share of energy is absorbed by managing dysfunction rather than creating value.
Why it matters
Many companies try to improve performance by asking teams:
- to go faster,
- to produce more,
- or to work harder.
But in reality, performance losses often come from the system itself.
Teams sometimes spend more time:
- waiting,
- searching for information,
- correcting errors,
- handling emergencies,
- working around problems,
- or replanning,
- than actually producing value.
Lean therefore seeks to improve the system before trying to "speed people up".
Reducing waste generally helps to:
- improve lead times,
- increase quality,
- reduce costs,
- limit operational stress,
- and make operations smoother and more predictable.
Concrete example
On a construction project, a field team arrives in an area scheduled for work.
But:
- the drawings are not up to date,
- another company is still occupying the area,
- materials are not available,
- some approvals are not finalized.
The team waits, reorganizes, improvises, or switches tasks.
Meanwhile:
- the schedule drifts,
- costs increase,
- tensions appear,
- and real productivity drops.
The problem is not a lack of effort from the teams.
The problem is the coordination system.
In Lean logic, these interruptions are treated as major forms of waste that must first be made visible and then addressed systemically.
Common mistakes
Confusing activity with value creation
Being busy does not necessarily mean creating value.
Trying to optimize each team separately
Local optimization can sometimes degrade overall system performance.
Treating rework as normal
Corrections and rework often represent major invisible losses.
Adding control to compensate for an unstable system
Multiplying approvals or reporting can make slowdowns worse.
Cutting costs without understanding flows
Removing resources without stabilizing the system often creates more disorder.
Indicators to track
Several indicators can be used to measure losses and value creation:
- Waiting time
- Cycle time
- Number of rework loops
- Defect rate
- Level of corrections
- Truly productive time
- Commitment reliability
- Service level
- Number of interruptions
- Time spent coordinating
- Work in progress
- Real productivity
The objective is to measure how the system really operates, not just visible activity.
Frequently asked questions
Does Lean only seek to cut costs?
No. Lean mainly seeks to improve value creation and system flow.
Can all waste be eliminated?
Not always immediately. Some waste is linked to existing regulatory, contractual, or organizational constraints.
Why is waiting considered waste?
Because it immobilizes resources without producing value.
Does waste also exist in services and offices?
Yes. Queues, multiple approvals, email loops, unnecessary meetings, and late decisions are common forms of administrative waste.
Can value-added be measured?
Yes, especially through:
- lead times,
- quality,
- customer satisfaction,
- flow,
- and delivery reliability.
Leanfinity offer link
Gemba maturity diagnostic
Leanfinity helps organizations make real performance losses visible:
- flow interruptions,
- waiting,
- rework,
- misalignment,
- overload,
- and operational dysfunction.
Our field diagnostics identify the systemic causes that degrade value creation and overall performance.
How it works
Define
Clarify the concept and its role in the operating system.
See
Make flows, constraints, gaps, and interfaces visible.
Act
Turn the principle into concrete routines, decisions, and commitments.
Learn
Measure gaps to improve the system without looking for someone to blame.
Lean is built around a simple question:
Does this activity really create value for the customer or the project?
If the answer is no, three situations are possible:
Value-added activity
It contributes directly to the expected result.
→ Preserve it and make it flow.
Necessary but non-value-added activity
It does not directly create value, but remains necessary in the current system.
Examples:
→ Simplify it as much as possible.
Pure waste
It creates no value and could be removed without negative impact.
Examples:
→ Eliminate it.
Lean then aims to: