Top 100 Vocabulary for Adults | UX/UI Designers
UX and UI vocabulary is the language of turning human needs into usable interfaces. Designers must understand what users are trying to do, how information is organised, where friction appears, and how visual decisions affect comprehension, trust and action.
This profession-specific flagship belongs to the eduKate Adult Vocabulary for Professionals system. It complements Product Management Professionals, Architects & Designers and Software & Technology Professionals.
The Four Banks
Research & Users: user, customer, persona, segment, need, goal, task, journey, workflow, pain point, interview, observation, usability test, research, insight, assumption, hypothesis, context, behaviour, accessibility, inclusion, empathy, evidence, validation, discovery.
Structure & Interaction: information architecture, navigation, hierarchy, sitemap, taxonomy, label, affordance, signifier, feedback, state, flow, interaction, microinteraction, control, input, form, error, recovery, onboarding, progressive disclosure, consistency, convention, discoverability, learnability, efficiency.
Visual & System Design: layout, grid, spacing, alignment, typography, colour, contrast, icon, component, pattern, design system, token, variant, responsive, breakpoint, hierarchy, emphasis, whitespace, density, visual rhythm, consistency, brand, accessibility contrast, dark mode, prototype.
Testing & Delivery: wireframe, mock-up, prototype, fidelity, scenario, task success, completion rate, error rate, satisfaction, heuristic, usability, accessibility audit, iteration, handoff, specification, annotation, developer, stakeholder, acceptance criteria, bug, regression, release, measurement, telemetry, outcome.
Top 100 UX/UI Vocabulary: Working Meanings
| # | Word | Professional meaning |
|---|---|---|
| 1 | User | The person interacting with a product or service. |
| 2 | Customer | The person or organisation purchasing or receiving value. |
| 3 | Persona | A research-informed representation of a user type. |
| 4 | Segment | A group sharing relevant needs or behaviours. |
| 5 | Need | An outcome or condition a user requires. |
| 6 | Goal | The result a user wants to achieve. |
| 7 | Task | A defined action a user performs. |
| 8 | Journey | The sequence of interactions across an experience. |
| 9 | Workflow | A series of steps used to complete work. |
| 10 | Pain point | A source of friction or difficulty. |
| 11 | Interview | A structured conversation used to understand users. |
| 12 | Observation | Direct study of user behaviour in context. |
| 13 | Usability test | A session where representative users attempt tasks while designers observe. |
| 14 | Research | Structured investigation used to reduce uncertainty. |
| 15 | Insight | A useful interpretation that changes understanding. |
| 16 | Assumption | A proposition accepted without complete proof. |
| 17 | Hypothesis | A testable claim about user behaviour or design effect. |
| 18 | Context | The conditions shaping user behaviour. |
| 19 | Behaviour | Observable user action. |
| 20 | Accessibility | The degree to which people with different abilities can use a product. |
| 21 | Inclusion | Design that meaningfully serves diverse users and needs. |
| 22 | Empathy | Understanding another person’s perspective and experience. |
| 23 | Evidence | Information supporting or challenging a design decision. |
| 24 | Validation | Testing whether a design or assumption holds under evidence. |
| 25 | Discovery | Work intended to understand problems before or during design. |
| 26 | Information architecture | The organisation and labelling of information within a product. |
| 27 | Navigation | The system helping users move through content or features. |
| 28 | Hierarchy | The ordering of elements by importance or relationship. |
| 29 | Sitemap | A structural map of pages or content areas. |
| 30 | Taxonomy | A classification system organising information into categories. |
| 31 | Label | Text naming a control, category or destination. |
| 32 | Affordance | A property suggesting how an element can be used. |
| 33 | Signifier | A cue indicating where or how an action can occur. |
| 34 | Feedback | A system response communicating the result of user action. |
| 35 | State | The current condition of an interface element or system. |
| 36 | Flow | The sequence of screens or actions for a task. |
| 37 | Interaction | An exchange between user action and system response. |
| 38 | Microinteraction | A small focused interaction supporting one task or feedback event. |
| 39 | Control | An interface element allowing user action. |
| 40 | Input | Information entered by the user. |
| 41 | Form | A structured interface for collecting user input. |
| 42 | Error | A condition in which a task or action fails. |
| 43 | Recovery | The path enabling users to recover from error. |
| 44 | Onboarding | The experience helping new users begin successfully. |
| 45 | Progressive disclosure | Revealing complexity gradually as needed. |
| 46 | Consistency | Use of predictable patterns across an interface. |
| 47 | Convention | A widely recognised design pattern or interaction rule. |
| 48 | Discoverability | How easily users can find available actions or information. |
| 49 | Learnability | How easily new users become effective. |
| 50 | Efficiency | How quickly and easily users complete intended tasks. |
| 51 | Layout | The arrangement of elements on a screen. |
| 52 | Grid | A structural system for alignment and spacing. |
| 53 | Spacing | The controlled distance between interface elements. |
| 54 | Alignment | The positioning of elements along shared lines or relationships. |
| 55 | Typography | The design and arrangement of type. |
| 56 | Colour | A visual property used for meaning, identity or emphasis. |
| 57 | Contrast | Difference used to improve visibility and hierarchy. |
| 58 | Icon | A visual symbol representing an action or concept. |
| 59 | Component | A reusable interface element. |
| 60 | Pattern | A reusable solution to a recurring interface problem. |
| 61 | Design system | A governed collection of reusable components, rules and tokens. |
| 62 | Token | A named design value such as spacing, colour or typography. |
| 63 | Variant | A controlled alternate version of a component. |
| 64 | Responsive | Adapting layout and behaviour to different screen sizes. |
| 65 | Breakpoint | A screen-width threshold triggering layout change. |
| 66 | Emphasis | Visual prominence given to an important element. |
| 67 | Whitespace | Unused visual space improving readability and grouping. |
| 68 | Density | The amount of information or control within a given area. |
| 69 | Visual rhythm | Repeated spatial and visual patterns supporting flow. |
| 70 | Brand | The recognisable identity and promise associated with a product. |
| 71 | Accessibility contrast | Colour contrast sufficient to meet applicable accessibility requirements. |
| 72 | Dark mode | An interface theme using predominantly dark surfaces. |
| 73 | Prototype | An interactive or static model used to test a design idea. |
| 74 | Wireframe | A low-detail representation of layout and structure. |
| 75 | Mock-up | A more polished visual representation of a design. |
| 76 | Fidelity | The level of realism or detail in a prototype. |
| 77 | Scenario | A realistic situation used to frame a design task. |
| 78 | Task success | Whether users can complete a defined task. |
| 79 | Completion rate | The proportion of users who complete a task. |
| 80 | Error rate | The frequency of user or system errors during a task. |
| 81 | Satisfaction | The user’s evaluation of the experience. |
| 82 | Heuristic | A practical usability principle used for evaluation. |
| 83 | Usability | The effectiveness, efficiency and satisfaction of product use. |
| 84 | Accessibility audit | A structured review against accessibility requirements and best practices. |
| 85 | Iteration | A cycle of designing, testing and improving. |
| 86 | Handoff | Transfer of design intent and specifications to implementation teams. |
| 87 | Specification | A detailed statement of design requirements. |
| 88 | Annotation | Notes explaining design behaviour or details. |
| 89 | Developer | A professional implementing software behaviour and interfaces. |
| 90 | Stakeholder | A party influencing or affected by the design. |
| 91 | Acceptance criteria | Conditions defining when a design implementation is acceptable. |
| 92 | Bug | An unintended product behaviour. |
| 93 | Regression | A new defect introduced into previously working functionality. |
| 94 | Release | A product version made available to users. |
| 95 | Measurement | Quantification of product or user behaviour. |
| 96 | Telemetry | Usage or system data collected from live products. |
| 97 | Outcome | The user or business result produced by the design. |
| 98 | Delight | A positive experience exceeding functional expectation without harming usability. |
| 99 | Friction | Unnecessary difficulty slowing or discouraging task completion. |
| 100 | Design rationale | The evidence-based reasoning explaining why a design choice was made. |
A Beautiful Interface Can Still Fail
Visual polish does not guarantee discoverability, accessibility or task success. Professional UX language keeps appearance connected to behaviour and outcome.
Scenario: Users Keep Missing a Button
Do not only enlarge it. Check hierarchy, placement, wording, surrounding information, expected workflow and whether the action is visible at the right moment. The problem may be information architecture, not button styling.
Seven-Day UX/UI Vocabulary Plan
| Day | Practice |
|---|---|
| 1 | Map users, goals, tasks and journeys. |
| 2 | Separate information architecture from visual styling. |
| 3 | Audit one interface for affordance and feedback. |
| 4 | Prototype and test one critical user flow. |
| 5 | Review accessibility and error recovery. |
| 6 | Recall 75+ UX/UI terms by function. |
| 7 | Write a one-page design rationale linking evidence, decision and outcome. |
Continue the Digital Experience Wing
- Cloud & DevOps Professionals
- Database & Platform Professionals
- IT Support & Systems Administration Professionals
- Product Management Professionals
Conclusion
UX/UI vocabulary helps professionals explain why an interface works or fails. It turns taste into evidence, screens into systems and visual decisions into measurable user outcomes.