The Death of Best Practice: Why Continuous Improvement Beats Benchmarking

There is a comfortable idea in management circles that goes something like this: find the organisations that do something well, study what they do, copy it, and you will get similar results. This is benchmarking, and its output is called "best practice." It sounds rational. It sounds efficient. And it is, in many cases, the opposite of genuine improvement.

The pursuit of best practice has become one of the most widespread substitutes for actual thinking in modern organisations. Rather than understanding your own system, your own constraints, your own variation, you import someone else's answer and call it progress. Toyota, the organisation most frequently cited as the source of best practices worth copying, has been explicit about why this approach fails. Their 14th management principle states it clearly: become a learning organisation through relentless reflection and continuous improvement. Not through copying. Through learning.

The Factory That Was Already Lean

One of the most revealing stories in Lean literature comes from Jeffrey Liker's study of Toyota's supplier support programme. A US factory had been recognised as a Lean exemplar. It had implemented value stream mapping, 5S, kanban, and pull systems. By any benchmarking standard, it was performing well.

Then Toyota's Operations Management Consulting Division visited. After a thorough analysis, they identified a 93% reduction potential in lead times and an 83% reduction potential in work-in-progress inventory. The factory that everyone was benchmarking against still had enormous room for improvement. The tools were there, but the thinking was not.

This is the fundamental problem with best practice: it creates a ceiling, not a foundation. When you define "best" as what someone else has already achieved, you anchor your ambition to their current state. You stop looking for improvement because you have already reached "best." Kaizen, the principle of continuous improvement, requires the opposite mindset. There is no best. There is only better than yesterday.

Standardised Work Is Your Baseline, Not Theirs

One of the most misunderstood concepts in Lean thinking is standardised work. Many organisations interpret it as finding the "best way" to do something and then enforcing it. That interpretation misses the point entirely.

Standardised work in the Toyota Production System is not a permanent instruction. It is a current baseline, the best way we know how to do this work right now, documented so that deviations become visible. When a deviation occurs, it is not a failure. It is information. Either the standard needs updating or the process needs attention.

The critical word is "we." Standardised work is developed by the people who do the work, based on their understanding of their process, in their context. It cannot be imported from another organisation and retain its meaning. When you adopt someone else's standard, you lose the most valuable part: the understanding of why each element exists and what it protects against.

This is why copying Toyota's tools without Toyota's thinking produces disappointing results. The tools are expressions of deep understanding. Without the understanding, they are just procedures.

Deming and the Tyranny of External Comparison

  1. Edwards Deming, whose philosophy shaped much of what became the quality movement, was deeply sceptical of benchmarking. His approach centred on understanding variation in your own system. Every process has natural variation, what Deming called common cause variation, and every process occasionally experiences special cause variation from external disruptions.

The critical management skill is knowing which type you are dealing with. Tampering with common cause variation, reacting to every fluctuation as if it were a crisis, makes the system worse. Ignoring special cause variation, treating a genuine disruption as normal noise, allows problems to persist.

Benchmarking obscures this distinction entirely. When you compare your numbers to another organisation's numbers, you are comparing the outputs of two different systems with different variation patterns, different constraints, and different histories. A metric that is normal in one system may indicate a crisis in another, and vice versa. The comparison tells you almost nothing about what to do next.

Deming's alternative was to study your own system, understand its capability, reduce variation where possible, and improve steadily. This requires statistical thinking, patience, and a willingness to learn from your own data rather than someone else's highlights.

Why Best Practice Is the Enemy of Kaizen

Kaizen, often translated as "continuous improvement," requires a specific psychological condition: the belief that the current state, no matter how good, can be improved. This is not a motivational platitude. It is a practical necessity. Without it, improvement activities stop.

Best practice directly undermines this condition. When an organisation declares that it has adopted "best practice," it sends a clear signal: we have arrived. The search is over. Any further improvement would take us beyond "best," which is by definition unnecessary. The language itself is a barrier.

Consider the difference between two statements:

"We follow industry best practice for deployment."

"Our current deployment process takes 45 minutes. We believe we can reduce it to 20."

The first statement closes the door to improvement. The second opens it. The first anchors to an external, vague standard. The second anchors to a specific, measurable reality that invites experimentation.

Toyota's internal culture reinforces this constantly. When a team completes an improvement, the question is never "Are we at best practice now?" The question is "What is the next problem to solve?" The improvement cycle has no endpoint by design.

The Consultancy Problem

The benchmarking industry is worth billions, and a significant portion of management consulting revenue comes from telling organisations what other organisations do. There is a structural incentive to promote best practice: it is easier to sell a known answer than a learning process.

But the organisations that sustain excellence over decades do not operate this way. They study others for inspiration, certainly. Toyota studied US supermarkets to develop the kanban system. But they did not copy supermarket operations. They extracted a principle, pull-based replenishment, and adapted it to their own context through extensive experimentation. The difference between "copy" and "learn from" is enormous.

This distinction matters for any organisation serious about improvement. Visiting other companies, attending conferences, reading case studies: all valuable. But the value lies in expanding your thinking, not in finding answers to copy. The answers must come from your own experimentation, in your own context, with your own constraints.

What We Do Differently

At TaiGHT, we have lived this lesson. We come from manufacturing environments where Lean tools were adopted without the underlying thinking, and we saw the gap between "we do 5S" and genuine continuous improvement. That experience, combined with statistics education and software development skills, means we approach every engagement the same way: understand your current state through data, identify your specific constraints, and build from there.

We do not arrive with playbooks. We arrive with questions: what does your process actually look like, what does the data say, and what is your next problem to solve? If that approach resonates, we would welcome the conversation.

References

  • Liker, J. K. (2004). The Toyota Way: 14 Management Principles from the World's Greatest Manufacturer. McGraw-Hill.
  • Deming, W. E. (1993). The New Economics for Industry, Government, Education. MIT Press.
  • Deming, W. E. (1986). Out of the Crisis. MIT Press.
  • Rother, M. (2010). Toyota Kata: Managing People for Improvement, Adaptiveness, and Superior Results. McGraw-Hill.
  • Spear, S., & Bowen, H. K. (1999). Decoding the DNA of the Toyota Production System. Harvard Business Review, 77(5), 96-106.
  • Imai, M. (1986). Kaizen: The Key to Japan's Competitive Success. McGraw-Hill.