Greeting someone by first name feels warm in one culture and disrespectful in another

What it is

A system greeting a user with "Hi, Alex" reads as warm and natural in one culture; in another culture that places more weight on age or status-based politeness, that same first-name greeting can come across as abrupt or even disrespectful. At the core of this is forms of address and politeness hierarchy — in many languages, how a name is used (bare first name, surname plus honorific, title plus surname) itself encodes information about how close or distant, how equal or unequal, the speaker considers the relationship to be. Pick the wrong form of address and the social signal sent is wrong, independent of whether the content itself is correct.

Why it happens

Choice of address form affects how a user reads a system because, in many language systems, a form of address is not just a label pointing at a person — it is part of a grammar or vocabulary that encodes social relationship. Whether an honorific or a plain form is used, whether a title or kinship term is attached, directly signals what relational distance and status gap the speaker assumes. When a system addresses a user a certain way, the user unconsciously reads it as "this is what the system thinks our relationship is," even when the system had no such intention at all. This is comprehension at the level of social appropriateness, unrelated to whether the content translation is accurate — a perfectly correct translation with the wrong politeness register still reads as awkward or offensive.

Where it stops holding

This mismatch is most visible where a system actively addresses the user (greetings, notifications, reminders that name the user) and has little effect in purely internal data storage or backend display. Politeness expectations also aren't fixed once and for all by nationality — they shift within the same culture by age group and context: a younger user on a social product may welcome a casual, first-name tone, while an older user, or the same user in a formal financial or medical context, may expect a more formal address. A given address convention shouldn't be treated as one culture's fixed default and applied uniformly across every context and every user.

Applying it

• How to split name fields, and how to support different orderings and numbers of name components at the data-structure level, is a localization-implementation question outside the scope of this entry;
• Focus review on text the system actively generates that addresses the user directly (greetings, reminders, error messages that include the user's name), and confirm its politeness register matches the target market's expectations, rather than translating the source language's address form word for word;
• For a single market where politeness expectations may split across contexts (a product serving both casual social users and formal business users), consider letting the tone of address adapt by context or user preference rather than being fixed globally;
• Verification: have native speakers from the target market review all system-generated address text and judge whether the politeness register is appropriate for that context, rather than only proofreading for linguistic correctness.

Related

• Same group: A11.09.4 high-context and low-context preferences for information density · A11.09.6 cultural differences in privacy expectations
• Nearby: A11.05 domain knowledge and terminology comprehension
• Search terms: honorifics · forms of address · politeness hierarchy