UX Writing That Sounds Like You
UX Writing That Sounds Like You. The goal isn’t clever—it’s clarity people can repeat after hearing it once.
Content that works trades novelty for usefulness repeated consistently.
Steps
- Document decisions in one page — People use what they can read in two minutes.
- State the promise in plain words — Avoid poetry; say the outcome a buyer can point to later.
- Define the audience and their stakes — Name who loses what if nothing changes; real stakes sharpen choices.
- Design constraints before concepts — Constraints produce coherence; they are not creative jail.
- List three proof points — Social, data, demos. Proof turns belief into trust.
Why this matters: People use what they can read in two minutes. In branding, consistency is a function of decisions captured and reused.
Why this matters: Avoid poetry; say the outcome a buyer can point to later. In branding, consistency is a function of decisions captured and reused.
Why this matters: Name who loses what if nothing changes; real stakes sharpen choices. In branding, consistency is a function of decisions captured and reused.
Why this matters: Constraints produce coherence; they are not creative jail. In branding, consistency is a function of decisions captured and reused.
Why this matters: Social, data, demos. Proof turns belief into trust. In branding, consistency is a function of decisions captured and reused.
Toolkit
- Palette tokens — CSS variables / design tokens for color and spacing across apps.
- Voice ladder — From formal to playful with examples for each channel.
- Messaging blocks — Headline • subhead • bullets • CTA mapped to page sections.
How to use it: CSS variables / design tokens for color and spacing across apps. Save the final in a shared doc; link from tickets so execution matches intent.
How to use it: From formal to playful with examples for each channel. Save the final in a shared doc; link from tickets so execution matches intent.
How to use it: Headline • subhead • bullets • CTA mapped to page sections. Save the final in a shared doc; link from tickets so execution matches intent.
Example
A dev‑tools startup replaced clever taglines with a plain promise and saw demo requests up 34% in six weeks.
Related Articles
- A Visual Identity You Can Scale — Pro Tips #2
- Case Studies with a Plot — Guide #2
- Brand Guidelines in One Page — Field Notes #2
- Personas That Don’t Lie — Playbook #2
← Previous: Story Structures That Sell Next: Proof: Social, Data, and Demos →