/ Library/ Not Enough Meaning/ Reactive Devaluation
Connect Bias № 102 · Last updated 6 June 2026

Reactive Devaluation.

"If they proposed it, it must be worse — even when it's the same idea we had."

01Overview

Reactive devaluation is rejecting an option because of its source — competitor, opposing team, vendor, or leadership — even when objective quality is unchanged. The same idea wearing a different badge gets different scores.

Designers dismiss competitor patterns, research from sales, or engineering constraints framed by rivals. Users devalue features when brand they dislike ships them first. Reactive devaluation wastes good ideas and duplicates work under internal labels.

02Detailed explanation

Source poisoning appears in org and market dynamics:

  • Competitor feature mocked until internal team repackages it.
  • User research from support discounted as "anecdotal" vs identical design finding.
  • Acquisition team's roadmap discarded to assert identity.
  • Policy change rejected because unpopular executive sponsored it.

Reactance is user-side pushback on perceived control — related but user-directed. Reactive devaluation is evaluator-side source bias.

03Why it exists

Accepting rival ideas threatens identity and status. Devaluation protects in-group narrative.

Heuristics shortcut: untrusted source → low quality prior — efficient, often wrong.

The short version

Would you approve this idea if the author field were blank?

04Effects on users

Users devalue good features from brands they distrust — reputation poisons utility. Design must overcommunicate value or inherit reactive devaluation.

They also react to "suggested by partner" labels — devaluing integrations that feel imposed.

05Effects on designers & teams

Teams encode source bias in process:

  • Competitor contempt. Automatic mockery in teardowns.
  • Cross-functional discounting. Sales/support insights lower status.
  • Rebadging to adopt. Waste cycles renaming acceptable ideas.
  • Sponsor toxicity. Good proposals die with bad politics.

06Practical takeaways

  • Blind review options. Strip author and source in critiques.
  • Separate idea from sponsor. Explicit facilitation in cross-team workshops.
  • Credit external origins. Reduces need to hide source to adopt.
  • User-test without brand. When benchmarking competitors.
  • Track rejected-then-adopted ideas. Organisational learning metric.
  • Address trust deficits. If users devalue you, over-deliver proof.

07Design examples

Competitive

Mock then mirror

A competitor's filter pattern ridiculed in critique. Six months later internal "discovery lens" ships — identical interaction. Reactive devaluation cost half a year.

Cross-team

Support knew first

Support documents top confusion for months. Design dismisses until moderated tests replicate. Same insight, different source, delayed fix.

Acquisition

Not their roadmap

Acquired team's onboarding flow superior. Discarded for rebranding exercise. Users suffer until partial re-import under new name.

Executive

Sponsor poison

Unpopular VP suggests sensible defaults fix. Team resists. Consultant repackages idea; team adopts. Reactive devaluation via consultant mask.

08Ethical risks

Devaluing ideas from marginalised voices inside orgs — junior staff, support, community — perpetuates inequity and ships worse product.

Users lose when tribal devaluation blocks adoption of accessible patterns from rivals.

Self-test: What good idea did you reject recently because of who said it?

10Suggested reading

Browse recommended reading →