Write interface labels for the task, not the brand
Customers do not open your site to admire your brand voice. They open it to finish a job: change a password, find a price, cancel a booking, or check whether a feature exists.
When labels on buttons, menus, and headings talk about the brand instead of the task, people slow down. They scan, hesitate, and click the wrong thing. That hesitation is not a personality quirk. It is a design failure.
Good labels are boring on purpose. “Change password,” “Download invoice,” and “Contact support” tell people what will happen. “Unlock your journey,” “Get inspired,” and “Connect with us” sound friendly in a meeting and vague on a page.
Start with the task verb. Ask what the person is trying to complete in the next thirty seconds. Name that action in the words they already use when they search or call support. If your analytics, search logs, or help-desk tickets already show those words, prefer them over the marketing glossary.
Feature names are especially risky. Teams invent internal titles for products, then promote those titles into the navigation. Customers have never heard them. A menu that lists “Horizon Suite,” “Pulse Desk,” and “Nexus Hub” forces people to decode your org chart before they can act.
Keep brand language for places that are not critical path: homepage hero lines, about pages, campaign landers. On forms, settings, checkout, and support flows, clarity beats cleverness every time.
Test labels the way you test links. Cover the surrounding paragraph and ask a colleague what they think the control does. If they guess wrong, rewrite. If two controls feel interchangeable, make them more distinct. Ambiguous neighbors create the same forest of wrong clicks that confusing menus always create.
Consistency helps more than novelty. If “Account” means profile settings on one page, do not rename it “My space” on another. Moving the same task under a new label teaches people that your interface cannot be trusted, so they fall back to search or support.
Length matters too. A button should usually hold three to five words. Longer phrases belong in helper text under the control, not in the control itself. People reading on a phone need the action to fit in one glance.
When you rewrite a label, ship the change with the neighboring copy. Helper text, empty states, and error messages should repeat the same task words. A clear button that leads into jargon-heavy instructions only moves the confusion one click downstream.
Writing for the task is not anti-brand. It is customer-centric design. Your brand earns trust when people finish what they came to do without translating your slogans into plain English first.
