Not-Invented-Here Syndrome

Not-invented-here (NIH) describes the reflexive skepticism or dismissal that can greet external ideas: "It won’t work here," "They don’t understand our context," or "We should build our own version." While local knowledge matters, NIH goes beyond healthy scrutiny and becomes a barrier to learning from others.

In organizations, NIH can show up when teams insist on building custom tools rather than adopting proven open-source or commercial solutions, or when leaders ignore successful practices from other companies or sectors because they are "not how we do things."

The Psychology Behind It

Several motives feed NIH:

• Identity and pride: Teams take pride in their expertise and culture; admitting that outsiders have better ideas can feel like a threat.
• Control and ownership: Internally built solutions provide a sense of control and reduce dependence on external vendors or partners.
• Trust and familiarity: People trust what they have seen and shaped themselves more than external black boxes.

These motives are not inherently irrational, but NIH becomes problematic when they lead to systematically undervaluing external options, ignoring evidence of effectiveness, or reinventing the wheel.

Real-World Examples

In software development, a company might invest heavily in building an in-house framework or analytics platform that reproduces features already available in mature open-source projects, incurring higher maintenance costs and slower innovation.

In public policy and healthcare, decision-makers may discount evidence-based interventions developed in other regions or systems, insisting on homegrown programs that lack rigorous testing.

Consequences

NIH can waste resources, slow progress, and isolate organizations from useful knowledge. It can also reinforce parochial thinking, where teams assume their context is uniquely special and therefore immune to lessons learned elsewhere.

At the same time, blind adoption of external solutions without adaptation is also risky. The challenge is distinguishing justified customization from reflexive rejection.

How to Mitigate It

Mitigation involves building cultures that value learning wherever it comes from. Leaders can publicly celebrate cases where adopting an external idea or tool produced strong results, signaling that borrowing is a strength, not a weakness.

Practical steps include systematic scanning of external best practices, pilots that fairly compare in-house and external options, and criteria that weigh evidence and total cost of ownership rather than origin. Cross-organizational collaborations, conferences, and communities of practice can reduce the sense of "us vs. them."

On a personal level, noticing knee-jerk reactions against "outside" ideas and asking, "If this had come from my team, would I evaluate it differently?" can surface NIH tendencies.