Summary
Applied business research is the practice of using empirical data to reduce uncertainty and improve decisions. The framework organizes six levels (goal, scope, subject, execution, practitioners, audiences) and explains how they connect.
The different models, layers, and disciplines discussed across UX research can feel like separate topics to learn and file away. They are components of a unified system.
The Unified System
We can call this system applied business research: the practice of using empirical data to reduce uncertainty and make better business decisions.
This framework clarifies how the pieces fit together.
The Overarching Goal: Why We Do It
The purpose of applied business research is to generate insight and foresight that de-risks investments and leads to better outcomes.
Academic and applied research differ in their primary success criteria and their audience. Academic work is judged by contribution to a field's body of knowledge; applied work is judged by whether it helped the organization make a better decision. Good applied work can be theoretically informed, and good academic work often has practical yield. The two sit on a continuum rather than in opposition.
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 [1]:
- 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 [2].
These methods can be applied with different orientations [3]:
- 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: Who Conducts the Research
This work is performed by people in various research disciplines: market research, UX research, product research, employee research, and others [4]. Each brings different emphases and expertise, but all use variations of the same foundational methods.
The Audiences: Who Acts on the Findings
Research is only useful once people with decision authority understand and use it. Developers need technical specificity. Product managers need prioritization guidance. Executives need strategic clarity. Marketers need messaging insights. Translating findings for each audience is part of the practitioner's job, and the framework is only complete when that translation happens.
The Action Research Connection
Applied business research is sometimes traced to Kurt Lewin's Action Research, first described in 1946 [5]. The connection is partial. Action Research and applied business research share a pragmatic orientation, a preference for iteration, and a focus on solving concrete problems rather than producing generalizable theory [6].
The difference matters. Lewin's Action Research has a participatory, often emancipatory core: researchers and participants co-diagnose a problem and co-design the response, typically in social-reform or community-development contexts. Applied business research usually does not meet that criterion. Stakeholders commission research on participants, not with them, and the decisions being informed belong to the organization rather than to the people studied.
Applied business research therefore shares features with Action Research but is distinct in structure and goals. Treat Lewin as historical context, not as the origin of the commercial discipline.
Visualizing the Framework
The framework can be represented as six interconnected levels:
Why the Framework Matters
Without a framework, research activities stay disconnected from business value: studies happen, reports are delivered, 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.
Audience translation: Different audiences need findings framed differently. The framework helps you understand what each audience needs in order to act.
Where This Framework Doesn't Help
The framework assumes a decision is waiting to be informed. It is the wrong tool for basic or theory-building research, where the goal is contribution to a discipline rather than the resolution of a specific business question.
It is also the wrong tool when a request is pure exploration with no decision pending, or when a long-horizon study (extended ethnography, cultural research) is commissioned before the decision has taken shape. In those cases the framework's six levels collapse: without a goal to anchor the scope, method selection becomes arbitrary and the audiences layer stays empty.
The framework also fails when stakeholders disagree on the underlying goal. Surface and resolve that disagreement before planning the study; applied research cannot substitute for a decision that has not yet been made.
A Worked Example
A B2B SaaS product team reports that users seem confused by the new onboarding flow. Walking through the framework: the goal is to decide whether to iterate, rewrite, or roll back before the next release. The scope is one task flow at the Micro-UX layer, not the full Customer Experience. The subject focuses on pragmatic qualities (usability, usefulness) before experiential ones. Execution combines an evaluative usability test (observing) with a short post-task survey (asking). Practitioners are UX researchers working alongside the product team. The audiences are PMs, who need a clear iterate/rewrite/rollback recommendation, and developers, who need task-level findings specific enough to act on.
From Framework to Practice
The framework is a thinking tool, not a checklist. Its value is in providing a mental structure for decisions that would otherwise be made ad hoc. Apply the six levels as questions when planning a new study, and use the same questions when critiquing one that already exists.
Related Concepts
References
- [1]
- [2]Mike Kuniavsky. (2003). "Observing the User Experience: A Practitioner's Guide to User Research". Morgan Kaufmann.Link
- [3]John W. Creswell & Vicki L. Plano Clark. (2018). "Designing and Conducting Mixed Methods Research". SAGE Publications.Link
- [4]Yvonne Rogers et al.. (2023). "Interaction Design: Beyond Human-Computer Interaction". Wiley.Link
- [5]
- [6]Glenda Mac Naughton. (2001). "Action Research". In G. Mac Naughton, S. A. Rolfe, & I. Siraj-Blatchford (Eds.), Doing Early Childhood Research: International Perspectives on Theory and Practice (pp. 208-223). Open University Press.Link