/ Library/ Not Enough Meaning/ Not Invented Here
Connect Bias № 118 · Last updated 6 June 2026

Not Invented Here.

"If we didn't build it, it can't be right — even when users already know it elsewhere."

01Overview

Not invented here (NIH) is the reflex to reject external knowledge — competitor patterns, open-source components, academic research, vendor tools — in favour of internal origin. Pride, identity, and uncertainty avoidance dress as quality bar.

Designers fight standard patterns users already learned elsewhere because "our brand is different." Engineering rebuilds solved infrastructure. Research ignores published findings. NIH taxes time, increases defect rates, and confuses users who expected conventions you dismissed as not invented here.

02Detailed explanation

NIH manifests across disciplines:

  • Custom date picker worse than platform native — rejected because external.
  • Design system ignores widely adopted accessibility patterns until audited.
  • UCD methods reinvented internally with new names — same methods, worse docs.
  • Acquisition product shelved; rebuilt internally for identity reasons.

In-group bias supplies social preference for internal voices. Appeal to novelty sometimes flips NIH — internal novelty good, external good bad — inconsistently.

03Why it exists

Ownership breeds trust in one's own work. External solutions carry unknown risk and visible dependency.

Careers reward visible creation more than adoption. NIH is incentive-aligned.

The short version

Are you rejecting it because it fails users — or because you didn't invent it?

04Effects on users

Users pay learning tax when NIH breaks conventions — hamburger menus moved, checkout flows exotic, icons novel for novelty's sake.

They also lose integrated solutions when acquired features are discarded for internal rebuilds during multi-year gaps.

05Effects on designers & teams

Teams encode NIH in standards and politics:

  • Brand exceptionalism. Different for difference sake.
  • NIH review gates. External proposals higher burden of proof.
  • Rebuild vs buy taboo. Vendor stigma.
  • Acquired product neglect. Integration as identity threat.

6Introspective view

Look inward. Teams dismiss external ideas and solutions in favour of internally built ones.

From an introspective perspective, ask how Not Invented Here may already be shaping your research, critique, planning, and interpretation — not only what users encounter in the finished interface.

Stakeholders

The loudest frame wins

Alignment workshops on Not Invented Here can converge on whoever articulated a direction first, even when the room never formally agreed. Teams dismiss external ideas and solutions in favour of internally built ones.

Critique

First comp on the wall

In critique, Not Invented Here ties later options to whichever direction was shown first — alternatives read as tweaks, not genuine forks. Teams dismiss external ideas and solutions in favour of internally built ones.

Ideation

Sketches that look familiar

Brainstorms about Not Invented Here recycle what the room already knows — competitors, past launches, favourite patterns — rather than stretching into uncomfortable territory. Teams dismiss external ideas and solutions in favour of internally built ones.

User Interviews

What you hear first sticks

In early interviews about Not Invented Here, the opening participant can set the frame for everyone after — which pains feel central, which workflows seem broken, which quotes get repeated in synthesis. Teams dismiss external ideas and solutions in favour of internally built ones.

07Practical takeaways

  • Default to platform and standards. Deviate with user evidence, not pride.
  • Benchmark adoption cost vs rebuild. Include maintenance.
  • Cite external research proudly. Standing on shoulders is strength.
  • Integrate acquisitions visibly. User value over turf.
  • Run convention tests. Do users expect external pattern here?
  • Reward smart adoption. KPIs for shipped value, not only greenfield.

08Design examples

Components

Custom date picker

Native picker rejected for brand. Custom widget ships with timezone bugs. Two sprints later, partial native revert — NIH cost delay and trust.

Research

Reinvented method

A lead designs a "discovery sprint" ignoring published JTBD work. Team reads internal PDF only. Same steps, no lessons from external failures — NIH in knowledge.

Acquisition

Shelved product

Acquisition includes working auth. Internal team rebuilds for two years. Users lose features during gap — not invented here won over continuity.

Accessibility

Ignored WCAG patterns

Known focus patterns rejected as "not our system." Audit forces adoption. NIH delayed inclusion months.

09Ethical risks

NIH harms users who depend on standard accessible patterns and cross-product continuity — especially when rebuilds ship immature.

Dismissing external ethical critiques as "not understanding our context" can entrench harm.

Self-test: What external solution are you rebuilding — and what is the user cost of waiting?

10Suggested reading

Browse recommended reading →