You are a new PM at Google. Design a wearable for children.

• Clarification -
  • Children age group is 5-19?
  • Is there a price range we are looking at? Maximum device price of <= 200$ - Children so they don’t want to get expensive stuff as that might get more unwanted attention
  • Only wearable or does it have another device to be paired? Single device only
  • Geos: US/Europe
  • Goal: Adoption, selling units at the beginning
• There are multiple wearable devices - glasses, watches, bands.
  • Glasses are obtrusive and children might not want to wear it as it might hamper with their play activities
  • Watches and Bands are less obtrusive
• There are a few pain points and use cases I can think of when I imagine of kids and wearables
  • Children lose it by keeping at different places
  • Hesitancy to wear it and might keep it off somewhere and wear when parents are near
  • Might forget to charge
  • Other pain points I can think of can be bucketed into
    • Safety
      • Children can wander away and get lost
      • Strangers can come and talk
      • Might get anxious when in different surroundings
    • Eating habits - allergy
      • Might be more prone to eating junk
      • Might eat something they are allergic to
    • Study Habits
      • Might get too engrossed in playing

• Foundational elements of the Solutions:

Giving a high level view of the foundational elements and then going to prioritize based on the adoption criteria vs effort involved vs cost.

There is also a software component to the wearable device that stores all the data that the wearable collects in the cloud.

Ability to make calls to certain numbers - 911, parents phone from the device.

Lack of Bluetooth to save costs - all data uploaded to cloud and an app to view the data.

A mobile transceiver and data connection with a SP

• Solutions for the pain points and effort involved
  • Tracking for the device - An app that can trigger ringtones from the cloud on the phone. Effort - Low, Impact - Low to medium, Cost involved - Low. Must have for adoption initially - good to have
  • Hesitancy to wear - Make it fun - cases and designs targeting the contemporary things in the world at that. Effort - Can be in house or partnerships. At the beginning in house and then partnership for wider options. Costs - Manufacturing costs incremental, can also be priced at a higher premium. Effort - Low, No S/W effort. Adoption - Medium to high. Must have for adoption
  • Might forget to charge - For initial release just a beeper at parents device. Later can incorporate solar/heat charging etc. Effort - Low, Not an Important feature to have for first release
  • Safety
    • Panic button - Call to 911, parents phone. Must have. Automatically sends location data, nearby picture and video information.
    • Location - GPS to send periodic location coordinates. Must Have
    • In build camera in the device to take a 360 degree view video and picture. Cost of a 360 degree camera is 40$ (based on a startup I worked on). Feature - Must have, Effort - S/W costs, mostly open source audio/video encoding, processing costs low as in cloud.
      • First release - Manually turning on via parents device or by the child.
      • Next releases - Can be auto recording based on new sounds, people, panic (heartbeat), pulse rate
  • Eating:
    • Camera can be used to identify allergy contents and ability to input allergy items into the app - Effort - Medium. Good to have
    • Calorie counter/Junk eating counter
  • Study reminder:
    • Ability to input school schedules and homework in the cloud. Effort - Low, Impact - High. To actual buyer Parents, after the first release
    • Tracks # of hours played outside, video games and calculates the hours studied etc. Effort Low as most is data collection through the device sensors , Impact - High to actual buyer - parents after first release
• Metrics:
  • Awareness - Pre launch efforts
    • # of organic searches
    • Site visits
    • Based on advertising medium - # of impressions
  • Acquisition
    • # of purchases over a period of 30 days
    • # of app downloads
  • Engagement
    • # of profile creations
    • # of cloud account setups
    • Recharge % amongst users - how many of them recharge regularly.
    • Usage past the first 30 days - first 30 days generally show higher engagement because of the new toy phenomenon. Continued usage to be tracked
    • Customer reviews, feedback
• Not focusing on the referral/revenue during the first phase

Summary