The Applied Research Framework: How Everything Fits Together

The different models, layers, and disciplines discussed across UX research can feel like separate topics to learn and file away. But they are not isolated concepts, they are components of a single, unified system.

Understanding how these pieces connect transforms research from a collection of activities into a strategic practice.

The Unified System

We can call this system Applied Empirical Business Research: the practice of using empirical data to reduce uncertainty and make better business decisions.

This framework clarifies how all the pieces fit together:

The Overarching Goal: Why We Do It

The purpose is to conduct applied business research, to generate insight and foresight that de-risks investments and leads to better outcomes.

This is fundamentally different from academic research, which aims to generate new knowledge for its own sake. Applied research is judged by a pragmatic standard: Did it help the organization make a better decision?

The Scope: What We Can Study

Our scope is defined by two dimensions:

Research Targets range from entire business models to internal processes. You can research products, services, marketing campaigns, employee workflows, anything where human experience affects outcomes.

Layers of Experience define the depth of focus, from the broad Customer Experience (CX) down to Micro-UX (individual tasks and interactions). The layer you choose determines what conclusions you can draw and what findings you can generalize.

The Subject: What We Investigate

When we examine an experience, we are assessing the Components of Experience:

• Foundational qualities like technical stability (QA) and accessibility
• Pragmatic qualities like usability and usefulness
• Experiential qualities like cognition, emotion, and aesthetic perception

These components tell us what dimensions of experience we can measure and evaluate.

The Execution: How We Do It

Execution is grounded in the three Building Blocks of research, Asking, Observing, and Testing, which combine into the three Core Methods: UX Tests, Interviews, and Surveys.

These methods can be applied with different orientations:

• Qualitative or Quantitative: Seeking depth of understanding or breadth of measurement
• Generative or Evaluative: Discovering what to build or assessing whether it works

The Practitioners: Collaboration

This work is performed by people in various research disciplines, market research, UX research, product research, and others. Each brings different emphases and expertise, but all use variations of the same foundational methods.

Critically, research must be understood and acted upon by stakeholders with different mindsets: developers who need technical specificity, product managers who need prioritization guidance, executives who need strategic clarity, marketers who need messaging insights.

The framework is only complete when insights translate into action.

The Action Research Connection

The iterative, problem-solving approach of applied business research is a practical application of a methodology known as Action Research, first coined by MIT professor Kurt Lewin in 1946 ^[1].

Its core tenet is to link theory and practice by having researchers and participants collaborate to solve immediate problems ^[2]. Action Research prioritizes practical change over pure knowledge generation.

This distinction matters. When stakeholders question why your sample size is "too small" for statistical significance, or why you are not following academic conventions, the answer lies here: We are doing applied research. The goal is not publishable findings but actionable insights that reduce uncertainty for this specific decision.

Visualizing the Framework

The framework can be represented as interconnected layers:

Why the Framework Matters

Without a unifying framework, research activities can feel arbitrary or disconnected from business value. Individual studies happen, reports are delivered, but the strategic thread is lost.

The framework provides:

Clarity on purpose: Every study should connect to the overarching goal of reducing uncertainty for a decision. If you cannot articulate what decision your research informs, question whether it should be done.

Scope discipline: Understanding layers and targets prevents over-generalization. Research on a single task cannot make claims about overall customer experience; research on one user segment cannot speak for all users.

Method selection logic: Instead of picking methods by habit or convenience, you select based on what Components of Experience you need to assess and what Building Blocks are required to assess them.

Stakeholder translation: Different audiences need findings framed differently. The framework helps you understand what each stakeholder needs to act.

From Framework to Practice

The framework is a thinking tool, not a checklist. Its value is in providing mental structure for decisions that would otherwise be made ad hoc.

When you encounter a new research request:

1. Clarify the goal: What decision will this research inform? What uncertainty needs to be reduced?
2. Define the scope: What are we studying, and at what layer of experience?
3. Identify the components: Which aspects of experience matter for this decision?
4. Select the execution: What combination of Building Blocks and methods will get us there?
5. Plan for action: Who needs to understand and act on findings? How will insights be communicated?

All the methods, techniques, and tools discussed throughout applied UX research are in service of this unified framework. Master the framework, and individual methods become tools you select purposefully rather than habits you follow blindly.