Quality
and the Not Invented Here Syndrome: When Your Organization Rejects Best
Practices Because They Came From Somewhere Else — and the Solutions You
Refused to Copy Became the Failures You Were Forced to Repeat
The
Quality Department That Rebuilt Everything From Scratch
In 2011, a mid-size automotive supplier in Slovakia landed a contract
with a major German OEM. The deal was transformative — enough revenue to
double the company’s capacity and establish it as a tier-one player in
the European market. There was one condition: the supplier needed to
implement a formal quality management system certified to ISO 9001
within twelve months.
The quality director, a capable engineer named Milan, assembled his
team and began working. But when a consultant recommended adopting a
proven QMS framework already successfully deployed at three similar
suppliers in the region, Milan’s response was immediate and firm: “We
are not those companies. We have our own way of doing things. We will
build our own system.”
Over the next eleven months, Milan’s team designed a quality
management system from the ground up. They created their own document
control procedures, their own CAPA workflow, their own audit protocols,
and their own supplier evaluation forms. Every template was custom.
Every process was original. Every form had the company’s logo freshly
designed into the header.
The certification audit failed. The auditor found seventeen major
nonconformities — every single one of them related to issues that had
been solved decades ago by the quality profession and documented in
freely available frameworks. The corrective actions Milan’s team needed
to implement were, ironically, almost identical to the standard
procedures the consultant had recommended in the first place.
The company lost the contract. Milan was replaced. And the new
quality director implemented an off-the-shelf QMS framework in four
months, passed the audit, and regained a modified version of the
contract at a lower margin.
The original system Milan’s team built from scratch? It wasn’t
innovative. It wasn’t superior. It was simply theirs. And that was the
only reason they wanted it.
This is the Not Invented Here syndrome in quality management. And it
costs organizations more than almost any other cognitive bias in the
professional landscape — because unlike most biases, it doesn’t just
distort your thinking. It actively prevents you from using solutions
that already exist.
What Is Not Invented Here
Syndrome?
Not Invented Here syndrome — commonly abbreviated as NIH — is an
organizational attitude where teams reject external knowledge, tools,
methods, or practices simply because they were developed outside the
organization. It’s not skepticism, which is healthy. It’s an
identity-driven refusal to adopt anything that wasn’t created in-house,
regardless of its proven effectiveness.
The concept emerged in the 1960s from research at IBM, where
engineers were observed routinely rewriting software that already
existed elsewhere. But the phenomenon predates computing by centuries.
Medieval guilds guarded their techniques so fiercely that innovations
spread at a glacial pace across Europe. Entire cities rebuilt solutions
that neighboring cities had already perfected.
In quality management, NIH manifests in specific, recognizable
patterns:
- Refusing to adopt industry-standard frameworks
(ISO, IATF, AS9100) and instead creating bespoke quality systems - Rejecting proven tools (FMEA software, SPC
platforms, calibration management systems) in favor of building custom
tools internally - Ignoring published best practices from professional
bodies (ASQ, SAE, AIAG) because “our situation is different” - Dismissing competitor improvements as irrelevant
rather than studying them for applicable lessons - Avoiding cross-industry learning — a pharmaceutical
company refusing to study automotive quality methods, or vice versa - Requiring internal validation of externally validated
methods — running your own studies to confirm what decades of
research already established
The psychological foundation is straightforward: identity. When a
team or organization has built its sense of competence around its own
methods, adopting external methods feels like an admission of
inferiority. The defense mechanism is to devalue whatever comes from
outside.
Why NIH
Is Particularly Dangerous in Quality Management
Quality management sits in a unique position within organizations. It
is simultaneously one of the most standardized professions in the world
and one of the most vulnerable to NIH thinking. This creates a paradox
that makes the bias especially destructive.
The standardization is real. Quality tools like
FMEA, SPC, MSA, APQP, and PPAP are not suggestions. They are structured
methodologies refined over decades by thousands of practitioners across
industries. The AIAG core tools manuals represent the collective
learning of an entire profession. ISO standards encode lessons paid for
by countless failures. These aren’t theoretical frameworks — they’re
distilled experience.
But the NIH impulse is also real. Quality
professionals are, by training, critical thinkers. They question
assumptions. They challenge claims. They demand evidence. This is
exactly what makes them good at their jobs — and exactly what makes them
vulnerable to NIH. Because the line between healthy skepticism and NIH
is remarkably thin. “Show me the evidence” is the quality professional’s
credo. “I don’t trust evidence from outside my organization” is NIH
wearing a lab coat.
The result is that quality departments — the very functions that
should be most inclined to adopt proven best practices — are often the
most resistant to doing so. And the consequences are severe:
1. You Waste
Resources Reinventing Solved Problems
Every hour spent designing a custom CAPA form is an hour not spent
actually correcting and preventing defects. Every week spent debating
whether to use an industry-standard FMEA methodology is a week of
unanalyzed risk. The opportunity cost of NIH is staggering.
I once consulted with a medical device manufacturer that spent
eighteen months and over €200,000 developing an internal training system
for quality auditors. When I showed them the ASQ Certified Quality
Auditor body of knowledge — a comprehensive, internationally recognized
framework available for free — the quality manager’s response was: “Yes,
but that’s generic. Ours is specific to our company.”
Their system covered 70% of what the ASQ framework covered. It lacked
any mention of risk-based auditing, process-based auditing, or remote
audit techniques. The 30% it missed were the areas where the company
subsequently experienced the most audit findings.
2. You Repeat
Failures Others Have Already Survived
The history of quality is written in failures. Every major quality
framework, every standard, every tool exists because something went
catastrophically wrong somewhere, and the profession learned from
it.
When you reject external knowledge, you don’t just reject the
solutions. You reject the accumulated experience of every failure that
led to those solutions. You are, in effect, choosing to learn the hard
way — to make the mistakes yourself instead of learning from the
mistakes of others.
The pharmaceutical company that refuses to study automotive supplier
quality practices will learn about supply chain failures the same way
the automotive industry did twenty years ago — through experience, at
cost. The aerospace manufacturer that dismisses pharmaceutical GMP
principles will discover contamination control issues that pharma solved
decades ago.
3. You Create
Isolation That Breeds Complacency
Organizations suffering from NIH don’t just reject external solutions
— they stop looking for them. The quality team stops attending industry
conferences. They stop reading professional journals. They stop
benchmarking against other organizations. They stop participating in
professional networks.
This isolation is corrosive. Without external reference points, the
organization’s quality system drifts. Standards that once seemed
rigorous become outdated. Methods that were adequate five years ago fall
behind current best practices. The team doesn’t notice because they have
nothing to compare against.
I’ve walked into quality departments that were proud of their 2%
defect rate, completely unaware that their competitors were running at
0.3%. Their pride wasn’t based on excellence — it was based on
ignorance. NIH had insulated them from the information that would have
revealed how far behind they had fallen.
4. You Signal Arrogance
That Repels Talent
Talented quality professionals want to work with cutting-edge tools
and methods. They want to learn and grow. When an organization’s culture
says “we know better than everyone else,” it attracts people who agree
with that sentiment and repels people who know better.
The result is a quality team that reinforces its own isolation. The
people who stay are the ones who believe the organization’s way is the
best way. The people who leave are the ones who have seen enough of the
outside world to know it isn’t.
The
Root Causes: Why Smart Organizations Fall Into the NIH Trap
Understanding NIH requires understanding what drives it. It’s not
stupidity. It’s not laziness. It’s a combination of psychological and
organizational dynamics that are deeply human.
Identity and Competence
For many professionals, their methods are part of their identity.
“I’m the person who developed our FMEA process” is a statement about
professional worth, not just process design. Adopting someone else’s
FMEA method feels like admitting that your method — and by extension,
you — was inadequate.
This is especially powerful in quality, where professionals are often
the smartest people in the room. They’re the ones who see the problems
others miss. They’re the ones who solve the puzzles that stump everyone
else. Being told that someone else already solved the puzzle — and
solved it better — is a direct challenge to their self-concept.
Organizational Pride
Organizations, like people, have egos. Companies that have succeeded
through their own innovations develop a narrative of exceptionalism: “We
succeeded because we did things our way.” This narrative makes it
psychologically difficult to adopt external methods, because doing so
contradicts the story the organization tells about itself.
This is particularly dangerous in organizations that have experienced
genuine success. A company that built a market-leading product through
internal innovation may extend that confidence to areas where internal
innovation is actually a liability — like quality systems, where
standardization is more valuable than originality.
The “Our Situation Is
Different” Argument
This is the most common and most seductive NIH justification. And it
has a grain of truth: every organization’s situation is, in some ways,
unique. Your products are different. Your processes are different. Your
customers are different.
But this argument is usually applied far too broadly. The principles
of statistical process control don’t change based on your product. The
logic of failure mode analysis doesn’t depend on your industry. The
structure of a corrective action process isn’t specific to your company.
The fundamental tools of quality are universal precisely because they
address universal patterns of variation, failure, and human error.
When someone says “our situation is different,” the correct response
is: “Different in what specific way? And does that specific difference
actually change how this tool should be applied?” Most of the time, the
honest answer is no.
Not Invented Here
vs. Not Invented by ME
There’s a particularly toxic variant of NIH that operates at the
individual level: “Not Invented by Me.” This occurs when a manager or
director rejects not just external solutions, but solutions proposed by
other departments, other teams, or even other individuals within the
same organization.
In quality management, this manifests as quality directors who reject
engineering’s process improvement suggestions, or plant managers who
override quality recommendations because “operations knows best.” It’s
NIH scaled down to interpersonal dynamics, and it’s often more damaging
than the organizational version because it’s harder to detect and
address.
How to
Overcome NIH in Your Quality Organization
Recognizing NIH is the first step. Overcoming it requires deliberate
structural and cultural changes.
1. Make External
Benchmarking Mandatory
Don’t just encourage benchmarking — require it. Every quality process
should be periodically compared against external best practices. Every
quality tool should be evaluated against industry standards. This isn’t
about blindly copying — it’s about ensuring that your organization’s
“our way” is actually competitive with “the best way.”
Build benchmarking into your management review process. At least once
a year, present a comparison between your current quality methods and
industry best practices. If your methods are genuinely better, the
comparison will confirm it. If they’re not, the comparison will show you
exactly where to improve.
2. Celebrate Adoption,
Not Just Innovation
Most organizations celebrate innovation — the new method, the
original approach, the creative solution. This reinforces NIH by
rewarding originality over effectiveness.
Change what you celebrate. When a team adopts an industry best
practice and it improves performance, celebrate that adoption with the
same enthusiasm you’d give to an original innovation. “We found a better
way” should be as valued as “we invented a better way,” because in
quality management, results matter more than originality.
3. Create a “Proven
Practices” Library
Maintain a curated collection of externally validated methods, tools,
and templates that teams can adopt without needing to reinvent them.
Include industry standards, published methodologies, conference
presentations, and case studies from other organizations.
Make it the default starting point. Before any team designs a new
process, they should review what already exists. The burden of proof
should be on creating something new, not on adopting something
proven.
4. Rotate People
Through External Exposure
Send your quality professionals to industry conferences. Arrange
visits to other facilities — even in different industries. Encourage
participation in professional organizations. The more your people see of
how others solve quality problems, the less susceptible they’ll be to
NIH thinking.
This is especially important for senior quality leaders. The quality
director who hasn’t left the building in three years is the quality
director most likely to believe that the building contains all the
answers.
5. Distinguish NIH
from Healthy Customization
Not every rejection of an external practice is NIH. Sometimes
external solutions genuinely don’t fit. The key is to distinguish
between NIH-driven rejection and evidence-based customization.
A simple test: Can the person rejecting the external practice
articulate specific, factual reasons why it won’t work in their context?
If the reasons are vague (“it won’t fit our culture,” “our people won’t
accept it,” “it’s not how we do things”), that’s NIH. If the reasons are
specific and evidence-based (“our process has a unique thermal profile
that this SPC method doesn’t account for”), that’s legitimate
customization.
The Paradox of Quality
Innovation
Here’s the ultimate irony: organizations that overcome NIH don’t
become less innovative. They become more innovative — because they stop
wasting their innovation capacity on solved problems.
When your quality team adopts proven FMEA methodology instead of
designing its own, it frees up intellectual resources to innovate where
innovation actually matters: in applying that methodology to your
specific products and processes, in developing novel quality strategies
for emerging challenges, in finding creative solutions to the problems
that genuinely haven’t been solved yet.
The best quality organizations in the world — the ones that win
quality awards, that achieve zero-defect performance, that set industry
benchmarks — are not the ones that invented everything themselves.
They’re the ones that adopted everything that worked, adapted it
intelligently, and focused their creative energy on the frontier where
no solutions yet exist.
Toyota didn’t invent statistical process control. It adopted it from
Deming. Then it innovated on top of it — creating the Toyota Production
System, one of the most influential quality innovations in manufacturing
history. The adoption came first. The innovation built on it.
That’s the pattern. Adopt what works. Adapt it to your context. Then
innovate where innovation adds genuine value. Everything else is ego
dressed up as excellence.
The Bottom Line
Not Invented Here syndrome is one of the most expensive biases in
quality management because it converts available solutions into
unnecessary problems. Every proven method you reject is a problem you’ve
chosen to solve again. Every best practice you ignore is a lesson you’ve
chosen to learn the hard way.
The quality profession has spent decades — collectively, centuries —
developing tools, methods, and frameworks that work. These aren’t
theoretical abstractions. They’re battle-tested solutions refined
through thousands of applications across industries and organizations
worldwide.
Rejecting them because they weren’t invented here isn’t discernment.
It’s self-sabotage. And the cost isn’t measured in abstract terms. It’s
measured in defects that could have been prevented, in customers that
could have been retained, in recalls that could have been avoided, and
in the countless hours your brightest people spent reinventing wheels
when they could have been building chariots.
Your organization’s competitive advantage was never supposed to be
its ability to reinvent quality management from scratch. It’s supposed
to be its ability to apply quality management better than anyone else —
starting from the best foundation available, regardless of where it came
from.
Peter Stasko is a Quality Architect with 25+ years
of experience transforming organizations across automotive, aerospace,
and pharmaceutical industries. He has helped companies on three
continents overcome systemic quality failures, build world-class
management systems, and develop the kind of quality culture that doesn’t
just prevent defects — it prevents the thinking that allows defects to
seem inevitable.
