The 5 Principles of Lean Management

Photo by Aaron Burden on Unsplash

Lean Management occupies a paradoxical place in the history of modern management. Born in the Toyota factories of post-war Japan, it revolutionized global industrial production and progressively spread to services, software development, healthcare, and even nonprofit organizations. Yet despite its massive popularity, Lean remains often misunderstood, poorly applied, and sometimes diverted from its original intentions.

Too often reduced to an obsessive quest for cost reduction and the elimination of “waste,” Lean has been instrumentalized to justify waves of layoffs, an intensification of work, and a dehumanization of organizations. This drift is not authentic Lean – it is its betrayal. Because at its origin, the Toyota Production System rested on a deeply humanist conviction: the people at the heart of the system are experts in their own work, and it is by freeing their intelligence and creativity that we achieve excellence.

For 1Clusif, a humanist movement committed to reducing exclusion and promoting professional inclusion, Lean Management deserves to be revisited in light of our values: equality, transmission, responsibility, creativity and entrepreneurial spirit. How can the five fundamental principles of Lean be understood and applied in a way that values people, fosters inclusion, and helps create organizations that are more just while being more high-performing?

This article offers an in-depth exploration of the five principles of Lean Management, examining not only their technical and operational dimension, but also their human, ethical and social implications. We will see how these principles, when authentically understood and applied, can serve inclusion rather than exclusion, fulfillment rather than exhaustion, and collective creativity rather than blind standardization.

Origins and Philosophy of Lean: Beyond the Myths

Before exploring the five principles, it is essential to understand Lean’s philosophical roots, often obscured in Western training and manuals.

The Context of Emergence: Post-War Japan

The Toyota Production System (TPS), the ancestor of Lean Management, was born in a very particular context: post-World War II Japan, a country constrained by scarcity. Taiichi Ohno and Shigeo Shingo, the architects of the TPS, did not have the abundant resources of American factories. They could not afford overproduction, massive inventories, or wasted materials.

This constraint forced systemic creativity: how do you produce quality vehicles with limited resources? The answer was not “work harder,” but “work smarter” by mobilizing the intelligence of all operators.

The Philosophical Foundations: Respect for People

The TPS rests on two pillars often forgotten in Western implementations:

Continuous improvement (Kaizen): constantly seeking to progress
Respect for people: considering every worker as an intellectual contributor, not just a pair of hands

This second pillar is fundamental. In the original TPS, operators have the authority to stop the production line if they detect a quality problem (Andon system). This delegation of power to the lowest levels was revolutionary. It affirms that those who do the work understand better than anyone how to improve it.

This philosophy deeply aligns with our 1Clusif values of equality (every person has a voice that counts) and shared governance (decision-making power is distributed).

The Western Drift: Lean Without Respect

Unfortunately, when Lean was exported to the West in the 1980s-1990s, it was often stripped of its human dimension. The tools were retained (5S, Kanban, Value Stream Mapping) but the philosophy was forgotten. The result: organizations that mechanically apply Lean recipes while maintaining rigid hierarchical structures where workers have no real power.

Our goal in this article is to rediscover the authentic spirit of Lean, the one that honors every person’s intelligence and sees in the diversity of perspectives a richness rather than an obstacle.

Principle 1: Define Value from the Customer’s Point of View

The first Lean principle states: value is defined by the customer, not by the organization. This seems obvious, but it is actually deeply counter-intuitive for many organizations.

Understanding What Value Is (and Is Not)

In Lean vocabulary, value refers to what the customer is willing to pay for. Everything else – waiting, unnecessary movement, overproduction, defects – is considered waste (Muda).

This definition is powerful but requires nuance. Take an example: a developer who cleans up and documents their code doesn’t produce a feature visible to the end customer. Is this waste? No, because code quality and maintainability create long-term value. Lean therefore distinguishes:

Value-added activities (VA): directly perceptible by the customer
Necessary non-VA activities: essential but invisible to the customer (regulatory compliance, technical maintenance)
Pure waste (Muda): to be eliminated

Customer Empathy as an Organizational Skill

To define value from the customer’s point of view, the organization must develop deep empathy. This requires:

Direct observation: going to see how customers actually use the product/service (Genchi Genbutsu – “go and see for yourself”)
Active listening: not only hearing what customers say they want, but understanding their underlying needs
Rapid iteration: testing, learning, adjusting in short cycles

This approach aligns with agile principles, which value collaboration with the customer and the ability to respond to change rather than follow a rigid plan.

Who Defines Value? A Question of Inclusion

Here is where inclusion becomes crucial. Too often, the “voice of the customer” is filtered by a few people – salespeople, product managers, executives – who claim to know what customers want. But this mediation creates biases: we mostly hear from customers who resemble the decision-makers.

An inclusive approach to the first Lean principle involves:

Diversifying customer feedback sources: not limiting to the biggest accounts or the most vocal customers
Directly involving production/development teams in listening to customers (not just salespeople)
Recognizing that frontline workers (cashiers, support technicians, delivery drivers) often have the best understanding of what customers really value
Being attentive to marginalized customers whose needs are systematically ignored

Principle 2: Map the Value Stream

The second principle invites us to visualize the entire process that transforms raw material (or the initial idea) into a product/service delivered to the customer. This mapping, called Value Stream Mapping (VSM), is a powerful diagnostic and transformation tool.

What Is a Value Stream?

The value stream includes all the steps – those that add value AND those that don’t – from the initial request to final delivery. For a software product, this may include:

Customer expresses a need
Prioritization in the backlog
Feature design
Development
Testing
Code review
Deployment
Documentation
User training

The Power of Visualization

Mapping the value stream reveals realities often invisible:

Hidden wait times: development takes 3 days, but the code waits 2 weeks before being deployed
Unnecessary back-and-forth: a form requiring 5 signatures when 2 would suffice
Bottlenecks: a step where everything slows down (often an overloaded person)
Redundancies: three teams doing the same check

This visualization is democratizing. It creates a common language accessible to everyone, not just experts. An operator can point at the diagram and say “There, we always wait 3 days” – their lived expertise becomes visible and valued.

Mapping Together: An Act of Collective Intelligence

The real power of VSM doesn’t come from the final diagram, but from the process of collective creation. At 1Clusif, we encourage mapping the value stream by mobilizing collective intelligence:

Bring together all the functions involved: not just managers, but the people who actually do the work
Use a large physical wall with sticky notes rather than a PowerPoint made by a consultant
Start from real experience, not documented theoretical processes
Celebrate uncomfortable revelations: “Ah, so my work creates a bottleneck for the next team?”

This collective process embodies our values of transparency (making visible what was hidden) and shared responsibility (understanding how our individual actions affect the system).

Beyond Efficiency: Mapping Human Impacts

A truly humanist mapping is not limited to product flows. It also includes:

Impacts on well-being: where are people stressed, exhausted, demotivated?
Skills mobilized or wasted: where are talents fully used?
Learning opportunities: where do people develop new skills?
Points of inclusion or exclusion: where are certain people systematically marginalized?

This human dimension of the value stream is often neglected, but it is crucial to prevent Lean from becoming a tool of dehumanization.

Principle 3: Create an Uninterrupted Flow of Value

The third principle seeks to make value flow smoothly, without interruptions, without waiting, without unnecessary inventory. The Lean ideal is “one-piece flow”: one piece comes in, is transformed, and immediately moves to the next step.

Why Flow Is Powerful

The benefits of continuous flow are numerous:

Reduced lead times: the product reaches the customer faster
Faster problem detection: a defect is spotted immediately, not 3 weeks later
Less inventory: therefore less tied-up capital and less space needed
Less complex coordination: no need to manage huge batches in transit
Increased motivation: teams quickly see the result of their work

Obstacles to Flow: The 7 Wastes (Muda)

Lean identifies seven types of waste that prevent flow (mnemonic: TIM WOOD or DOWNTIME):

Transport: unnecessary movement of products
Inventory: excessive stock that ties up capital and space
Motion: unnecessary movement of people
Waiting: time wasted waiting (information, approvals, deliveries)
Overproduction: producing more or earlier than necessary
Over-processing: doing more than necessary (over-engineering)
Defects: errors requiring rework and correction

To these seven, an eighth is often added: wasted talent (underused skills, stifled creativity, ignored ideas). This last one is of particular interest to us at 1Clusif.

Human Flow: Beyond Products

From a humanist perspective, flow is not just about physical products or tickets in an IT system. It also concerns:

The flow of information: does knowledge circulate freely or is it siloed?
The flow of decision-making: are decisions made quickly, or are they stuck in heavy hierarchies?
The flow of learning: can people continuously learn and develop, or are they stuck in fixed roles?
The flow of recognition: are contributions quickly recognized and valued?

This attention to human flows aligns with our value of transmission: knowledge must circulate, not stagnate in silos.

Creating Flow: Practical Tools

Several practices support the creation of continuous flow:

Reduce batch size: process small quantities at a time (in software development: small user stories deployed frequently)
Eliminate unnecessary approvals: trust teams to decide
Co-locate teams: physically or virtually, facilitate direct communication
Automate repetitive tasks: free human intelligence for value-added tasks
Standardize (intelligently): create stable processes that enable fluidity

These practices align perfectly with agile methods like Scrum, which advocate short iterations and continuous delivery of value.

Principle 4: Establish a Pull System

The fourth principle introduces the pull system as opposed to the push system. This is perhaps Lean’s most counter-intuitive principle, and yet one of its most powerful.

Push vs Pull: Two Opposing Logics

In a push system, production is based on forecasts and products are “pushed” toward the next steps or toward customers, whether they’re ready or not. Result: overproduction, excessive inventory, unsold goods.

In a pull system, production only happens when there is real demand. Each step “pulls” work from the previous step only when it’s ready to process it. It is the end customer who, through their demand, triggers the entire production chain.

Kanban: The Visualization of Pull

Kanban (meaning “card” or “signboard” in Japanese) is the emblematic tool of the pull system. On a Kanban board, each card represents a piece of work, and the columns represent process steps (To Do, In Progress, Done, etc.).

The fundamental rule: limit work in progress (WIP). For example, the team decides there can be no more than 3 tasks “In Progress” simultaneously. When a task is finished and moves to “Done,” and only then, can a new one be pulled from “To Do.”

This apparently simple discipline has profound effects:

Prevents overload: you don’t start 20 things you’ll never finish
Forces prioritization: since you can’t do everything, what really matters?
Reveals bottlenecks: if cards pile up in one column, there’s a problem to solve
Improves predictability: paradoxically, by limiting WIP, you deliver faster and more regularly

Pull and Autonomy: A Convergence with Shared Governance

The pull system has a profound implication for organizing work: it requires teams to have the autonomy to pull work when they’re ready, rather than having arbitrary deadlines imposed by management.

This autonomy aligns with the principles of distributed governance: decision-making power is pushed down to the level of the teams doing the work, not concentrated at the top.

For 1Clusif, this convergence between Lean and shared governance is not accidental. Both rest on the same conviction: those who do the work are best placed to organize their work.

The Limits of Pull: When Forecasting Is Necessary

The pure pull system is not always applicable. Some situations require forecasting:

Products with long manufacturing lead times: you can’t wait for the customer’s order to start
Rare or expensive materials: you need to anticipate to secure supply
Strong seasonality: some sectors must produce in advance for the high season

The art is finding the right balance between pull and push, pulling as much as possible toward pull while recognizing real constraints.

Principle 5: Pursue Excellence Through Continuous Improvement (Kaizen)

The fifth and final principle is perhaps the most important: Kaizen, continuous improvement. It’s not just one principle among others – it’s the meta-principle that encompasses all the others.

Understanding Kaizen: Philosophy, Not Technique

Kaizen (改善) is made up of two kanji: kai (change) and zen (good, better). Literally: “change for the better” or “improvement.”

But Kaizen is not just an improvement technique. It is an existential stance: the conviction that everything can always be improved, that perfection doesn’t exist but progress is always possible, and that this progress emerges from small daily changes rather than grand revolutions.

The Two Dimensions of Kaizen

Kaizen has two complementary dimensions:

1. Daily Kaizen (Kaizen at the Individual Level)

Each person, every day, looks for small improvements in their work. A developer who refactors a piece of code, a nurse who reorganizes her cart to save a few seconds, a teacher who adjusts their teaching after each class.

This dimension of Kaizen is deeply democratic: it affirms that everyone, regardless of hierarchical level, can and must contribute to improvement. No one is “too junior” or “not expert enough” to propose an idea.

2. Kaizen Events (Kaizen Workshops)

Periodically, the organization sets up Kaizen workshops: multidisciplinary teams gather for a few days to solve a specific problem or improve a process. These workshops are intensive, focused, and aim for quick, tangible improvements.

These events mobilize collective intelligence and can use tools like Bono’s Six Thinking Hats to structure collective thinking.

PDCA: The Continuous Improvement Cycle

Kaizen is often operationalized through the PDCA cycle (Plan-Do-Check-Act), also called the Deming wheel:

Plan: Identify a problem, analyze its causes, design a solution
Do: Implement the solution on a small scale (experimentation)
Check: Measure the results, compare with the goals
Act: If it works, standardize; if it doesn’t, learn and start again

This experimental, iterative approach perfectly aligns with the spirit of agile methods: we prefer empiricism (test and learn) to rationalism (plan perfectly then execute).

Kaizen and a Culture of Psychological Safety

For Kaizen to work, it requires high psychological safety. People must be able to:

Report problems without fear of being blamed
Propose ideas, even “crazy” ones, without risk of ridicule
Experiment and fail without punishment (failure is a source of learning)
Question established processes, even if they come “from above”

This psychological safety is fostered by Nonviolent Communication practices that allow disagreements and difficulties to be expressed without violence or judgment.

Kaizen and Inclusion: Valuing All Voices

Kaizen is intrinsically inclusive IF (and it’s a big if) the organization truly creates the conditions for all voices to count. Too often, improvement suggestions do move up from the base to the top, but:

Only “reasonable” ideas are taken seriously
Proposals that question established power are ignored
Junior, minority, or atypical people don’t dare speak up
Technical improvements are valued, relational or organizational improvements are neglected

A truly inclusive Kaizen culture requires an active commitment to:

Actively seek out the perspectives of usually silent people
Value cognitive diversity: neurodivergent people, people from different cultures bring valuable perspectives
Measure and celebrate everyone’s contributions, not just the “stars”
Create safe spaces where minorities can express themselves without fear

For 1Clusif, whose mission is to reduce exclusion, Kaizen is a powerful lever for inclusion IF it is practiced with this vigilance.

The 5 Principles in Synergy: A Systemic Vision

The five Lean principles are not five independent recipes to apply one after the other. They form a coherent system where each principle reinforces the others:

Defining value (1) guides the mapping of the value stream (2)
Mapping reveals where to create flow (3)
Flow is optimized by pull (4), which avoids overproduction
Kaizen (5) continuously improves all the previous elements
And Kaizen itself is guided by the definition of customer value (back to 1)

This circularity makes Lean a living, constantly evolving system, rather than a set of fixed rules.

Lean Management and 1Clusif Values: A Natural Convergence

Let’s return to the alignment between authentic Lean and 1Clusif’s founding values.

Equality: Respect for Every Contributor

The TPS’s “respect for people” pillar affirms that every worker possesses an intelligence that must be mobilized, not just their muscles. This conviction is deeply egalitarian: the line operator has as much intelligence and capacity for improvement as the engineer – simply applied to different domains.

Transmission: Organizational Learning

Kaizen rests on continuous learning. Every experience – success or failure – is an opportunity to learn. This learning culture aligns with our value of transmission: knowledge circulates, skills develop, people progress.

Responsibility: Autonomy Within Constraints

The pull system gives teams the responsibility to organize their work. With this autonomy comes accountability for results. It’s adult empowerment, neither infantilizing nor overwhelming.

Creativity: Everyday Problem-Solving

Lean values everyday creativity: finding ingenious solutions to recurring problems, imagining new ways of doing things. This creativity is not reserved for an elite of “creatives” – it is democratized at every level.

Entrepreneurial Spirit: Distributed Initiative

In a mature Lean culture, every person becomes an entrepreneur in their domain: they identify opportunities for improvement and take the initiative to realize them (with the organization’s support). This distributed entrepreneurial spirit aligns with our vision of organizations where innovation is born everywhere, not just at the top.

Drifts and Vigilance: For an Authentically Human Lean

Like any powerful philosophy, Lean can be misused. Let’s be clear-eyed about the possible drifts.

Drift 1: Lean as a Tool for Headcount Reduction

The worst drift consists of using Lean to “optimize” through layoffs. The reasoning: “We’ve eliminated waste, so we need fewer people.” This is a total betrayal of the Lean spirit.

In authentic TPS, efficiency gains are reinvested in improvement, not in layoffs. If a team becomes more productive, it can take on new projects, improve quality, or innovate – it should not be downsized.

1Clusif vigilance: We reject any Lean that dehumanizes or excludes. Efficiency must never come at the cost of excluding people.

Drift 2: The Intensification of Work

Another drift: using Lean to speed up the pace of work to the point of exhaustion. “We’ve eliminated dead time, so you must produce without interruption for 8 hours.”

Authentic Lean recognizes that humans are not machines. “Dead time” includes necessary moments of recovery, socializing, reflection. Eliminating all human “waste” leads to burnout.

1Clusif vigilance: Lasting efficiency requires respecting human rhythms, not denying them.

Lean encourages the standardization of best practices. But pushed to the extreme, this standardization can become bureaucratic rigidity: “The standard process says to do it this way, so we can’t do it any other way.”

Lean’s paradox is that standardization must serve continuous improvement, not freeze it. A standard is a base to improve upon, not an immutable dogma.

1Clusif vigilance: Valuing creativity and local adaptation over rigid uniformity.

Drift 4: Lean Without Respect

You can apply all the Lean tools (5S, Kanban, VSM) while maintaining a hierarchical and authoritarian culture where workers have no real power. That’s “mechanical Lean” without the human dimension.

1Clusif vigilance: Lean without respect for people is not Lean – it’s Taylorism in disguise.

Implementation: Where to Start?

For an organization wishing to embark on an authentic, humanist Lean approach, here are some directions.

Step 0: Clarify Intentions

Above all, why do you want to adopt Lean? If it’s mainly to reduce short-term costs, better be honest about it. If it’s to create a culture of continuous improvement that values every person, then the journey will be long but fruitful.

Step 1: Train in the Philosophical Fundamentals

Don’t start with the tools. Start with the philosophy: respect for people, systems thinking, humility in the face of complexity. This philosophical foundation will guide all subsequent decisions.

Step 2: Choose a Real Problem

Identify a concrete problem that truly affects people (customers or teams). Don’t choose an abstract “textbook case.” Lean transformation happens on real problems.

Step 3: Experiment with a Volunteer Team

Don’t roll out Lean to the whole organization at once. Work with a volunteer pilot team that wants to experiment. Learn together, celebrate successes, analyze failures.

Step 4: Create Spaces for Collective Reflection

Set up regular rituals (weekly or bi-weekly) where the team gathers to:

Visualize the value stream
Identify problems and waste
Propose experiments
Measure results
Celebrate progress

These spaces can use collective intelligence techniques to maximize everyone’s participation.

Step 5: Measure and Celebrate

Define simple indicators that show progress: delivery time, defect rate, team satisfaction, etc. And above all, celebrate victories, even small ones. Kaizen is a marathon, not a sprint.

Step 6: Spread Progressively

If the experiment works, neighboring teams will naturally want to adopt the approach. Let the transformation spread organically rather than imposing it by decree.

Lean and Digital: A Natural Affinity

For 1Clusif, the connection between Lean and software development deserves attention.

Lean Software Development

Lean principles were adapted to software development by Mary and Tom Poppendieck in their book “Lean Software Development.” The seven principles they propose flow directly from the five fundamental principles:

Eliminate waste: unused code, superfluous features, bugs, waiting
Amplify learning: short iterations, fast feedback
Decide as late as possible: keep options open in the face of uncertainty
Deliver as fast as possible: continuous deployment
Empower the team: autonomy and self-organization
Build integrity in: native quality, not added afterward
See the whole: systems thinking

DevOps: The Embodiment of Continuous Flow

The DevOps movement (a fusion of Development and Operations) is deeply Lean: it seeks to create an uninterrupted flow from developed code to code deployed in production. DevOps practices (continuous integration, continuous deployment, infrastructure as code) are direct applications of Lean principles.

Accessibility and Inclusion in Code

A humanist Lean perspective applied to software development also includes accessibility: creating software usable by everyone. Accessibility is not an optional “extra” – it is customer value for a significant portion of the population.

Similarly, a truly Lean development team seeks to be inclusive in its practices: pair programming accessible to juniors, documentation enabling easy onboarding, kind code reviews, valuing diversity of approaches.

Conclusion: Toward a Truly Humanist Lean

The five principles of Lean Management – defining customer value, mapping the value stream, creating uninterrupted flow, establishing a pull system, practicing Kaizen – constitute a powerful framework for creating more effective organizations. But their true power is only revealed when they are understood and applied in their deeply human dimension.

Authentic Lean is not an obsessive quest to eliminate costs. It is a philosophy of respect: respect for customers by delivering exactly what they value, respect for workers by valuing their intelligence and creativity, respect for resources by avoiding waste.

For 1Clusif, this humanist Lean resonates with all our values:

Equality: everyone can contribute to improvement
Inclusion: all perspectives are necessary to understand value
Transmission: continuous learning is at the heart of Kaizen
Responsibility: autonomy accompanied by commitment to results
Creativity: daily problem-solving unleashes innovation

But we are also clear-eyed about possible drifts. A Lean that intensifies work to the point of exhaustion, that standardizes to the point of robotization, that “optimizes” by excluding people – that is not Lean, it is its perversion.

The challenge of our time is to reinvent Lean for the 21st century: a Lean that fully integrates the issues of inclusion, diversity, well-being at work, environmental sustainability. A Lean that recognizes that true, lasting efficiency can only be built by fully honoring the humanity of every person involved.

This humanist Lean is not a distant utopia. It already exists in pioneering organizations that have understood that excellence and humanity are not opposed – that, on the contrary, the highest-performing organizations are those that mobilize the intelligence, creativity and engagement of all their members.

The five principles are our roadmap. It’s up to us to embody them with wisdom, vigilance and humanity.

To Go Further

Explore these additional resources to enrich your understanding of Lean and agile methods:

Discover the Agile Manifesto and its convergences with Lean
Explore the Scrum method for practical implementation
Understand how distributed governance amplifies Lean principles
Use Bono’s Six Thinking Hats in your Kaizen workshops
Practice Nonviolent Communication for improvements without violence

Written by Jérôme Savajols