Save ownership feeling

Companies invest in innovation, and customers search for solutions. External expertise should be welcome—consultants, partners, and best practices promise faster results. Yet teams often reject external ideas, preferring their own solutions even when these are inferior. The question is: Why are external inputs systematically devalued? Which factors intensify this rejection, and what does the evidence tell us?

Studies

The Communication Study in R&D Teams

Ralph Katz and Thomas Allen investigated the performance of 50 research and development teams at MIT in 1982 over a 15-year period. They tracked how frequently teams communicated with external experts and how project leaders assessed technical performance. The striking pattern: the highest-performing teams had a sweet spot in external communication—not too little, but not too much either. Teams that were heavily externally oriented paradoxically showed declining performance. The researchers found that the longer a team worked together, the more strongly a 'Not-Invented-Here' attitude developed. Teams that had worked together for more than five years evaluated external inputs 40% more critically than newer teams—regardless of the objective quality of the information.

The Innovation Sources Experiment

Anne Burcharth, Ulrik Knudsen, and Helle Søndergaard conducted a large-scale study in 2014 involving 423 Danish companies. Each company was asked to rate how valuable different knowledge sources were for their innovations—from internal R&D departments to universities to customers and suppliers. In parallel, the researchers tracked which sources actually led to successful innovations. The results were striking: subjective evaluations and objective performance diverged significantly. Companies rated internal sources as "very important" (7.2 out of 10 points), even though these accounted for only 31% of successful innovations. External sources were rated at 4.8 points as "moderately important," yet contributed to 69% of innovations. The discrepancy was greatest in companies with a strong technical identity.

Principle

Which principle for Customer Experience Design can be derived from this? The Not-Invented-Here Syndrome can be overcome through strategic framing of external solutions as internal developments—the key factor being the active participation of affected teams in the adaptation process. When employees can not only adopt external ideas but also further develop, adapt, or co-shape them, a sense of co-authorship emerges that breaks down the psychological barriers to external solutions. This approach is particularly effective in creative and technical domains, where autonomy and expertise represent core aspects of professional identity—though less relevant for standardized processes where efficiency takes precedence over authorship. The following guidelines demonstrate how to implement this principle in practice.

Guidelines

Staging Co-Creation

Present external solutions not as finished products, but as raw materials for collaborative development. Invite internal teams to adapt, refine, and complete the solution. Through modification, the external solution becomes hybrid—and therefore acceptable. For example, a software manufacturer could position an external best-practice template as "a beta version that still needs your expertise." This approach lowers psychological resistance because the team develops ownership through contribution.

Highlight internal origins

When you integrate external expertise, emphasize its connections to internal processes or previous projects. Use phrases like "This method builds on your work from 2022" or "The consultant used your insights as a foundation." Even if the solution is 90% external, the 10% internal contribution can be enough to create acceptance. This isn't deception—it's strategic framing. Every external solution must be adapted to your context anyway, so make this adaptation process visible and acknowledge it explicitly.

Organize peer validation

People trust similar others more than they trust experts. Rather than positioning external consultants as authorities, enable internal teams to serve as advocates. "Team B has already successfully tested this method" carries more weight than "A Harvard professor recommends it." Organize pilot projects within individual teams, document their successes, and leverage these results as social proof for broader adoption. The psychological mechanism at work: The solution no longer feels externally imposed but instead resembles an internal best practice.

Democratize the selection process

Democratize the Selection Process Don't involve the team only during implementation—engage them during the selection of external solutions. Instead of announcing "We've purchased System X," organize a collaborative selection process: "We've shortlisted three options—which one fits best?" This approach helps the team develop ownership over the decision. Even if the external solution is chosen, it was selected by the team, not mandated from above. While this requires more effort, acceptance increases dramatically. For example, a CX team could involve users in selecting analytics tools—their commitment to using them later will be significantly higher.