How Pronoun Choice in UX Writing Affects User Trust
Here's a UX writing question that comes up more often than you'd expect: when labeling a navigation item for a user's saved content, do you write "My Favorites" or "Your Favorites"?
The pronoun you use signals something about the relationship between your product and the person using it. Get it right and it feels intuitive. Get it wrong and something just feels... off. Users can rarely articulate why.
My vs. Your: Tool vs. Assistant Framework
According to Vitaly Friedman's breakdown on Smart Interface Design Patterns, this is fundamentally a product personality question: does your interface feel like a tool the user controls, or an assistant that's guiding them? His framework is worth understanding before you default to whatever feels natural.
In Friedman's view, "My" implies ownership. The user is the one labeling things. "My Account," "My Orders," "My Saved Items" all communicate that this is the user's space, shaped around their identity. He argues it works best for content users create or curate themselves, personal settings, privacy controls, and anything where a sense of agency matters.
"Your," on the other hand, implies the product is speaking. Friedman describes it as appropriate when the interface is helping a user through a process or surfacing something on their behalf. "Your Recommendations," "Your Activity Summary," "Your Next Steps" all make sense coming from a system that's doing something for the user.
He points to Netflix as a real-world example of both being used deliberately: "Your" for algorithmically generated recommendations (the product is doing the work), and "My" for the watchlist the user curates themselves. That's a considered choice, not an accident.
No Pronoun Is Also Valid
Sometimes the right answer is to drop the pronoun entirely. "Settings," "Profile," and "Drafts" work fine without one. Adding "My" or "Your" in front of obvious, unambiguous labels can actually make them feel cluttered or oddly formal.
That said, label clarity matters. "Stories" alone doesn't tell you much. Are these the user's stories? Editor picks? Related content? A label like "Your Stories" or "Recommended Reads" does real communicative work that the noun alone can't.
Nielsen Norman Group's breakdown of microcopy makes a similar point: small UI text carries disproportionate weight in shaping user comprehension and trust, and every word should have a clear purpose — whether that's informing, influencing, or guiding interaction. Pronoun choice fits squarely into that framework.
The "Who's in the Room" Test for Pronoun Choice
An older but still-useful framework from Diana MacDonald poses a useful gut-check question: "Who else is in the room?"
If it's just the user and no one is talking to them, skip the pronoun. If the product is addressing the user directly, use "Your." If the user is the one speaking or taking action, use "My." That mental model is remarkably effective for resolving debates quickly.
John Saito's piece on Medium adds another dimension: "My" makes the product feel like an extension of the user's identity, while "Your" positions the product as a separate entity in conversation with them. Neither is inherently better. It depends entirely on what you're trying to communicate.
Consistency Is Non-Negotiable
Mixing pronouns creates subtle confusion. If half your navigation uses "My" and half uses "Your," users start to wonder whether those are different contexts with different rules. They usually aren't, but the inconsistency plants a seed of doubt.
Pick a register that fits your product's personality and commit to it. If you're building a utility where users are clearly in control (a project management tool, a file system, a personal finance app), "My" probably fits. If you're building something more service-oriented or conversational (a health app walking someone through a care plan, a travel booking flow), "Your" is more natural.
At Marker Seven, we treat pronoun choice as a design system decision from day one, not a copy polish pass before launch. On enterprise platforms with dozens of contributors, an unresolved "My" versus "Your" question surfaces in every new feature ticket. Documenting the rule once, with the reasoning behind it, saves that debate from repeating itself for the life of the product.
Why Pronoun Choice Belongs in Your Design System
UX writing decisions at this level rarely get the strategic attention they deserve. Pronoun choices, button labels, empty state copy, error messages: these are often treated as implementation details rather than design decisions. But they accumulate. They're the texture of your product's voice. It's the same reasoning we've laid out in [link to cognitive load and conversions post], where small friction points compound the same way pronoun mismatches do.
When teams invest in content design alongside visual and interaction design, it shows. The Content Design London Readability Guidelines are a solid reference if you want a framework for making these calls consistently across a larger product.
It's worth building explicit guidance into your design system documentation. Not just "use sentence case" and "avoid jargon" but also the pronoun question, along with the rationale. That way the decision gets made once, not re-litigated every sprint.
