What is User Experience Design?

User experience covers what a person notices, feels, and does across an entire interaction with a product. That includes the parts nobody thinks of as design work.

It’s a research discipline as much as a design one. People doing it work on software, physical objects, and services, and they lean on structured models like the UX honeycomb and standardized scores like the System Usability Scale to keep the work from turning into opinion trading.

Jakob Nielsen published research in March 2000 showing that watching just five people use a product surfaces roughly 85% of its usability problems, a finding that still shapes how UX teams size their studies today (Nielsen, Nielsen Norman Group).

What Is User Experience?

The cleanest definition comes from a standards body rather than a design blog. ISO 9241-210:2019, officially titled Ergonomics of human-system interaction, Part 210: Human-centred design for interactive systems, describes it as a person’s perceptions and responses resulting from the use or anticipated use of a product, system, or service (International Organization for Standardization, 2019).

That “anticipated use” clause matters more than people realize.

Experience starts before anyone touches an interface, in the moment someone forms an expectation about what the thing will be like. It keeps running after the task ends, while they work out whether the expectation held up.

A few things it isn’t:

• It isn’t a screen. Packaging, support calls, onboarding emails, the return policy, all of it counts.
• Whole teams shape it. One designer with the title doesn’t own the outcome, no matter what the org chart implies.
• Pretty is not the job. Visual polish is one input, and rarely the one that decides whether people come back.

Apple’s original iPod is a decent reference point. The scroll wheel wasn’t designed around looks first, it was built around how someone would operate a device one-handed, in a pocket, without looking at it.

What Are the Core Elements of User Experience?

Ask a practitioner to break “the experience” into parts and you’ll get one of two answers, depending on which book they read first. Both try to pin down what exactly is being designed when a team says it’s designing an experience.

The Five Planes of User Experience

Jesse James Garrett stacked five layers in his book The Elements of User Experience, running from abstract business intent up to the pixels people look at.

• Strategy holds what the business wants alongside what the user needs
• Scope is the features and content that satisfy both
• Structure sets how those pieces relate, usually mapped as information architecture
• Skeleton puts buttons, forms, and navigation in specific places, tracing the user flow step by step
• Surface is the visual layer. Color, type, the parts people screenshot.

The skeleton plane is usually where a wireframe gets built, long before anyone touches color.

The surface plane is where user interface decisions live. It’s also the layer most people mistake for the whole discipline.

Slack’s early onboarding gets cited here often. The skeleton pointed new users toward sending a first message before the surface layer bothered explaining every sidebar feature.

The UX Honeycomb Model

Peter Morville went a different direction, arranging seven facets in a honeycomb shape that a product has to hit all at once.

Useful, usable, desirable, findable, accessible, credible, valuable.

Drop one and the whole thing wobbles. A product can be usable without being desirable, which describes most internal expense tools. It can also be desirable without being findable, which describes a great feature buried three menus deep.

Morville built the model partly to stop teams from using usability and user experience as if they meant the same thing, which is the confusion the next section untangles.

How Does User Experience Differ From Usability, UI, and Customer Experience?

User experience is the umbrella term. Usability, user interface, and customer experience each sit underneath it, covering a narrower slice.

User Experience vs Usability

ISO 9241-11 defines usability as the extent to which a product lets users achieve goals with effectiveness, efficiency, and satisfaction.

So usability wants to know whether someone can finish the task and how much friction they hit getting there. User experience wants to know how it felt afterward, and whether they’d come back.

Jeff Sauro’s analysis of more than 5,000 usability scores across 500-plus studies put the average System Usability Scale result at 68 out of 100. That number is useful precisely because it only measures the usability slice, not the full experience (MeasuringU).

A product can score well on usability and still lose people. A banking app can let someone complete a transfer in four taps and leave them anxious the entire time.

User Experience vs User Interface

User interface is the layer people actually touch. Buttons, menus, colors, motion.

It sits inside user experience the way a single room sits inside a house. The interface question is whether it looks right and responds correctly. The experience question is whether the whole interaction, including everything around it, felt worth repeating.

Craigslist is the classic counter-example. The interface still looks like 2004, yet daily traffic stays enormous because posting and finding listings works without friction.

User Experience vs Customer Experience

Customer experience runs wider. It picks up the sales call before anyone signs up, the invoice and billing process, and the support chat at 11pm when something breaks.

• The sales call before anyone signs up
• The invoice and the billing process
• The support chat when something breaks

User experience feeds into customer experience without covering all of it. A checkout flow can be flawless while a shipping delay wrecks the relationship anyway, which is why teams that only optimize product screens eventually hit a ceiling they can’t design their way past.

Where Did User Experience Design Originate?

Don Norman joined Apple in 1993 as an Apple Fellow, working on a small team called the User Experience Office. His title there, User Experience Architect, was the first recorded instance of the phrase appearing in a job title.

He wasn’t new to any of this by then. Norman had already spent over a decade researching how people misread machine interfaces, including a look at the control room design failures behind the Three Mile Island nuclear incident.

Five years before Apple, he published The Design of Everyday Things (1988), the book most practitioners still point to as the field’s founding text.

Norman later explained his reasoning for the term. “Usability” felt too narrow to him, and he wanted something that covered industrial design, graphics, the interface, and the physical experience of the product all at once.

Before any of that, he’d been pushing user-centered design as an academic idea, studying how people build mental models of unfamiliar objects.

He co-founded the Nielsen Norman Group with Jakob Nielsen in 1998, after Steve Jobs returned to Apple and dissolved the Advanced Technology Group Norman had been running.

What Principles and Psychology Shape User Experience?

Good interfaces aren’t guesswork. They lean on decades of research into how people move, choose, and scan a screen.

Fitts’s Law and Target Size

Psychologist Paul Fitts showed in 1954 that the time it takes to reach a target depends on how far away it is and how big it is.

Move a button farther away, or shrink it, and reaction time climbs.

Designers use this constantly. Primary buttons sit large and close to the thumb on mobile layouts, while destructive actions like “delete account” get pushed farther out and made smaller on purpose.

Amazon’s “Buy Now” button placement gets cited as the real-world case, sized and positioned so the highest-intent action needs the least effort to reach.

Hick’s Law and Decision Time

William Edmund Hick and Ray Hyman found in 1952 that decision time rises with the number and complexity of the choices on offer.

More options doesn’t mean more satisfaction. Usually it means hesitation, added cognitive load, and past a certain point, people just leave.

• Restaurant menus with fewer items often move faster at the counter
• Pricing pages with three tiers convert better than pages with eight
• Navigation menus holding five or six top-level items outperform ones with fifteen
• Filter panels with everything expanded get used less than ones that start collapsed

The usual fix is progressive disclosure. Show the core choices, let people opt into complexity when they want it.

Gestalt Principles and Reading Patterns

Gestalt psychology explains why people group related elements automatically, based on proximity, similarity, and alignment.

Proximity beats explanation, every time.

Put a label close to its input field and users read them as one unit. Space them apart and that pairing breaks, even though nothing else on the page changed.

The same research explains a pattern eye-tracking studies keep finding on text-heavy pages. People fall into an F-pattern reading habit, scanning left to right along the top, then trailing down the left edge as attention fades.

Strong visual hierarchy works with that habit rather than against it, putting the important information where the eye already lands.

What Standards Govern User Experience Design?

Once the work touches anything public-facing or regulated, the same standards bodies keep coming up.

ISO 9241-210 governs the human-centered design process itself, covering research, iteration, and evaluation across a product’s lifecycle. WCAG, maintained by the World Wide Web Consortium, governs whether the result is usable by people with disabilities.

The current version, WCAG 2.2, published in October 2023, defines 86 testable success criteria across four principles: perceivable, operable, understandable, and robust (W3C, 2023).

Meeting Level AA, the benchmark referenced by most accessibility laws including the ADA and the European Accessibility Act, means satisfying 55 of those 86 criteria.

In practice, that shows up as:

• Contrast ratios between text and background colors
• Keyboard-only navigation, with no mouse required for any function
• Text alternatives for non-text content, including images and icons
• Consistent navigation patterns across every page of a site

Most of those contrast rules fall under color contrast guidelines, and they’re usually the fastest thing to fix on an accessibility audit.

GOV.UK, the UK government’s digital service, is one of the more visible examples of a large site rebuilt around web accessibility requirements instead of bolting them on at the end.

Skipping this layer doesn’t only risk a lawsuit. It quietly narrows who can use the product at all, which contradicts everything user-centered design claims to stand for.

What Is the User Experience Design Process?

The process runs in five stages on paper. In practice teams loop back constantly instead of moving in a straight line.

1. User research. Interviews, contextual inquiry, and persona-building establish what users actually need, not what the team assumes they need
2. Design and wireframing. Structure and flow get mapped out, usually starting with rough sketches before anyone thinks about visual polish
3. Prototyping. A clickable mockup replaces static screens so the flow can be tested for real
4. Usability testing. Real people attempt real tasks while researchers watch for confusion, hesitation, and errors
5. Iteration. Findings get folded back into the design, and the cycle repeats

That last stage is the one teams cut under deadline pressure. It’s also usually the one that mattered most.

The five-stage arc borrows heavily from the broader design thinking process popularized by IDEO and Stanford’s d.school.

Google Ventures compressed the whole cycle into the five-day design sprint, squeezing research, prototyping, and testing into a single work week instead of months.

Iteration isn’t a failure signal. It’s the feedback loop separating a product that shipped on time from one that works.

Jumping straight from research to a finished interface, with no wireframe or prototype in between, is the shortcut that causes expensive rework later.

How Is User Experience Measured?

Turning “the experience felt good” into an actual number usually means reaching for one of these.

Net Promoter Score asks one question. How likely are you to recommend this to a friend or colleague, scored 0 to 10.

Fred Reichheld introduced it in a December 2003 Harvard Business Review article, “The One Number You Need to Grow,” arguing that one clean question beat most multi-page satisfaction surveys.

Enterprise Rent-A-Car was among the companies Reichheld pointed to early on, tying branch-level promoter scores directly to which locations grew fastest.

Google’s HEART framework takes a wider view, tracking happiness, engagement, adoption, retention, and task success at once rather than collapsing everything into a single score.

Researchers Kerry Rodden, Hilary Hutchinson, and Xin Fu published it at the ACM CHI conference in 2010, aiming to give product teams a small set of user-centered metrics instead of raw clickstream data.

None of it works without watching real people struggle first.

Nielsen Norman Group’s research, based on modeling by Jakob Nielsen and Tom Landauer, found that testing with just five users surfaces roughly 85% of a product’s usability problems. Add a sixth or seventh participant and returns drop fast, since most of what they hit already surfaced with the first five.

Numbers on their own can mislead, too. A rising score paired with a shrinking user base usually means the people who disliked the product already left, and the survey only reaches whoever stayed.

Which Tools Support User Experience Design Work?

The tool market narrowed hard over the past several years.

The 2024 Design Tools Survey by UX Tools, based on responses from 2,220 design professionals, found a 46-to-1 ratio of Figma users to Sketch users, calling it the most complete tool consolidation the industry has seen (UX Tools, 2024).

Figma

Real-time multiplayer editing is the reason it won. It runs in any browser, and one file carries a project from first sketch through developer handoff.

The downsides are real though. Heavy files crawl on very large design systems, and offline work is limited enough that a flight without wifi means finding something else to do.

Duolingo gets cited as a team that moved its entire design workflow into Figma once multiplayer editing shipped.

Sketch and Adobe XD

Adobe announced Adobe XD’s sunset in 2023, with full retirement in 2024. Even so, 1.4% of designers surveyed in 2024 still reported using it day to day, mostly finishing out legacy projects (UX Tools, 2024).

Sketch stays macOS-only, and that’s the single biggest reason teams give for leaving once a project needs cross-platform collaboration.

Its plugin ecosystem is still mature and it’s fast for solo vector work. But there’s no native Windows or Linux support, and real-time collaboration lags well behind Figma.

InVision and Axure

Both sit further down the funnel, past wireframing and into detailed interaction work.

InVision makes simple click-through prototypes and shareable stakeholder review links, which was a genuinely big deal for a while. It lost ground once Figma added native prototyping, so fewer teams treat it as a primary tool now.

Axure handles conditional logic and complex data-driven flows that most other tools can’t touch. The learning curve is steep and it’s overkill for a simple marketing site.

Why Does User Experience Design Matter for Business Outcomes?

Poor experience costs revenue, not just goodwill.

PwC’s global customer experience survey found that 32% of customers will stop doing business with a brand they otherwise love after just one bad experience (PwC).

Checkout is where this gets ugly fastest.

Baymard Institute has tracked global cart abandonment for over a decade across a meta-analysis of 49 independent studies, putting the current average at 70.19% (Baymard Institute).

Not all of that is fixable. Plenty of shoppers are browsing or price-comparing and were never going to buy.

But Baymard’s own checkout usability testing across large US and EU retailers, including Walmart and Wayfair, found that the average large ecommerce site can lift conversion by 35.26% through checkout redesign alone (Baymard Institute).

Worth keeping in your head:

• 32% of customers leave a brand after one bad experience (PwC)
• 70.19% average cart abandonment rate across ecommerce (Baymard Institute)
• 35.26% average conversion lift available through checkout redesign alone (Baymard Institute)

Most of that lift comes from boring fixes. Fewer form fields, a clearer call-to-action, and showing shipping costs before the final screen instead of springing them at the end.

Same logic carries over to landing page design, where stripping out anything competing with the primary action tends to move conversion further than a full visual overhaul.

When Does User Experience Design Not Apply?

Not every system needs a research process built around it.

A backend service moving files between two servers overnight has nobody watching a screen while it runs. There’s no experience to design in the traditional sense.

Same goes for a pure API endpoint called only by other machines. No interface, no perception, nothing for ISO 9241-210’s definition to attach to.

Formal UX work adds little in a handful of other places too:

• Machine-to-machine systems with no human operator in the loop
• Short-lived internal tools built for a handful of people who already know the system cold
• Regulatory or legal requirements that override design preference entirely, regardless of what testing shows
• Early-stage decisions where no usable research exists yet, and guessing would be worse than waiting

That last one trips up a lot of teams. Running a full research cycle on a feature that might get cut next quarter burns budget nobody gets back.

Internal tools are the everyday example. A company’s deployment dashboard, used by a dozen engineers who already understand every button, rarely justifies the same research spend as a consumer product.

What Commonly Goes Wrong in User Experience Design?

Most failures trace back to skipped steps, not bad taste.

Skipping research is the big one. Teams under deadline pressure jump from a stakeholder meeting straight to high-fidelity screens, skipping the interviews that would have caught a wrong assumption while it was still cheap.

Healthcare.gov’s troubled 2013 launch is still the textbook case, where a site built without adequate user testing collapsed under real traffic and confusing flows on day one.

Testing only with people inside the building is the second failure mode. Employees already understand the product’s internal logic, so they walk past the confusion a first-time visitor hits in the first ten seconds.

Treating research as a one-time checkbox does slower damage. A product tested once before launch and never again drifts out of sync with how people actually use it a year later.

Then there’s the polished surface hiding broken navigation. A site can look sharp and still bury the thing people came for three menus deep, because visual polish and structural clarity get solved by completely different work.

Warning signs worth watching for:

• Opinion over data. Design decisions justified by gut feeling instead of observed behavior
• Late testing. Usability sessions scheduled only after the interface is already built
• Echo chamber reviews. The same handful of colleagues reviewing every round of feedback
• Directionless redesigns. A navigation structure that changes every cycle without anyone asking why

None of these need more budget to fix. They need research moved earlier in the sequence instead of squeezed in at the end.

FAQ on What Is User Experience

Is formal user experience design worth it for a small or short-lived project?

Depends on lifespan and audience size. A landing page running two weeks doesn’t need a full research cycle. A tool meant to last years, or reach thousands of users, earns that investment fast through fewer support tickets and higher retention.

What does a user experience designer actually do day to day?

Interviews, wireframes, and meetings fill most days. A typical week mixes user interviews, sketching flows, building prototypes in Figma, running usability tests, and defending decisions to stakeholders who want the button moved for reasons unrelated to research.

What skills does someone need to work in user experience design?

Interviewing, wireframing, and visual design skills matter, but curiosity about why people struggle matters more. Strong UX designers read research clearly, sketch fast, take feedback without ego, and translate findings into structure a development team can actually build.

Can user experience design be self-taught, or does it require certification?

No license or certification is legally required. Many practitioners are self-taught through bootcamps, portfolio work, and mentorship. Formal credentials from programs like Nielsen Norman Group’s UX Certification help with hiring screens, but a strong portfolio still carries more weight.

What Should You Fix First?

User experience improves fastest when a team closes research gaps before touching visual design. Accurate research about what people need prevents an expensive, polished interface from getting built around the wrong problem.

The order that tends to work:

• Research gaps first, before any screen gets built
• Structure and navigation second, once real needs are confirmed
• Visual polish last, after the flow already works

Fixing research first slows visible progress. Stakeholders see fewer screens early on, and that delay tests patience even when it’s preventing costlier rebuilds later.

From here, UX design covers the craft side in more depth, including wireframing conventions and the portfolio expectations recruiters actually screen for.