Product Sense: Create a Car Stereo That Solves a Real Driver Problem

You are the product manager for a new car stereo. Work out who the stereo is for and which of their problems it should solve, propose what it does, choose what goes into the first version, and explain how you would judge whether it is succeeding. ```hint Ride along Follow one driver from getting into the car to parking at the destination, and note each moment they reach for the stereo or their phone, and why. ``` ### Clarifying Questions - Who builds and sells it: a startup selling units that drivers install in cars they already own, an established electronics or tech company, or a car maker fitting it at the factory? - Does "car stereo" mean only audio, or the whole dashboard unit, including calls, navigation and vehicle settings? - Which market and which vehicles are in scope: personal cars only, or also fleets such as rideshare and delivery? - Is there a target price band, or should the price follow from the segment chosen? ### What a Strong Answer Covers - A scoped definition of the product, who builds and sells it, and the goal it serves - Driver or buyer segments compared, with one chosen and the reason for the choice - Pain points from that segment's time in the car, ranked, separating what a stereo can fix from what phones and cars already handle well - Features prioritized by impact, effort and their effect on driver distraction, with a first version defined - Success metrics with guardrails, and the main risks to the product ### Follow-up Questions - Phones already handle music, maps and calls. Why would someone buy your stereo instead of a phone mount, and how would you test that before building it? - How would your design change if a car maker wanted it fitted at the factory rather than sold to drivers? - How do you keep new features from adding distraction while the car is moving?