What is User Experience (UX)? Definition, Pillars, Examples
User Experience (UX) is the holistic experience a person has interacting with a product — usability, accessibility, performance, design, content, emotion.
What is User Experience (UX)?
User Experience (UX) is the totality of how a person feels and what they accomplish when interacting with a product, system, or service. It spans far more than visual design: UX includes usability (can users complete tasks?), accessibility (can everyone use it?), performance (does it feel fast?), information architecture (can users find things?), content quality, emotional response, and even pre/post-interaction context.
The term was coined by Don Norman at Apple in the early 1990s. UX is now a discipline with its own job titles (UX designer, UX researcher, UX writer), methodologies (user research, usability testing, journey mapping), and metrics (task success rate, time on task, NPS, SUS).
UX vs UI: not the same
| UX (User Experience) | UI (User Interface) |
|---|---|
| Holistic experience | Visual surface |
| Includes performance, accessibility, content | Buttons, colors, typography |
| How it works + feels | How it looks |
| Research, testing, journey mapping | Mockups, prototypes, design systems |
UI is part of UX, not the other way around. A beautiful UI on a slow, confusing app = poor UX.
The 7 pillars of UX (Peter Morville's honeycomb)
| Pillar | Question |
|---|---|
| Useful | Does it solve a real problem? |
| Usable | Can users accomplish tasks easily? |
| Findable | Can users locate what they need? |
| Credible | Do users trust it? |
| Desirable | Is it appealing emotionally? |
| Accessible | Can people with disabilities use it? |
| Valuable | Does it deliver business + user value? |
How performance affects UX
Performance is foundational to UX — slow apps are bad apps regardless of how pretty they look. Google's research:
- Page load > 3s = 53% mobile users bounce
- 1s delay = 7% conversion drop
- Slow LCP correlates with cart abandonment, lower NPS, churn
Core Web Vitals (LCP, INP, CLS) directly measure user-perceived performance.
Common UX research methods
| Method | What it tells you |
|---|---|
| Usability testing | Where users get stuck on tasks |
| User interviews | Goals, motivations, pain points |
| Surveys (NPS, SUS) | Satisfaction at scale |
| Analytics (funnels) | Where users drop off |
| Session recordings (Hotjar, FullStory) | Real user behavior patterns |
| A/B testing | Quantitative impact of changes |
| Card sorting | How users mentally group content |
| Heuristic evaluation | Expert review against principles |
UX best practices
- Test with real users. 5 users uncover ~80% of usability issues (Nielsen).
- Design for accessibility from day one. Retrofitting is expensive.
- Performance is UX. Optimize Core Web Vitals.
- Reduce cognitive load. Minimize choices, defaults that work.
- Consistency over cleverness. Familiar patterns beat novel ones.
- Mobile-first. Most traffic is mobile; constraints force focus.
- Error messages should help. "Email format invalid" beats "Invalid input."
- Progressive disclosure. Show advanced options on demand, not upfront.
- Measure outcomes, not outputs. Task success rate matters more than feature count.
Common UX pitfalls
- Designing for yourself. "I think it's intuitive" ≠ user-tested.
- Ignoring performance. Slow = unusable, regardless of design.
- Skipping accessibility. 15-20% of users have a disability; legal exposure too.
- Pop-ups and interruptions. Hurt task completion and trust.
- Inconsistent patterns. Same action behaves differently across pages.
- Walls of text. Users scan; structure with headings, lists, bold.
- Hidden navigation. Hamburger menus on desktop hurt discoverability.
- Vanity metrics. Pageviews don't measure satisfaction.
Tools for UX work
| Tool | Purpose |
|---|---|
| Figma / Sketch | Design + prototyping |
| Maze / UserTesting | Remote usability testing |
| Hotjar / FullStory | Session recording, heatmaps |
| Lighthouse / PageSpeed | Performance audits |
| Axe / WAVE | Accessibility audits |
| Optimal Workshop | Card sorting, tree testing |
| Notion / Dovetail | Research repository |
FAQ: User Experience
Is UX the same as UI?
No. UI is the visual surface. UX is the entire experience including performance, accessibility, content, emotion.
How do I measure UX?
Task success rate, time on task, NPS, SUS, error rate, Core Web Vitals, retention, churn. Combine quantitative + qualitative.
What's the most important UX principle?
"Don't make me think" (Steve Krug). Reduce cognitive load; make the obvious thing the right thing.
How does performance affect UX?
Critically. Slow apps drive bounces, cart abandonment, churn. Optimize Core Web Vitals (LCP, INP, CLS).
Do I need a UX designer?
For any app users actually use, yes. Smaller teams: cross-trained PMs/devs do basic UX. Mature teams have dedicated UX.
What's the difference between UX research and usability testing?
UX research = the broader discipline (interviews, surveys, analysis). Usability testing = one method (watching users complete tasks).
Is accessibility part of UX?
Yes — and increasingly mandated by law (ADA in US, EAA in EU). Accessible design is good design for everyone.
Measure UX-affecting performance with LoadFocus
LoadFocus runs Lighthouse audits + load tests from 25+ regions, surfacing the performance issues that hurt real-user experience. Sign up free at loadfocus.com/signup.
Related LoadFocus Tools
Put this concept into practice with LoadFocus — the same platform that powers everything you just read about.