Examples

Real-world UX writing improvements with before/after analysis and scoring

These real transformations show UX text scored against the four quality standards: Purposeful, Concise, Conversational, and Clear.

Scoring guide

9-10: Excellent — Best practice example
7-8: Good — Minor improvements possible
5-6: Adequate — Notable issues to address
3-4: Needs work — Significant problems
0-2: Poor — Major revision required

---

E-commerce checkout error

Before

“An error has occurred while processing your payment. Please try again later or contact customer support if the problem persists.”

Analysis

Purposeful · score · default: "2/10"

Doesn’t help user recover or understand next steps

Concise · score · default: "4/10"

18 words, vague timeframe (“later”)

Conversational · score · default: "4/10"

Robotic system-speak (“an error has occurred”)

Clear · score · default: "2/10"

What error? When is “later”? Why did it fail?

Overall: 3/10 — Poor user experience

After

“We couldn’t process your payment. Check your card details and try again.”

Analysis

Purposeful · score · default: "9/10"

Provides specific next action

Concise · score · default: "9/10"

11 words, direct instruction

Conversational · score · default: "9/10"

Natural language (“we couldn’t”)

Clear · score · default: "9/10"

Specific problem and solution

Overall: 9/10 — Excellent

Why it works: Users know exactly what failed (payment), likely cause (card details), and what to do (check and retry).

---

SaaS dashboard empty state

Before

“No data available.”

Analysis

Purposeful · score · default: "2/10"

Doesn’t explain why or guide next steps

Concise · score · default: "10/10"

Very brief, but too brief

Conversational · score · default: "5/10"

Cold and unhelpful

Clear · score · default: "3/10"

Technically accurate but not helpful

Overall: 4/10 — Needs significant work

After

“No data yet. Connect your account to see insights.”

Analysis

Purposeful · score · default: "9/10"

Explains state and provides clear CTA

Concise · score · default: "9/10"

9 words, includes action

Conversational · score · default: "8/10"

Friendly “yet” implies this is temporary

Clear · score · default: "9/10"

Tells you exactly what to do

Overall: 9/10 — Excellent

Why it works: “Yet” creates expectation of future value, CTA is specific and actionable.

---

Mobile app permission request

Before

“‘AppName’ Would Like to Access Your Location”
[Allow] [Don’t Allow]

Analysis

Purposeful · score · default: "4/10"

Doesn’t explain benefit to user

Concise · score · default: "7/10"

Adequate length but no context

Conversational · score · default: "6/10"

Standard iOS pattern, not particularly engaging

Clear · score · default: "5/10"

Action is clear but reason isn’t

Overall: 5/10 — Adequate but could be better

After

“Enable location to find coffee shops near you”
[Allow] [Not now]

Analysis

Purposeful · score · default: "9/10"

Clear user benefit (find shops)

Concise · score · default: "8/10"

7 words with value proposition

Conversational · score · default: "9/10"

Direct, benefit-focused

Clear · score · default: "9/10"

Exact benefit stated upfront

Overall: 9/10 — Excellent

Why it works: Leads with user benefit, not system need. “Not now” is less final than “Don’t Allow.”

---

Account deletion confirmation

Before

“Are you sure you want to delete your account? This action cannot be undone. All your data will be permanently deleted.”

Analysis

Purposeful · score · default: "6/10"

Warns of consequences but feels heavy-handed

Concise · score · default: "5/10"

19 words, some redundancy (“permanently deleted”)

Conversational · score · default: "5/10"

Somewhat robotic multiple sentences

Clear · score · default: "7/10"

Consequences are clear

Overall: 6/10 — Adequate but could be improved

After

“Delete your account? You’ll lose all your data and this can’t be undone.”

Analysis

Purposeful · score · default: "8/10"

Clear warning without being preachy

Concise · score · default: "9/10"

13 words, no redundancy

Conversational · score · default: "9/10"

Natural phrasing, contraction

Clear · score · default: "9/10"

Consequences clearly stated

Overall: 9/10 — Excellent

Why it works: Question format engages user, contractions feel human, consequences clear without repetition.

---

Password requirements

Before

“Password must contain at least 8 characters including uppercase letters, lowercase letters, numbers and special characters.”

Analysis

Purposeful · score · default: "7/10"

Provides requirements but hard to scan

Concise · score · default: "4/10"

17 words in one dense sentence

Conversational · score · default: "5/10"

List reads like technical documentation

Clear · score · default: "6/10"

Complete info but overwhelming format

Overall: 5/10 — Adequate but not optimal

After

“Create a strong password (8+ characters)
Use a mix of letters, numbers, and symbols”

Analysis

Purposeful · score · default: "8/10"

Explains why (strong) and what

Concise · score · default: "9/10"

14 words, broken into scannable lines

Conversational · score · default: "9/10"

“Create” vs “must contain”

Clear · score · default: "9/10"

Easy to scan and understand

Overall: 9/10 — Excellent

Why it works: Two short lines easier to scan, “strong password” explains purpose, active voice.

---

Newsletter unsubscribe confirmation

Before

“You have been successfully unsubscribed from our mailing list. You will no longer receive emails from us. Thank you for your participation.”

Analysis

Purposeful · score · default: "4/10"

Overly formal for someone leaving

Concise · score · default: "3/10"

23 words, lots of redundancy

Conversational · score · default: "3/10"

Corporate, stiff

Clear · score · default: "7/10"

Message is clear but verbose

Overall: 4/10 — Needs work

After

“You’re unsubscribed. You can resubscribe anytime in your settings.”

Analysis

Purposeful · score · default: "9/10"

Confirms action, offers easy reversal

Concise · score · default: "10/10"

9 words, direct

Conversational · score · default: "10/10"

Casual, respectful

Clear · score · default: "9/10"

Simple and actionable

Overall: 9/10 — Excellent

Why it works: Respects user’s decision, provides exit ramp without guilt, uses contraction.

---

File upload progress

Before

“File uploading… Please wait.”

Analysis

Purposeful · score · default: "5/10"

Shows status but no time estimate

Concise · score · default: "8/10"

Very brief

Conversational · score · default: "5/10"

Somewhat robotic

Clear · score · default: "6/10"

Basic info only

Overall: 6/10 — Adequate

After

“Uploading report.pdf… Almost done”

Analysis

Purposeful · score · default: "8/10"

Shows filename and reassuring progress

Concise · score · default: "8/10"

4 words plus filename

Conversational · score · default: "9/10"

Encouraging “almost done”

Clear · score · default: "9/10"

Specific file being uploaded

Overall: 8/10 — Good

Why it works: Filename confirms right file is uploading, “almost done” reduces anxiety.

---

Common patterns across these improvements

Lead with specifics

“We couldn’t process your payment” vs “An error occurred”

Show user benefit first

“Find coffee shops” before “access location”

Use contractions

“You’re” feels human, “You are” feels robotic

Break dense text

Two short lines beat one long sentence

Remove redundancy

“Permanently deleted” → “can’t be undone”

Use active voice

“Create a password” vs “Password must contain”

Provide recovery paths

Always tell users what to do next

Respect user decisions

Don’t guilt-trip people who opt out

---

Quick self-audit questions

Use these to improve any UX text:

Can I remove any words without losing meaning?

Every word should have a job. Cut filler words like “basically,” “actually,” “just.”

Does this explain what the user needs to know right now?

Focus on immediate, actionable information. Save details for help docs.

Would I actually say this out loud to a friend?

If it sounds robotic or corporate when spoken, rewrite it.

Is there a specific verb I could use instead of a generic one?

“Delete” is clearer than “remove” for permanent actions. “Save” is clearer than “OK.”

Am I showing value before asking for something?

Lead with user benefit: “Find nearby stores” before “Allow location access.”