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.
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.
6Introspective view
Look inward. Teams devalue a proposal because of who suggested it rather than its content.
From an introspective perspective, ask how Reactive Devaluation may already be shaping your research, critique, planning, and interpretation — not only what users encounter in the finished interface.
The loudest frame wins
Alignment workshops on Reactive Devaluation can converge on whoever articulated a direction first, even when the room never formally agreed. Teams devalue a proposal because of who suggested it rather than its content.
First comp on the wall
In critique, Reactive Devaluation ties later options to whichever direction was shown first — alternatives read as tweaks, not genuine forks. Teams devalue a proposal because of who suggested it rather than its content.
The story of the sprint
Retros on Reactive Devaluation tend to rehearse the narrative that is easiest to tell — usually the one that matches how people already feel about the work. Teams devalue a proposal because of who suggested it rather than its content.
Sketches that look familiar
Brainstorms about Reactive Devaluation recycle what the room already knows — competitors, past launches, favourite patterns — rather than stretching into uncomfortable territory. Teams devalue a proposal because of who suggested it rather than its content.
07Practical 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.
08Design examples
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.
Support knew first
Support documents top confusion for months. Design dismisses until moderated tests replicate. Same insight, different source, delayed fix.
Not their roadmap
Acquired team's onboarding flow superior. Discarded for rebranding exercise. Users suffer until partial re-import under new name.
Sponsor poison
Unpopular VP suggests sensible defaults fix. Team resists. Consultant repackages idea; team adopts. Reactive devaluation via consultant mask.
09Ethical 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
Suggested reading is temporarily unavailable. Please check back later.