The real cost of ignoring microcopy
The version of this that works is simpler than the version most people imagine. Nobody bills you for neglecting microcopy. The cost shows up somewhere else.
Pages that answer a real question outlive pages written to fill a slot in a sitemap. The version that survives contact with a real deadline is the simple one.
Where the cost lands
- Time spent on work that should not have been necessary
- Enquiries that quietly never arrive
- The small words carry a lot of the experience
- Rework, once the problem is finally visible
Button and error text deserve real drafting. That sounds obvious written down. It is still the thing most often skipped. It is the sort of thing that looks like polish right up until it costs you an enquiry.
What to do next
Reassurance next to an action reduces hesitation. There is a version of this that is over-engineered, and it is worth avoiding. It is worth deciding this deliberately rather than inheriting whatever the last person set up.
What this looks like day to day
Content is the part of a project most likely to be underestimated and most likely to delay a launch. 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.