Product Manager
User research questions
66 questions on User research for product managers, easiest first.
Easy 21
- A good customer interview questioneasy
- The core idea of Jobs to be Doneeasy
- Why add qualitative researcheasy
- When to use a heatmapeasy
- Watching session replayseasy
- Requests versus usage dataeasy
- Notes that only support the ideaeasy
- Observation or insighteasy
- The job story formateasy
- What each research type answerseasy
- Interviewing only happy userseasy
- The say–do gapeasy
- Research in the user's own settingeasy
- A useful personaeasy
- What a journey map showseasy
- An empathy mapeasy
- What a service blueprint addseasy
- Learning from app store reviewseasy
- Asking users in the momenteasy
- Open or closed survey questionseasy
- Asking why people canceleasy
Medium 27
- Opportunity score from a surveymedium
- The Buy a Feature gamemedium
- Who answers the NPS surveymedium
- A worry about switchingmedium
- "Our Excel works fine"medium
- Who to recruit for a switch interviewmedium
- Clustering notes from interviewsmedium
- Capturing each interview quicklymedium
- When to run a diary studymedium
- Why triangulate findingsmedium
- The risk of a focus groupmedium
- Recording customer callsmedium
- Answers that sound goodmedium
- What a workaround tells youmedium
- Using the customer's own wordsmedium
- Sales picks the intervieweesmedium
- Margin of error for a surveymedium
- A survey question asking two thingsmedium
- Using session recordingsmedium
- Only testing with your own teammedium
- Personas made in a meeting roommedium
- Where a journey map points youmedium
- Assumption types beyond the usual threemedium
- A social jobmedium
- Searches that find nothingmedium
- Running a customer advisory boardmedium
- Using AI to summarise interviewsmedium
Hard 18
- One customer shouting loudesthard
- Interviews disagree with the datahard
- Research only in big metroshard
- "We need a faster report"hard
- One person does all the synthesishard
- Ranking problems by how often they come uphard
- Remote calls or field visitshard
- Showing the prototype too earlyhard
- A pilot that was too friendlyhard
- Collecting money for a product not builthard
- An "average" personahard
- A nudge that works too wellhard
- The real competitor is doing nothinghard
- Discovery when users are colleagueshard
- AI "synthetic users" instead of interviewshard
- Pasting interviews into an AI toolhard
- "Too expensive" in exit surveyshard
- Who answers an in-app surveyhard