Why a Good Fix Can Lose to Its Origin
An outside proposal enters an organization carrying two questions: Will it work? And what would adopting it say about the people already here? When a team has spent months diagnosing a problem, a ready-made answer can feel like a judgment on its effort or expertise—even if the proposal is sound. The reaction may look like stubbornness, but it often reflects incentives built into how organizations assign credit and blame.
Who Gets Credit—and Who Carries the Risk?
Employees are often rewarded for visible contributions, not for choosing the best idea regardless of its source. A manager who backs an outside solution may receive little credit if it succeeds, while being held responsible if it fails. The original team, by contrast, can point to its own work as proof of competence. That makes rejecting an unfamiliar fix a safer career move than testing it.
There are practical concerns, too. An outside team may not understand local systems, customer needs, or hidden dependencies. Adopting its proposal can require retraining, new contracts, or changes to established processes. Those costs are real, but they can also become convenient reasons to dismiss an idea without comparing it fairly with the cost of doing nothing.
Make the Test About Results
Organizations can reduce this bias by separating the proposal’s source from its performance. Define what a successful trial would look like, test the fix on a limited scale, and compare its results with the current approach. This gives skeptics a way to surface genuine risks while making it harder for status or ownership to decide the outcome in advance.
A small trial also changes the stakes: leaders need not declare the outside team right, only agree to gather evidence. The organization can then keep what works, adapt what does, and reject what fails—with the decision grounded in results rather than in who first had the idea.
