UI/UX Designer
User research questions
170 questions on User research for ui/ux designers, easiest first.
Easy 50
- A participant gets stuck during testingeasy
- What makes a persona usefuleasy
- Qualitative or quantitativeeasy
- Avoiding leading questionseasy
- What a journey map showseasy
- Recording a test sessioneasy
- Payment tasks in a testeasy
- Generative or evaluative researcheasy
- Spotting behavioural dataeasy
- Research question versus interview questioneasy
- What a screener is foreasy
- Why research participants are paideasy
- A participant wants to stopeasy
- What contextual inquiry meanseasy
- A main weakness of focus groupseasy
- Using silence in an intervieweasy
- Why have a separate note-takereasy
- Interviewing your own colleagueseasy
- Start with desk researcheasy
- Why interview stakeholderseasy
- Asking why more than onceeasy
- What a field visit addseasy
- What a Likert item iseasy
- A double negative in a surveyeasy
- Piloting a surveyeasy
- NPS score bandseasy
- What CSAT measureseasy
- Customer Effort Scoreeasy
- Working out a response rateeasy
- Adding an "Other" optioneasy
- Ranking or ratingeasy
- The list you sample fromeasy
- Random or convenience sampleeasy
- Too many required text boxeseasy
- Survey length and drop-offeasy
- A "Not sure" optioneasy
- Average of a skewed numbereasy
- Observation or insighteasy
- What thematic analysis doeseasy
- Using more than one sourceeasy
- The parts of an empathy mapeasy
- What a service blueprint addseasy
- Writing a "How might we" questioneasy
- Why keep a research repositoryeasy
- A quick debrief after each sessioneasy
- Naming participants in a reporteasy
- Why share video clipseasy
- What ResearchOps coverseasy
- Codes in qualitative analysiseasy
- A user's mental modeleasy
Medium 67
- How many users for a usability testmedium
- Reading an early A/B test resultmedium
- Jobs to be Done framingmedium
- Moderated or unmoderated testingmedium
- When to use a diary studymedium
- Fixing a survey questionmedium
- Making sense of research notesmedium
- Copy the competitormedium
- Usability tests with disabled usersmedium
- Planning for no-showsmedium
- Budgeting a recruited studymedium
- A screener that gives the game awaymedium
- The same faces in every studymedium
- Reacting to what participants saymedium
- Over-reported good habitsmedium
- Asking what people would paymedium
- Remote or in-person interviewsmedium
- Interviewing through an interpretermedium
- Knowing when you have enough interviewsmedium
- Asking about a memorable eventmedium
- Laddering in an interviewmedium
- What a research plan must statemedium
- Stakeholders who want to ask questionsmedium
- A participant goes off topicmedium
- Recruiting from your own customersmedium
- Quick research at a mallmedium
- Why people switch productsmedium
- Handling interview recordingsmedium
- People who agree with everythingmedium
- Calculating an NPSmedium
- Margin of error for 400 responsesmedium
- Responses needed for ±5%medium
- Halving the margin of errormedium
- Who did not answermedium
- Survey shown only after successmedium
- Asking current users why people leavemedium
- Order of answer optionsmedium
- Same answer down a gridmedium
- Weighting a skewed samplemedium
- Using quotas in recruitmentmedium
- Using skip logicmedium
- Prioritising 20 featuresmedium
- A Kano "must-be" featuremedium
- Finding the top tasksmedium
- Averaging Likert answersmedium
- Top-2-box satisfactionmedium
- Translating a survey into Arabicmedium
- Feature use and retentionmedium
- When to show an in-app surveymedium
- Inductive or deductive codingmedium
- Having a second person codemedium
- Personas made from assumptionsmedium
- Persona or market segmentmedium
- Reading an opportunity solution treemedium
- Storing research as nuggetsmedium
- Letting designers and PMs run researchmedium
- Diary entries drying upmedium
- User flow or journey mapmedium
- Aligning support with mental modelsmedium
- An actionable recommendationmedium
- Presenting to leadershipmedium
- Showing how sure you aremedium
- Studying change over timemedium
- Synthesising togethermedium
- Planning research for the quartermedium
- AI transcripts of Hinglish interviewsmedium
- Talking to customers every weekmedium
Hard 53
- The CEO wants a carouselhard
- Interviews and analytics disagreehard
- Sample size for a usability benchmarkhard
- Feedback only from power usershard
- The buyer is not the userhard
- Limits of heuristic evaluationhard
- They liked it but failedhard
- Consent for research recordingshard
- Personal ID shown on screenhard
- A demo at the start of interviewshard
- "60% of users" from five interviewshard
- Research with low-literacy participantshard
- Interviewing users who missed loan paymentshard
- A participant who knows the PMhard
- Recruiting from app store reviewershard
- Consent buried in the termshard
- Only the quotes that support the planhard
- Research with only one weekhard
- Scheduling research in Ramadanhard
- Why pilot an interview guidehard
- Asking about incomehard
- When research is not worth ithard
- People change when watchedhard
- Two segments want opposite thingshard
- Is a 10% vs 12% difference realhard
- An uneven 50/50 splithard
- Detecting a smaller effecthard
- A lift that fadeshard
- Twenty metrics, one winnerhard
- What a p-value of 0.03 meanshard
- Finding the leakiest funnel stephard
- A result that flips by segmenthard
- A dramatic result from a tiny segmenthard
- An NPS drop from 42 to 38hard
- Explaining a survey numberhard
- Designing subscription planshard
- A feature nobody seems to usehard
- Reading cohort retentionhard
- Measuring long-term impacthard
- Findings that nobody acts onhard
- Research that contradicts the roadmaphard
- Recordings found on a personal drivehard
- A quote that identifies someonehard
- AI-generated "synthetic users"hard
- Pasting transcripts into an AI toolhard
- Showing the impact of researchhard
- Testing an AI assistant before building ithard
- Personas that no longer fithard
- A study that was done beforehard
- Too many research requestshard
- Researching an app for childrenhard
- Research with screen reader usershard
- Research after a feature shipshard