Thesis: Friendly tone is not the same as credible tone. Hedging language (“maybe”, “just a sec…”, “looks like…”) lowers confidence, slows decisions, and hides accountability. Warm + direct beats warm + vague every time.
Why this matters
Users judge competence in seconds. Tone is part of the signal. When copy refuses to commit, people infer the product won’t either. The result:
- Slower task completion (extra reading to decode intent)
- Higher abandonment at decision points (uncertain outcomes)
- Support tickets that ask what happened and what next
Clarity is not cold; it’s a service. It reduces cognitive load and accelerates action.
The Politeness Pattern (and how to fix it)
Symptoms: apologetic banners, chirpy empty states, vague errors, CTA verbs that describe chores.
Replace with: facts, outcomes, and specific next steps.
| Situation | Polite (weak) | Clear (strong) |
|---|---|---|
| Error | “Oops! Something might’ve gone wrong.” | “We couldn’t save your changes. Try again or reload.” |
| Destructive | “Are you sure you want to cancel? You’ll lose some data.” | “Cancel now deletes unsaved edits on this page. Keep editing or cancel anyway.” |
| Empty state | “Looks like nothing’s here yet :)” | “No items yet. Add your first item to continue.” |
| Spinner | “Just a sec…” | “Uploading files. You can navigate away—we’ll keep working.” |
| CTA | “Let’s maybe try saving this now?” | “Save and continue” / “See your cost breakdown” |
Design rule: say what happened, what happens next, and what you want the user to do.
A compact style guide
Voice: warm and direct.
Verbs: will/won’t over might/maybe.
Buttons: outcomes, not chores.
Headings: facts, not vibes.
Error formula (C-I-A-R):
- Cause (what failed)
- Impact (what’s affected)
- Action (what to do now)
- Reassurance (what won’t be lost / what we’ll do)
Example: Payment failed (cause). Your subscription is paused (impact). Update your card to resume (action). Your projects remain safe (reassurance).
Loading states: say the operation and set expectations (progress, time, or backgrounding). Prefer skeletons to jokes.
Empty states: explain purpose and give one action. What this is, why it matters, how to start.
Tooltips: if a tooltip explains a basic control, redesign the control and remove the tooltip.
Quick audit (30 minutes)
- Collect 10 instances of hedging words: maybe, just, a bit, looks like, might, heads up, should, kinda.
- Score each message for: a) fact stated, b) outcome stated, c) single next step offered.
- Rewrite anything that misses two or more.
- Swap CTAs from tasks to outcomes across the top three flows.
- Move proof (stat, benchmark, logo) to decision points.
Ship the first five changes today. Measure for a week.
What to measure
- Task completion rate on key flows
- Time to first value for new users
- Error recovery time (from failure to successful retry)
- Form completion on checkout/onboarding
- Support themes: drop in “confusing/unsure” mentions
Clarity should reduce reading time and retries. If it doesn’t, your issue isn’t tone—it’s flow.
When soft language is appropriate
- Sensitive contexts: health, safety, bereavement—be humane, not evasive.
- True uncertainty: communicate it precisely (“We’ll confirm in 10–15 minutes. We’ll email you either way.”) Uncertainty is not hedging when time bounds and next steps are explicit.
- Brand moments: marketing pages can earn playfulness; core actions cannot.
For larger teams
Tone often degrades in review loops. Protect it with:
- A source-of-truth voice doc with examples for errors, empty states, and CTAs
- Ownership: someone accountable for UX design writing across flows
- Banned list: words/phrases you won’t ship (maybe, just a sec, feel free…)
- PR checklist: C-I-A-R applied to any new error/loading text
Legal can shape claims; it should not own product voice. If the UI handles chargebacks, deletions, or limits, it must speak with precision.
Field notes (before → after)
- “We’re sorry, something’s not quite right.” → “Service unavailable. We’ll retry in 2 minutes or you can refresh now.”
- “Click here to continue when you’re ready :)” → “Continue to billing.”
- “You’re almost there!” (step 3/6) → “Step 3 of 6: Company details.”
- “Let’s go!” on delete → “Delete account.”
Small changes; large perceived competence.
Bottom line
Soft is fine. Vague is not. If your product never states facts or next steps, it isn’t polite—it’s indecisive. Write like an adult who knows what happens next. Say the thing.
Warm + direct. Facts + outcomes. One next step.
Top comments (0)