Not invented here

Not Invented Here is discounting a useful external idea, tool, or solution because it came from outside the team or organization. Internal ownership feels like evidence of quality; external origin feels like a reason for suspicion.

Mechanism

How it works

Building something ourselves brings understanding, control, status, and a visible contribution. An outside solution threatens those benefits and may be judged by a harsher standard than an internal one. Compatibility, security, and strategic fit can be real concerns, but NIH turns provenance itself into a veto before those concerns are examined.

Examples

Where it shows up

  • A product team rebuilds a commodity capability internally because adopting a mature external tool feels like surrendering ownership, despite higher cost and slower delivery.
  • A researcher discounts a rival lab's result more harshly than an equally strong result from their own collaborators.
  • A company rejects a partner's proven process without a trial, then spends a year recreating a weaker version under its own brand.
Consequences

What it can distort

  • Teams reinvent solved problems, delay customer value, and lose the learning that comes from external comparison and collaboration.
  • Internal work receives a gentler evaluation, so its true cost and quality are hidden by uneven standards.
Countermeasures

How to work around it

  • Evaluate internal and external options with the same written criteria: total cost, speed, fit, security, maintainability, and strategic control.
  • Require a build-versus-buy comparison before funding a reinvention, including the opportunity cost of the team that would build it.
  • Reward teams for adopting the best solution, not only for creating original artifacts.
Caveats

Critiques and limits

Building internally can be rational for differentiated capabilities, privacy requirements, or deep integration. The bias appears when 'external' is treated as a quality defect rather than one factor to evaluate.

Taxonomy

Fields of impact

Evidence

How solid is the research?

Mixed — real but conditional

NIH is a well-recognized organizational pattern, but its empirical boundaries overlap with strategic make-versus-buy decisions, ownership effects, and organizational incentives.

Research

Relevant papers

Case studies

Real-world patterns.

Real-world examples showing how Not invented here manifests in practice

Case study

When Pride Delays Product: Innovatek's Rejection of an Open‑Source Engine

A real-world example of Not invented here in action

Context

Innovatek, a mid-sized SaaS company specializing in customer analytics, had built most of its stack in-house and prided itself on proprietary solutions. Market signals indicated that competitors were adopting community-built machine learning components to accelerate feature delivery.

Situation

A high-quality open-source recommendation engine emerged with strong community adoption and benchmarks matching Innovatek's needs. The product team proposed integrating the engine to launch a new personalized recommendations feature within three months and at low incremental cost.

The bias in action

Leadership dismissed the proposal without a technical evaluation, citing cultural preference for 'homegrown' systems and concerns about external dependencies. Engineers who supported the integration were asked to reimplement the same functionality internally to maintain 'ownership.' The procurement and legal teams were not involved because the idea was rejected before formal review, and comparisons to existing in-house work were not documented.

Outcome

The internal reimplementation took nine months instead of the estimated three, required reallocating two senior engineers and three contractors, and introduced new bugs that delayed release. A competitor that integrated the open-source engine shipped earlier, capturing customer accounts Innovatek had targeted.

What's inside the full case study

Unlock the deeper breakdown with real-world impact, measurable effects, lessons learned, better-approach recommendations, and relevant fields.

Real-world impact
Affected groups, timeframe, and measurable outcomes.
Lessons learned
Practical takeaways and a better path forward.
Full case breakdownEmail access

Want the full analysis?

Request access to the complete case study, including measurable impact, lessons learned, and the recommended better approach.

We'll use your email to follow up about case-study access.

Further reading

Recommended books

Entry last reviewed 2026-07-19 · sources verified against the published literature — methodology

Not invented here - The Bias Codex