A landing page might be written and rewritten many times. The checkout button, the password rule and the message that appears when a payment fails are often written once, by whoever built the screen, in a hurry. Yet these are the words people read at the moment they are deciding whether to continue.

Say what happens next

A button should describe the result of pressing it. “Submit” and “Continue” say little. “Pay ₹1,499”, “Send my quote” or “Book the slot” tell people exactly what they are agreeing to, which makes them more willing to press it.

The same goes for links. “Click here” tells a skimming reader nothing and tells a screen reader user even less. A link that names its destination is clearer for everyone.

Write errors that help

An error message has two jobs: say what went wrong and say how to fix it. “Invalid input” does neither. “The PIN code should be six digits” does both.

Error messages should never blame the user. They should appear next to the thing that needs fixing, not at the top of a long form, and they should keep whatever the person has already typed.

Answer the doubt before it arises

People hesitate at predictable points: when asked for a phone number, when a card is requested for a free trial, when a form asks for something personal. A single line next to the field, explaining why it is needed and how it will be used, removes the hesitation without anyone having to ask.

Do not leave empty screens empty

An empty cart, a search with no results or a new account with nothing in it are easy to forget. Left blank, they feel like a dead end. A line that explains what belongs there and a clear next step turns the empty moment into a useful one, and it is often the first thing a new customer sees.

Keep one voice throughout

The same action should have the same name everywhere. If one screen says “cart”, another “bag” and the email says “basket”, people start to wonder whether they are the same thing. A short list of agreed terms, kept with the design system, keeps everyone using the same words.

Include the messages sent by email and SMS in that list. They are part of the same conversation, even when a different team writes them.

Back to the journal