Success Criteria
Success criteria are the defined conditions that determine whether a task, interaction, service journey, or evaluation goal has been completed successfully.
UX Reference
A searchable A-Z reference for UX terms, human-centered design concepts, research methods, accessibility terminology, usability metrics, and digital service concepts.
Search across UX concepts and reference entries.
Reference index
Showing 145-168 of 180 entries.
Success criteria are the defined conditions that determine whether a task, interaction, service journey, or evaluation goal has been completed successfully.
Support ticket analysis is the systematic review of support requests, complaints, helpdesk records, or service queries to identify recurring user problems, operational burden, and service...
A survey is a structured research method that uses standardized questions to collect data from a defined group of respondents.
The System Usability Scale is a standardized questionnaire used to measure perceived usability after people use a system.
Task analysis is a method for studying what people need to do to achieve a goal, including the steps, decisions, tools, dependencies, constraints, and possible errors involved.
A task scenario is a realistic description of a situation that asks a participant to attempt a task without directly telling them which interface steps to take.
Task success is a UX evaluation measure that describes whether a user completes a specified task or goal under defined evaluation conditions.
A test plan is a structured document that defines how a usability test or evaluation will be conducted, including objectives, participants, tasks, measures, procedure, materials, and logi...
Thematic analysis is a qualitative analysis method for identifying, organizing, and interpreting patterns of meaning across a dataset.
Think-aloud protocol is a method in which participants verbalize what they are thinking while performing a task, allowing evaluators to examine reasoning, confusion, expectations, and dec...
Time on task records the elapsed time users take to complete a defined task under evaluation conditions.
A touchpoint is a specific point where a person interacts with a service, product, organization, system, communication, staff member, or artifact within an experience.
Tree testing is an information architecture evaluation method in which participants use a simplified text-based hierarchy to find where they would go to complete a task or locate informat...
Triangulation is the use of multiple data sources, methods, researchers, or perspectives to strengthen the interpretation of research findings.
Trust calibration is the alignment between a person’s level of trust in a system and the system’s actual capability, reliability, uncertainty, and limits in a given context.
Usability benchmarking is the process of measuring usability performance using repeatable tasks and metrics so results can be compared across time, versions, systems, or user groups.
A usability issue is a documented problem that prevents, delays, misleads, frustrates, or increases effort for users trying to complete a task or achieve a goal.
Usability testing is an evaluation method in which representative users attempt realistic tasks while a team observes what helps, blocks, confuses, or supports use.
A use case is a structured description of how an actor interacts with a system, service, or process to achieve a goal under specific conditions.
User confidence is a perception-based measure of how certain users feel about their understanding, decision, or task outcome after interacting with a product, service, or interface.
A user flow represents the sequence of steps, decisions, screens, actions, and system responses a user follows to complete a task or reach a goal.
A user interview is a qualitative research method in which a researcher asks participants open-ended questions to understand their experiences, expectations, reasoning, needs, and constra...
A user need is an evidence-based statement of what a user must understand, decide, access, provide, or accomplish in order to complete a task or receive value from a service.
A user requirement is a statement of what a system, product, service, or interaction must support so that users can meet identified needs in a specific context.