We scan new podcasts and send you the top 5 insights daily.
Jeff Patton says the most important product work is finding the problem or need, not just building and seeing how people respond. He calls this 'sense and respond,' crediting Josh Seiden and Jeff Gothelf. If AI just builds what people ask for, you get the worst requested solutions.
A common trap is starting with the assumption that AI must be used, leading to a search for a place to tack it on. This results in superfluous features like a generic "AI assistant," rather than solving a real user need. The correct approach begins with the user's pain.
The design firm Herbst Product operates on the principle that elegantly solving an irrelevant problem is a total failure. This emphasizes the supreme importance of the discovery and definition phases in product development. Before building, teams must ensure they are addressing a genuine, high-value customer need.
Many teams jump straight into tools like n8n or Claude before defining user problems, which produces low-value features. High-performing product builders prioritize possibilities, opportunities, and workflows before touching code or tools. Job market analysis reveals identifying the right problem yields far higher compensation than engineering syntax.
AI tools are causing an explosion of features, making execution a commodity. The core skill for product teams is no longer building, but deeply understanding user needs. The winning products will be those that solve real problems, not those that are merely built fast.
Don't wait for post-launch metrics to validate an idea. The essential evidence for whether to build something is gathered through direct, face-to-face conversations with users about their problems. This pre-build signal is far more reliable than any data collected after shipping.
Don't let the novelty of GenAI distract you from product management fundamentals. Before exploring any solution, start with the core questions: What is the customer's problem, and is solving it a viable business opportunity? The technology is a means to an end, not the end itself.
Without a strong foundation in customer problem definition, AI tools simply accelerate bad practices. Teams that habitually jump to solutions without a clear "why" will find themselves building rudderless products at an even faster pace. AI makes foundational product discipline more critical, not less.
The ease of AI development tools tempts founders to build products immediately. A more effective approach is to first use AI for deep market research and GTM strategy validation. This prevents wasting time building a product that nobody wants.
In the rush to adopt AI, teams are tempted to start with the technology and search for a problem. However, the most successful AI products still adhere to the fundamental principle of starting with user pain points, not the capabilities of the technology.
The misconception that discovery slows down delivery is dangerous. Like stretching before a race prevents injury, proper, time-boxed discovery prevents building the wrong thing. This avoids costly code rewrites and iterative launches that miss the mark, ultimately speeding up the delivery of a successful product.