Connected Door Lock as a Google Home Product: Users, Features and Metrics

Design a smart lock as a Google product. Decide who it is for, which problems it should solve, which features come first, and how you would know it succeeded. ```hint Look past the owner The person who installs a lock is rarely the only one who uses the door. Think about everyone who needs to get in, and the moments when ordinary keys fail them. ``` ### Clarifying Questions - Is the lock meant for home front doors, or could it also target hotel rooms, offices or vehicles? Is the segment my call? - Should it work with Google's existing smart-home products, such as the Google Home app, Assistant and Nest cameras and doorbells, or stand alone? - Should it suit renters who cannot replace their lock, or only owners who can install new hardware? - Is Google after hardware revenue, growth of its smart-home ecosystem, or both? ### What a Strong Answer Covers - A deliberate choice among homes, rentals, hotels and businesses, with the reason the others wait - Concrete door-access pain points for the chosen users, including people other than the owner - Prioritized features with fallbacks for dead batteries, lost connectivity and people without phones - Success metrics with guardrails for lockouts, security incidents and privacy - The security, privacy and trust risks of Google holding a record of who enters a home ### Follow-up Questions - Would you put a fingerprint or face reader on the door? How would you handle the biometric data? - How would the product change if you targeted hotels instead of households? - A security researcher publishes a way to unlock the lock remotely. What do you do first, and how do you rebuild trust?