If it's embarrassing read aloud, it isn't finished

Design reviews cover spacing, hierarchy, colour. They almost never cover the words, even though the words are the first thing anyone actually processes.

Nobody looks at a page. They read it, decide what it is, decide whether to stay, and all of that happens well before anyone deliberately evaluates a single design decision you agonised over.

Lorem ipsum lies to you

A layout built on placeholder text is built on a fiction: that content runs roughly the same length everywhere, distributes evenly, and never throws an awkward edge case.

Real copy? Nothing like that. One product name is three characters, the next is thirty-one. One testimonial is a sentence, the one directly under it is a paragraph and a half. A design that only works with content you invented isn't a design, it's an illustration of one.

So design with the real words. Or better, the worst-case real words. The layout that survives "Allure New York" and "Ftg" sitting in the same column is the one that actually ships.

Submit, or send it over

Two buttons. Identical in every measurable way. One says "Submit." The other says "Send it over."

Same pixels. Completely different product. Voice changes how a component feels more reliably than most styling decisions do. You can spend a week perfecting a hover state and undo all of it with one badly chosen verb.

Which is why handing copy off at the end is backwards. By then the layout has already committed to a tone, and the writer's filling boxes that were shaped around Latin nobody read.

The headline that runs three lines

A heading running three lines on mobile isn't a copy problem to fix later. It's a layout nobody has designed yet.

The constraint runs both directions, which is the genuinely interesting part. Sometimes the answer is a wider column. More often it's a shorter heading, because the long one was hiding a fuzzy idea. Copy that won't fit is usually copy that hasn't been decided.

Cut a heading from eleven words to four and you'll typically improve the layout and the thinking behind it in the same motion.

Error messages are copy too

Button labels. Error messages. Empty states. Form validation. Placeholder text. Confirmation toasts.

Who writes these? Nobody. They accumulate. Someone types "Something went wrong" at 6pm on a Thursday and it sits in production for three years. People hit this writing at the exact moment they're most likely to leave, which makes it the worst imaginable place for a default.

An error that says what happened and what to do next will beat most visual polish. Costs less, too, which nobody wants to hear.

Write it badly, then design it

Write the copy first, badly if necessary. Design against it. Rewrite when the layout teaches you something. Rewrite again when you hear someone read it aloud and trip over a clause.

If reading it out loud is embarrassing, it isn't finished, however good it looks on screen.