Microcopy, explained without the jargon

This is one of those topics that looks small until it costs you something. Here is microcopy without the vocabulary that usually surrounds it.

Content is the part of a project most likely to be underestimated and most likely to delay a launch. It is the sort of thing that looks like polish right up until it costs you an enquiry.

The short version

The small words carry a lot of the experience. None of that requires a large budget, only a decision and someone to own it. Check it against what you would want a competitor's site to get wrong.

Why people complicate it

Most of the confusion comes from tooling rather than from the idea itself. The cost of getting this wrong is rarely visible on the day it happens.

Button and error text deserve real drafting. This is the sort of thing that compounds, quietly, in both directions. The practical test is whether someone new to the project could tell, in a minute, that it had been handled.

What to do next

Reassurance next to an action reduces hesitation. It is worth being explicit about, because assumptions differ quietly. The failure mode is not doing it wrong, it is doing it once and assuming it stays done.

The short version

Pages that answer a real question outlive pages written to fill a slot in a sitemap. Three things worth confirming about microcopy before you move on:

• Someone can say what the current setup is without going to look
• Reassurance next to an action reduces hesitation — and you know whether that is true here
• There is a way to tell whether the last change to this helped

The point is not perfection, it is knowing which of these you have consciously chosen to skip.