Product Sense Case: Building a Babysitting Service Parents Can Trust

Design a product for babysitting. Decide what problem around arranging childcare it should solve and for whom, which features belong in the first version, and how you would know it is working. ```hint Who has to say yes? Think about everyone whose participation the product depends on, and what each of them must believe before a parent leaves a child with someone else. ``` ### Clarifying Questions - Is the product meant to connect families with sitters, to help a family coordinate care it already has (relatives, a regular nanny), or something else such as a monitoring device? - Are we solving for occasional care, such as an evening out or a last-minute need, or for recurring care such as daily after-school help? Is the care in the family's home? - Is this a standalone app, or should it build on an existing social platform and the connections people already have there? - Which market do we launch in? Background-check options, payment habits and labor rules differ by country. ### What a Strong Answer Covers - A chosen product scope and goal, justified against the other ways to read the prompt. - The groups involved (parents, sitters, children) and a reasoned choice of whom to solve for first. - Pain points in how families find, book and pay a sitter today, tied to prioritized features and a first version. - Safety and trust treated as core requirements, with their cost, friction and privacy trade-offs. - Success metrics and guardrails, plus a plan for having enough sitters when launching in a new area. ### Follow-up Questions - Sitters say the background check slows sign-up so much that many give up. How do you balance growth in sitters against safety? - Families and sitters who meet through the product start arranging repeat bookings privately. What would you do? - How would you launch in a new city where no sitters are on the platform yet?