/ Library/ Not Enough Meaning/ Masked Man Fallacy
Connect Bias № 126 · Last updated 6 June 2026

Masked Man Fallacy.

"Change the name and we act like it's a different thing entirely."

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.

The short version

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.

06Practical 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.

07Design examples

Rebrand

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.

Research

Tracking vs personalisation

Concept A "usage tracking" fails. Concept B "personalised tips" wins. Specs reveal identical data collection — two roadmaps for one pipeline.

IA

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.

Compliance

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.

08Ethical 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

Browse recommended reading →