TOPIC
Product discovery
These are the same questions found in the library, grouped here by the capability each one mainly examines.
49 questions
A · Professional problem solving and implementation12
- A core flow passes mouse testing, but keyboard or screen-reader users cannot complete it. How would you include accessibility in release gates?
- A workspace contains hundreds of items that people find by customer, status, owner, or date. Its navigation follows the company org chart, so users struggle to find things. How would you reorganize it and test findability?
- Different teams own creation, editing, and review, and their form feedback is becoming inconsistent. How would you decide which patterns to standardize and which to keep distinct? How would you check loading, empty, error, and recovery states?
- A study was commissioned to validate a new dashboard. Most users say current reports are sufficient; a few advanced users want more. The project lead wants to highlight supportive interviews. How would you summarize the findings?
- In research for a new feature, a small group of frequent users strongly supports the concept, while novice participants repeatedly fail the core task and the analytics show no clear difference. How would you interpret what each piece of evidence can tell you and decide whether to proceed, revise, or run more research?
- In a usability session, the moderator repeatedly asks whether the design is clearer, and users agree. Video shows repeated hesitation during tasks. How would you handle the evidence and next study?
- Interview participants are almost all power users and community members. Feedback on the latest redesign is positive, but retention continues to fall. How would you redesign recruitment and research questions?
- During user interviews, people repeatedly suggest buttons, filters, and reminders but rarely describe their goals or blocked situations. How would you adjust question order and wording to distinguish real experiences, stated preferences, and proposed solutions?
- The team believes a new flow is simpler, but usability tests show only familiar users succeed; newcomers get stuck on permission explanations and next steps. How would you recruit, design tasks, and define observations to judge whether it is actually usable?
- Researchers can recruit only active users but need to understand why occasional or churned users leave. How would you identify sample bias, adjust recruitment, and limit the reach of conclusions?
- A feature targets people who have never used the product, but all usability participants are core users. Which design decisions can the current evidence support?
- Review feedback centers on “not premium enough” or “I dislike this color,” but the team has no shared user goal. How would you run the next review?
No questions in this section match your target. ·
B · Business understanding and domain modeling4
- Besides your product, what else could users do to get the same job done? What does each alternative compete for, and when is it actually the better choice?
- Teams define “done,” “awaiting acceptance,” and “paused” differently, distorting roll-up data. How would you design a shared state model and transition rules?
- A user can belong to several organizations and hold different roles in each. How would you model identity, membership, and permissions without conflating accounts with business roles?
- Administrators want all data on the settings page, while members need only task information. How would you define a common information structure and role-specific presentation?
No questions in this section match your target. ·
C · Value judgment and direction setting20
- Visits and registrations are growing, but match success is falling. Demand concentrates in a few regions while suppliers are scattered. How would you find the liquidity bottleneck and choose where to invest first?
- A major customer will pay a high price for a custom feature, but reuse by other customers is uncertain. Ongoing maintenance, permissions, and data rules add cost, and sales has promised a delivery date. How would you compare a one-off build, productizing it, a service, or declining—and decide whether to invest?
- Interviews and support tickets repeatedly mention the same problem, but few users in a pilot are willing to change their current workflow. How would you determine whether the issue is how the need was expressed, switching cost, target-user selection, or problem priority?
- You inherit a mature product with a stable user base and stalled growth, and the team wants to launch new features immediately. What product understanding would you build in the first two weeks before deciding where to invest?
- A major competitor makes a feature free that large customers have repeatedly requested, but you have not observed customer losses because of it. How would you determine whether this is an emerging competitive risk, a negotiation signal, or a feature gap not worth following?
- A feature is used often but has not improved retention or payment. How would you determine whether it creates core value, reflects habit, or rewards the wrong behavior?
- Overall conversion improves, but new users and low-connectivity regions worsen. How would you examine segmentation, selection bias, and problems hidden by the aggregate?
- After several teams optimize the same north-star metric, duplicate content and low-quality interactions appear. How would you diagnose metric distortion and adjust guardrails?
- A design-research team has two researchers, while three product lines want critical interviews this month. One decision is irreversible; another can start with low-cost data. How would you allocate capacity?
- Retention rose during a marketing campaign, and the team credits the channel, but a new product flow also launched and participants may already have been more active. How would you establish a credible comparison, estimate the campaign’s net lift, and state the limits of the conclusion?
- The request is 'add an Export to Excel button to the order list page.' Show how you move from the surface request to the user's behavioral obstacle, and then to the value outcome.
- A colleague proposes adding a settings switch to a feature. Before discussing how to build it, which questions would you ask to judge whether the switch is worth building?
- Overall onboarding conversion falls. The funnel shows the most exits at address verification, but support records point to identity checks. How would you choose research and fix priorities?
- After a redesign of an important flow, the expected completion rate does not improve. Support requests decline, existing users respond more positively, but new users behave worse. How would you check metric definitions and user segments, determine what effect the design had, and choose the next action?
- Analytics show target users skipping the product's main flow and using exports, spreadsheets, or manual coordination instead; the team believes this is a user-habit problem. How would you decide whether the product conflicts with real work practices?
- Task completion reaches 95%, but half of users rely on support or colleagues. The team plans to use completion as its launch-success metric. What would you add?
- Search returns hundreds of records, yet users repeatedly combine filters and export to spreadsheets. How would you distinguish retrieval, ranking, task understanding, and result explanation problems?
- A key customer wants to skip an approval step to speed up processing, but other roles rely on approval records for audits. How would you assess local efficiency and system risk?
- Customers keep asking for options, and support teams use flags as workarounds. How would you distinguish stable needs, temporary exceptions, and a broken product abstraction?
- High-value customers want more approvals, everyday users want fewer steps, and internal teams want extra checks. How would you return to the shared task and decide what to validate first?
No questions in this section match your target. ·
E · Collaboration, communication, and influence2
- A research team wants broad exploration and user access, but only two weeks remain and the business needs one key decision. How would you negotiate scope?
- Research finds users struggle at a critical step, but engineering and operations see change as too costly. How would you get the evidence discussed and turn it into action?
No questions in this section match your target. ·
F · People and organization building1
G · Learning, adaptation, and sustained growth9
- A study finds users often misunderstand status messages in a form. How would you tell whether this is local or a transferable design principle?
- You move from consumer products to enterprise software with different user roles, buyers, and contexts. How would you adapt your interview method?
- Prototype testing was positive, but adoption is low after launch. How would you examine research context, participant selection, and implementation differences?
- The team produced several visual concepts, but users still struggle with the core task. How would you assess the exploration direction, problem definition, or validation?
- The team adopts many review suggestions, making the interface more complex without retesting user tasks. How would you review feedback handling?
- A recruiting partner cancels planned research, but the team still must decide on a key experience. How would you recover and find credible alternative evidence?
- A major review rejects a direction you spent weeks on because user evidence is weak. How would you process feedback and decide what to explore next?
- The roadmap has no experience work, but user feedback shows persistent confusion in a flow. How would you decide whether to explore proactively?
- The team plans to serve a new user group with no immediate research budget. You own design and do not want to reuse old patterns blindly. How would you begin?
No questions in this section match your target. ·
H · Professional responsibility and work style1
No questions in this section match your target. ·