In 1988, Donald Norman joined Apple and brought with him a title that had not previously existed: User Experience Architect. He coined the term himself, dissatisfied with existing labels like "human interface" or "usability," because he wanted to capture something broader — not just whether a product's interface worked, but the entire quality of a person's experience with a product, from first encounter through regular use and eventual abandonment.
The term stuck, spread, and has since proliferated to the point of occasional meaninglessness. Today "UX" appears on business cards, in job postings, in product roadmaps, and in organizational strategy documents with a range of meanings from precise to vague. A UX designer at one company might spend most of their time conducting user research and synthesizing behavioral insights into design recommendations. A UX designer at another might be primarily creating high-fidelity visual mockups.
Understanding what UX design actually is — what practitioners do, what methods the field uses, what principles underpin it, and where it sits relative to other design disciplines — is useful for anyone building products, working in technology, or considering a career in the field.
What User Experience Design Is
User experience design is the practice of designing products, services, and systems with careful attention to the quality of experience they create for the people who use them. It is concerned with:
- Whether a product is useful: does it address a real need?
- Whether it is usable: can people accomplish their goals with it without excessive difficulty?
- Whether it is findable: can users navigate to what they need?
- Whether it is accessible: can people with disabilities use it effectively?
- Whether it is credible: does it build appropriate trust?
- Whether it is desirable: does the aesthetic and emotional experience encourage engagement?
- Whether it is valuable: does it deliver sufficient value to both users and the organization?
These seven dimensions, from information architect Peter Morville's "User Experience Honeycomb" model (2004), describe the full scope of what UX aspires to address. In practice, different projects prioritize different dimensions, and individual designers specialize in different parts of this scope.
"Design is not just what it looks like and feels like. Design is how it works." -- Steve Jobs
UX vs. UI: The Persistent Confusion
The most common question about UX is how it differs from UI (user interface) design. The distinction is real but blurry in practice.
UI design is primarily concerned with the visual and interactive layer of a product: the appearance of screens, the style of interactive elements (buttons, inputs, menus), typography, color, iconography, animation, and the micro-interactions that give visual feedback to user actions. UI design is visual in nature and closely related to graphic design, though specialized toward digital interfaces.
UX design is concerned with the broader experience: the overall structure and information architecture of a product, the logic of user flows, the research process that reveals what users need, the testing process that reveals where designs succeed and fail, and the strategic decisions about what to build and how to organize it. UX operates at a higher level of abstraction than UI.
The relationship can be summarized: UX design shapes what exists and how it is organized; UI design shapes how those things look and feel.
In small teams and startups, both are often done by the same person — commonly called a product designer. In larger organizations, the roles may be distinct. There are also related specializations: UX researchers who focus exclusively on the research and testing component; interaction designers who focus on the behavioral logic of interfaces; information architects who focus on content organization and navigation systems; service designers who apply UX thinking to end-to-end service experiences beyond the digital product.
| Role | Primary Focus | Key Deliverables |
|---|---|---|
| UX Designer | Experience structure, user flows, research | Wireframes, user flows, research synthesis, prototypes |
| UI Designer | Visual layer, aesthetics, interactions | Visual designs, style guides, animation specs |
| UX Researcher | User understanding, behavior, needs | Research reports, usability findings, persona documents |
| Product Designer | End-to-end: research through visual design | All of the above |
| Information Architect | Content structure, navigation, taxonomy | Site maps, navigation models, content audits |
Don Norman's Principles
Don Norman's 1988 book "The Design of Everyday Things" (originally published as "The Psychology of Everyday Things") is the foundational text of user-centered design. It argues that when design fails — when people cannot figure out how to use a door, a thermostat, or a software interface — the failure is usually the designer's, not the user's.
Norman articulated several principles that have become standard vocabulary in UX:
Affordances and Signifiers
An affordance is a relationship between an object and a person that enables a particular action — a chair affords sitting, a button affords pressing. But affordances are only useful if they are perceived; a button that looks like a decorative graphic is not a functional affordance.
A signifier is the element that communicates the affordance — the visual or physical cue that tells a person what to do. Good design makes affordances visible through clear signifiers: a button that looks pressable, a scrollbar that shows there is more content, a text field with a visible cursor insertion point.
Much poor digital design fails on signifiers: interactive elements that look like static text, navigation labels that do not indicate their function, form fields with no clear indication of expected input.
Feedback
Feedback is the signal that an action has been taken and what its result was. When you press a physical button, it clicks and depresses — feedback confirms the action. When feedback is absent or delayed in digital interfaces, users repeat actions, creating errors. Loading states, confirmation messages, error messages, and visual state changes are all feedback mechanisms.
Conceptual Models
A conceptual model is the mental model a design communicates to its users about how the system works. When a design's conceptual model matches users' mental model — their intuitions about how the system should work — it is easy to use. When they diverge, users make predictable errors.
The file-and-folder metaphor in desktop operating systems is a designed conceptual model. It maps to users' existing mental model of physical files and folders, making the abstract concept of hierarchical file storage immediately understandable. Interfaces that fail to establish coherent conceptual models — that seem to work differently in different contexts without obvious reason — generate confusion even when individual screens are well-designed.
Mapping
Mapping describes the relationship between a control and its effect. Natural mapping — where the spatial relationship between controls mirrors the spatial relationship between effects — is intuitive. Car audio controls placed on the steering wheel at the position corresponding to the speaker locations are naturally mapped. Controls organized arbitrarily require users to memorize relationships rather than intuit them.
The UX Research Process
UX without research is guesswork. The defining discipline of professional UX practice is the systematic investigation of user needs, behaviors, and mental models before, during, and after design.
Discovery Research
Before designing, UX researchers investigate the space: who are the users, what are their goals, what problems do they encounter, what context do they use the product in, and what alternatives do they currently rely on?
Methods include:
- Contextual inquiry: Observing users in their natural environment while they work or complete relevant tasks
- User interviews: Semi-structured conversations to understand goals, workflows, mental models, and pain points
- Surveys: Broader quantitative picture of user demographics, preferences, and reported behavior
- Analytics review: Understanding what users are currently doing in an existing product
Discovery research is about understanding the problem space before defining solutions. Skipping it — assuming you know who the user is and what they need — is one of the most common and costly errors in product development.
Usability Testing
Usability testing involves watching representative users attempt to complete defined tasks with a design — whether a prototype or a live product — and observing where they succeed, where they struggle, and what mental models they apply.
A basic usability test involves:
- Recruiting 5 to 8 participants who represent the target user population
- Defining 3 to 5 tasks that reflect real usage goals
- Asking participants to think aloud while attempting the tasks
- Observing and noting points of confusion, error, and unexpected behavior
- Synthesizing findings into prioritized design recommendations
Research by Jakob Nielsen and others has found that 5 participants uncover approximately 85 percent of usability problems in a given design — a finding often cited to justify lean testing rather than large sample sizes. The principle of diminishing returns applies quickly: the first few testers reveal the most significant problems; additional testers surface diminishing numbers of new findings.
Quantitative Research
Qualitative methods (interviews, observation, usability tests) generate deep understanding of why users behave as they do. Quantitative methods measure how many users behave in particular ways and with what frequency.
- A/B testing: Randomly splitting users between two design variants and measuring behavioral differences (conversion rates, task completion, click-through) to determine which performs better
- Funnel analysis: Tracking the percentage of users who complete each step in a multi-step flow to identify where drop-off occurs
- Heatmaps and session recordings: Visualizing where users click, scroll, and hover to identify areas of confusion or missed affordances
The combination of qualitative and quantitative research is more powerful than either alone. Analytics tells you where users are dropping off; qualitative research tells you why.
Accessibility: Designing for Everyone
Accessibility in UX design means ensuring that products can be used effectively by people with a range of abilities, including visual, auditory, motor, and cognitive disabilities.
The primary international standard is the Web Content Accessibility Guidelines (WCAG), published by the World Wide Web Consortium (W3C). WCAG 2.1 defines three levels of compliance (A, AA, AAA) across four principles: Perceivable, Operable, Understandable, and Robust.
Perceivable: Information must be presentable in ways users can perceive. This means text alternatives for images (alt text), captions for video, and sufficient color contrast between text and background.
Operable: Interface components must be operable by users who cannot use a mouse. This means full keyboard navigation, sufficient time to complete tasks, and no content that could trigger seizures.
Understandable: Information and operation must be understandable. This means readable language, predictable behavior, and helpful error identification and recovery.
Robust: Content must be robust enough to work across a variety of technologies, including assistive technologies like screen readers and voice control software.
Accessibility is legally required in many jurisdictions. In the United States, the Americans with Disabilities Act has been applied to websites and apps through litigation, with courts ruling that digital products constitute "places of public accommodation." Similar requirements exist in the EU through the European Accessibility Act. Beyond legal obligation, accessible design consistently improves the experience for non-disabled users — captions help people in noisy environments, keyboard navigation helps power users, high-contrast text reduces eye strain.
A Day in the Life of a UX Designer
The daily experience of a UX designer varies substantially by organization type, seniority, and phase of project. A rough sketch:
At a startup or small company: UX designers often own the entire design scope — research, wireframing, visual design, and sometimes front-end implementation. They work closely with founders and engineers, and the pace is fast with frequent pivots.
At a large technology company: Roles are more specialized. A UX designer might focus on specific parts of a product, working within established design systems, and collaborating with dedicated researchers, product managers, and engineers on a defined feature area. There is more process, more review, and more documentation.
In an agency or consultancy: Projects are defined-scope engagements with external clients. Work is often faster-paced with tighter deadlines, and the designer must quickly develop enough domain understanding to design effectively without years of exposure to the specific product.
Across contexts, common daily activities include:
- Reviewing and annotating designs in tools like Figma, Sketch, or Adobe XD
- Collaborating in standups or review meetings with product and engineering teams
- Conducting or preparing user research activities
- Iterating on wireframes or prototypes based on feedback
- Reviewing design implementations in the live product or staging environment
- Documenting design rationale and specifications for engineering handoff
The Business Case for UX
Investment in UX generates measurable returns. The Forrester Research consultancy has estimated that every $1 invested in UX returns $100 — a ratio of 9,900 percent ROI. This figure is frequently cited and contested, but the directional finding is consistent across multiple sources: well-designed products convert better, require less customer support, reduce development rework, and generate stronger customer loyalty.
IBM's design thinking practice, developed from the mid-2010s onward, found in internal tracking that projects that applied design thinking delivered products twice as fast with 33 percent lower development costs compared to projects without. McKinsey's 2018 McKinsey Design Index found that companies in the top quartile on design metrics outperformed their industry peers by 32 percentage points in total return to shareholders.
The business case for UX is not merely that it makes products prettier. It is that understanding users before building, testing designs before engineering them, and iterating based on evidence rather than assumption systematically reduces the cost of building the wrong thing.
Getting Into UX Design
UX design has become an accessible career path without a single required educational track. Practitioners enter from backgrounds including visual design, psychology, sociology, anthropology, computer science, library science, and communications.
Portfolio quality is more important than credentials for most hiring decisions. A portfolio demonstrating a complete UX process — problem definition, research, ideation, wireframes, testing, iteration — is more compelling than a degree without evidence of applied work. Many practitioners build initial portfolios through personal projects, redesign exercises, volunteer work for nonprofits, or bootcamp capstone projects.
Core tools to know: Figma (the dominant current industry tool for design and prototyping), basic user research methods, HTML/CSS familiarity (not required but helpful for engineering collaboration), and data analysis basics (for quantitative research).
The field continues to evolve. AI-assisted design tools are changing the production side of the work; the research, synthesis, and strategic judgment components are proving more durable and differentiated.
Frequently Asked Questions
What is UX design?
User experience (UX) design is the practice of designing products and services so they are useful, usable, and enjoyable for the people who use them. It encompasses the entire experience a person has while interacting with a product — from discovering it to using it to resolving problems. The field draws on cognitive psychology, information architecture, visual design, and research methods to understand user needs and translate them into product decisions.
What is the difference between UX design and UI design?
UX design focuses on the overall experience and structure of a product: how it is organized, whether it solves users' problems, whether it is easy to navigate. UI (user interface) design focuses on the visual and interactive details: colors, typography, button styles, animations, and the visual hierarchy of a specific screen. In practice, the two overlap substantially, and many designers do both; in larger organizations, they are often distinct roles.
What does a UX designer actually do day to day?
A UX designer's daily work varies by seniority and company stage, but typically includes: conducting or analyzing user research (interviews, surveys, usability tests), creating wireframes and prototypes, collaborating with product managers and engineers on requirements, testing designs with users and iterating, and contributing to design system standards. Senior UX designers often spend substantial time in stakeholder communication and design strategy rather than hands-on production.
What are Don Norman's design principles?
Don Norman, in 'The Design of Everyday Things,' identified several fundamental design principles: affordances (design elements that signal how they should be used), signifiers (visual cues that guide use), constraints (limitations that prevent misuse), mapping (logical relationship between controls and their effects), feedback (clear indication of actions taken), and conceptual models (the mental model the design communicates to users). These principles have become foundational vocabulary in UX practice.
Why does accessibility matter in UX design?
Accessibility means designing so people with disabilities — visual, auditory, motor, or cognitive — can use the product effectively. Beyond the ethical and legal obligations (the Americans with Disabilities Act and similar laws in other countries apply to digital products), accessible design typically improves the experience for all users: high-contrast text is easier for everyone, clear navigation helps users with cognitive load as well as those with cognitive disabilities, and captions benefit people in noisy environments as well as those with hearing loss.