Nobody owns the small words
Headlines get written by a copywriter; button labels get typed by whoever built the component. Yet the button is the last thing a visitor reads before acting, and the error message is the thing that decides whether they try again.
Buttons should name the outcome
“Submit” describes what the software does. “Send project brief” describes what the person gets. Naming the outcome measurably outperforms naming the mechanism, and it is the cheapest change on the page where you lose them.
“Submit” is what the form does. Nobody arrives wanting to submit anything.
Labels beat placeholders
Placeholder text disappears the moment someone types, leaving them unable to check what a field wanted, and it is poorly handled by assistive technology. Visible labels are both a usability and an accessibility requirement.
Errors need to say what to do
“Invalid input” assigns blame and offers no route forward. Say which field, what is wrong, and what a correct value looks like. Never clear what someone already typed — that is the moment enquiries are abandoned permanently.
Set expectations near the action
A line under the button saying who replies and how quickly reduces hesitation more than most persuasion above it, and it belongs beside the action rather than in a policy page nobody opens.
Read it aloud, in sequence
Read every label, button and message on a page in order, as if speaking to someone. Anything that sounds like a system talking to itself needs rewriting — the same test that catches a headline written by committee.