F6.05.3metaphor market validationdesignresearch

Metaphors have to be validated in the target market

Aliases: metaphor testing · localisation testing · destination-market validation

What it is

A metaphor that is "obvious" in a headquarters critique can be blank, a joke, or an insult in the destination market. Validation is not showing the draft to the same office again. It is taking evidence in that market, with those people, under those readings. Without that step, taboos and rot stay as items on a risk list, and the product still ships the team's mother-tongue metaphor.

Why it happens

If sender and receiver do not share objects, gestures, and idioms, the sender's "obvious" is the receiver's noise. Headquarters usability tests satisfy the shared-assumption early: participants have used the same apps, sat in similar classrooms, and have no charge on a raised thumb. Scores look fine and do not travel. Market validation removes that share so failure happens before release. It does not ask whether the drawing is attractive. It asks what the drawing is read as here, whether it offends, and whether younger users still know the original object. Fail any of the three and the metaphor has not passed.

Studying it

Write the destination market as a sampling frame, not as a name on a ship calendar. In each market run a small open-naming plus an offence follow-up, excluding employees and people who have long lived at headquarters. Contrast with a headquarters sample: does the same set keep the same dominant meaning. The independent is market, not draft version — confirm that the metaphor holds here before stroking the path. Remote sessions still need tasks in the local language, not a translated headquarters script that local people are asked to "help complete".

Where it stops holding

  • One market, one language, users who match the team: an extra "destination" round buys little.
  • A passed metaphor still ages. Objects keep leaving, gestures get re-tagged. Retest; do not treat one certificate as a decade of cover.
  • This step does not fix "the function never had an object". It only judges whether the metaphor already chosen works here.
  • Red/green inversion for financial up and down is a separate validation. Do not fold it into one composite score with pictorial metaphors.

Applying it

  • Make destination-market validation an exit gate for metaphor icons: at least one local open-naming and offence round per market that will ship.
  • A headquarters pass does not replace that round. Headquarters checks whether the subject was drawn; the market checks whether the meaning arrived.
  • How to check: archive transcripts by market. If the dominant meaning misses the intended one, or offence is nominated, the metaphor has not passed in that market. Swap words or drawings and test again; do not patch with a caption and ship.

Related

  • Same group: F6.05.1 Gesture icons carry cross-cultural taboos · F6.05.2 Physical metaphors fail as the objects disappear
  • Nearby: S3.02 Cultural taboos of icons, gestures, and images · A11.09 Cultural differences in interface understanding · F5.10 Cultural meanings of colour
  • Search terms: metaphor market validation · localisation testing · icon comprehension

Cards in the same group

Quick Actions

Share

Share this page

ios_share

https://hci.top/en/handbook/F6.05.3