Components of Experience: What We Actually Measure in UX Research

The overall User Experience is not a single, monolithic thing. It is a complex result of several interconnected components, which can be grouped into distinct, hierarchical qualities.

Understanding this structure is essential for two reasons: it tells you what to measure, and it gives you the language to translate vague stakeholder desires into actionable research criteria.

The Hierarchy of Experience

The Components of Experience are organized in layers, from foundational prerequisites to subjective perception.

Experience is not a single layer; it is a pyramid. You must satisfy the lower levels before the higher ones matter:

• Foundational (The "Must Haves")
  • QA and Accessibility
  • "Does it work? Can everyone access it?"
  • If a button is broken or invisible to a screen reader, nothing else matters.
• Pragmatic (The "Basics")
  • Usability and Usefulness
  • "Is it easy? Does it solve a problem?"
  • This is where most teams stop.
• Experiential (The "Differentiators")
  • Aesthetic, Emotion, and Meaning
  • "Does it build trust? Is it delightful?"
  • You cannot paint over a broken foundation with "delight."

Foundational Qualities

These are the absolute prerequisites for any experience. Without them, nothing else matters.

Quality Assurance (QA) answers the most basic question from a technical perspective: Does it work? A product that crashes, throws errors, or fails to load has failed before the user can even attempt to use it. QA is the floor upon which everything else is built.

Accessibility is the next foundation. If a person cannot access the product or service, due to a disability, situational limitation, or technical barrier, no other component of experience is relevant to them. Accessibility issues cut across all layers; they are not a feature to add later but a foundational requirement from the start.

Pragmatic Qualities

These are the functional pillars of the experience, the practical, goal-oriented aspects of an interaction.

Usefulness: Does it solve a real need? A product can be technically flawless, beautifully designed, and perfectly accessible, but if it does not solve an actual problem for users, it fails at usefulness. This is the question of whether you are building the right thing.

Usability: Is it effective, efficient, and satisfying? Per ISO 9241-11 ^[2], usability is defined by:

• Effectiveness: Can users complete their intended tasks?
• Efficiency: What resources (time, effort, errors) are required?
• Satisfaction: How do users feel about the interaction?

Usability is the question of whether you are building the thing right.

Experiential Qualities

These represent the user's internal world, the subjective, emotional lens through which they interpret a product's functional aspects.

Cognition and Mental Models: How does the user understand the system to work? Does the product's conceptual model match the user's mental model? Mismatches here cause confusion, errors, and frustration even when the product is technically sound.

Affect and Emotions: How does the product make users feel? This spans a wide range, from frustration and anxiety to delight and trust. It includes deeper states like immersion and flow ^[3], where users become so engaged that they lose track of time.

Values and Aesthetic Perception: Do users find the product beautiful, trustworthy, or aligned with their own principles? Aesthetic perception influences emotional response, and values alignment affects whether users want to be associated with a product at all.

How the Components Interact

All of these components, foundational, pragmatic, and experiential, come together to create the holistic User Experience (or, at a broader level, Customer Experience).

The relationship between usability and broader user experience has been the subject of significant research ^[4]. The key insight: UX extends beyond usability to include emotional and aesthetic dimensions.

Consider these failure modes:

Component	Failure Mode	Result
QA	Product crashes frequently	Users cannot complete any goals
Accessibility	Screen reader incompatible	Subset of users completely excluded
Usefulness	Solves non-existent problem	No one needs the product
Usability	Tasks take too long, too many errors	Users abandon in frustration
Cognition	Interface contradicts mental model	Users confused, make errors
Affect	Interaction feels anxiety-inducing	Users avoid the product
Values	Product feels untrustworthy	Users refuse to engage

Translating Stakeholder Desires

This framework is a practical tool that highlights the researcher's role as a translator between informal stakeholder desires and formal, actionable research criteria.

When you ask stakeholders for their goals for a new product, they will often provide variations of:

• "It needs to be easy to use"
• "People should grasp it immediately"
• "It needs to delight users"
• "Users should trust us"

These are valuable inputs, but they are vague. Using the Components of Experience, you can translate them into operationalized plans:

Stakeholder Desire	Maps To	Research Approach
"Easy to use"	Usability (Pragmatic)	UX Tests measuring effectiveness, efficiency, satisfaction
"People should grasp it immediately"	Cognition / Learnability	First-time user tests, mental model studies
"Delight users"	Affect and Emotions (Experiential)	Emotional response measurement, experience sampling
"Users should trust us"	Values (Experiential)	Trust perception studies, credibility assessment
"It needs to work"	QA + Usability (Foundational/Pragmatic)	Technical testing + task-based evaluation

The Assumption Behind "Usefulness"

When stakeholders request research on whether something is "easy to use," there is often an implicit assumption: that the product solves a real problem in the first place. This assumption, that the product is useful, should be questioned early.

The most polished, usable product in the world fails if it solves a problem no one has. Generative research addresses this by exploring user needs before committing to a specific solution.

Implications for Research Design

When designing research, consider which components you need to assess:

For evaluating a prototype or existing product: Focus on Pragmatic qualities (Usability) through UX Tests. Add experiential measurement if emotional response is important.

For validating a concept: Focus on Usefulness and potentially Values. Does this solve a real need? Do users want to be associated with this?

For understanding user context: Focus on Cognition and mental models through interviews and contextual inquiry.

For measuring at scale: Focus on specific, measurable aspects of Usability and Affect through surveys with validated instruments.

A Complete Picture Requires All Components

No single research study can assess all components comprehensively. But over time, a robust research program should touch all levels of the hierarchy:

• Foundational issues should be caught through QA processes and accessibility audits
• Pragmatic qualities are the bread-and-butter of evaluative UX research
• Experiential qualities require deliberate attention, they will not surface unless you design for them

The Components of Experience framework ensures you are not optimizing one dimension while ignoring critical failures in another. A product can score perfectly on task completion while simultaneously driving users away through poor emotional design.

Understanding this hierarchy is how you build products that do not just work, but that users actually want to use.