Taiichi Ohno spent forty years, from 1943 to the late 1980s, building what became known as the Toyota Production System.
The system produced Japan’s dominance of the global auto industry. It produced the philosophies that became lean manufacturing, just-in-time inventory, kanban, and dozens of other operational disciplines that have since been adopted across industries far beyond automotive manufacturing.
Throughout those forty years, executives from around the world visited Toyota to study what Ohno had built. They watched the production lines. They saw the results. They understood, in principle, what was being done differently.
Then, almost universally, they returned to their own companies and did not implement it.
The reasons they gave were consistent. Our industry is different. Our workers are different. Our customers are different. Our regulatory environment is different. Our scale is different. Our culture is different.
Ohno heard these objections for decades. His response, documented in Mike Rother’s Toyota Kata (McGraw Hill, 2010) and in Donald Reinertsen’s Principles of Product Development Flow (Celeritas, 2009), was the same every time.
He would ask, in effect: is your situation different at the level of physics? Because the physics of production — the effects of variability, the mathematics of queues, the compounding cost of defects, the value of small-batch flow — are universal. If your situation is different only at the level of your specific industry or your specific culture, then the physics still applies to you. The specific applications differ. The underlying principles do not.
The uniqueness defense
The pattern Ohno identified — “our situation is different” as a reason not to implement a demonstrated better approach — is one of the most common executive responses to any transformational proposal.
It is comfortable because it protects the existing organization from having to change. It is defensible because it is technically true at some level — every situation is different in some particulars. It is dangerous because it systematically prevents the adoption of principles that would produce dramatic improvement.
The defense operates as a diagnostic. When you hear it from senior leaders in your organization about a proposed transformation, what you are hearing is not an argument. You are hearing a refusal to engage with the underlying principles.
The 2026 application
Every senior leader I work with in 2026 is hearing some version of the uniqueness defense about AI transformation.
Our industry is different — AI won’t work in regulated financial services / healthcare / defense / education / manufacturing.
Our customers are different — they don’t want AI-mediated interactions.
Our workflows are different — they can’t be represented in a form that AI can operate on.
Our data is different — it doesn’t have the structure that AI systems require.
Our regulatory environment is different — we can’t deploy AI at scale.
Every one of these claims is technically true at some level of specificity. Every one of them is being used, in most organizations, as a reason not to engage with the underlying transformation.
The Ohno response applies: is your situation different at the level of physics? The underlying physics of AI transformation — that dramatically cheaper cognitive capability changes what work can be done at what cost, that this changes the competitive dynamics of every knowledge-intensive industry, that early adopters compound advantages that late arrivals cannot recover — are universal. Your specific industry, workflows, and regulatory environment shape the specific applications. They do not exempt you from the underlying principles.
The proper use of uniqueness
To be clear: the uniqueness defense is not always wrong. There are specific situations in which a proposed transformation genuinely does not apply to a specific context.
The correct use of uniqueness is not “we are different, therefore we should not do this.” The correct use is “we are different in this specific way, therefore the implementation must be modified in this specific way.” The first framing prevents transformation. The second framing enables context-appropriate transformation.
Senior leaders can test which version of uniqueness their organization is operating on by asking a simple question: what specific modification to the standard approach would make it work in our context?
If the answer is a specific technical, regulatory, or organizational adjustment, the uniqueness is being used properly. If the answer is a vague gesture at complexity — “we would need to think about it” or “we would need consultants to help us figure it out” — the uniqueness is being used as a refusal.
Three practical questions
One: which specific AI transformation proposals in your organization have been slowed or rejected on uniqueness grounds? List them. For each, ask what specific modification would make it work in your context.
Two: at the level of physics, is your situation actually different from the situations where AI transformation is producing value? If the physics is the same, the principles apply. Only the applications differ.
Three: who in your organization is entitled to invoke the uniqueness defense without producing the specific modification that would enable the transformation? The people occupying this position are, structurally, the veto points on your AI transformation. Change the terms of their authority.
The closing thought
Taiichi Ohno died in 1990. His response to the uniqueness defense outlived him and applies more directly in 2026 than it did in his lifetime.
The senior leaders who accept the uniqueness defense uncritically will continue running organizations that watch competitors deploy transformative approaches, understand them in principle, and fail to implement them. This has been the pattern for four decades. AI is not going to break the pattern. AI is going to make it more expensive.
The senior leaders who insist on the Ohno test — is your situation different at the level of physics? — will produce organizations that adopt underlying principles while adapting specific applications to their context. This is what Toyota’s imitators, when they eventually appeared, actually did. It is what the AI-adopting organizations that will define the next decade are doing right now.
The world has changed. The leaders who notice will be the ones the next decade is built around.
