Product Sense: Diagnose a Low-Tech Product That Let You Down and Improve It

Think of an everyday low-tech product, one with little or no software in it, that gave you a frustrating experience. Walk me through what happened and why the product let you down. ```hint Separate the moment from the cause Start from the exact moment it went wrong, then name the design property behind it, and ask what pressure on the maker produced that design. ``` ### Clarifying Questions - Does "low-tech" mean purely mechanical items such as a stove knob or a can opener, or do simple electronics such as a hotel alarm clock or a parking meter count? - Should I finish with a redesign, or does the interviewer mainly want my diagnosis of the failure? - If I propose fixes, should they stay low-tech and cheap to make, or may I add software or connectivity? ### What a Strong Answer Covers - A specific failure moment tied to the job the user was trying to get done - A diagnosis in design terms (affordance, mapping, feedback, error recovery) and whether the problem affects many users or only the candidate - The constraints that plausibly led the maker to this design, such as unit cost, safety rules, manufacturing or a buyer who is not the user - Prioritized improvements that respect those constraints, with a way to check that they worked ### Follow-up Questions - If every fix raised the unit cost, which one would you ship first, and why? - How would you find out whether other people hit the same problem before changing the design? - Would adding software actually fix this product, or would it introduce new ways to fail?