Dictionary Wiki
Good UX work depends on shared language. When a designer says “prototype,” “mental model,” or “task success rate,” the team needs to understand exactly what is being discussed and why it matters. User experience design covers the full relationship between people and a product: how they discover it, learn it, move through it, recover from mistakes, and decide whether it is useful enough to keep using. This guide explains the core UX design vocabulary used by designers, researchers, developers, product managers, and other stakeholders who build digital products around real human needs.
Contents at a Glance
- 1. Core Ideas Behind UX Design
- 2. Common UX Research Techniques
- 3. Organizing Information Clearly
- 4. Designing Product Interactions
- 5. UI and Visual Design Language
- 6. Wireframes, Mockups, and Prototypes
- 7. Testing Ease of Use
- 8. Measuring the User Experience
- 9. Human Behavior in Design
- 10. Using UX Terms Professionally
1. Core Ideas Behind UX Design
These basic UX concepts explain what the practice includes and where it sits in product work. They define the purpose of UX, the people it serves, and the methods teams use to shape better experiences.
User experience (UX) — The complete experience someone has with a product, system, or service, including ease of use, accessibility, emotional response, usefulness, and the value the person believes they received.
User interface (UI) — The visible and interactive parts of a digital product that people use directly, such as screens, pages, icons, buttons, forms, menus, and other points of contact.
Human-centered design (HCD) — A design approach that keeps end users’ needs, habits, abilities, and constraints at the center of decisions throughout design and development.
Design thinking — A problem-solving process built around empathy, defining the problem, generating ideas, prototyping possible answers, and testing them with users.
User-centered design (UCD) — An iterative process in which user needs guide each stage of design, with research, testing, and validation used to keep decisions grounded in real behavior.
These terms form the working base for UX conversations. Knowing the difference between UX and UI, for example, helps teams avoid confusion when discussing strategy, interface details, and the overall quality of a product experience.
2. Common UX Research Techniques
UX research gives teams evidence instead of guesses. It helps reveal what users need, what they do, what frustrates them, and how they think about a product or task. Methods can be exploratory, observational, evaluative, or experimental.
User persona — A research-informed fictional profile that represents a target user group, including details such as goals, motivations, demographics, behaviors, and frustrations so design choices stay connected to user needs.
User journey map — A visual outline of the stages a user passes through while using a product or service, showing actions, thoughts, emotions, obstacles, and opportunities along the way.
Contextual inquiry — A research method where a researcher observes and interviews people in their usual setting as they complete real tasks, making it easier to see how environment and context affect behavior.
Card sorting — A technique in which participants group content, topics, or features into categories that feel logical to them, helping teams design clearer navigation and content structures.
Affinity mapping — A collaborative way to sort research notes, observations, quotes, or ideas into related groups so patterns and themes become easier to identify.
Research terminology is especially useful when explaining why a design recommendation is based on evidence. A UX professional who can name the right method and describe its purpose is better equipped to plan studies and present findings to stakeholders.
3. Organizing Information Clearly
Information architecture, often shortened to IA, is about structuring content so people can find what they need and understand where they are. It is not always visible on the surface, but it strongly affects whether a product feels simple or confusing.
Information architecture (IA) — The practice of arranging, structuring, and labeling content so users can locate information, understand relationships, and complete tasks without unnecessary effort.
Navigation — The set of menus, links, breadcrumbs, tabs, and other wayfinding elements that help users move through a site or application and recognize their place within it.
Taxonomy — A hierarchical system for classifying and grouping content, showing how categories and individual pieces of information relate to one another.
Sitemap — A diagram or visual plan of a website’s structure that shows page hierarchy, content sections, and relationships between areas before or during design work.
Breadcrumbs — A secondary navigation pattern that displays a user’s location in a site hierarchy as a path of links from a higher-level page to the current page.
IA vocabulary gives teams a way to talk about the structures behind usable content. When visitors say they cannot find something on a site, weak information architecture is often part of the problem.
4. Designing Product Interactions
Interaction design, or IxD, deals with what happens when a person takes action in an interface. It covers responses, states, timing, sequences, and behaviors, from a simple tap on a button to a complex gesture-based workflow.
Interaction design (IxD) — The design of how users and a product communicate through actions, system responses, feedback, and state changes while users work toward a goal.
Affordance — A quality of an object or interface element that hints at how it can be used, such as a slider suggesting it can be dragged or an underlined label suggesting it can be clicked.
Feedback — A system response that tells users their action was received and what happened next, such as an inline validation message, a progress indicator, or a confirmation notice.
Microinteraction — A small, focused interaction that supports one task or moment, such as a checkbox changing state, a password field showing strength, or a menu icon animating open.
Progressive disclosure — A design pattern that presents only the most useful information or controls at first, then reveals additional options when they become relevant to the user.
Interaction design terms help teams describe motion, responsiveness, and behavior with precision. They connect static screen layouts to the actual experience of using a working product.
5. UI and Visual Design Language
Visual and UI design shape what users see, read, scan, and touch. Through typography, layout, color, imagery, spacing, and components, designers create an interface that communicates both brand personality and functional meaning.
Design system — A structured set of reusable components, design patterns, rules, and standards that keeps a product or group of products visually and functionally consistent.
Style guide — A reference document that defines visual rules for a product or brand, including type choices, colors, spacing, icons, imagery, and other elements used to maintain consistency.
Visual hierarchy — The way design elements are arranged to show importance, using contrast, size, position, color, and spacing to guide attention through an interface.
Whitespace (negative space) — The open space around and between interface elements that improves readability, reduces clutter, and helps important content stand out.
Responsive design — A design approach that allows an interface to adjust well across different devices, screen sizes, and orientations while preserving usability and visual quality.
These terms describe the parts of an interface that users can directly see and use. In modern product teams, a strong design system is especially valuable because it reduces duplicated work and makes consistency easier to maintain.
6. Wireframes, Mockups, and Prototypes
Wireframes and prototypes let teams explore ideas before engineering work begins. They make abstract concepts easier to discuss, test, revise, and share with people who need to understand the proposed product experience.
Wireframe — A simple, low-fidelity representation of a screen or page that shows layout, content placement, structure, and navigation without polished visual details such as color, type styling, or final images.
Prototype — An interactive model of a product or feature that users and stakeholders can try before development, ranging from a basic clickable flow to a highly realistic near-final experience.
Mockup — A static high-fidelity design image that shows the intended look of a screen, including elements such as typography, color, icons, and imagery, but without interactive behavior.
Fidelity — The degree of detail and realism in a wireframe, prototype, or mockup, from rough sketches focused on structure to polished designs that closely match the intended final product.
User flow — A diagram of the route a user follows to complete a task, showing screens, decisions, actions, and the sequence from starting point to successful completion.
This vocabulary prevents avoidable misunderstandings. Asking for a prototype when you actually need a static mockup can waste time, while choosing the right level of fidelity helps a team match the design artifact to the stage of work.
7. Testing Ease of Use
Usability focuses on whether people can use a product effectively, efficiently, and with reasonable satisfaction. Testing puts a design in front of real or representative users, revealing obstacles that may not be obvious to the team that created it.
Usability — A measure of how well users can learn, remember, and use a product to reach their goals, including effectiveness, efficiency, error prevention, and satisfaction.
Usability testing — A research method in which representative users attempt assigned tasks with a product or prototype while observers record where they succeed, hesitate, make mistakes, or become confused.
A/B testing — A comparison method where two versions of a design are shown to different user groups at random, then measured against a target outcome such as conversion, clicks, or sign-ups.
Heuristic evaluation — An expert review in which usability specialists inspect a product using established usability principles to find likely problems before or alongside user testing.
Think-aloud protocol — A testing technique where participants speak their thoughts, reactions, and reasoning while using a product, giving researchers insight into expectations and decision-making.
Usability and testing terms give teams a shared way to evaluate designs with evidence. They also help prioritize fixes and explain recommendations using observed behavior rather than personal preference.
8. Measuring the User Experience
UX metrics turn parts of the user experience into measurable signals. Teams use them to track progress, compare design options, identify problem areas, and show how UX improvements can support business goals.
Metrics Based on User Behavior
Task success rate is the percentage of users who complete a specified task successfully. Time on task records how long users need to finish a particular action, with shorter times often suggesting a smoother experience. Error rate measures how frequently users make mistakes while interacting with a product. Conversion rate is the percentage of users who take a desired action, such as making a purchase, creating an account, or subscribing. Bounce rate shows the percentage of users who leave a page without taking another action.
Metrics Based on User Attitudes
The System Usability Scale (SUS) is a standard ten-question survey that produces a score from 0 to 100 and offers a quick measure of perceived usability. Net Promoter Score (NPS) asks users, on a 0-to-10 scale, how likely they are to recommend a product, then groups responses into promoters, passives, and detractors. Customer Satisfaction Score (CSAT) asks how satisfied users are with a product or interaction, commonly using a five-point scale. Customer Effort Score (CES) measures how difficult or easy it was to complete a task, with lower effort generally associated with greater satisfaction and loyalty.
9. Human Behavior in Design
UX design draws heavily on how people perceive, remember, decide, and act. Psychology helps designers create interfaces that feel natural because they work with human attention and expectations instead of fighting them.
Cognitive load — The mental effort required to use a product or complete a task; too much cognitive load can cause confusion, errors, hesitation, and frustration.
Hick's law — A principle stating that decision time increases logarithmically as the number of available choices increases, which supports limiting options when users need to decide quickly or clearly.
Fitts's law — A predictive model stating that the time needed to reach a target depends on the target’s distance and size, guiding how designers place and size interactive controls.
Mental model — A user’s internal idea of how a system works, built from past experience and expectations, which designers should understand and either align with or carefully adjust.
Gestalt principles — Perceptual rules describing how people naturally organize visual elements, including proximity, similarity, continuity, closure, and figure-ground, all of which influence interface layout.
Psychology terms help UX designers explain the reasoning behind design choices. Concepts such as cognitive load, mental models, and Gestalt grouping make it easier to describe why an interface feels clear, confusing, fast, or slow.
10. Using UX Terms Professionally
Learning UX vocabulary is practical career preparation, not just theory. Clear terminology helps designers explain decisions, collaborate with engineers and product managers, earn stakeholder trust, and present work more confidently in reviews, interviews, and client conversations. When UX professionals can speak precisely, they can advocate more effectively for both users and the resources needed to improve the product.
The language of UX also changes as products and technology change. Voice interfaces, augmented reality, conversational design, and AI-based personalization continue to add new terms and patterns to the field. Keeping up requires regular learning through industry writing, professional communities, conferences, critique, and hands-on project work.
The terms in this guide cover major areas of UX design, including research, information architecture, interaction patterns, usability testing, visual systems, metrics, and psychology. Whether you are starting a UX career, strengthening your design practice, or working with UX teams from another role, this vocabulary gives you a shared foundation for building more useful, human-centered digital products.
Look Up Any Word Instantly on Dictionary Wiki
Get definitions, pronunciation, etymology, synonyms & examples for 1,200,000+ words.
Search the Dictionary