Excellence is an eminent degree of quality. A simple, almost obvious definition, but one that becomes formidably demanding the moment you confront it with the daily reality of a technical team. Because in a world where customer expectations keep evolving, reaching that level of quality isn’t enough: you have to maintain it, again and again, despite the incidents, the bugs, and the debt that piles up. How do you do that? That’s precisely the question Lean Management answers concretely, provided you don’t reduce it to what it isn’t.
Lean is not a toolbox
The first mistake is to see Lean as a collection of methods or tools: sticky notes on a wall, a Kanban board, a few copy-pasted rituals. That’s missing the point entirely. Lean is, above all, a continuous learning system. Its purpose isn’t to optimize processes in the abstract, but to grow people’s skills: individually and collectively.
That growth in skills, however, is anything but random. It’s strictly aligned with a single goal: value creation on the Gemba: the field, the real place where the work gets done and where value is produced. You don’t learn for the sake of learning; you learn to serve the customer better, right where things actually happen. It’s this grounding that sets Lean apart from a purely cosmetic improvement effort.
Turning every malfunction into a learning opportunity
If Lean is a continuous stream of learnings, you still need to know how to feed it. The key is a shift in perspective: treating every malfunction, every bug, every incident that arises in the value production chain not as a nuisance to clear away as fast as possible, but as an opportunity to learn.
It’s a profound reversal of stance. In software, the reflex when facing a bug is well known: you apply a quick fix, a hot fix. The software works again, the customer is satisfied… for now. And that’s exactly the trap: you have the feeling you’ve done the work, when you’ve only done half of it.
The invisible half of the work
Once the symptom is fixed, three questions remain open, and they’re the ones that hold all the learning value:
- Why did this bug happen? What’s the root cause, not merely the visible manifestation?
- How do we prevent it from happening again? What guardrail, what test, what design change would make it structurally impossible?
- What lessons can we draw from it, and above all, spread to the rest of the team?
As long as these questions go unaddressed, the work is only half done. The hot fix treated the symptom; it taught no one anything.
The cost of uncapitalized learning
What happens when you neglect that second half? The learning from the problem is neither drawn out nor shared, and two consequences follow mechanically.
The first is the repetition of mistakes. Without having understood and spread the root cause, the problem stands every chance of resurfacing, in a slightly different form, somewhere else, or simply later. You end up living that familiar scene: a chat with a colleague who lets slip, “ah, but that problem, I had it too.” Two people hit the same wall, with nothing passing between them. That’s wasted learning, and therefore time lost collectively.
The second consequence, more direct still, is the drop in customer satisfaction. Customer satisfaction is one of the pillars of Lean, and every recurring problem erodes it, all the more sharply as it repeats. It’s exactly what the approach seeks to avoid at all costs: the silent degradation of trust, bug after bug, because no one ever took the time to capitalize.
Don’t solve, eradicate
In the end, the whole difference comes down to a nuance that one of my Lean sensei, Philippe Fenot, captures perfectly:
With Lean, you don’t seek to solve a problem but to eradicate it.
Solving means making the symptom disappear here and now. Eradicating means ensuring that the problem can never reappear, because you’ve understood its cause, modified the system that produced it, and spread the learning to the whole team. The first stance deals with the present; the second builds the future.
It’s that demand, applied to every incident, that makes Lean a genuine engine of technical excellence. Not one more method, but a way of turning every failure into an acquired skill, and of protecting, over the long run, the quality the customer perceives.