Summary
Research scope is defined by Layers of Experience: Customer Experience (CX) encompasses all company touchpoints, User Experience (UX) focuses on product interaction, and Micro-UX examines individual scenarios and tasks. Combining a layer with a Research Target (product, marketing, EX, business model) produces a specific, defensible research question.
Before you begin any research, you must define its scope. Scope means identifying the Layer of Experience you will focus on — from the broadest business context to the most granular interaction detail — and pairing it with the Research Target you are investigating.
This article is one piece of the Applied Research Framework, which covers goal, scope, subject, execution, practitioners, and audiences. Here we focus on scope.
The Three Layers
In most consumer contexts these layers nest cleanly: Micro-UX lives inside UX, UX lives inside CX. That containment is a useful simplification, not a law. In B2B products, internal tools, and Employee Experience work the boundaries overlap rather than nest — an employee's full relationship with their employer is not a superset of their tool interactions in the same way a consumer's customer relationship is a superset of their product use.
Keep the caveat in mind, but work with the nested model as your default.
To make the layers concrete, one example threads through each section below: a customer who wants to buy a birthday present for a friend.
Customer Experience (CX)
This is the outermost, macro-level layer. Customer Experience [2] encompasses every touchpoint a customer has with your company:
- Marketing impressions
- Sales interactions
- Product usage
- Customer support
- Physical store visits
- Post-purchase communications
A CX problem — such as a marketing campaign promising something the product cannot deliver — spans multiple touchpoints and requires cross-functional solutions.
Birthday-gift example (CX): How does the prospective gift-buyer first encounter the retailer? Does the social ad set an expectation that the post-purchase email confirms or contradicts? What happens if the delivery is late and they call support? The unit of analysis is the entire relationship.
User Experience (UX)
This meso-level layer is a subset of CX. User Experience [1] refers specifically to a person's perceptions and responses from using a product, system, or service.
A UX problem is typically contained within the product itself. The user struggles with a feature, cannot find something, or has a frustrating interaction, but the issue does not span the entire customer relationship.
Birthday-gift example (UX): Once inside the retailer's mobile app, can the gift-buyer find appropriate products, compare them, and check out? The unit of analysis is the product used to fulfill the goal.
Micro-UX
This is the most granular level, which can be broken down further:
Scenario / User Goal: The high-level human goal and the context behind it — for example, "to buy a birthday present for a friend." This describes what the person is trying to achieve, not what the system does.
Task / Step to the Goal: A specific, concrete step a user must take to achieve their goal. Examples include "search for a product" or "enter payment information." This sequence of tasks is also known as a user flow — the intra-product path a person takes to complete a goal. Don't confuse it with a user journey, which spans multiple touchpoints (marketing, product, support) and belongs to the CX layer.
Birthday-gift example (Micro-UX): On the payment step of checkout, does the card-entry field accept pasted numbers? Does a missed field show an error that tells the user what to fix? The unit of analysis is the individual interaction moment.
System-Centric vs. Human-Centered Framing
To keep terminology clear, distinguish between the system's functions and the user's motivations:
| Framing | Example | Focus |
|---|---|---|
| System-centric use case | "User authenticates" | What the system does |
| Human-centered user goal | "Access my account securely" | What the person is trying to achieve |
The guiding principle: For most evaluative and generative research, design the study around the user's natural objective (the Scenario) rather than the system's granular functions (the Tasks). The exceptions are narrow — conformance checks and technical QA, where the unit of analysis genuinely is the system function.
When you design evaluative or generative research around system functions, you risk missing the forest for the trees. A user might successfully complete every individual task you test while still failing to achieve their actual goal, or achieving it in a way that feels painful.
For how different research disciplines map to these scope layers, see Research Disciplines: A Practitioner's Map.
Why Scope Matters
Understanding which layer you are researching is critical for two reasons:
1. It Determines What Conclusions You Can Draw
Research on a specific checkout payment step (Micro-UX) cannot make claims about the overall customer relationship (CX). Tested whether the gift-buyer can enter payment information? You have not shown that customers are satisfied with the retailer as a whole.
Scope defines boundaries. Exceeding them produces misleading findings.
2. It Allows Clear Communication
When presenting research, explicitly stating scope prevents stakeholders from over-generalizing:
- "This research examined the mobile checkout flow [UX layer]. It does not assess the broader customer journey or marketing touchpoints [CX layer]."
- "We tested the payment step within the gift-buyer scenario [Micro-UX]. Overall product satisfaction was not measured [UX layer]."
Layers and Research Targets
Pairing a layer with a target produces a specific research question — the matrix below shows typical questions per cell.
While the Layers of Experience define the depth of focus, Research Targets define the specific business area under investigation. The two dimensions are orthogonal — you can study any target at any layer.
| Layer ↓ / Target → | Product | Marketing | EX | Business Model |
|---|---|---|---|---|
| CX | Does the whole relationship — marketing, support, billing, renewals — hold up? | Does the campaign's promise match the journey that follows? | How do employees experience the full employer relationship from hiring to exit? | Does the pricing match the value customers perceive over their lifetime? |
| UX | Can users accomplish their goals in the product interface? | Can visitors navigate the campaign landing page and convert? | Can staff complete their tasks in the internal tool? | Can prospects compare tiers and choose a plan? |
| Micro-UX | Does the checkout payment step flow cleanly, moment by moment? | How does the hero animation feel on slow connections? | Is the timesheet field painless on a Monday morning? | Does the upsell modal feel respectful or predatory? |
A research question that does not resolve to one cell is either under-scoped or crosses layers — both are worth catching before fieldwork starts.
For the experience components that scope decisions ultimately target, see Components of Experience.
Cross-Cutting Foundations
Some qualities are foundational — they cut across every layer rather than living on one of them. Scope them out explicitly; do not let them fall between layers.
Accessibility is the clearest example. An accessibility issue means some users cannot access the product effectively due to a disability or situational limitation. It impacts their experience at every level, from the broadest CX (they cannot be a customer at all) to the most granular Micro-UX (individual interactions are impossible or painful). Accessibility is not a feature for one layer; it is a quality that affects the whole hierarchy.
Other cross-cutting foundations worth naming:
- Performance: Slow load times degrade every layer — a five-second delay ruins a Micro-UX moment, a chronically slow product bleeds CX loyalty.
- Privacy: Data-handling decisions affect trust at the CX level and specific permission flows at the Micro-UX level. Scope them explicitly when research touches consent, collection, or disclosure.
- Trust: Security indicators, reassuring copy, and visual hierarchy contribute at every layer and can be studied at every layer.
- Internationalization (i18n): Applies from marketing copy down to micro-copy. Locale-specific friction often hides on the Micro-UX layer but has CX-wide consequences.
- Brand consistency: Voice and visual continuity carry from campaign to UI detail; inconsistency reads as distrust even when users can't name the cause.
A note on Service Design: Service Design operates across CX touchpoints rather than forming a separate layer. A service blueprint maps how product, staff, physical spaces, and digital channels combine to deliver a customer outcome. It is CX research with a specific lens — not a new depth of focus.
For the methods that operate within the chosen scope, see Building Blocks and Core Methods.
Applying Scope in Practice
When planning research, use the gift-buyer thread as a stress test — can you answer each step in concrete terms?
1. Identify the layer
What level of experience does your research question address?
- Broad customer journey → CX
- Product interaction → UX
- Specific task or flow → Micro-UX
For the gift-buyer: "Does our support process recover well after a late delivery?" is CX. "Can shoppers find appropriate products in the app?" is UX. "Does the payment step work on iOS Safari?" is Micro-UX.
2. Define the target
What business area are you investigating? A product, a marketing campaign, an internal process, a pricing model — match your question to one column of the matrix above.
3. Set explicit boundaries
What is in scope? What is explicitly out of scope? Document this in your research plan. If stakeholders ask for conclusions outside the boundary, point back to the plan.
4. Choose appropriate methods
Different layers may require different approaches:
- CX research often requires journey mapping across touchpoints
- UX research typically uses UX tests and interviews
- Micro-UX research might focus on specific task flows with detailed metrics
5. Communicate scope with findings
When reporting, remind stakeholders what you studied and what you did not. Scope statements are not disclaimers — they are essential context for interpreting findings correctly.
Scope and Strategic Research
You will sometimes hear the term "Strategic Research" — research that moves beyond standard generative or evaluative work to deliver foresight by synthesizing insights across disciplines.
While the term fits the Layers of Experience model (highlighting a shift away from single tasks toward the entire customer journey), it has one issue: it implies all other research is "unstrategic."
But when would you ever do something deliberately unstrategic? A great Customer Experience is built from the ground up. Making a core task usable is deeply strategic — it is the prerequisite for everything above it.
Scope is not about importance. Research at every layer matters. The question is what conclusions each layer can support.
For how scope decisions connect to the broader research framework, see The Applied Research Framework: How Everything Fits Together.