Metaphors necessarily break where they exceed the original object’s properties; define their boundary in advance

What it is

A metaphor holds only where the source domain overlaps the target function. Trash implies permanent loss, paper lacks multiple parents, carts do not allocate inventory, and desktops do not manage concurrent collaboration. Once function exceeds the original object, design must define the boundary, introduce new rules, or move to abstraction.

Why it happens

Metaphor transfers structural relations and action expectations. Users import assumptions from “file,” “trash,” and “cart”: recoverable, destroyable, cumulative. When digital capability exceeds the source domain, those assumptions become wrong constraints. If the interface keeps the appearance without explaining the rule, users predict nonexistent limits or feel uneasy about reasonable capability. Breakdown is inevitable; unmanaged breakdown is the failure.

Where it stops holding

Some breaks can be taught, such as “cloud folders can be shared but remain permission-controlled”; others should abandon the metaphor because correction costs exceed benefit. Source-domain experience varies by generation, region, and device, and outdated skeuomorphism can reduce efficiency. Critical actions must not rely solely on a fragile visual metaphor.

Applying it

• Create a metaphor mapping table: inherited properties, rejected properties, exception rules, and likely misunderstandings.
• At each break, provide text, examples, and first-use guidance, such as “Trash empties permanently after 30 days.”
• Test what users predict they can and cannot do, then convert surprising boundaries into explicit rules or another model.
• Review deletion, sharing, payment, and collaboration paths so consequences are not conveyed only by a metaphor icon.

Related

• Same group: B3.14.1 The match targets users’ world, not the designer’s or the engineering implementation’s world · B3.14.3 Terminology consistency outranks terminology accuracy; synonym rotation is read as different concepts · B3.14.4 Numbers, dates, and units should follow users’ local conventions
• Nearby: B2.01 Affordances · B3.02 Match with the Real World
• Search terms: metaphor breakdown · interface metaphor · skeuomorphism