The author reflects on the evolution of the "Picnic" over the past year and highlights a pressing issue in the industry: the importance of problem design. With the rise of large language models (LLMs), many roles in tech are shifting toward output generation at the expense of critical thinking. Programming, once a secure domain, is also facing this shift. The focus has moved from genuinely understanding customer needs to producing solutions that sound appealing but lack depth, leading to a commodification of outputs. Users are increasingly frustrated with products that seem designed to maximize their annoyance rather than provide real value. The article argues that defining the problem correctly is essential for effective strategy and product design. Efforts to solve poorly defined problems result in wasted resources and unsatisfactory user experiences. The author emphasizes a collaborative approach to problem design, where teams articulate solutions without relying on technology and consider the behavior changes they aim to achieve. The piece stresses the importance of understanding the core issues that customers face and suggests that businesses should prioritize problems people are willing to pay to solve. Many teams fail to maintain a holistic understanding of the problems they tackle, reverting to mechanical processes that lead to uninspired outcomes. Tools and strategies exist to foster collaboration and shared understanding, but the author insists that the process and culture around problem framing are what truly matter.