Tone choices must remain consistent across the product

What it is

A per-locale voice profile turns product communication intent into executable decisions for each language: honorific level, person and pronoun perspective, formality, syntax, punctuation, and prohibited expressions. Interface copy, notifications, email, help, and support then ship against the same version. Consistency here does not require every language to imitate source wording and does not redefine a general brand persona. It requires touchpoints within one locale to share native-reviewed language choices and makes changes to those choices traceable.

Why it happens

An abstract source guideline such as “friendly and professional” cannot determine which second-person form a target language uses, whether it omits subjects, which honorific morphology applies, or how it frames a request. When vendors and channels interpret it independently, the app can sound formal, email casual, and support use a third form of address even when every string is locally grammatical. A maintainable pipeline takes global communication principles as input and publishes a structured voice profile, positive and negative examples, relationship and gravity variants, and terminology dependencies for each locale. Messages, translation memory, content management, and support templates reference one profile version. A missing or incompatible profile blocks release or falls back to a reviewed neutral baseline for that locale rather than inheriting source-language voice.

Studying it

Locale QA samples across touchpoints, not only translation files. Group navigation, confirmation, errors, push, email, help, and support responses from the same journey by message ID, situation gravity, and profile version. Native-language reviewers mark honorifics, pronouns, participant relationships, formality, and prohibited expressions against the profile, separating a profile that does not fit the language from an implementation that violates it. Blinded string grouping, journey-comprehension tasks, and production feedback can reveal touchpoints perceived as different institutions or relationships. Sample language varieties, channels, and actual roles; one translator or country label cannot represent an entire locale community.

Where it stops holding

A consistent profile does not make celebration, safety warning, and legal notice equally casual or formal; intensity can vary within profile-defined bounds. One language tag can also contain regional, organizational, generational, and channel variation, requiring explicit scope or profile branches. Mandated wording, user-generated content, and verbatim quotations generally sit outside brand-voice rewriting. Automated lint can find banned terms and version mismatches but cannot judge whether a clause is pragmatically appropriate; target-language review remains necessary. If a language lacks a contrast assumed by the source profile, field symmetry must not force an unnatural distinction.

Applying it

• Publish a versioned voice profile for every supported locale, covering honorific or formality level, first- and second-person strategy, subject omission, request and refusal constructions, punctuation, prohibited expressions, and conditions for relationship or gravity variants.
• Record profile ID and version on strings, translation memory, CMS content, notifications, email, help, and support templates. Produce an affected-message manifest for upgrades, migrate together, and prevent incompatible versions from appearing in one journey.
• In CI, check for missing profiles, stale versions, prohibited expressions, variables, and message-branch coverage. Block high-risk content when a profile is unavailable; for low-risk content, permit only a reviewed neutral baseline for that locale and record remediation work.
• Run periodic cross-touchpoint locale QA along realistic journeys. Native reviewers inspect honorifics, pronouns, grammar, and formality, write defects back to a specific message or profile rule, and verify through version regression that app, email, and support update together.

Related

• Same group: S3.05.1 Verb forms in some languages vary with honorific level · S3.05.2 Personal-pronoun conventions differ
• Adjacent: T1.01.3 Voice must stay consistent across the product · T1.04.2 The glossary must cover interface, docs, and support
• Search terms: locale voice profile · multilingual voice governance · localization QA