Quality
and the Not Invented Here Syndrome: When Your Organization Rejects Every
Best Practice It Didn’t Invent — and the Pride That Protects Your Worst
Processes Becomes the Wall That Keeps Every Improvement Out
It happened in a Tier 1 automotive supplier in Slovakia, a company I
worked with for eighteen months. They had a soldering defect rate on
their PCB assemblies that ran at 2,300 PPM — not catastrophic, but
persistent, expensive, and deeply irritating to their OEM customer, who
had started making noise about re-sourcing.
I had seen this exact defect pattern before. Same component geometry,
same thermal profile issue, same root cause. A plant in Germany I’d
consulted with two years earlier had solved it with a modified reflow
profile and a pre-heat stage adjustment that dropped their defect rate
to under 200 PPM. The solution was documented, validated, and available.
I brought it to the quality director in Slovakia on a Tuesday
morning.
He looked at the documentation, flipped through the pages, and said
something I have heard in one form or another in probably sixty percent
of the organizations I’ve ever worked with: “That’s interesting. But our
process is different.”
It wasn’t different. I had compared the process maps. Same equipment,
same solder paste, same component suppliers, same thermal challenges.
The only difference was that the solution had been invented somewhere
else.
That is the Not Invented Here syndrome, and it is one of the most
expensive psychological forces operating in quality management
today.
What Is the Not Invented
Here Syndrome?
Not Invented Here — or NIH — is a well-documented organizational bias
where teams, departments, or entire companies reject external knowledge,
solutions, or practices simply because they originated outside their own
boundaries. The concept was first formally described by Robert Claxon in
his 1967 study of NASA’s approach to technology transfer, though the
phenomenon itself is as old as organized human work.
In quality management, NIH manifests in specific, recognizable
patterns:
- An engineering team redesigns a solution that already exists in
another plant within the same company - A quality department develops its own FMEA template rather than
adopting the one that three other divisions have refined over five
years - A manufacturing manager dismisses benchmarking data from a
competitor because “they’re in a different market” - A leadership team invests months developing a custom QMS software
platform when proven commercial solutions are available - An auditor’s corrective action recommendation is resisted because
“the auditor doesn’t understand our process”
Notice what all of these have in common: the rejection is not based
on technical merit. It is based on origin. The solution works, the data
supports it, the logic is sound — but it came from the outside, and that
fact alone is treated as a disqualification.
The Psychology Behind NIH
NIH is not stupidity. It is a convergence of several deeply human
psychological forces, and understanding them is the first step to
dismantling the syndrome in your organization.
Identity and Competence. Professionals derive a
significant portion of their self-worth from their ability to solve
problems independently. When an external solution is presented, it can
feel like an implicit message: “You couldn’t figure this out yourself.”
The resistance to external solutions is often a defense of professional
identity, not a critique of the solution.
Ownership and Control. People value what they
create. This is the IKEA effect applied to organizational processes. A
team that builds its own inspection checklist will defend it more
fiercely than an externally supplied one, regardless of which is more
effective. The act of creation produces emotional investment that
overrides objective evaluation.
In-Group Favoritism. Decades of social psychology
research demonstrate that humans systematically favor their own group’s
output over outsiders’. In organizational settings, “our plant,” “our
team,” or “our industry” becomes the in-group, and solutions from
outside that boundary are viewed with automatic suspicion.
Attribution Errors. When an internal solution fails,
the team attributes it to circumstances: “The material was bad.” When an
external solution fails, the team attributes it to essence: “Their
approach doesn’t work.” This asymmetry makes external solutions seem
riskier than they actually are.
The Competence Threat. In hierarchical
organizations, adopting an external solution can feel like admitting
inferiority. If Plant B’s solution works in Plant A, it implicitly
raises the question: “Why didn’t we think of that?” For managers whose
status depends on perceived expertise, this question is threatening
enough to reject good solutions.
What NIH Costs Your Quality
System
The financial cost of NIH is substantial but often invisible, because
it doesn’t show up as a line item. It hides in duplicated effort,
delayed improvement, and repeated failures that could have been
prevented.
Duplicated Engineering Effort. I once consulted for
a multinational automotive components company with seven plants across
Europe. Each plant had independently developed its own control plan
template. The total engineering hours invested across all seven
templates exceeded 2,000 hours. A single well-designed template, adapted
from best practices, would have required perhaps 200 hours total —
including customization for each plant. That’s 1,800 hours of pure NIH
waste.
Delayed Problem Resolution. When a team insists on
solving a problem from scratch rather than adapting a proven solution,
the timeline for resolution stretches from weeks to months. During that
extended period, defects continue, customers continue to be affected,
and costs continue to accumulate. In the Slovakia example I opened with,
the company spent four additional months developing their own solution —
which, incidentally, was functionally identical to the one they rejected
— while absorbing warranty costs, customer complaints, and the growing
risk of lost business.
Missed Innovation. The most dangerous cost of NIH is
not what you spend duplicating effort. It’s what you miss entirely.
External solutions often carry innovations, perspectives, or
technologies that your team would never have developed because they
emerge from different constraints, different failure modes, and
different customer demands. When NIH blocks these, your organization
doesn’t just duplicate — it stagnates.
Cultural Isolation. Organizations with strong NIH
cultures tend to become increasingly isolated over time. They stop
sending people to conferences, stop participating in benchmarking
studies, stop engaging with industry working groups. Each rejection of
external knowledge reinforces the belief that internal knowledge is
sufficient, which leads to further isolation, which further widens the
gap between what the organization knows and what the industry has
learned. It is a slow, quiet decline into irrelevance.
The
Paradox: Quality Systems Are Built on External Standards
Here is what makes NIH in quality management particularly ironic: the
entire quality management framework your organization operates within
is, by definition, invented elsewhere.
ISO 9001 was not developed by your company. IATF 16949 was not your
engineering team’s idea. The core tools — FMEA, SPC, MSA, APQP, PPAP —
were all developed externally and adopted by your organization. The
Plan-Do-Check-Act cycle came from Deming, who adapted it from Shewhart.
Lean came from Toyota. Six Sigma came from Motorola.
Every quality professional builds their career on externally invented
knowledge. The frameworks, the tools, the methodologies, the standards —
none of them originated in your plant, your company, or probably even
your industry.
And yet, when it comes to the specific application of these
externally invented frameworks — a particular FMEA approach, a specific
SPC implementation, a proven corrective action — organizations suddenly
develop strong preferences for internal origination.
The paradox reveals something important: NIH is not a rational
position. It is an emotional response dressed in technical language. The
quality director who accepts ISO 9001 without complaint but rejects a
proven reflow profile adjustment from another plant is not making a
technical judgment. He is managing a psychological threat.
How NIH Disguises Itself
One of the reasons NIH persists is that it is rarely expressed
honestly. Nobody says, “I’m rejecting this solution because I didn’t
invent it.” Instead, NIH wears a wardrobe of professional-sounding
justifications:
“Our situation is unique.” This is the most common
NIH defense. And yes, every process has unique elements. But the
question is whether the unique elements are relevant to the specific
problem being solved. Most of the time, they aren’t. Solder paste
behaves according to physics, not company culture.
“We need to understand it ourselves.” This sounds
noble — a commitment to deep learning. But the timeline tells the truth.
If “understanding it ourselves” means spending four months rediscovering
what another team learned in four weeks, it’s not learning. It’s NIH
with a educational veneer.
“Let’s adapt it to our context.” Adaptation is
legitimate. But when “adaptation” becomes a complete rewrite that
happens to arrive at the same solution as the original, it’s not
adaptation. It’s NIH in slow motion.
“We want to own the solution.” This is the most
honest expression of NIH, and it’s worth engaging with directly.
Ownership matters for implementation commitment. But ownership can be
built through participation in adapting an external solution — it
doesn’t require inventing from scratch.
“Their data might not apply to us.” This is the
scientific-sounding version, and it deserves a scientific response: show
me why. What specific factor in your process is different enough to
invalidate the external data? If the answer is vague — “It’s just
different” — it’s NIH. If the answer is specific and testable — “Our
board thickness is 1.6mm versus their 2.4mm, which affects thermal mass”
— that’s legitimate technical reasoning.
Breaking the NIH
Cycle: A Practical Framework
Dismantling NIH in a quality organization requires a combination of
structural changes, cultural shifts, and specific practices. Here is a
framework that has worked across multiple organizations I’ve consulted
with.
1. Make
External Benchmarking a Structured Requirement
Don’t make benchmarking optional. Build it into your problem-solving
methodology. Before any team begins a root cause investigation or
corrective action development, require them to complete a benchmarking
scan: Has this problem been solved elsewhere? What approaches were
tried? What worked and what didn’t?
In the automotive industry, the AIAG’s benchmarking guidelines
provide a framework, but the specific mechanism matters less than the
requirement itself. When benchmarking becomes a mandatory step rather
than an optional supplement, teams stop treating external solutions as
threats and start treating them as inputs.
2. Reframe Adoption as
Adaptation
Language matters. Stop talking about “adopting” external solutions
and start talking about “adapting” them. Adoption implies passive
acceptance — taking someone else’s solution wholesale. Adaptation
implies active engagement — evaluating, selecting, and customizing
external knowledge for your specific context.
This reframing addresses the competence threat directly. When a team
adapts an external solution, they are still creators. They are still
exercising judgment, still applying their expertise. They’re just
starting from a better foundation than zero.
3. Create Internal Knowledge
Markets
Many large organizations have vast reserves of solved problems
sitting in the institutional memory of individual plants, teams, or
engineers — but no mechanism for connecting problems to solutions across
boundaries.
Build one. Internal knowledge-sharing platforms, cross-plant
problem-solving communities, regular best-practice showcase events — the
specific format matters less than the principle: make it easy for
someone with a problem to find someone who has already solved it.
One automotive company I worked with instituted a monthly “Solution
Speed Dating” event where engineers from different plants presented
solved problems in five-minute lightning talks. Within six months, the
company documented over 200 instances of cross-plant solution transfer
that would not have occurred without the structured forum.
4. Reward the Source, Not
Just the Solver
In most organizations, the person who solves a problem gets
recognized. The person who found the existing solution and brought it to
the table gets nothing. This incentive structure actively discourages
external knowledge seeking.
Change it. Create recognition for “best adapted solution” alongside
“best new solution.” Celebrate the engineer who found a proven approach
from another plant and adapted it successfully. Make knowledge brokering
a visible, valued contribution.
5. Track the Cost of NIH
What gets measured gets managed. Start tracking the specific costs of
duplicated effort and delayed improvement that result from NIH. When a
team spends three months developing a solution that already existed
elsewhere, quantify the cost: engineering hours, continued defect costs,
customer impact, lost production time.
Presenting NIH costs in financial terms changes the conversation from
abstract preference to concrete waste. It’s harder to defend NIH when
the price tag is visible.
6. Model the Behavior at the
Top
If senior leaders never reference external sources, never bring back
insights from conferences, and never acknowledge learning from other
organizations, NIH will persist regardless of any structural changes you
make.
Quality directors and plant managers need to visibly demonstrate that
learning from outside is not a weakness but a strength. When a leader
says, “I saw this approach at a conference last month, and I think we
should evaluate it,” it sends a message that external knowledge seeking
is not just acceptable — it’s expected.
The Slovakia Story: The
Ending
You might be wondering what happened with the quality director in
Slovakia.
He rejected the German solution. His team spent four months running
their own DOE, testing their own thermal profiles, and developing their
own corrective action. The solution they arrived at was, as I mentioned,
functionally identical to the one they had rejected: a modified reflow
profile with a pre-heat stage adjustment.
The defect rate dropped to 180 PPM. The OEM customer was satisfied.
The quality director presented the result at a divisional meeting as a
triumph of his team’s analytical capability.
And in one sense, it was. His team was talented, methodical, and
persistent. They had solved a genuine problem through genuine
engineering effort.
But the cost of that pride was four months of continued defects, four
months of customer risk, and thousands of engineering hours spent
rediscovering what was already known. The solution was identical. The
only difference was the origin story.
That is the tax of Not Invented Here. You pay it in time, in money,
in customer patience, and in opportunity cost. And the worst part is,
the receipt never shows up on any dashboard — because the cost of NIH is
always recorded as the cost of “normal problem-solving.”
The Deeper Question
Here is the question every quality leader should ask themselves: Is
your organization’s quality system designed to produce the best possible
outcomes, or is it designed to produce outcomes that feel like they came
from you?
These are not the same thing. The best possible outcomes draw on
every available source of knowledge — internal and external, invented
and adopted, novel and borrowed. Outcomes that feel like they came from
you are limited by the boundary of your own organization’s
experience.
In a world where quality challenges are increasingly complex,
interconnected, and fast-moving, no single organization has a monopoly
on good solutions. The quality systems that will thrive in the next
decade are not the ones with the most original ideas. They are the ones
with the fastest learning cycles — the ones that can identify, evaluate,
and integrate external knowledge faster than their competitors.
Not Invented Here is not a quality philosophy. It is a quality
obstacle. And the organizations that learn to overcome it will discover
that the best solution to most problems already exists somewhere —
waiting for someone humble enough to use it.
Peter Stasko is a Quality Architect with 25+ years
of experience transforming organizations across automotive, aerospace,
and pharmaceutical industries. He has led quality transformations in 14
countries, advised OEMs and Tier 1 suppliers on quality system design,
and spent more time than he’d like to admit watching organizations
reject perfectly good solutions because they came from somewhere
else.
