Product Design Case: Reinventing the Everyday Alarm Clock

Design an alarm clock that improves on what people use today. You decide who it serves, which problem it fixes and what form it takes. ```hint Look at the whole morning Map everything from setting the alarm the night before to actually being up and moving, then find the step where today's alarms let people down most. ``` ### Clarifying Questions - Is this a physical bedside device, an app such as the phone's built-in clock, a feature on a watch or smart speaker, or is the form factor ours to choose? - Should it build on Google's existing devices and services, or stand on its own? - What does success mean for the business here: selling a new device, more use of an existing app, or making the company's devices work better together? - Is there a particular group of sleepers in mind, or is choosing one part of the exercise? ### What a Strong Answer Covers - A chosen user segment and the specific waking problem it has, justified against other segments - Pain points across the full routine, not only the moment the alarm rings, with an honest look at what existing alarms and sleep products already do - Solution ideas compared and prioritized into a first version, with what is deliberately left out - Success metrics that capture waking outcomes, plus guardrails - Risks specific to alarms, such as a wake-up that silently fails, sleep data privacy and other people in the room ### Follow-up Questions - An alarm that fails to ring can make someone miss a flight or a shift. How would you make reliability a requirement, and how would you test for it? - How would you test demand before committing to new hardware? - How would you know people actually wake up better, rather than just using the new features?