A product designer recently showcased a prototype aimed at tracking gratitude journaling streaks, complete with eye-catching animations. However, when she tested it with users, their feedback revealed a disconnect: most didn’t journal at all, and some found the concept performative. This highlighted a significant issue in her approach—she spent two weeks constructing something users didn’t want or need. This process, termed "need-finding," was misapplied. True need-finding involves listening to users talk about their experiences and frustrations before any solution is developed, rather than jumping to validate a pre-formed idea. The article criticizes "vibe-coding," a method where developers quickly create prototypes based on their vision, which can lead to a false sense of progress. It argues that real progress comes from engaging directly with users. To do this effectively, one should conduct interviews as conversations, focusing on follow-up questions that dig deeper into user experiences. The author recommends listening actively without pitching ideas until a clear understanding of user pain points is established. Defining the right problem is crucial. For user experience (UX), it’s about identifying issues that users genuinely care about. In product development, it involves recognizing problems people will pay to solve. For businesses, it’s finding a problem that aligns with their capabilities and brand. The article emphasizes that a problem meeting all these criteria is uncommon, making the time spent on proper need-finding essential before diving into the build phase. A well-crafted prototype that fails to address a legitimate user need is ultimately wasted effort.