Writing for Interfaces

There is a persistent myth in product design that copy is secondary to visuals. That the designer lays out the screen and then someone, often the designer themselves at the last minute, fills in the words. This is backwards. The words are the interface. Everything else is scaffolding.

A button that says "Submit" is a different product than a button that says "Create account." A label that says "Error" is a different product than a label that says "That email is already registered. Would you like to log in instead?" The visual treatment of these elements matters, but it matters less than what they say.

The Economy of Interface Language

Interface copy operates under constraints that prose does not. Space is limited. Attention is scarce. Every word that does not earn its place is stealing from the words that do. Start by writing what you mean. Then cut every word that can be inferred from context. Then cut every word that the user already knows. Then read what remains aloud. If it sounds like a human talking to another human, you are close.

Tone Is Functionality

Tone is not decoration. It is part of the functional behaviour of the interface. A friendly error message reduces frustration. A confident onboarding flow builds trust. A playful confirmation message rewards the user for completing a task. These are measurable effects, not aesthetic preferences. But tone must be appropriate to context. Getting this balance right is one of the hardest and most undervalued skills in product design.

Consistency Is a Promise

If you call it "Settings" on one screen and "Preferences" on another, you have broken a promise. The user now has to wonder whether these are different things. Terminology is part of the information architecture of your product. Build a glossary. Use it. When you change a term, change it everywhere at once. Once the terminology decisions are made and documented, you stop having the same argument in every design review and start spending that energy on harder problems.