In-vehicle television product design: target users, core use cases and a first version

You are a product manager asked to design a TV meant to be used in a car. Decide what the product is and who it is for, work out what those people need from it, propose and prioritize what goes into a first version, and explain how you would judge whether it succeeds. ```hint Start with who is in the car List the people who could watch a screen in a vehicle and when each of them could safely do so, then compare their needs before you commit to one group and its features. ``` ### Clarifying Questions - Is this a screen a carmaker builds into new vehicles, or a standalone device that owners buy and fit to the car they already have? - Which vehicles are in scope: private cars, taxi and ride-hailing fleets, long-haul trucks, or cars that can drive themselves? - Does "TV" mean live broadcast channels only, or any video, including streaming services and content sent from a phone? - Which markets do we launch in, and what rules there limit video that the driver can see while the vehicle is moving? ### What a Strong Answer Covers - A settled product form and a goal for it, agreed before any features - Candidate user groups compared by who would watch, when and why, with one chosen and the reason for the choice - Constraints of the vehicle treated as requirements: driver distraction, a shared cabin, glare and heat, power, and patchy connectivity - A clear reason someone would use this rather than a phone or tablet they already own - Solutions ranked on explicit criteria into a scoped first version, with success metrics, guardrails and the main risks ### Follow-up Questions - How would your design change for a car that drives itself, where the person in the driver's seat is free to watch? - How would you test demand cheaply before committing to building hardware? - If early data showed that most viewing came from content cast from phones, what would that tell you, and what would you change?