Microcopy That Removes Doubt
Most interface text answers the wrong question. Write the sentence that unblocks the click.
Wickham is an invoicing tool for tradespeople. On the payment settings screen there is a button that says Connect bank account. Analytics shows people reaching that screen, hovering, and leaving. In five user sessions, four people said a version of the same thing: does this mean you can take money out?
No copywriting exercise about tone would have found that. The button was clear, friendly and short. It just did not answer the question standing between the user and the click.
Writing the sentence that unblocks the click
Find the doubt before you write
Every hesitation in a product is a specific unanswered question. Usually it is one of five: what will happen when I press this, can I undo it, who will see this, how long will it take, and what does this cost me. microcopy: The small interface text: labels, hints, errors, button words. is the practice of answering whichever of those is live at this exact moment, in the smallest number of words, at the point of hesitation rather than in a help article.
The discipline is finding the question, not polishing the sentence. Watch three sessions with the sound on, or read the last twenty support tickets about a screen. The doubt will be stated almost verbatim by somebody.
Copy that describes the control
- Connect bank account
- Save changes
- Upload your logo
- Invite team member
- Choose a plan
Copy that answers the doubt
- Connect bank account (read-only). We can see payments arriving. We can't move money.
- Save. Your clients won't see these changes until you send the next invoice.
- Upload your logo. PNG or JPG, at least 400px wide. It appears top-left on every invoice.
- Invite a team member. They can create and send invoices. Only you can change bank details.
- Choose a plan. You can switch or cancel any time, and we bill the difference pro rata.
Two things to notice. The right column is longer, and length is not the enemy. Steve Krug's point about mindless choices is about ambiguity, and a sentence that removes ambiguity is cheaper than a click that has to be undone. The other thing: every sentence on the right is falsifiable. A colleague could read it and tell you it is wrong. Copy nobody can disagree with is usually copy that says nothing.
A three-line test for any microcopy
- Is it true
- Check the behaviour, not the ticket. If the invite really does let a team member change bank details, the copy above is a lie and you have made things worse.
- Is it the live question
- The right sentence in the wrong place is noise. Reassurance about cancellation belongs on the plan screen, not in the welcome email.
- Would you say it out loud
- Read it to someone. If you would not say Please ensure all requisite fields are populated to a plumber standing in front of you, do not ship it.
Worked example
One line, 40 percent of a problem
Wickham changes the button label to Connect bank account and adds one line beneath it: Read-only access. We can see when invoices get paid. We can never move money out. They change nothing else. Connection rate on that screen goes from 22 percent to 38 percent over three weeks. The engineering cost is one string.
Three habits worth stealing
- Label buttons with the outcome, not the mechanism. Send invoice beats Submit, because Submit describes what the form does and Send invoice describes what the user gets.
- Put the caveat next to the control, not in a tooltip. If a user has to hover to learn something important, they will find out by getting it wrong.
- Name the thing the user named. If tradespeople say job and your product says project, you are adding a translation step to every sentence.
A last note on voice. Teams often try to fix doubt with warmth: exclamation marks, a friendly aside, a reassuring adjective. It does not work, because warmth is not information. A person worried about their bank account is not soothed by Don't worry! They are soothed by read-only. Pick the fact that dissolves the worry and put it where the worry happens.
Quick check
Why did adding a longer label to Wickham's bank button improve conversion?
The takeaway
Microcopy is answering the specific question a user is silently asking at that control, in words they would use.
Try this tomorrow
Sit with three session recordings or twenty support tickets for one screen, write down the question people keep asking, and ship one sentence that answers it next to the control.
Answer the check above, then bank the day.
Where this comes from
- Don't Make Me Think, Steve Krug
- 10 Usability Heuristics for User Interface Design, Jakob Nielsen, NN Group
- The Design of Everyday Things, Don Norman
Craft is one of six tracks. These lessons summarise and build on the work above, they do not reproduce it. Buy the books, they are better.