Popular Tags

Lean Thinking Is Not Cost-Cutting: The Five Principles Leaders Often Miss
Ask ten executives what “lean” means and a surprising number will say some version of “doing more with less” — fewer people, tighter budgets, leaner headcount. That is a long way from what the idea’s originators described. Lean, as it was developed in Toyota’s production system and later named and popularised in the West, is a way of thinking about value and flow. Cost reduction can follow from it, but it is not the starting point, and treating it as the starting point is one of the most reliable ways to wreck a lean programme.
Where “lean” actually comes from
The Toyota Production System was developed over decades, with Taiichi Ohno as one of its central architects. The word “lean” itself was introduced to a wider audience by James Womack, Daniel Jones and Daniel Roos in The Machine That Changed the World (1990), and the framework most change leaders now cite was set out by Womack and Jones in Lean Thinking (1996). Jeffrey Liker’s The Toyota Way (2004) added the cultural dimension, describing the approach as resting on continuous improvement and respect for people.
That last point matters. In the original thinking, people are the engine of improvement, not the line item to be trimmed. Organizations that adopt the tools while quietly using them to justify layoffs tend to discover that the improvement ideas stop coming — which is exactly what you would predict if the people who hold those ideas have learned that sharing them is dangerous.
The five principles
Womack and Jones summarised lean thinking in five principles, and they work as a practical sequence for any leader.
1. Specify value from the customer’s point of view. Value is defined by the person who receives the product or service, not by the department that produces it. Most organizations skip this step and optimise whatever they are already doing.
2. Identify the value stream. Map every step that takes something from request to delivery, including the ones nobody owns. The map usually shows that a large share of elapsed time is spent waiting, not working.
3. Make the work flow. Once the steps that add no value are visible, remove the queues and hand-offs that break the sequence. Flow is the principle that most often exposes organizational boundaries — the point where one team’s priorities collide with another’s.
4. Let the customer pull. Produce what is actually requested, when it is requested, rather than building up work in progress because a plan or forecast says so.
5. Pursue perfection. Treat the first four principles as a loop, not a project. Each improvement reveals the next problem. There is no finish line, which is why lean is a leadership practice, not a one-off initiative.
Waste is a diagnosis, not an accusation
Ohno’s classic list of wastes (muda) names seven categories: overproduction, waiting, unnecessary transport, over-processing, excess inventory, unnecessary motion, and defects. Many practitioners add an eighth — unused talent — which is a useful reminder of the people-first reading above.
These categories translate easily outside manufacturing. A proposal that waits a week for sign-off is waiting. A report nobody reads is over-processing. Rework after a missed requirement is a defect. The point of naming waste is to see it clearly, and the useful discipline is to direct the lens at the process, never at the person doing the work inside it.
Five practical steps to start
Pick one value stream, not the whole company. Choose a process your customers actually feel — onboarding a client, answering a support request, releasing a feature — and keep the scope small enough to finish.
Go and see the work. The lean term is gemba: the place where the work happens. Walk the process with the people who run it before drawing any conclusions from reports.
Map it end to end, honestly. Record each step, who does it, and how long work sits between steps. Resist the urge to tidy the map; the ugly version is the useful one.
Ask the people doing the work what gets in their way. Frontline teams usually know where the delays and defects originate. Your job is to make it safe and worthwhile to say so.
Fix one thing, then check whether it helped. Run a small experiment, look at the result, and keep or drop the change. This is the improvement loop in miniature, and it builds the habit that makes later, larger changes easier.
Three common mistakes
Starting with tools instead of purpose. Value-stream maps, 5S and visual boards are useful, but a team that adopts them without agreeing what the customer values is only decorating the workplace.
Optimising one step in isolation. Speeding up a single department often just moves the queue to the next one. Lean asks you to improve the flow of the whole stream, which is why the mapping step comes first.
Declaring victory too early. A tidy before-and-after slide is not the same as a changed habit. If the improvement loop stops when the consultants leave, the gains usually leak away within months. The test of a lean organization is whether people keep finding and fixing problems when nobody is watching.
Where lean connects to leadership and change
Lean fails far more often because of leadership behaviour than because of method. If senior leaders ask for savings in the first week, staff will read the programme as a threat. If improvement ideas disappear into a backlog, people stop offering them. If leaders never visit the place where the work happens, they will keep deciding on the basis of reports that lag reality. These are change-management problems wearing process-improvement clothes, which is why lean sits naturally alongside the change models covered earlier in this series.
The takeaway
Lean is a discipline of seeing value, removing obstacles to flow, and building an organization where people are expected to improve their own work. Cost savings are a by-product of doing that well, not a substitute for it.
If you are planning a change or process-improvement effort and want an outside view on where to start, get in touch with Capacia Group — we work with leaders on exactly this intersection of leadership, change and operational improvement.
Mats Kallmyr

Written by
Mats Kallmyr
Mats works with leaders on innovation and change, process improvement and organisational development through Capacia Group. His background spans senior roles at Saab, Ericsson, Norsk Hydro, Preem and Swedavia.











