Physician-Finder App Product Design: Segments, Pain Points, MVP and Metrics

Your task is to design an app for people who need to find a doctor. Walk the interviewer through who the app serves, which of their problems it solves, what you would build first, and how you would know it is working. ```hint Walk the whole journey Trace everything a person goes through between deciding they need a doctor and actually being seen, and look for the step where people most often give up or settle for a poor choice. ``` ### Clarifying Questions - Which market is this for? Insurance networks in the United States make the problem very different from a country with a national health service. - Is this a new standalone product, or part of an existing company's apps and services? - Does helping someone find a doctor include booking the appointment, or only choosing whom to see? - Should the app cover in-person visits only, or telehealth as well? ### What a Strong Answer Covers - Users segmented by their situation and need, with one segment chosen and justified - Pain points for that segment, prioritized by how often they occur and how badly they block care - A scoped first version, with reasons for what is left out - The supply side: why doctors and clinics would provide the data and availability the app depends on - Success metrics with guardrails, plus health-data privacy, accuracy and trust risks ### Follow-up Questions - How would you rank doctors in search results, and what would you never let payment influence? - After launch in one city, many searches return no doctor who can see the person soon. What do you change? - How would the design change if most users were booking care for an aging parent rather than for themselves?