← Selected work
UX Writing / Content Design / Brand Voice

Brand voice and UX writing work

Project note

A supporting project note about turning product language, brand voice, and UX writing guidelines into practical communication rules for complex analytical products.

UX WritingContent DesignBrand VoiceDocumentationTerminologyProduct CommunicationTone of Voice
User journey showing how a client moves from searching for solutions to using the product, meeting different teams and communication touchpoints along the way.
The work started from the real journey: clients and partners meet the company through many people, channels, and product touchpoints, so the communication needs to feel coherent.
Role
UX Writer, Content Designer
Status
Ongoing
Relevant for
UX Writer roles, Content Designer roles, Product Designer roles with strong communication needs, SaaS/product teams, brand voice projects.
Evidence focus
UX writing, terminology, product language, and communication systems.

Context

Products often grow faster than their language. In an organization with many products, markets, authors, and communication channels, users can meet slightly different versions of the same brand and product language.

Problem

How can product, marketing, support, documentation, and internal teams communicate with one recognizable voice while still adapting tone to different audiences, channels, and situations?

My role

My work included UX writing, interface copy, system messages, onboarding communication, verification flows, email communication, naming and terminology, brand voice guidelines, practical examples, documentation, and collaboration with product, support, business, marketing, and design teams.

Key challenges

  • Mapping how different groups experience the brand across websites, social media, product UI, documentation, emails, support, presentations, and sales conversations
  • Turning abstract brand traits into writing principles that teams can actually use
  • Balancing expert, data-based communication with clarity and accessibility
  • Keeping the voice consistent while adapting tone to audience, channel, and situation
  • Creating reusable examples so multiple authors can write in a similar way

Process

The process included auditing existing communication, mapping audiences and touchpoints, clarifying the difference between voice and tone, defining tone dimensions, preparing do/don't examples, shaping rules for data-first communication, and translating the guidance into practical material for teams.

What I worked on

Interface and system copy

Labels, buttons, hints, empty states, errors, success messages, verification flows, onboarding, permissions, and transactional communication where users need clear next steps.

Product language and terminology

Consistent names and terms across screens, documentation, emails, and internal communication so users and teams describe the same things in the same way.

Brand voice guidelines

Voice principles, tone sliders, examples, do/don't rules, and communication patterns that make brand language usable in daily product and marketing work.

Data-first communication

Guidance for rankings, charts, comparisons, tables, audience insights, trend posts, and market updates where the message needs to support the data instead of competing with it.

Key design decisions

Problem

Brand voice can stay abstract if it only describes personality in broad words.

Decision

Translate voice principles into concrete examples, tone choices, and do/don't rules.

Why it mattered

Teams need practical guidance they can apply while writing real product messages.

Problem

Different audiences need different levels of context, but the brand still needs to feel recognizable.

Decision

Separate stable voice from flexible tone and map tone choices to audience, channel, and situation.

Why it mattered

The communication can feel consistent without sounding identical in product UI, sales material, documentation, social media, or support.

Problem

Analytical products need precise language, but precision can easily turn into jargon.

Decision

Use data-first writing rules: clear title, metric, period, source, context, and short takeaway.

Why it mattered

Users can understand the message without losing the accuracy needed in analytical or business contexts.

Problem

Different teams often write for the same product in slightly different voices.

Decision

Treat communication as a shared system across UI, emails, documentation, support, sales, marketing, and internal materials.

Why it mattered

Consistency builds trust and reduces the amount of interpretation users and teams have to do.

Solution

The work resulted in clearer communication principles, tone-of-voice guidance, practical writing rules, examples of better product and data communication, and documentation that helped teams write more consistently across product and business contexts.

Visual evidence

Brand archetype slide explaining Explorer and Sage as the closest archetypes to the brand.

Grounding the voice in brand research

The brand voice direction was connected to research-based archetypes. Explorer supported curiosity and experimentation, while Sage supported expertise, data, and credible knowledge.

Communication style matrix mapping audience groups, touchpoints, and recommended communication traits.

Adapting communication to audience and touchpoint

The guidance mapped audience groups to touchpoints and writing traits, showing how the same brand voice can become more direct, expert, friendly, practical, or concise depending on context.

Tone scale showing the intended balance between formal and casual, serious and funny, matter of fact and enthusiastic, distanced and close.

Making the tone range visible

Tone sliders made the desired communication style easier to discuss: more casual than formal, more matter-of-fact than enthusiastic, close but still professional.

Before and after examples showing how dense product copy can be rewritten to be clearer and more consistent with brand voice.

Turning principles into better product copy

The work did not stop at principles. It included concrete before-and-after examples that made complex product and data communication clearer, more structured, and easier to act on.

What this project demonstrates

  • UX writing
  • content structure
  • brand voice thinking
  • tone of voice
  • terminology decisions
  • documentation
  • communication clarity

Reflection

Writing is design. In complex products, language does not only explain the interface. It shapes how trustworthy, understandable, and usable the product feels.

Ask the assistant about this project

Portfolio Assistant
Based on Patrycja's approved portfolio knowledge

Hi, I'm Patrycja's AI portfolio assistant. I can help you explore her experience, projects, AI work, UX writing skills, and potential fit for your role or team. You can ask a specific question or paste a job description for a role-fit check.

Please do not paste confidential or sensitive personal information. This assistant sends your question to Google Gemini API free tier and answers from Patrycja's approved portfolio knowledge base. Some details may still need to be confirmed directly with her.