01Overview
The masked man fallacy is the error of treating something as unknown or different because it is described differently — "I know it's Jones; I don't know who the masked man is" — when the description and the thing are the same. In design, rename a feature and teams debate as if capability were new.
Rebrands, synonym swaps in copy, and technical renames spawn duplicate flows, broken links, and user confusion. The fallacy also hits research: users reject a solution described one way and accept the same solution described another — teams build two features.
02Detailed explanation
Label–identity confusion appears across product surfaces:
- "Wallet" renamed "Balance" launches a parallel UI while old wallet persists in code.
- Users reject "tracking" but accept "personalisation" in concept tests — same data use.
- Engineering renames a service; design files still reference old term — two truths.
- Compliance mandates new consent language; teams rebuild flows instead of updating copy.
Essentialism whispers that categories have true cores; masked man fallacy is the copy-level version — new label, supposedly new essence.
03Why it exists
Language frames cognition. New words feel like new concepts even when referents are unchanged.
Organisational silos mean renaming happens in marketing before engineering — identity splits across systems.
Before you build "the new thing," check if it is the old thing in a mask.
04Effects on users
Users map by function, not rebrand deck. Two names for one capability feels like two unreliable products — or they miss that old feature still exists under new badge.
They also fall for masked framing in consent: "analytics" vs "insights" — accepting what they would reject if vocabulary were consistent.
05Effects on designers & teams
Teams multiply entities through naming churn:
- Rebrand-driven duplication. New IA instead of alias and redirect.
- Synonym concept tests. Two winning concepts, one mechanism.
- Glossary drift. Design, eng, and support use different masks for same object.
- Feature flags forever. Old and new names both live — users see ghosts.
6Introspective view
Look inward. Teams treat the same thing as different when only its label changes, confusing labels with identity.
From an introspective perspective, ask how Masked Man Fallacy may already be shaping your research, critique, planning, and interpretation — not only what users encounter in the finished interface.
Themes that fit the deck
During synthesis, Masked Man Fallacy nudges teams toward a tidy narrative — quotes that support the emerging story rise to the top; outliers stay in the spreadsheet. Teams treat the same thing as different when only its label changes, confusing labels with identity.
The brief you inherited
Strategy work on Masked Man Fallacy often starts from a problem statement someone else wrote — and that opening frame limits which solutions feel in scope. Teams treat the same thing as different when only its label changes, confusing labels with identity.
What you hear first sticks
In early interviews about Masked Man Fallacy, the opening participant can set the frame for everyone after — which pains feel central, which workflows seem broken, which quotes get repeated in synthesis. Teams treat the same thing as different when only its label changes, confusing labels with identity.
Question order shapes answers
A survey built to study Masked Man Fallacy often primes respondents before the key item: lead with a vivid scenario and later ratings drift toward that frame. Teams treat the same thing as different when only its label changes, confusing labels with identity.
7Extrospective view
Look outward. Renaming a feature can make users think it's a new thing, relevant to IA and labelling.
From an extrospective perspective, Masked Man Fallacy is a property of the product experience itself — visible in pricing, copy, defaults, layout, and the moments where users decide whether to continue, convert, or leave.
What looks like the main path
Information architecture exposes Masked Man Fallacy through prominence — items at the top level, repeated labels, and familiar placement feel "correct" even when a better route exists. Renaming a feature can make users think it's a new thing, relevant to IA and labelling.
Words that set the frame
Button labels, helper text, and error messages carry Masked Man Fallacy in miniature — a single verb choice can reframe the same action as gain, loss, risk, or relief. Renaming a feature can make users think it's a new thing, relevant to IA and labelling.
Shortcuts that stick
Friction reduction can trigger Masked Man Fallacy when users adopt a default path simply because it was easiest — not because it was best for their situation. Renaming a feature can make users think it's a new thing, relevant to IA and labelling.
Everyday tasks
In regular use, Masked Man Fallacy shows up in habit — users repeat what worked once, notice what is salient, and miss gradual interface changes. Renaming a feature can make users think it's a new thing, relevant to IA and labelling.
08Practical takeaways
- Maintain canonical identity maps. One object, many labels — document aliases.
- Test function, not only vocabulary. Show what happens, not just what it is called.
- Consolidate on rename. Redirects, unified search, deprecation banners.
- Align cross-functional glossary. Weekly rename tax is expensive.
- Audit consent and privacy language. Same practice, different masks = legal and ethical risk.
- Challenge "new feature" claims. Ask what capability changed, not what label changed.
09Design examples
Wallet and Balance
Marketing launches Balance. Engineering keeps Wallet endpoints. Users see two balances. Support macros use both terms — masked man fallacy at org scale.
Tracking vs personalisation
Concept A "usage tracking" fails. Concept B "personalised tips" wins. Specs reveal identical data collection — two roadmaps for one pipeline.
Library becomes Hub
A content library renames to Resource Hub with new nav entry. Old URLs die. Users email "where did Library go?" — identity continuity broken by label change.
New consent flow
Legal updates policy title. Product rebuilds onboarding. Diff shows copy change only — months of work because masked language felt like masked product.
10Ethical risks
Renaming harmful practices without changing behaviour deceives users who rejected the unmasked version.
Duplicate systems from naming drift waste user attention and erode trust in consistent mental models.
Self-test: What did you ship as "new" this year that is functionally the same thing with a different name?
10Suggested reading
Suggested reading is temporarily unavailable. Please check back later.