Pick an App and a Data Plan for a New Google Device That Senses the Body

Suppose Google has just developed a new device that can sense information from the human body. As the product manager, decide what application you would build on top of it, and which kinds of body data that application should collect. ```hint Let the need pick the signals Choose the people and the problem first, then work back to the few body signals that problem actually requires. Each extra signal has a cost. ``` ### Clarifying Questions - What can the device measure, and how: is it worn on the body, placed near it, or used in a clinic, and how accurate and continuous are its readings? - Is the application meant to be a consumer wellness product, or a regulated medical one that makes diagnostic claims? - Will the device be sold to consumers, provided through doctors or insurers, or bundled with an existing Google product, and at roughly what price? - Is the goal adoption of the device, a new health business, or a showcase for the sensing technology? ### What a Strong Answer Covers - A survey of user groups and problems the sensing could address, and a reasoned choice of one. - The chosen users' pain points and an application whose features follow from them, prioritized into a first version. - A specific data plan: which signals, how often, what is derived from them, and what is deliberately left out. - Privacy, consent, data ownership, and the line between wellness features and medical claims. - Success metrics tied to a health or safety outcome, with guardrails such as false alarms and abandonment. ### Follow-up Questions - Your alerts produce many false alarms in the first month. What do you change, and how do you know the change worked? - An insurer offers to pay for devices if it can see the data. How do you respond? - How would your answer change if the device were contactless and sat in a room rather than being worn?