Not-Invented-Here Syndrome

Category: Social

The tendency to reject, downgrade, or ignore an idea, tool, or solution mainly because it came from outside your group, even when the outside version is cheaper, faster, and better. You are not evaluating the thing. You are evaluating who made it, and marking down anything with someone else's fingerprints on it.

How it works

Not-Invented-Here starts with identity. When your group's status rests on being the smart ones, an outside solution that already solves your problem is a small insult, so you protect the ego by finding reasons the outside thing "doesn't fit." Antons and Piller (2015) break it into two moves: you underestimate the value of the external knowledge, and you overestimate the cost and pain of adopting it, which together make rebuilding it yourself look rational. The bias gets worse with group tenure and isolation. Katz and Allen found that R&D teams grew more insular the longer they stayed together and communicated with the outside world less, which quietly starved them of exactly the ideas they were dismissing. The tell that it is bias and not judgment is that the rejection happens before any real evaluation, and the criteria for "fit" keep shifting to whatever the external option happens to lack.

Where you'll see it

  • Engineering teams reinventing standard infrastructure (auth, job queues, ORMs, state management) from scratch because the popular library 'has too much bloat' or 'wasn't built for our use case,' then maintaining a buggier version of it forever.
  • Katz and Allen's 1982 study of 50 R&D project groups: performance rose for about the first 1.5 years, then declined as teams passed roughly five years together, because they talked to outside information sources less and less and treated their own group as the monopoly holder of knowledge in their field.
  • Kodak and Xerox PARC style stories where a company's own labs invent the future (the digital camera, the graphical interface, the mouse) but the core business rejects or under-funds it because it did not come from the dominant internal group and threatens the existing product.
  • A marketing or ops team dismissing a proven playbook from a competitor or a consultant with 'that works for them, not for us,' and burning a quarter rediscovering the same lesson the outsider already handed them for free.

Where it comes from

The phrase circulated inside the R&D community for years before it was studied. It was pinned down academically by Ralph Katz and Thomas J. Allen in their 1982 paper in R&D Management, "Investigating the Not Invented Here (NIH) Syndrome," based on 50 R&D project groups at a large lab. They described NIH as a group coming to believe it holds a monopoly of knowledge in its field and therefore rejecting ideas from outsiders, and they linked it to long team tenure and falling communication with external sources. Later work extended it well past R&D. Menon and Pfeffer (2003) showed the flip side, that managers sometimes over-value outsider knowledge precisely because it is scarce and status-safe, and Antons and Piller (2015) built the modern model of NIH as an attitude driving predictable decision biases.

How to counter it

Make the outsider's case for them, in writing, before you reject it. Require whoever wants to build in-house to first write an honest one-page summary of the external option's actual strengths and a real cost estimate for rebuilding it. If they cannot describe the outside thing fairly, they have not evaluated it, they have flinched at it.

Separate "does it work" from "did we make it." Score external solutions on fixed, pre-agreed criteria (cost, security, time to ship, maintenance load) written down before you know the source. If your "fit" objections only appear after you learn something was built elsewhere, that is NIH, not analysis.

Rotate people and pull in outside voices on purpose. Katz and Allen's core finding was that isolation drives the bias, so bring in external reviewers, new hires, or a devil's advocate whose explicit job is to argue for the bought option. Teams that never talk to the outside stop being able to see it.

Default to buy, and make build the exception you have to justify. Flip the burden of proof. Adopting the proven external tool is the baseline, and building your own requires a specific documented reason (a real differentiator, a hard constraint, a licensing wall), not just a vague feeling that ours would be cleaner.

The tell

You catch yourself saying "that wouldn't work for us" or "our situation is different" about an external solution you have not actually read the docs for or run a trial of. The objection arrives fully formed before any evaluation, and your reasons for rejecting it keep changing.

Related biases

References

  1. Ralph Katz, Thomas J. Allen (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. David Antons, Frank T. Piller (2015). Opening the Black Box of 'Not Invented Here': Attitudes, Decision Biases, and Behavioral Consequences. Academy of Management Perspectives, 29(2), 193-217
  3. Tanya Menon, Jeffrey Pfeffer (2003). Valuing Internal vs. External Knowledge: Explaining the Preference for Outsiders. Management Science, 49(4), 497-513
  4. David Antons, Marc Declerck, Kai Diener, Ina Koch, Frank T. Piller (2017). Assessing the Not-Invented-Here Syndrome: Development and Validation of Implicit and Explicit Measurements. Journal of Organizational Behavior, 38(8), 1227-1245
  5. Gwendolyn K. Lee, Robert E. Cole (2003). From a Firm-Based to a Community-Based Model of Knowledge Creation: The Case of the Linux Kernel Development. Organization Science, 14(6), 633-649