Design and Experience
UX writing
In complex products, users read before they “get the layout.” We define voice and tone, clarity patterns (titles vs body vs help), and messages that work on mobile, under stress (payment errors), and in regulated contexts—aligned with brand and accessibility.
We curb internal jargon leaking into the UI and duplication across toast, modal, and error pages. For mixed locales we keep PT-BR consistency with a domain glossary.
Deliverables built to scale: message matrix per error code, variants by product plan, and guidelines so marketing does not misalign promises with what the app actually does.
Portfolio of UX writing
Deliverables
Voice and tone guide
Do and don’t examples with rationale.
Microcopy library
Strings by component or flow with variants.
Error → message matrix
Codes or failure types mapped to text and next step.
Product glossary
Domain terms and agreed internal translations.
Inclusion and clarity checklist
Reduce bias, ambiguity, and blaming the user.
In-app SEO recommendations (when applicable)
Help titles and empty states that are findable.
Execution methodology
-
Product content audit
Critical screens, tone inconsistencies, high-anxiety points (auth, billing, data).
-
Voice, tone, and principles
Who “speaks,” how we handle errors, formality level, forbidden or preferred words.
-
Writing and design iteration
Microcopy in components; length for truncation and future translation.
-
System and edge-case messages
Timeouts, permissions, empty states, destructive confirmations.
-
Governance and handoff
Where copy lives (CMS, repo, Figma), legal/compliance review when needed.
