Product Manager
Product discovery questions
182 questions on Product discovery for product managers, easiest first.
Easy 59
- A stakeholder brings a feature ideaeasy
- What is an MVPeasy
- A good customer interview questioneasy
- A good problem statementeasy
- The core idea of Jobs to be Doneeasy
- Using support ticketseasy
- Testing before buildingeasy
- Cutting scope for an MVPeasy
- Jobs to be doneeasy
- The four big product riskseasy
- Asking about real past behavioureasy
- Notes that only support the ideaeasy
- Who is in the product trioeasy
- Discovery and delivery side by sideeasy
- Observation or insighteasy
- The job story formateasy
- What each research type answerseasy
- Interviewing only happy userseasy
- Spot a concierge MVPeasy
- Customers asking for featureseasy
- Why use an interview guideeasy
- What a screener doeseasy
- The say–do gapeasy
- Research in the user's own settingeasy
- What a Wizard of Oz test iseasy
- A smoke testeasy
- The right prototype for a rough ideaeasy
- A hypothesis you cannot checkeasy
- Taking pre-orderseasy
- How many users for a usability testeasy
- What card sorting is foreasy
- What tree testing checkseasy
- Working out NPSeasy
- The "very disappointed" testeasy
- The "aha" momenteasy
- Moderated or unmoderated testingeasy
- Why the first click matterseasy
- A five-second testeasy
- Why keep a control groupeasy
- A Kano delightereasy
- What an impact map connectseasy
- The double diamondeasy
- Why "How might we" questionseasy
- Length of a design sprinteasy
- The customer side of the value proposition canvaseasy
- What the lean canvas addseasy
- A useful personaeasy
- What a journey map showseasy
- An empathy mapeasy
- Outcome or outputeasy
- Problem space or solution spaceeasy
- The two axes of an assumption mapeasy
- IDEO's three lenseseasy
- What a service blueprint addseasy
- Learning from app store reviewseasy
- Asking users in the momenteasy
- Open or closed survey questionseasy
- Asking why people canceleasy
- Product–market fiteasy
Medium 72
- A sudden drop in sign-upsmedium
- Reading retention curvesmedium
- Opportunity solution treemedium
- Which assumption to test firstmedium
- A fake door testmedium
- Opportunity solution treesmedium
- A worry about switchingmedium
- "Our Excel works fine"medium
- Who to recruit for a switch interviewmedium
- Fixing a leading questionmedium
- Asking "how much would you pay?"medium
- The strongest signal of demandmedium
- Enough interviews for nowmedium
- Clustering notes from interviewsmedium
- Capturing each interview quicklymedium
- When to run a diary studymedium
- Why triangulate findingsmedium
- The risk of a focus groupmedium
- Helping during a usability taskmedium
- Thinking aloud in a testmedium
- Buyer and user are different peoplemedium
- Recording customer callsmedium
- Answers that sound goodmedium
- What a workaround tells youmedium
- Using the customer's own wordsmedium
- Sales picks the intervieweesmedium
- Wizard of Oz versus conciergemedium
- When to set the pass markmedium
- Clicks from the wrong audiencemedium
- NPS from raw countsmedium
- Scoring a SUS questionnairemedium
- Who should get the PMF surveymedium
- Defining activationmedium
- Testing whether it can be builtmedium
- Limits of a clickable prototypemedium
- Picking the cheapest good testmedium
- Twelve versus nine sign-upsmedium
- Stopping a test at first significancemedium
- A spike that fadesmedium
- Margin of error for a surveymedium
- A survey question asking two thingsmedium
- Where the funnel leaks mostmedium
- Overall retention hides progressmedium
- Using session recordingsmedium
- Only testing with your own teammedium
- Digging past the first reasonmedium
- A feature that annoysmedium
- Yesterday's delightermedium
- Why talk to extreme usersmedium
- Spotting a solution in an opportunity treemedium
- How many solutions per opportunitymedium
- A well-scoped "How might we"medium
- Calculating an opportunity scoremedium
- Which outcome is more under-servedmedium
- A product outcome for the teammedium
- Personas made in a meeting roommedium
- Where a journey map points youmedium
- Sizing a market from the bottom upmedium
- Top-down or bottom-up sizingmedium
- What happens on day fivemedium
- A real unfair advantagemedium
- Assumption types beyond the usual threemedium
- Running a pre-mortemmedium
- How often to talk to customersmedium
- From request to opportunitymedium
- A social jobmedium
- Searches that find nothingmedium
- Running a customer advisory boardmedium
- Accessibility in usability researchmedium
- Reading a rival's one-star reviewsmedium
- Too few users for an A/B testmedium
- Using AI to summarise interviewsmedium
Hard 51
- Daily active users are fallinghard
- One customer shouting loudesthard
- Interviews disagree with the datahard
- Research only in big metroshard
- "We need a faster report"hard
- An interview that turned into a pitchhard
- Learning from people who chose a rivalhard
- Users love it, the deal stallshard
- Discovery for an AI summary featurehard
- One person does all the synthesishard
- Ranking problems by how often they come uphard
- Remote calls or field visitshard
- A generous incentive for testershard
- Why keep a research repositoryhard
- Running research in the Gulfhard
- Showing the prototype too earlyhard
- How many users an A/B test needshard
- A result just under the barhard
- A Wizard of Oz test that never endshard
- Automating a concierge servicehard
- Easy to use, but not wantedhard
- A pilot that was too friendlyhard
- A demand test on WhatsApphard
- Up overall, down in every grouphard
- Customers love it, but can it pay?hard
- Five users for a benchmarkhard
- A test with no way to failhard
- Collecting money for a product not builthard
- A before-and-after during Ramadanhard
- Watching what else could breakhard
- Forcing the activation actionhard
- Marketing a feature everyone hashard
- An opportunity tree full of featureshard
- A sprint with no deciderhard
- A real problem, but not worth solvinghard
- Leadership hands you a solutionhard
- "If we get just 1% of India"hard
- An "average" personahard
- A redesign already in flighthard
- Choosing the wrong outcomehard
- Revenue at risk from one problemhard
- A nudge that works too wellhard
- Regulation as a discovery riskhard
- The real competitor is doing nothinghard
- Two segments, one roadmap slothard
- 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
- When a different segment loves ithard