Writing Is a Design Skill
The words on a button are a design decision. The empty state copy is a design decision. How to treat product writing as a first-class craft.
Every word is a design decision
The label on a button is a design decision. The copy in an empty state is a design decision. The error message when something fails is a design decision. Yet in most teams, these decisions are made last, by whoever is available, with no review. The result is products that look designed but sound accidental.
Writing is not the garnish on a design. It is part of the structure. A button that says "Submit" creates a different experience than one that says "Send invitation." The first is bureaucratic. The second is human. Both are valid, but the choice should be intentional, not default.
The principles of product writing
First, write for the user who is in a hurry. They are not reading your copy. They are scanning for the next action. Every word that is not helping them find that action is noise. Cut ruthlessly. If a sentence does not help the user do something, remove it.
Second, write at a fifth-grade reading level. This is not about dumbing down. It is about cognitive load. A user who is trying to complete a task does not have spare capacity to parse complex sentences. Simple writing is not simple-minded. It is considerate.
Third, write with a consistent voice. If your empty states are warm and your error messages are cold, the product feels like two different teams built it. A voice guide does not need to be long. Three or four principles — "be helpful, be honest, be brief" — are enough to keep a team aligned.
Making writing part of the process
The fix is process, not talent. Include a writer in the design review. Write the copy as part of the design, not after it. Test the copy with users, not just the layout. When the copy is treated as a first-class part of the design, the product sounds like it was designed. When it is an afterthought, it sounds like it was assembled.
