Cultural Adaptation

Origin & evolution

The distinction grew out of localisation practice itself. Early l10n treated a market as a language to translate into; experience taught the field that language is one variable among many. The industry settled on a sharper split, sometimes called culturalisation: translation converts the words, while localisation adapts the whole experience, and the cultural layer covers everything words alone cannot reach.

That layer is broad. Date and number formats flip with region. Currency and tax presentation change. Imagery and iconography that read as neutral in one market can mislead or offend in another, and colour carries meaning that does not travel: a colour signalling celebration in one culture signals mourning in another. The most structural change is reading direction. Adapting a left-to-right product for right-to-left languages like Arabic, Hebrew, and Farsi mirrors navigation and visual hierarchy, and the discipline is specific about not blindly flipping everything, since asymmetric assets and embedded numerals need🫀NeedUserA user need, pain, desire, or constraintView reference → deliberate handling rather than a horizontal flip. Legal norms add another axis: consent flows, age gating, and data-handling defaults differ by jurisdiction.

How it works in practice

A wellness app translated into Arabic passes linguistic review and still feels wrong to testers in the Gulf. The fix is cultural, not lexical. The team mirrors the layout for right-to-left reading, so progress bars fill from the right and the back gesture reverses. They swap a hero image whose iconography carried an unintended religious reading. They change a "success" colour that local users associated with warning. They adjust the date picker to the locale's calendar conventions and rework a consent screen to match regional data law. None of this touched a single translated string; all of it decided whether the product felt made for its audience.

Cultural adaptation vs. its neighbours

• Translation bundle🈂️Translation BundleLocalisationA bundle of translation keysView reference → handles the words: keys mapped to strings for a locale. Cultural adaptation handles everything else, the formats, visuals, direction, and norms that a bundle cannot express. A locale needs both, and they fail independently.
• Locale is the addressable target both attach to. The locale names language and region; cultural adaptation is the depth of work done to satisfy that region beyond its strings.
• Persona🎭PersonaUserAn archetype representing a user segmentView reference → is who the adaptation serves. A cultural_adaptation_targets_personaCultural AdaptationtargetsPersonacross-domain edge ties the work to a specific user whose expectations it must meet, keeping the change anchored to a person rather than a guess about a country.

In the graph

In the Unified Product Graph, cultural adaptation sits in the localisation region and attaches to a locale through locale_adapted_via_cultural_adaptationLocaleadapted viaCultural Adaptationhierarchy, deliberately separate from the translation path so the graph can show a locale that is fully translated yet culturally raw. It points outward through cultural_adaptation_targets_personaCultural AdaptationtargetsPersonacross-domain and cultural_adaptation_targets_market_segmentCultural AdaptationtargetsMarket Segmentcross-domain, which connect the work to the people and the market it is meant to fit. Modelling adaptation as its own node, distinct from the bundle, is what stops a team from mistaking translated for localised.