What Lean Experts Know That Most Managers Don’t: 8 Principles Worth Internalising
Lean gets misrepresented constantly. In boardrooms it becomes a cost-cutting mandate. On the shop floor it becomes a 5S blitz that fades within a quarter. In training catalogues it becomes a certificate programme with no follow-through. None of that is Lean.
The thinkers who built the intellectual foundation of lean continuous improvement were not offering productivity tricks. They were describing a fundamentally different way of thinking about work, people, and organisational systems. For Canadian managers navigating competitive pressure, labour market shifts, and supply chain complexity, these principles are worth reading carefully and internalising slowly.
What follows is not a motivational quotes list. It is eight ideas, expressed in the words of those who originated them, with commentary on what each one actually demands in practice.
1. The system is responsible for most of what goes wrong
“A bad system will beat a good person every time.”
W. Edwards Deming
Most performance conversations in organisations focus on individual behaviour: who missed the deadline, who made the error, who needs to improve. Deming spent decades arguing that this framing is almost always wrong. In his analysis of variation in manufacturing and service systems, he concluded that roughly 94 percent of problems originate in the system itself, not in individual effort or attitude.
The practical implication is significant. When a Canadian manufacturer sees rising defect rates, or when a healthcare organisation sees long patient wait times, the instinct to retrain individuals or add supervision layers rarely addresses the root cause. The process design, the measurement system, the information flow, the equipment condition: these are the levers that actually produce results.
Lean continuous improvement starts with the humility to ask what does our system make easy, and what does it make hard, before it asks anything about people.
2. Waste is not the exception; it is the norm
“All we are doing is looking at the time line, from the moment the customer gives us an order to the point when we collect the cash. And we are reducing that time line by removing the non-value-added wastes.”
Taiichi Ohno
Ohno, the architect of the Toyota Production System, described waste (muda) with ruthless specificity. Overproduction, waiting, unnecessary transport, over-processing, excess inventory, unnecessary motion, defects: these seven categories, later expanded to eight, were not edge cases. They were the dominant feature of most production and service environments.
In Canadian operations, this framing is clarifying. A purchasing team that generates purchase orders in triplicate, a logistics function that moves product through three staging areas before shipping, an onboarding process that requires new employees to enter the same information into four separate systems: all of these contain substantial non-value-added time. The customer pays for none of it.
The discipline is in learning to see it. Value stream mapping, time-observation studies, and process walk-throughs are not bureaucratic exercises. They are the tools by which waste moves from invisible assumption to visible target.
3. Go to where the work actually happens
“Data is of course important in manufacturing, but I place the greatest emphasis on facts.”
Taiichi Ohno
Ohno’s insistence on genchi genbutsu (go and see for yourself) is one of the most consistently violated principles in management practice. Decisions made from dashboards, from second-hand reports, and from conference room assumptions routinely miss the reality of the work. The gap between how a process is documented and how it is actually performed is almost always larger than managers expect.
Gemba walks are a structured application of this principle. A leader who spends thirty minutes on the floor, at the workstation, at the customer service desk, or in the warehouse, asking questions and observing flow, learns things that no KPI report surfaces. Deviations from standard, informal workarounds, recurring small problems that frontline staff have stopped escalating because nothing happened last time: these are the facts that drive meaningful improvement.
For Canadian organisations with distributed sites or remote operations, this requires intentional scheduling. The discipline to go and see must be built into operational rhythms, not left to chance.
4. Standard work is a precondition for improvement
“Without standards, there can be no kaizen.”
Taiichi Ohno
This is perhaps the most misunderstood principle on this list. Standard work is often resisted as rigid, bureaucratic, or contrary to professional judgment. Ohno’s point is the opposite: without a documented baseline of how work is currently done, you have no reference point against which to measure improvement. You are changing something, but you cannot know whether the change was an improvement.
Standard work is not a ceiling. It is the current best-known method, documented clearly enough that deviations are visible and improvements can be captured and shared. In a professional services firm, a healthcare team, or a manufacturing cell, the absence of standard work means that each person improvises independently. Variation accumulates. Problems are solved again and again. Knowledge walks out the door when experienced staff leave.
Lean continuous improvement requires a stable platform. Standard work provides it.
5. Improvement must be relentless, not episodic
“There is something called standard work, but standards should be changed constantly. Instead, if you think of the standard as the best you can do, it’s all over.”
Shigeo Shingo
Shingo, whose contributions to rapid changeover (SMED) and mistake-proofing (poka-yoke) transformed manufacturing practice globally, understood improvement as a continuous obligation, not a periodic project. The standard is not the goal. It is the floor you stand on while reaching for the next improvement.
Many Canadian organisations approach continuous improvement as a series of discrete initiatives: a kaizen event this quarter, a process review next year. This produces real results in the short term, but it is not the operating system Shingo and his contemporaries were describing. The goal is a culture in which every team member, every day, is looking for small improvements in their own work and surfacing problems to the team.
The structural enablers for this are well understood: daily huddles, visual management boards, clear escalation paths, and leadership that responds to problems with curiosity rather than blame. Building these habits is harder than running a kaizen event. It is also more durable.
6. Specify value from the customer’s point of view
“Value can only be defined by the ultimate customer. And it’s only meaningful when expressed in terms of a specific product which meets the customer’s needs at a specific price at a specific time.”
James P. Womack and Daniel T. Jones, Lean Thinking
This is the starting point of lean thinking as Womack and Jones codified it. Before mapping value streams, before identifying waste, before improving flow: first, define what the customer actually values. This sounds obvious. In practice it is routinely skipped or assumed.
In Canadian organisations, value is frequently defined by internal convenience, historical practice, or regulatory compliance rather than by what customers are actually willing to pay for. A manufacturer that offers twelve product variants because the sales team has always offered twelve product variants, regardless of whether customers value that variety, has confused capability with value. A professional services firm that produces dense deliverables because that is what demonstrates effort, rather than what clients need to act, has made the same mistake.
The discipline of starting with the customer forces a productive discomfort. It asks teams to distinguish between what they do and what the customer needs, and to close that gap deliberately.
7. Flow and pull are the structural goals
“The Toyota style is not to create results by working hard. It is a system that says there is no limit to people’s creativity. People don’t go to Toyota to work, they go there to think.”
Taiichi Ohno
Lean’s structural ambition is to create systems where work flows continuously toward the customer without interruption, and where production is triggered by actual demand rather than forecast and push. Flow and pull are technical concepts with deep practical implications. They require redesigning how work is sequenced, how inventory is managed, how information moves through the organisation, and how scheduling decisions are made.
For Canadian operations teams, the journey toward flow often starts with identifying the biggest sources of waiting and batching. Work that sits in inboxes, approval queues, or staging areas is not flowing. Capacity that is consumed producing output no one has yet asked for is not pulled. These are design problems, and they are solvable, but only when the system is viewed as a whole rather than as a collection of departmental functions each optimising independently.
This is why Lean is organisational change work, not just a set of tools.
8. Lean is a management system, not a toolkit
“The Toyota Way is really about problem-solving. It’s about challenging and developing people to become better problem-solvers.”
Jeffrey K. Liker, The Toyota Way
Liker’s research into Toyota surfaced something that many organisations miss entirely. The visible tools of Lean, 5S, kanban, A3 reports, value stream maps, are not the point. They are the scaffolding for a management system in which leaders develop people, problems are surfaced early, root causes are investigated rigorously, and countermeasures are tested and standardised. The tools work when the management system supports them. They do not work when they are deployed without that context.
This is the most important principle on this list for Canadian managers to carry into implementation. If your lean continuous improvement programme consists of running workshops and deploying visual boards without changing how leaders spend their time, how problems are escalated, and how improvement is recognised, you will produce short-term gains and long-term reversion. The organisations that sustain Lean are the ones that have built it into how management actually works: daily, at every level.
Putting These Principles to Work in Your Organisation
These eight ideas are not a checklist. They are a coherent philosophy of how work should be designed, how problems should be approached, and how people should be developed. Internalising them takes time, and applying them takes structure.
Leading Edge Associates works with Canadian manufacturing, healthcare, and service organisations to build lean continuous improvement capability that lasts. Whether you are beginning your lean journey or looking to deepen an existing programme, our advisory and training services are grounded in the same principles Deming, Ohno, Shingo, and Womack articulated: go to the work, understand the system, eliminate waste, and develop your people.
If you would like to explore what a structured approach to lean principles could look like for your organisation, contact our team or browse our training programmes.
