A Core Method combining all three Building Blocks: testing task completion (effectiveness and efficiency), observing behavior and non-verbal cues, and asking questions about the experience. The most comprehensive single research method.
Definition: A Core Method combining all three Building Blocks: testing task completion (effectiveness and efficiency), observing behavior and non-verbal cues, and asking questions about the experience. The most comprehensive single research method.
A UX Test is a Core Method that combines all three Building Blocks—Asking, Observing, and Testing—to comprehensively assess how users interact with a product or service.
In a standard UX Test:
These terms are often used interchangeably, but there is a distinction. A Usability Test specifically evaluates against the ISO 9241-11 standard: effectiveness, efficiency, and satisfaction in a specific context of use.
A UX Test is the broader umbrella term. It encompasses usability measurement but also captures other Components of Experience—cognition, emotion, perceived aesthetics—that go beyond the ISO definition. Throughout practice, UX Test is the preferred term unless explicitly measuring only the ISO usability criteria.
UX Tests can be moderated (with a researcher guiding the session) or unmoderated (self-directed by the participant). They can be conducted in-person or remotely. The Building Blocks remain the same; the environment and facilitation method change based on your constraints and goals.
The three foundational research activities—Asking, Observing, and Testing—that combine to form all UX research methods. A framework for understanding that complex methods are built from simple components.
The three primary UX research methods built from Building Blocks: the UX Test, the User Interview, and the Survey. Each represents a different combination of asking, observing, and testing activities.
Per ISO 9241-11: the extent to which a product can be used by specified users to achieve specified goals with effectiveness, efficiency, and satisfaction in a specified context of use.
A Core Method of structured asking designed for deep exploration of user needs, behaviors, and motivations. Distinguished from casual conversation by its defined goals, protocol, and systematic approach.
This term is referenced in the following articles:
An interactive tool that guides you to the right research method based on your goals, constraints, and context.
Standardized measurement instruments provide benchmarks and comparability. But using them effectively requires understanding what each one actually measures, and what it does not.
Before you begin any study, you must define its scope. This involves identifying the Layer of Experience you will focus on, from broad customer journey down to individual task steps.
One of the most common points of friction is not about budget or methods, it is about timing. Your core job is to reframe research from a single, disruptive event into a continuous, value-adding loop.
What to say and when to say it. A standard protocol for intros, the 'Think-Aloud' instruction, and neutral probing.
Good research does not happen by accident. The research plan is the single most important tool for avoiding unfocused, low-impact research, and for ensuring your work drives real decisions.
Before you design a single screen, the structure of your content must make sense to users. Card sorting and tree testing are specialized techniques for designing and validating information architecture.
Market research, UX research, CX research, product research, are these different things? At their core, they are all related methods for gathering data to reduce uncertainty. The key is understanding what each is best suited for.
Good research is not a series of disconnected activities, it is a cohesive process that transforms business questions into actionable insights. This is the map for that journey.
Don't wait for the beta. The 3 critical moments to test: Concept (Generative), Prototype (Formative), and Live (Summative).
Rather than a sharp divide, qualitative and quantitative research exist on a continuum. The most powerful insights come from combining both, understanding why something happens and measuring how often.
Research disciplines, methods, and principles are not isolated concepts, they form a unified system. Understanding this framework is what separates scattered activities from strategic research practice.
User Experience is not a single thing, it is a complex result of interconnected components organized in a hierarchy. Understanding this structure is essential for translating stakeholder desires into actionable research.
Research does not happen in a vacuum. It happens in a complex, messy, human ecosystem of competing priorities, overlapping roles, and different ways of thinking. Success depends less on perfecting methods and more on navigating this reality.
No matter how complex a method sounds, it can be broken down into three simple activities. Understanding this framework transforms how you plan and execute research.
There are two fundamentally different ways we gather data. Research we design and control, and data users generate without our prompting. Most teams over-rely on one and misunderstand the other.