UX Research
41 bites tagged UX Research — interview questions with model answers, and 60-second explainers.
How do you reconcile conflicting qualitative stories with quantitative data?
Integrating mixed-methods without picking sides. A strong answer triangulates definitions, scope, and timing; uses qualitative context to explain outliers; and treats conflict as a signal to dig deeper.
Explain what a p-value represents in an A/B test and interpret 0.03
This tests frequentist hypothesis testing literacy. It is the chance of seeing a result this extreme if the null of no effect were true; 0.03 means 3% chance of such data under the null, not 97% chance the variant wins. Red flag: saying 97% likely.
How do you trace data points to journey map stages?
Tests auditable evidence chains for technical buy-in. Answer covers a traceability matrix linking quotes to stages and pain points, plus validation sessions where engineers inspect source data. Red flag: presenting the map as intuition without source docs.
Explain coding in qualitative analysis and your codebook process
Tests systematic tagging of observations/quotations to discover themes, not ad-hoc skimming. Strong answers mention uploading transcripts to software or affinity diagramming, and stress that themes emerge across multiple participants.
How do you mitigate confirmation bias when a user validates your solution?
In the moment, probe for exceptions; in synthesis, triangulate and invite reviewers. Self-awareness around confirmation bias in UX research.
Implement verifiable informed consent before a remote usability test
This tests whether you treat GDPR consent as an architectural gate. Strong answers cover CMP-powered pre-session disclosure, gating the test on active consent, server-side recording for auditability, and first-party data alignment.
How would you instrument a feature to validate qualitative findings quantitatively?
Mapping themes to events, picking guardrail and success metrics, and sampling. turning UX hunches into telemetry. generic analytics with no traceability to the original insight.
Describe a lightweight research method to validate a feature with no researcher
What it tests: bootstrapping validation without research headcount. Answer outline: unmoderated concept tests or concierge MVPs; behavioral vs attitudinal data; lightweight recruiting. Red flag: shipping A/B tests or using only internal opinions.
The 8 Pillars of ResearchOps
ResearchOps is the operating system behind scalable user research, not just scheduling. The 8 pillars map ops gaps like governance or tools. The footgun is treating it as a checklist to implement all at once rather than a diagnostic for triaging pain.
HIPAA in UX Research: Health Data as Hazardous Material
HIPAA in UX research treats health data as toxic: collect only what you need and de-identify fast. When interviewing patients or handling medical logs, treat every note as PHI. The footgun is dropping raw transcripts into consumer apps without a signed BAA.
Q-Methodology: Mapping Subjective Viewpoints
Q-methodology treats a person's viewpoint as the data. Clinicians track patient progress over time with it; researchers map how people think about a topic. The footgun is treating its findings as objective truth rather than captured subjectivity.
Localization Testing Validates Regional Adaptation
Localization testing verifies that regional adaptation accounts for differences in distinct markets. It validates the second phase of internationalization and localization, catching the assumption that translation alone is enough.
i18n Testing: Check Scripts, Not Just Strings
i18n testing checks your product works across languages, scripts, and cultures before shipping. It catches rendering and layout failures in Arabic, Hebrew, Chinese, Japanese, or Korean contexts.
ResearchOps Maturity Matrix: Built for Operations
UX maturity scores insights; ResearchOps maturity scores the factory producing them. Use it to audit governance, participant pipelines, and tooling strategy. The mistake is judging research quality instead of operational infrastructure.
T-test: Are Two Groups Actually Different?
A t-test asks whether the gap between two groups is a real signal or just sampling noise. UX researchers use it to compare task times or conversion rates between designs. The footgun is trusting results from tiny samples where the math gives false confidence.
Normal Distribution: Two Parameters, One Bell Curve
A normal distribution is a bell curve for real-valued variables, defined by mean and standard deviation. Use it when values cluster around a center. The footgun is forcing normality on skewed or bounded data, which corrupts the probability density.
Insight Statements: Frame Problems, Not Solutions
Insight statements frame what users must achieve, not how. Teams use them in design thinking's define stage to align on the right problem before ideating. The footgun is writing solutions like 'needs a dashboard' instead of goals like 'needs to compare'.
Get UX Research bites daily.
Five a day, five minutes, offline. With quizzes so it sticks.
Open testing — you’ll join as an early tester.