Not Invented Here Syndrome
Teams often reject or distrust a perfectly good idea, tool, or practice simply because it originated outside their own group, and defend the inferior thing they built themselves instead.
What Is It?
Ralph Katz and Thomas Allen studied the phenomenon in fifty R&D project groups in a 1982 paper. Longer-tenured groups communicated less with important sources of information outside the team, and groups with very long average tenure also performed less well. The authors described a pattern in which stable groups can become increasingly insulated from outside knowledge, what they called the Not Invented Here syndrome. The bias isn’t really about the quality of the outside idea. It’s about where the idea came from.
Why Does It Matter?
NIH syndrome quietly taxes almost every organization that has more than one team working on related problems. A team rebuilds a tool that already exists in a sister department because building it themselves feels like ownership. An acquired company’s product gets replaced with an inferior internal equivalent because the acquiring team can’t fully trust something it didn’t create. None of this usually looks like bias from the inside. It looks like standards, quality control, cultural fit.
The tenure finding is the part worth taking seriously. The finding suggests that NIH may be partly developmental: as teams accumulate shared history, expertise, and routines, they can also become more insulated from outside information.
What Changes Once You See It?
You start distinguishing between “we improved on this” and “we couldn’t accept this as-is,” which are very different processes wearing the same clothes. You get more suspicious of a rejection that leans on vague language, “that won’t work for us,” “we do things differently here,” without a specific technical or contextual reason attached. And you start treating team tenure itself as a variable worth watching, not because long-tenured teams are worse, but because they’re worth watching for this particular blind spot.
Common Misunderstandings
- It is not a claim that internal solutions are usually worse. Sometimes the internally built version genuinely is better; the bias is in the reflexive preference, not in every individual outcome.
- It doesn’t require hostility toward the outside idea’s source. NIH usually shows up as polite skepticism and scope creep on a rebuild, not open conflict.
- It isn’t unique to engineering teams, even though it’s most often discussed there. Any group with a shared identity and history, a marketing team, a regional office, a leadership team, can develop it.
- It is not the same as reasonable due diligence. The distinguishing question is whether the scrutiny applied to the outside idea is the same scrutiny the team would apply to its own.
Diagnostic Question
When was the last time this team adopted something significant that it didn’t build itself, and if the answer is “not recently,” is that because nothing good has come from outside, or because nothing from outside gets a fair hearing?
Explore Further
Field Notes
None yet.
Related Field Guide
Origin
Ralph Katz and Thomas J. Allen documented the effect empirically in “Investigating the Not Invented Here (NIH) Syndrome: A Look at the Performance, Tenure, and Communication Patterns of 50 R&D Project Groups,” R&D Management, 1982.