How do you balance UX studies with classic market research without doubling the work?
HCI Today summarized the key points
- •This article explores how a small UX research team building B2B products can integrate marketing research with user research.
- •The author describes a problem: they run quarterly market research alongside separate surveys, and also conduct user interviews and prototype testing—repeatedly reaching out to the same respondents.
- •As findings are stored separately and analyzed across Slides, Notion, and internal dashboards, the author feels that while the core of the questions is the same, studies with different names and formats keep repeating.
- •To reduce this, they plan to reuse the same screening questions and segments, ask the ‘why’ questions only once, and then split only the reports differently.
- •However, they still write separate discussion guides for marketing and UX for the same type of target audience, so there remains the task of consolidating the study design itself into a single system.
This summary was generated by an AI editor based on HCI expert perspectives.
Why Read This from an HCI Perspective
This article is worth reading because it shows how UX research and market research overlap—and sometimes clash—in B2B environments. In particular, the operational issues that small UXR teams face—participant fatigue from repeatedly contacting the same respondent pool, duplicated questions, and fragmented outputs—are common in HCI practice. It’s especially meaningful because it prompts you to check not just the study design, but ‘who asks the same questions, for what purpose, and how many times.’
CIT's Commentary
From a CIT perspective, the core of this article isn’t the ‘topic’ of the research, but the ‘organizational structure.’ The current problem isn’t the difference between interviews and surveys; it’s that product and marketing are requesting the same underlying decision problem in fragmented ways. So simply creating a shared repo isn’t enough. What’s needed is an operating principle that ties together the research question, segment, decision, and outputs into a single flow. In particular, if a 60-minute interview and an always-on survey are repeatedly consuming the same panel, this affects not only data quality but also the participants’ experience. CIT argues that in such situations, it’s more sustainable to design the research up front so that one study can accommodate interpretations from multiple stakeholders, rather than trying to ‘ask once and interpret in multiple ways.’ In other words, a single source of truth should be implemented first in the research operating system—not just in a repository.
Questions to Consider While Reading
- Q.If product and marketing are asking the same ‘why,’ what actual decision differences are causing them to run separate studies?
- Q.Do you have internal criteria for measuring how often participants are contacted and how fatigued they are?
- Q.Among Slides, Notion, and internal dashboards, which one is the final truth (source of truth), and who sets that standard?
This commentary was generated by an AI editor based on HCI expert perspectives.
Please refer to the original for accurate details.
Subscribe to Newsletter
Get the weekly HCI highlights delivered to your inbox every Friday.