Smart footwear product design: choose users, the problem and a first version

You are a product manager asked to create a smart shoe. Decide what "smart" should mean, who the shoe is for and which of their problems it solves, then propose a first version, prioritize its features, and explain how you would know whether it is succeeding. ```hint Start from the foot Ask what a shoe can sense or do that a phone or a watch cannot, and which group of people has a problem that only that capability solves well. ``` ### Clarifying Questions - Who is building it: a footwear brand adding technology, a technology company entering footwear, or a startup? - Is the goal adoption of a new product category, revenue from the hardware, or engagement with a wider platform the shoe connects to? - Does "smart" have to mean sensing and software, or can it include shoes that adjust physically, such as self-tightening laces? - Are there limits on price or target market, and should the shoe work with a companion phone app? ### What a Strong Answer Covers - A working definition of "smart" and a goal for the product, tied to who is building it - Several user segments compared, with one chosen and the reason for the choice - That segment's pain points, and why a shoe rather than an existing device is the right form to address them - Prioritized features for a first version that respect hardware limits such as battery life, durability, washing, comfort, sizing and cost - Success metrics with guardrails, and the main risks, including the privacy of body and location data ### Follow-up Questions - Shoes wear out much sooner than electronics do. How does that shape your design and business model? - How would you test demand before building the hardware? - What would make you expand to a second user segment, and which one would it be?