Jeff Patton says you do not need to be a brain surgeon to build software for one, but empathy is still hard. He recommends putting yourself in users' shoes, and describes conference-room pilot simulations where engineers and product managers step into user roles and feel the friction firsthand.
Jeff Patton says AI lets teams make monolithic mistakes. He cites a company that used AI to release new capabilities to 2.65 million users and hurt them; the failure was not assessing risk, not releasing to a small subset, and not checking what happened afterwards.
Jeff Patton warns that if you keep testing rough features on mainstream customers, they often eventually say they have had it and will not try new things. Release-to-learn depends on early adopters; after disappointing the majority, you have a reacquisition problem, not an acquisition problem.
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.
Jeff Patton cites the book Evil by Design and its seven deadly sins structure. He says people do not use Facebook, Instagram or TikTok to solve a problem; they may be feeding sloth, envy or greed. Products can exploit those drives, even when the result hurts users.
Jeff Patton's concrete advice is to find someone using what you built and watch or talk to them directly. He says not to have AI go talk to customers instead; firsthand observation often shocks product managers into empathy and shows them what they missed.
Jeff Patton retells B.F. Skinner's pigeon experiment: unpredictable food rewards make pigeons peck harder and faster. He thinks product organizations behave the same way, getting a dopamine hit from trying and launching features, not from confirming success, so they often keep shipping without checking outcomes.
Jeff Patton says nobody knows how much product success comes from luck. Organizations can earn huge rewards by chance, and teams that do everything right can still strike out. The practical takeaway is to acknowledge you cannot predict what happens when you release a feature or product.
Jeff Patton compares skilled AI use to Iron Man: Tony Stark is still inside the suit. The AI can help you fly and shoot, but a person must understand the user story, evaluate the output, and decide what to release. AI amplifies product thinking; it does not supply it.
Jeff Patton says many teams 'story map' by taking a solution they already have in mind and breaking the product into smaller pieces. That is feature decomposition, not a story map. A real story map starts with what a user does; without that narrative, the map does not help you understand outcomes.
Jeff Patton draws output, outcome and impact, then asks teams about their last releases. They often give him a 'slow blink'; they do not know whether anyone saw, tried, used, kept using or praised the feature. AI will not add usage metrics unless someone asks it to.
Jeff Patton points to Jira, released as a help desk ticketing system but adopted as agile project management. He says companies sometimes notice customers using a product for an unintended purpose, dig in, and find a problem they did not know needed solving; that signal can redirect strategy.
