Home › Cognitive Biases › Not-Invented-Here Syndrome

Not-Invented-Here Syndrome: Why Outside Ideas Get a Harder Hearing

You will read one five-point plan and rate it. Other visitors see the identical plan with a different author named. Rate it, then compare the live split for the two versions with the research.

About 1 minuteRuns in your browser5 sources cited
Not-invented-here syndrome: a craftsperson waves off an offered tool to grab their own near-identical one instead.

Judge a plan by where it came from

One question, two versionsAbout 1 minuteCounted anonymously

One plan, one judgment, and what the author's address did to it

One plan, five points, one judgment. The page assigns you one of two versions at random and remembers only which one, so a reload shows the same version.

At the end you see your own result next to the figure from Menon, and how visitors so far compare.

In Menon, Thompson and Choi's 2006 studies, managers avoided knowledge when it was said to come from an internal rival, another unit of their own company, and sought the same knowledge when it was said to come from an external rival, a competing firm; the content was held constant and only the stated source changed.

Source: Menon, Thompson and Choi (2006), Management Science

In short

Not-invented-here syndrome is the tendency of a group to undervalue knowledge, ideas, products and methods that originate outside it, and to prefer its own, whether or not its own are better. It shows up in engineering teams that rebuild a tool that already exists, research groups that stop reading outside their walls, and departments that reject a plan from across the hall and adopt the same plan a year later under their own name; in software, the phrase also names the habit of writing code in-house rather than reusing a library, which is the same preference applied to tools.

How not-invented-here syndrome works

Groups judge ideas partly by where they come from. An outside proposal arrives without the shared history that makes an insider's proposal legible: the evaluator does not know what was tried or what the author assumed. Adopting it also costs something that adopting your own does not. It says the group did not solve the problem itself, and where teams compete for budget, headcount or standing, that admission has a price.

Tanya Menon and colleagues showed in 2006 that the price depends on who the outsider is. Managers in their studies devalued knowledge from an internal rival, another unit of the same company, and were more willing to take the same knowledge from an external rival, a competing firm. Learning from a colleague down the hall threatens status in a way that learning from a competitor does not. Earlier, Menon and Pfeffer had found in 2003 that outsiders' knowledge is sometimes preferred to insiders', because an outsider's ideas are scarce and the insider's are easily scrutinized. The bias is not a blanket suspicion of everything foreign; it is sharpest for ideas from close rivals and for ideas whose adoption would cost the group face.

The same knowledge is blocked or welcomed at the doorwayIdentical documents travel to identical recipient doorways. Within a shared company roof, the internal rival’s knowledge meets a barrier; from a separate company, the same document reaches the recipient. The paths show avoidance and seeking, not acceptance rates or absolute refusal by every manager.Same idea, different doorwayOrdinal knowledge use · content unchangedInternal rivalAvoidedAnother unit, same companyExternal rivalSoughtA competing firmHere, internal rivalry blocked learning.
Menon, Thompson and Choi (2006) held knowledge content constant: managers avoided it when attributed to an internal rival and sought it when attributed to an external rival. This study-specific reversal is deliberate. Shared versus separate roofs identify the source; doors and barriers are an ordinal analogy.
Read the diagram and evidence as text

Identical documents travel to identical recipient doorways. Within a shared company roof, the internal rival’s knowledge meets a barrier; from a separate company, the same document reaches the recipient. The paths show avoidance and seeking, not acceptance rates or absolute refusal by every manager.

Same knowledge, different name on it

Content held constant; only the stated source changed. Ordering only

The same knowledge, word for word; only the stated source changes

From an internal rival: another unit of your own company: Avoided. Learning from down the hall costs the group standing

From an external rival: a competing firm: Sought. Learning from a competitor costs nothing in status

Evidence from the page study claim
ConditionValue and unitEvidence quote
Said to come from an internal rival, another unit of the same companyAvoided ordinal knowledge usemanagers avoided knowledge when it was said to come from an internal rival, another unit of their own company
Said to come from an external rival, a competing firmSought ordinal knowledge usesought the same knowledge when it was said to come from an external rival, a competing firm

Study source

Katz and Allen's account of the syndrome was about isolation rather than rivalry. Long-tenured project groups in their study talked less with colleagues outside the group, and with the outside world in general, than newer groups did, and their managers rated their performance lower. The authors' interpretation was that a stable group comes to believe it holds a monopoly of knowledge in its field and stops importing ideas, to its own detriment. Antons and Piller, reviewing the literature in 2015, defined the syndrome as a negative attitude toward external knowledge, held by the group, that acts as a decision bias.

The effect is easy to overstate. The Katz and Allen data are a correlation between tenure and rated performance in one laboratory, and Takahashi and Inamizu argued in 2012 that the famous curve comes from heavily smoothing a scatter plot with no clear trend, and that what Katz and Allen called the NIH syndrome was a tenure effect, not a measured rejection of outside ideas. The attitude itself has been demonstrated in controlled studies such as Menon's; its size in any particular organization is an empirical question, not a given.

The original study

Ralph Katz and Thomas Allen published "Investigating the Not Invented Here (NIH) syndrome: A look at the performance, tenure, and communication patterns of 50 R&D project groups" in R&D Management in 1982. The setting was the research and development facility of one large American corporation, where all 345 technical professionals were assigned to one of 61 project groups; complete data were obtained for 50 of the groups. The authors defined the syndrome as the tendency of a project group of stable composition to believe it possesses a monopoly of knowledge in its field, and so to reject new ideas from outsiders to the likely detriment of its performance.

Group tenure was the average time a project's members had worked together. Communication was measured by asking every professional, on one randomly chosen day each week for fifteen weeks, whom they had talked to about technical matters. Performance was rated by the laboratory's seven department managers and two research directors on a seven-point scale, with each project scored by about five raters and the scores averaged.

Plotting rated performance against average tenure, the authors reported that performance rose over the first year and a half, held steady for a time, and had declined noticeably by five years. The longest-tenured groups also talked least, among themselves and with the critical external sources of information in their field. Katz and Allen read the decline as the groups cutting themselves off, and suggested rotating members and giving groups new problems.

The paper shows an association between group tenure, communication and rated performance in one laboratory; it does not present any group rejecting a specific outside idea, and the performance measure is a manager's rating. The experimental evidence that people devalue knowledge by its origin came later, in studies such as Menon, Thompson and Choi's in 2006, where the content was held constant and only the stated source changed, which is the design the demo on this page borrows.

Everyday examples

The rows below are illustrations of where an idea's origin colors its reception, not findings from the studies cited on this page.

A workshop team labors with a clumsy frame saw while one of them raises a flat palm to a visitor in the doorway holding out a ready-to-use power saw.
Not-invented-here syndrome in a sawpit. The tool being offered through the doorway would do the cut faster and cleaner. It is turned away with a raised hand, and the team goes on heaving at their own awkward saw. The tool's origin, outside the group, is doing the rejecting, not any comparison of how well the two tools work.
SituationWhat the bias doesWhat helps
An engineering team rebuilds a scheduling tool that a sister team already runsThe existing tool's flaws loom large and the cost of building a new one is discountedWrite down the switching cost and the build cost in the same units before deciding
A hospital department receives a checklist developed by another hospitalThe checklist is read for what will not fit here rather than for what it would fixPilot it for a month and compare outcomes, with the pilot team free to adapt wording
A school adopts a reading program designed elsewhereTeachers who were not consulted judge it by its origin and defend their own approachInvolve the people who will use it in choosing it, so that adoption is theirs too
A proposal from a rival department arrives at a budget meetingThe same five points that would pass from an ally are picked apart line by lineHave proposals circulated without the author's name for a first reading
A research group stops reading work from a competing laboratoryThe group repeats mistakes the other laboratory published years earlierAssign someone to summarize outside work at a regular meeting

How to counter it

Because the bias rides on origin, most of the counters work by separating the judgment of content from the knowledge of where the content came from, or by changing what adoption costs.

  • Read first, attribute later. Circulate proposals for a first reading with the author removed, and record the first judgment before the name is revealed.
  • State the evaluation criteria before the proposal arrives. A plan judged against written criteria is harder to pick apart on whatever grounds happen to be available.
  • Make adoption cheap in status. Credit the team that adopts an outside idea as much as the team that produced it, and say so in advance; Menon's studies suggest the threat to standing is a large part of the resistance.
  • Put a price on building your own. A written estimate of the replacement makes the comparison fair.
  • Keep the group's edges open. Katz and Allen recommended rotating members and importing new problems for long-tenured teams; a group that talks to nobody outside has no way to notice what it is missing.

What it is not

Several biases concern where an idea comes from, and they overlap at the edges. The not-invented-here syndrome is specifically the group-level preference for its own output over outside output.

  • It is not reactive devaluation, in which a proposal is rated worse because an adversary in a negotiation made it. That effect concerns a counterpart's offer and the suspicion of concession; the syndrome concerns any outside origin, rivalry or not, including a tool nobody is bargaining over.
  • It is not in-group favoritism, the general tendency to favor members of one's own group. The syndrome is the special case about knowledge and ideas, and it has its own extra ingredient: the status cost of admitting the group did not think of something.
  • It is not the IKEA effect, the overvaluation of things you built yourself. That effect is about effort and ownership of a finished object; the syndrome operates before anything is built, at the point of deciding whose idea to use.
  • It is not the Semmelweis reflex, the rejection of new evidence because it contradicts an established view. The syndrome rejects ideas for coming from outside, even when they contradict nothing.

Tests and tools that use this

Related biases

Not-Invented-Here Syndrome FAQ

What is not-invented-here syndrome?

It is a group's tendency to undervalue knowledge, ideas and tools that come from outside it and to prefer its own, regardless of quality. The phrase comes from industrial research and development, where Katz and Allen used it in 1982 for project groups that stopped communicating with the outside world as they aged. In software it also names the habit of writing code in-house rather than reusing an existing library, which is the same preference applied to tools.

What did Katz and Allen find in 1982?

They studied 50 research and development project groups at one large laboratory, measuring average group tenure, technical communication and performance as rated by managers. Rated performance rose over a group's first year and a half, held steady, and had declined noticeably by five years, and the longest-tenured groups communicated least with colleagues and outside sources. They interpreted the decline as groups cutting themselves off from new ideas. A 2012 critique argued the curve rests on heavy smoothing of a scattered plot.

How does the demo on this page work?

When the page loads it assigns you one of two versions using a value kept only in your browser's session storage, so that a reload shows the same version. Both versions present the identical five-point plan; one says your own team wrote it and the other says a rival department did. You rate the plan, and the result screen shows the other version in full. Once each version has 50 or more responses the page shows the live split for both side by side.

Is not-invented-here syndrome the same as reactive devaluation?

No, though they are cousins. Reactive devaluation is the finding that a proposal is rated worse when it comes from the other side of a negotiation, and it depends on the counterpart being an adversary whose offer invites suspicion. Not-invented-here syndrome applies to any knowledge from outside the group, including from allies and from nobody in particular, and it includes a status cost: adopting an outside idea concedes that the group did not produce it.

Why do groups reject good ideas from outside?

Three reasons recur in the research. An outside idea arrives without the shared context that makes an inside idea easy to evaluate, so its gaps are visible and its strengths are not. Adopting it costs standing, especially when the source is an internal rival, as Menon, Thompson and Choi found in 2006. And a group that has worked together for years may stop seeking outside information, so the ideas it does not have never present themselves for rejection at all.

How can an organization reduce not-invented-here syndrome?

Separate the judgment of an idea from knowledge of its origin, for example by circulating proposals without the author's name for a first reading against criteria written in advance. Reward teams for adopting outside ideas as visibly as for producing their own, so that adoption carries no status penalty. Put a written cost on building a replacement. And keep groups in contact with the outside, through rotation, visitors and a standing slot for summarizing other people's work.

References

  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. doi.org
  2. Menon, T., Thompson, L., & Choi, H.-S. (2006). Tainted knowledge vs. tempting knowledge: People avoid knowledge from internal rivals and seek knowledge from external rivals. Management Science, 52(8), 1129-1144. doi.org
  3. Menon, T., & Pfeffer, J. (2003). Valuing internal vs. external knowledge: Explaining the preference for outsiders. Management Science, 49(4), 497-513. doi.org
  4. 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. doi.org
  5. Takahashi, N., & Inamizu, N. (2012). Mysteries of NIH syndrome. Annals of Business Administrative Science, 11, 1-10. doi.org

Cite this source

Psychology.com. (2026, October 24). Not-Invented-Here Syndrome. Psychology.com. https://psychology.com/biases/not-invented-here-syndrome

Important: This page and its demo are educational: they describe a pattern in how people think, not a diagnosis, a test of ability or a treatment. If something here touches a difficulty you are living with, reach out to a licensed mental-health professional.