Trap/Cognitive Bias/No. 0681
Not-Invented-Here Syndrome
Not-invented-here syndrome is resistance to or rejection of outside ideas or solutions based on their source rather than their merits. Studied by Ralph Katz and Thomas J. Allen in R&D teams, this organizational bias is closely related to the genetic fallacy.
Also called NIH Syndrome · Not Invented Here
- Evidence
- Useful, modest evidence
- Read
- 6 min
- Links
- 10 connections
01You've seen this when…
- at work
Another department offers code that handles the file format your team needs. Nobody runs it. The next sprint fills with tickets to build your own.
- in life
Your partner finds a ready-made budget spreadsheet with every category you need. You dismiss it before trying a single cell and spend Sunday rebuilding yours.
- out in the world
A city committee reviews software already used by neighboring towns. It requests a custom system before anyone checks whether the existing tools meet its requirements.
02The idea
The warning sign isn’t building something yourself. It’s deciding to build before giving an outside option a fair hearing.
Not-invented-here syndrome is resistance to outside knowledge, including ideas and solutions, because it comes from beyond a boundary you identify with. That boundary might surround a company, a department, a profession, or a team of four. Another division in the same building can count as outside.
The source becomes a substitute for evaluation. An unfamiliar tool needs exhaustive proof, while the proposed internal version gets credit for benefits it hasn’t delivered yet. Outside advice is dismissed as impractical; the same advice, developed internally, becomes a promising initiative.
The related genetic fallacy treats a claim’s origin as the basis for judging its merits. Not-invented-here names a more specific organizational pattern, often involving expertise and questions of ownership and control. It can also resemble status quo bias when a team is eager to replace its current system on the condition that it gets to invent the replacement.
03Why it happens
- Outside expertise can feel like a judgment on yours. Accepting another team’s solution may seem to concede that your own specialists missed something. Resistance protects status, even when nobody intends an insult.
- Making something creates attachment. Work invested in an internal approach can make it seem more valuable. The IKEA effect helps explain this pull, though attachment alone doesn’t establish that rejecting an alternative is mistaken.
- Our people get the benefit of the doubt. In-group favoritism can give internal proposals a warmer reception. You know the author’s competence and intentions; outsiders must establish both.
- Familiar problems feel more manageable. You know where the internal system breaks and whom to call. An outside system’s unknowns loom larger, even if its documented limitations are smaller.
- The rewards favor invention over adoption. A promotion case can feature a system you created. Finding and adapting someone else’s system may look less impressive, despite saving months of work. That makes dismissal personally convenient.
04A worked example
Imagine a product team adding spreadsheet uploads. An established library supports the required formats. Its license passes review, and it runs inside the company’s infrastructure. The team nevertheless plans a six-week internal build without testing it, arguing that external libraries won’t understand its customers.
What it looks like Taking responsibility for a feature the company will have to maintain. The team cares about reliability and wants control over the implementation.
What’s actually going on A reasonable concern has become an exemption from comparison. The outside library must already handle every awkward file. The internal proposal merely promises to handle them eventually. Nobody checks whether the claimed customer differences affect parsing at all. The team is comparing a real external product, complete with flaws, against an imagined internal one.
What would have helped A two-day test using the same sample files and acceptance criteria for both approaches. The comparison would assess the effort needed for integration, the maintenance each approach requires, how it handles security and errors, and the cost of delaying other work. It might favor the internal build. But if the library meets the requirements, rejecting it would need a reason beyond its birthplace.
05How to spot it
06What to do instead
- Write the requirements before choosing the source. Specify what success demands and which constraints are nonnegotiable. Apply them equally to buying, borrowing, adapting, and building.
- Remove the label where possible. Use blinding to compare proposals without revealing their authors. This won’t work for every procurement decision, but it can expose unequal treatment of ideas.
- Ask what would change your mind. Name an observable result that would make the outside option acceptable. If no possible result would qualify, your decision rests on defending a boundary. A consider-the-opposite strategy can help surface the strongest case for adoption.
- Compare complete costs. Use cost-benefit analysis that includes integration, training, maintenance, supplier dependence, and the work displaced by an internal build. Purchase price and development time each account for only part of the cost.
- Make reuse count as achievement. Credit people for finding and evaluating good work, then adapting it. Give successful adoption the same visibility as successful invention.
07When it isn’t not-invented-here resistance
An outside solution can be wrong for you. Its license may be incompatible with your product. A supplier may be unreliable. Integration may cost more than rebuilding. Developing something internally can also create expertise you’ll need later.
Source information can therefore be relevant to the decision. Knowing who maintains a tool can help you assess its security and whether you can count on support and continued operation. The test is whether you can connect the source to a concrete consequence—and whether you would apply the same scrutiny internally.
Be careful with the accusation itself. Calling colleagues biased can become a way to avoid answering their technical objections. And rejection because an idea comes from a hostile party is more specifically reactive devaluation, although the patterns can overlap.
Not-invented-here describes a decision process that bypasses evaluation. Evaluating outside options fairly can lead to a decision to build.
08Roots
In 1982, Ralph Katz and Thomas Allen published a study of 50 research-and-development project groups. They examined a tension inside experienced teams: working together should deepen expertise, but a group could also become convinced that the expertise it needed was already inside the room.
They studied communication, performance, and how long members had worked together. Some long-serving groups had become less connected to people beyond the group, and communication patterns were associated with performance. Their paper gave not-invented-here resistance an influential empirical treatment. It did not establish that tenure itself caused rejection or that external advice was always better.
The idea later became prominent in research on knowledge transfer and open innovation. A company needs absorptive capacity—the ability to recognize, understand, and use outside knowledge—but willingness matters too. Expertise that never receives a hearing cannot help. Persistent resistance can contribute to core rigidity, turning a once-useful strength into an obstacle.
An adaptive explanation is plausible but speculative: trusting familiar people may conserve effort and protect against unreliable outsiders. That could help explain the attraction of the shortcut. It does not establish an evolutionary origin for the syndrome, or justify refusing a testable alternative.
09How solid is this?
Organizational studies and reviews document source-based resistance to outside knowledge, but definitions and measures vary. Much of the evidence is observational or self-reported; it does not show that outside solutions are generally better or that every refusal reflects bias.
10Connections
- Often confused with Status Quo Bias
- Countered byBlinding, Cost-Benefit Analysis, Consider-the-Opposite Strategy, Absorptive Capacity
- Can lead toCore Rigidity
- Can follow fromIKEA Effect
- Part ofGenetic Fallacy, Reactive Devaluation, In-Group Favoritism
11Origin and sources
Ralph Katz and Thomas J. Allen (1982), who investigated not-invented-here resistance through the performance, tenure, and communication patterns of 50 R&D project groups.
- [1]Katz, R., & Allen, T. J. (1982). 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, 12(1), 7–20.
- [2]Antons, D., & Piller, F. T. (2015). Opening the Black Box of “Not Invented Here”: Attitudes, Decision Biases, and Behavioral Consequences. Academy of Management Perspectives, 29(2), 193–217.
- [3]Norton, M. I., Mochon, D., & Ariely, D. (2012). The IKEA effect: When labor leads to love. Journal of Consumer Psychology, 22(3), 453–460.
Suggest an edit· Updated 2026-10-02