Person choice positions the relationship between product and user

What it is

Person choice and relational stance use product self-reference, direct second-person address, third-person role labels, or impersonal constructions to establish who speaks to whom and frame distance, authority, and responsibility. The meaning of a form depends on language, organization, and situation. “You,” a formal form, a name, a role, and subject omission are not globally ranked solutions. First define the relationship the product intends, then select a person system that the target audience understands naturally and that fits the task's risk.

Why it happens

Person is a form of deixis. Expressing one fact as “we,” “the system,” “your account,” or a subjectless clause changes whether the speaker owns the action, whether the reader is directly asked to act, and whether the exchange feels close, formal, or institutional. Interfaces distribute short strings across controls, notices, help, and support, so those choices accumulate into a relationship. A choice based only on a writer's preference or source-language habit can make the product invite as a peer and command as an authority. Omitting actors to sound light can also remove accountability from consequential messages.

Studying it

Within one language and task, compare person strategies reviewed for native pragmatics while holding action, information, and length as constant as possible. Ask participants who is speaking, who must act, and what role the product claims; measure comprehension, first action, perceived distance, credibility, and discomfort rather than preference alone. Include the relationships the product actually serves—consumer, employee, administrator, caregiver, or institutional representative—and separate everyday from consequential situations. Results belong to that language, audience, and task; effects in one language cannot be generalized to other languages or identity groups.

Where it stops holding

Relational stance does not resolve the actor or owner of every message; complex actions still need local referent clarity. Address forms cannot establish real equality, care, or authority, and intimate copy increases distrust when product behavior contradicts it. Mandated text, user-generated content, verbatim quotation, and third-party messages retain their actual speaker. Emergency, financial, medical, security, and permission contexts prioritize explicit actor, action, object, and consequence over an intimate or consistently subjectless style.

Applying it

• Write a relationship model first: who the product speaks as, which role it gives the user, which touchpoints belong to a third party or human agent, and where that relationship changes under consequence.
• Provide allowed and disallowed examples for first, second, third person, and impersonal wording. Do not make “you,” “I,” or formal address a global default; choose natural forms again in each target language.
• Audit entry, controls, confirmations, errors, notifications, and help across critical journeys for one coherent relationship. In consequential copy, additionally identify executor, affected party, outcome, and recovery owner.
• Without showing the standard, ask target readers to label speaker, addressee, expected relationship, and next action. If their interpretation conflicts with the model, revise the copy or model rather than adding more tone adjectives.

Related

• Same group: T1.01.2 Mixing "you" and "my" confuses who is speaking · T1.01.3 Voice must stay consistent across the product · T1.01.4 Tone should adjust with situation gravity, not stay uniform
• Adjacent: S3.05.2 Personal-pronoun conventions differ · T1.08.1 Avoid default assumptions about ability, gender, or age
• Search terms: person deixis · direct address · relational stance