📖 Book
✓ Link checked
Paid
Beginner
Why we picked it
This is the single most practical book written entirely about the tiny words in your product (buttons, error messages, empty states, form hints). It walks through real screenshots and shows the difference between a label that stalls a user and one that moves them forward. If you only buy one thing on this topic, start here.
From
microcopybook.com (Nemala)
by Kinneret Yifrah
~350 pages
- Every button and message is a design decision, not filler text
- Write for the user's motivation and the barrier in their head at that moment
- Errors should name the problem in plain words and point to the fix
Open
microcopybook.com →
📖 Book
✓ Link checked
Paid
Intermediate
Why we picked it
This is the book most working UX writers point to when they need a system, not just tips, for the exact text on buttons, errors, labels, and confirmations. Chapter 4 walks through UX text patterns for each of these components, so it directly answers how to phrase a button so people know what will happen and how to turn a vague error into a next step. The 2nd edition is current (2025) and covers writing copy in a world of AI-generated UI text.
From
O'Reilly Media
by Torrey Podmajersky
- Treat every button and error as a pattern with a job to do, then write to that job (buttons name the action, errors name the fix), rather than reaching for generic words like Submit or OK.
- Keep button labels tight (Podmajersky's guidance is roughly three words max) and use an action verb so the label reads as what happens next.
- Anchor your voice and word choices to product principles so copy stays consistent across every screen, not written fresh and randomly each time.
Open
oreilly.com →
📖 Book
✓ Link checked
Paid
Beginner
Why we picked it
Kate Kiefer Lee shaped Mailchimp's famous voice, and this book teaches you to write clear, human interface and product copy and to adjust tone when a user is stressed or confused. It covers interface flows and building a simple style guide you can actually keep. Good for a founder who wants their whole product to sound like one calm person.
From
nicelysaid.co
by Nicole Fenton and Kate Kiefer Lee
~272 pages
- Clarity beats cleverness, especially in error moments
- Set a light style guide so labels stay consistent as you grow
- Adjust tone to the reader's state, not your brand mood
Open
nicelysaid.co →
📖 Book
✓ Link checked
Paid
Intermediate
Why we picked it
Most error copy is written for the calm, ideal user, and this short book forces you to design for the stressed, distracted, worst-moment user instead (they call these stress cases). It reframes an error not as a scolding but as help when someone is already frustrated. Fast to read and it will change the tone of your failure states.
From
A Book Apart
by Eric Meyer and Sara Wachter-Boettcher
~132 pages
- Write error copy for someone already anxious or in a hurry
- Never blame the user for a system's failure
- Design the worst moments first, not last
Open
abookapart.com →
📄 Article
✓ Link checked
Free
Beginner
Why we picked it
Nielsen Norman Group is the closest thing to a standard reference in usability, and this piece is a clean, specific checklist for turning a scary or vague error into something a user can actually act on. It groups the patterns into visibility, communication, and efficiency, with concrete phrasing rules like describe exactly what went wrong, offer a fix, and never blame the user. It is a good starting point you can hold your own error copy up against, not abstract theory.
From
Nielsen Norman Group
by Tim Neusesser and Evan Sunwall (Nielsen Norman Group)
- Say precisely what went wrong and what to do about it: a bare An error occurred leaves people stuck, so pair the problem with a next step.
- Put the message right next to the field or element that caused it, in plain language, and never phrase it as the user's fault.
- Preserve what the user already typed and anticipate common mistakes so they can correct one thing instead of starting over.
Open
nngroup.com →
📄 Article
✓ Link checked
Free
Beginner
Why we picked it
Sign-up and checkout forms are where founders lose users, and this piece is a focused rulebook for the error text on exactly those screens. It covers where to put the message, when to show it, and how to phrase it so people can recover fast. Concrete enough to apply to your form this afternoon.
From
Nielsen Norman Group
by Rachel Krause (Nielsen Norman Group)
~14 min read
- Show the error next to the field, not in a lump at the top only
- Keep the user's input so they never retype everything
- Phrase the fix, for example 'Use 8 or more characters'
Open
nngroup.com →
📄 Article
✓ Link checked
Free
Beginner
Why we picked it
A button or link label makes a promise, and this article gives you a simple test for whether it will be kept: specific, sincere, substantial, succinct. It is the clearest short piece on why 'Submit' and 'Click here' fail and what to write instead. Directly answers the read-it-out-loud test in our short answer.
From
Nielsen Norman Group
by Kate Moran (Nielsen Norman Group)
~8 min read
- A label should set an expectation the next screen instantly meets
- Be specific about the outcome, not the mechanism
- Two to four concrete words usually beats a vague verb
Open
nngroup.com →
📄 Article
✓ Link checked
Free
Intermediate
Why we picked it
Concrete rules for writing the words on your buttons and menus so nobody has to decode them. It covers using a verb plus a noun (Delete Folder, not just Delete) so a label makes sense on its own. Small change, big drop in second guessing.
From
Nielsen Norman Group
by Anna Kaley
~9 min read
- Add a noun after the verb so a label makes sense out of context.
- Keep command names consistent across the whole product.
- Write for the person's task, not the system's internal wording.
Open
nngroup.com →
📄 Article
✓ Link checked
Free
Beginner
Why we picked it
The UK government writes for millions of people in hard moments, and their public guidance is one of the best free sources on button and error wording. It is refreshingly blunt: describe the action on the button, tell the user how to fix an error, and skip the apologies. Battle-tested advice you can copy directly.
From
GOV.UK Service Manual
by GOV.UK / Government Digital Service
~10 min read
- Label a button with the action it does, for example 'Save and continue'
- Tell the user how to fix the problem, not just what broke
- Keep the same word for the same action across every page
Open
gov.uk →
📄 Article
✓ Link checked
Free
Beginner
Why we picked it
Apple's writing foundation is short, opinionated, and free, and it states the button rule plainly: almost always use a verb, and never explain what a button does if the label is clear. It also covers alert wording so your confirmations do not confuse people. A quick primary source to align a whole team on.
From
Apple Human Interface Guidelines
by Apple
~10 min read
- Label buttons and links with a verb for the action
- If the label is clear, do not add text explaining it
- Write short, complete sentences in plain language
Open
developer.apple.com →
📄 Article
✓ Link checked
Free
Beginner
Why we picked it
Shopify's design system spells out how to phrase actions for merchants running a business, which is close to what many founders are building. It pushes you to lead with a verb and cut every word that does not help someone act. Practical rules from a product used by millions of sellers.
From
Shopify Polaris
by Shopify
~6 min read
- Start action labels with a verb
- Cut words that do not help the user decide or act
- Write like a helpful person, not a formal notice
Open
polaris-react.shopify.com →
📄 Article
✓ Link checked
Free
Beginner
Why we picked it
Google's content design guidance is a free, thorough reference for clear UI writing, including the classic rule of naming the label on a control rather than the type of control. It covers error tone (do not blame, be specific, offer a path) with side-by-side good and bad examples. A solid team reference you can point people to.
From
Material Design 3 (Google)
by Google
~12 min read
- Refer people to the label they see, not 'the button'
- In errors, be specific rather than technical, and offer next steps
- Use short, scannable, second-person copy
Open
m3.material.io →
✍️ Essay
✓ Link checked
Free
Beginner
Why we picked it
Saito was the first UX writer at YouTube and a writer at Dropbox, and this widely read essay shows how a few well-chosen words in buttons, hints, and error text change how a product feels. It is full of concrete before-and-after examples you can mimic. The friendliest possible on-ramp to caring about this.
From
UX Collective (John Saito)
by John Saito
~8 min read
- Small wording changes carry real emotional weight
- Button and error text is where personality shows up honestly
- Read copy in context, on the actual screen, before shipping
Open
uxdesign.cc →
📄 Article
✓ Link checked
Free
Beginner
Why we picked it
If you are a founder or designer writing your own product copy without a UX writer on the team, this is the most practical single article we found, and it is written for exactly that reader. It walks through 15+ tips with real app screenshots covering buttons, empty states, and error messages, and ends with a copy checklist you can run against your own screens. It is honest about the traps too, like why leaning on "Oops" for every error stops feeling friendly and starts feeling lazy.
From
Smashing Magazine
by Irina Silyanova
About a 20 minute read
- Write buttons the way a user would say the action out loud ("I'll reserve" reads more human than a stiff generic "Submit").
- An empty state should hand the user their next move, not just announce that nothing is here yet.
- A good error names what happened, why if you know it, and what to do next, instead of hiding behind a cute one-liner.
Open
smashingmagazine.com →
📄 Article
✓ Link checked
Free
Beginner
Why we picked it
This is the reference everyone quietly copies when they first try to write down their brand voice, and it is public, free, and readable in one sitting. It separates voice (the part that never changes) from tone (the part that shifts by situation), which is exactly the distinction a marketer, an agency, and a freelancer need to share so their work sounds like one company. Treat it as a starting point for structure, not a template to mimic word for word.
From
Mailchimp Content Style Guide
by Mailchimp
- Write down your voice as a short set of named traits (Mailchimp uses plainspoken, genuine, translator, dry humor) so anyone new can point to what they were aiming for
- Voice stays fixed while tone flexes by context, so document both separately instead of hoping people intuit the difference
- Pair each principle with a rule of thumb (active voice, plain English, positive framing) that a reviewer can actually check against
Open
styleguide.mailchimp.com →
📄 Article
India
Free
Beginner
Why we picked it
Written by an India-based UX writer, this piece is a useful reality check on why product copy still gets ignored at many Indian startups and why that is starting to change. It helps you make the internal case for spending time on buttons and errors when the team thinks copy is an afterthought. Read it for the context and the argument, then apply the craft resources above.
From
UX Content Collective
by Sidika Sehgal
~8 min read
- Most early startups skip UX writing, which is a cheap edge to claim
- Clear product copy matters more, not less, across mixed literacy and languages
- Owning the words is a founder-level responsibility early on
Open
uxcontent.com →
