problem-definition

A product-management skill that helps users define problems clearly before jumping to solutions, distilling frameworks from 91 product leaders. It guides a four-step approach: understand how the user currently frames the problem, dig into the specific 'struggling moment' where users feel stuck, separate the underlying need from a desired feature, and validate that the problem is urgent and widespread enough to be worth solving. It targets scoping new features, validating product ideas, articulating what you are building, and avoiding the 'shiny object trap' of adopting a technology in search of a problem.

The core principles are attributed to named practitioners and cover common pitfalls: digitizing an analog predecessor is not enough without a native reason to exist, prototyping turns abstract concepts into something concrete to define around, and demand comes from a specific struggling moment rather than from the product itself. It also captures useful tension: some voices push to spend more time understanding the problem, while others note customers ultimately buy the solution, so problem validation should not be over-rotated when the problem is already well understood. Distinguishing a business problem from a customer problem is treated as essential to avoid 'customer-hostile' solutions.

Use it when a team is solution-first or technology-first, when problem statements are too abstract to point at any specific solution, or when business and customer needs are being conflated. The skill supplies probing questions (what the user is doing right before the problem, why it has not been solved already, how life would differ if solved perfectly) and a checklist of common mistakes to flag. For deeper material it references a guest-insights file containing all 123 insights from the 91 guests, and lists related skills such as positioning-messaging, prioritizing-roadmap, and scoping-cutting.