The scene is instantly familiar, no matter which factory I walk into. Red tags hang from unused fixtures. Fresh yellow floor markings divide the shop floor with geometric precision. A visual management board near the entrance displays hourly OEE, diligently updated by a supervisor who was trained, certified, and handed ownership of the process just a few months ago. In the first quarter after the rollout, productivity rises by 14 percent. At the regional review, the plant head presents the results and earns well-deserved applause.
Some months later, the picture looks very different. The tool audits have quietly disappeared. The visual board is still mounted on the wall, but the numbers haven’t been updated beyond the initial weeks. Operators who embraced the changes in the early months now dismiss them with a shrug, calling them “just another initiative” before the consultants have even left.
For anyone who has seen this cycle often enough, the outcome is hardly surprising. Everyone in the plant believed they were implementing Lean. In reality, they were practicing Industrial Engineering dressed up as Lean. The distinction is subtle on the surface, but profound in its consequences. It has quietly cost Indian manufacturing not only measurable productivity gains but also something far more valuable: credibility on the shop floor.
The root of the problem lies in how Lean is understood. Too often, organisations treat Lean as a collection of few operational tools — a buffet of 5S, Kaizen, SMED, Kanban, visual management, and value stream maps etc. while the Just-in-Time basket of Toyota Production System has about a hundred. By deploying some of them, the thinking goes, and transformation will follow. It never does.
That approach is closer to traditional Industrial Engineering than it is to Lean. It can remove some waste, improve layouts, reduce cycle times, and deliver impressive short-term gains. But because it focuses on implementing techniques rather than changing the way the organisation thinks and operates, the improvements gradually fade. The audits stop. The boards become wallpaper. Old habits return.
True Lean is something fundamentally different. Lean is not simply a better way to run operations; it is a way to build an enduring competitive advantage. At its highest level, Lean is not a shop-floor programme but a boardroom strategy. It creates an organisation that learns faster, adapts more quickly, solves problems more effectively, and continuously improves while competitors struggle to sustain yesterday’s gains.
This is the distinction that many organisations miss. Using Lean tools without Lean thinking is not Lean — it is Industrial Engineering pursuing productivity improvement under a different label. The tools may look identical, but the philosophy, the leadership, and ultimately the results are not.
Two Questions That Sound Similar But Aren’t
Industrial Engineering, the discipline that grew out of the scientific management movement a century ago, asks a fairly direct question: how can this task be done faster, cheaper, and with fewer resources? It is a question engineers are trained to answer well. Break the work into elements, measure the time, strip out unnecessary motion, design the most efficient method and roll it out. It works and has worked for a hundred years, and it still has a place on every serious shopfloor. But it is, by design, expert-driven. An IE study typically starts with someone holding a stopwatch and ends with a standard imposed on the people doing the work.
Lean Manufacturing, the version that emerged from the Toyota Production System, asks a different question entirely: how do you create value for the customer while developing people who can keep improving the system on their own? Notice what is missing from that sentence. There is no stopwatch in it. The person doing the work isn’t the subject of the improvement; they are the source of it. That difference between improving the process for people and building people who improve the process themselves is the entire ballgame. Get it backwards, and you can run every Lean tool in the book and still be doing IE.
Why the Tools Drive Failed
Go back to that plant. Every individual activity looked correct on paper. 5S audits happened. Time studies were run to set new standards. The line was re-laid out to improve flow. Targets were pushed down from the top, with dashboards to track them. None of that is wrong in isolation. The problem is where the energy was coming from. It was coming from outside the process, imposed on operators who were executing someone else’s plan. The early results were real. Most tool-driven interventions do produce a genuine first bump, because there is usually obvious waste sitting in plain sight, the kind any reasonably trained person can spot and remove.
What follows the bump is the part that gets skipped in most case studies. Discipline starts to slip once the the top management loses sight of Lean implementation as top priority and gets busy with something else. The workforce were never really involved in the thinking behind and making the changes, they may mechanically comply until another initiative blows over. Nothing about the culture has actually changed, because nothing about the culture was ever the target. Lean has not replaced IE in plants like this. It has simply rebranded it.
What Toyota Actually Built
The thing that makes the Toyota Production System (TPS) genuinely different isn’t a longer tool list. Toyota uses plenty of the same IE techniques: time and motion analysis, standardised work, layout optimisation. The difference is what those tools are for. In a true Lean system, a tool like standard work isn’t there to lock a method in place forever. It is there to expose the gap between how work is supposed to happen and how it is actually happening, so that gap becomes visible to the person closest to it and they can close it. An abnormality on the line isn’t a defect to be quietly absorbed into next quarter’s numbers. It is surfaced immediately, almost ceremonially, and treated as the start of a learning cycle rather than the end of a bad shift.
That changes who the improvement belongs to. Operators stop being people who execute a method someone else designed and start being people who notice problems and fix them, often with the same tools an IE team would use, but pointed in a different direction and owned by a different person.
The contrast plays out in:
- IE optimises for cost; Lean optimises for value as the customer defines it, and waste reduction follows from that rather than being chased for its own sake. Lean uses tools to expose problems and develop capabilities – not just drive metrics. IE is basically a toolkit, where as Lean is a Philosophy and a way of thinking.
- IE tends to set a method for a defined condition and hold it there. Improvements are often led by specialists. Lean expects the system to keep adapting as conditions change. In Lean everyone is an improver. Operators just don’t execute the work, they identify the problem, solve it and set the next standard.
- IE tends to optimise for a defined condition hence improvements are often local, Lean builds systems that adapt continuously, looking at the whole value stream, because a gain in one area could create a loss somewhere downstream. And the gains themselves could be temporary. Also a down stream problem could have been caused by an upstream decision or action.
- Productivity numbers generated by IE-style improvements run in silos can sit there without ever moving the needle on the company’s actual financial results. Gains from a genuine Lean system tend to show up on the balance sheet, because they are sustaining and connected to flow and customer value rather than isolated efficiency metrics.
The Plant That Got It Right
Not every story in this space ends with a tool board gathering dust. Look at India’s first (pioneer) full comprehensive lean transformation The Mysore Kirloskar Ltd Hubli Story. Leading the transformation, I spent the first couple of years working alongwith workmen and staff most of two shifts everyday bringing problems to surface, brainstorming to identifyroot causes and solving them. My training method was participative demonstration and not directorial. My playing a role of a participant motivated the people to make it habitual. Tools were used as tools to expose and solve problems, and by doing so everyday growing and develop people who could keep making improvements every day became a culture.
The beginning was less dramatic in result numbers as we had to stop production many times to solve problems – design, supply chain, process etc. But what changed was the enthusiasm with which the workmen began to expose and solve problems at root, while the staff worked on systemic improvements, visual signaling, failure proofing, simplification,improving flow etc. After the initial learning over three years we improved the enterprise value twelve hundred times, near hundred percent customer satisfaction, sixty percent reduction in costs, and more as you can read from the above link to the case study.
Where the Confusion Starts
Part of the problem is that the Lean and the IE toolkit that overlap. Standard work, value stream mapping, time studies, layout redesign, visual management: a consultant trained in either discipline reaches for the same shelf. The Toyota Production System or Lean integrates IE into a broader socio-technical system. TPS combines technical excellence through IE methods, Human Development through respect for people and their empowerment, and a Management Philosophy that’s long term and principle driven decisions. This integration creates a self-reinforcing cycle: better processes develop better people, better people create better processes and therefore better value.
In contrast, when Lean is reduced to tools, it loses this reinforcing loop. It behaves like IE — delivering episodic improvements without building enduring capability. Industrial Engineering is necessary for Lean — but not sufficient. Using tools alone is IE thinking applied harder, not Lean thinking applied differently. True Lean begins when tools are used not just to improve processes, but to develop people who can improve processes every day.
The Insight That Actually Matters
None of this is an argument against Industrial Engineering. IE is necessary. A Lean system without sound technical method underneath it is just enthusiasm with no engineering behind it, and that doesn’t last either. The point worth holding onto is narrower, and for that reason harder to argue with: IE is necessary for Lean, but it is not sufficient.
Using tools without the thinking behind them isn’t a lighter version of Lean. It is IE, applied with more energy and a different vocabulary. The transformation only starts when the tools stop being used purely to fix the process and start being used to build people who can identify and solve problems on a daily basis.
The difference between The Mysore Kirloskar Ltd. Hubli Story and the vast majority who claim to be Lean by using a dozen or so hand picked tools are vast and many, to highlight a few – Lean was their competitive strategy, cost was the advantage they built, competition was made irrelevant, enterprise value and profits soared, CAGR of revenue growth was close to seventy percent, the entire production from order receipt to delivery was controlled and executed by workmen including vendor procurement without the involvement of staff and lots more. Such excellence can never be achieved by mere implementation of IE or random lean tools.
The difference between Lean Manufacturing and Industrial Engineering is not in the tools — they often share the same ones. The difference lies in intent and system design. Industrial Engineering optimises the present. Tool-driven Lean imitates this optimisation. But true Lean builds the capability to continuously transform the future. And that is why the Toyota Production System remains not just a method of efficiency — but one of the most enduring sources of competitive advantage in modern industry.
