User research
36 bites tagged User research: interview questions with model answers, and 60-second explainers.
Test yourself: Top 30 User research interview questions →Multiple choice, with the correct answer and why it is correct on every question. Free, no sign-in.How do you synthesize low-level codes into high-level themes?
Tests systematic thematic analysis. Strong answers cover tagging observations with codes, grouping related findings into themes that emerge across participants, and choosing methods like affinity diagramming based on context.
What is the goal of contextual inquiry and what do engineers gain?
Tests grounding engineering in observed user behavior. Goal: watch users in their environment to uncover tacit work practices, workarounds, and mental models. Engineers learn system constraints, integrations, and reliability gaps.
Propose a strategy for finding and vetting low-incidence participants
This tests sourcing creativity and screening rigor for rare populations. A strong answer proposes niche outreach, snowball referrals, behavioral screeners, and anti-fraud checks. A red flag is simply boosting spend on generic panels or relying on coworkers.
What two techniques mitigate professional-tester bias in screener design?
Swap guessable questions for behavioral ones about real tasks, and add exclusion criteria to block web-savvy professional testers.
Research Incentives: Pay for Time, Not Opinions
Research incentives repay time, not buy opinions. Pay enough to respect schedules without pressuring people to enroll or fake answers. The footgun is overpaying, which attracts participants who need the money and biases your data.
Threat Modeling UX Research for Vulnerable Populations
Research with vulnerable populations is threat modeling: standard methods can harm people with diminished autonomy or trauma. Use these guardrails for disabilities, low literacy, or desperation. Never treat a signed consent form as proof of understanding.
Anonymity vs. Confidentiality in UX Research
Anonymity severs the link between data and identity; confidentiality hides that link under lock and key. Use anonymity for sensitive surveys and confidentiality for follow-up studies. The footgun is claiming anonymity while keeping names or emails on file.
Recruiting Participants Who Mirror Real Users
Bad recruiting kills research before the first question. Recruit people currently doing the behavior you study, not just matching demographics. The footgun is using convenience samples like staff or friends, who know your product and give false signals.
UX Research Plan: Alignment Before Fieldwork
A UX research plan is a pre-fieldwork contract that locks in what you must learn and how success is judged. It stops stakeholders from moving goalposts after interviews begin. The footgun is filing it away unread; a plan nobody references is just bureaucracy.
Informed Consent in UX Research
Informed consent is the ethical line between a casual chat and research abuse. Once you record, transcribe, or share participant data, you need explicit permission. The footgun is treating a friendly call as private when your notes permanently expose it.
Research Tool Stack Management
A UX research tool stack is your standardized toolkit, not a random app collection. It speeds up projects and helps onboard teammates through ResearchOps. Picking tools before you know your research question forces methods to fit software instead of problems.
Informed Consent Is Comprehension, Not Paperwork
Informed consent means understanding risks and alternatives before agreeing. It applies whenever researchers collect sensitive data or expose people to risk. The footgun is treating a signature as proof of understanding; comprehension beats paperwork.
Experience Sampling: In-the-Moment User Reality
ESM captures in-the-moment states before memory distorts them. Use it when you need longitudinal data on behavior fluctuations, not just recalled summaries. The footgun is delay: even brief lag lets participants reconstruct instead of reporting experience.
Critical Incident Technique: Story Mining
Skip asking what users want; ask for the exact moment something went great or terribly wrong. Researchers use this to pinpoint interactions that make or break an experience. Teams collect vague feedback instead of concrete stories with clear context.
ResearchOps: The Pit Crew for User Research
ResearchOps is the backstage crew that makes user research scale. It provides roles, tools, and processes so researchers focus on insights, not logistics. Teams often assume researchers self-manage operations, which bottlenecks research as companies grow.
Differentiate functional and non-functional requirements with user research examples.
This tests separating specific behaviors from measurable quality criteria. A strong answer defines functional requirements as behaviors and non-functional requirements as quality attributes with examples. A red flag is vague NFRs like fast.
NPS for Design Systems: Smoke Alarm, Not Scorecard
NPS for design systems is a smoke alarm for team trust, not a feature scorecard. Poll consuming teams quarterly to catch sentiment drops before adoption stalls. Never benchmark against consumer SaaS; internal tools face forced usage and different expectations.
The Kano Model: Not All Features Are Created Equal
The Kano Model classifies features by their impact on user satisfaction, separating "must-haves" from "delighters." Use it in product planning to prioritize impactful work. The footgun is misclassifying a novelty as a core need, starving basic functionality.
Heatmaps: Visualizing User Attention
Think of a heatmap as a weather map for your app, showing 'hot' spots of user clicks and 'cold' spots they ignore. It reveals if users are clicking key buttons or getting distracted. The footgun: a hot spot can mean rage-clicks, not just engagement.
Think Aloud Protocol: Hear Your User's Inner Monologue
See your product through a user's eyes by having them narrate their thoughts live during a task. It's used in usability testing to uncover confusion, mismatched expectations, and the "why" behind clicks.
UX Research Incentives: How Much to Pay Participants
Think of research incentives as an investment in data quality, not just a cost. For a 60-minute interview, budget $75-150 for consumers or $200-500 for specialists. The footgun is underpaying: you'll get poor data and waste everyone's time.
UX Sampling: Convenience vs. Probability
Convenience sampling is fast and cheap—ask whoever is easy to reach. Probability sampling is rigorous—ask a random slice of your population. Use convenience for quick usability tests, but probability for high-stakes decisions.
Card Sorting: Let Users Design Your Navigation
Card sorting reveals your users' mental models by having them group topics. Use this to design intuitive navigation menus and information architecture. The footgun is testing with internal teams instead of actual users or subject matter experts.
Continuous Discovery: Talk to Users Weekly, Not Yearly
Continuous discovery means small, weekly chats with customers, not a big upfront research phase. It's for teams building products that are never 'done,' like Netflix or your SaaS app. The footgun is treating discovery as a project, leading to stale insights.
Get User research bites daily.
Five a day, five minutes, offline. With quizzes so it sticks.
The iPhone app is on the way
We are building it. Until it lands, nothing here is held back from you: every interview card, your saved cards, streaks and the job board all work in Safari, plus hundreds of free practice quizzes of thirty questions each. Sign in and it all carries over to the app the day it arrives.
Want it as an icon? Tap Share at the bottom of Safari, then Add to Home Screen. It opens full screen and the cards you have read stay available offline.