UX Writing and Microcopy

A candidate can nail the Double Diamond, sketch a flawless information architecture, and still ship a product that frustrates users at the exact moments that matter most — the error message that says "Something went wrong," the blank screen after signup that explains nothing, the confirmation button that just says "OK" on an irreversible delete. Words are not a finishing touch applied after the layout is done. They are load-bearing UX, and interviewers who ask about microcopy are checking whether you treat writing as design work with its own principles, or as an afterthought filled in with whatever text fits the box.

This subject covers the specific, nameable patterns that separate deliberate UX writing from copy that just happens: the difference between a product's voice and its tone, a repeatable structure for error messages, why an empty state is either a missed onboarding opportunity or exactly the wrong message for the situation, how progressive disclosure applies to words as much as to layout, why button labels should name the action rather than reuse "OK," why building screens around lorem ipsum produces layouts that break on real content, and why a UI designed only for English-length strings breaks the moment it's translated. Every section below leads with the principle and follows with before/after copy, because in an interview, a candidate who can produce the actual rewritten sentence is more credible than one who can only describe what "good" copy would sound like.

This subject sits alongside interaction-design-principles (the flows the copy sits inside), design-critique-and-portfolio-presentation (how to talk about copy decisions when presenting work), and design-ethics-and-dark-patterns (what happens when microcopy is used to manipulate rather than clarify) elsewhere in this track.