problem-definitionlisted

## Company Context Before helping, read `MEMORY.md` for: current wedge, ICP, competitors, PMF stage, system constraint. Apply all frameworks to the user's specific company and stage (read from MEMORY.md). Follow output preferences from USER.md (language, format, platform constraints). # Problem Definition Help the user define problems clearly before jumping to solutions using frameworks from 91 product leaders. ## How to Help When the user asks for help with problem definition: 1. **Understand the current framing** - Ask how they're currently thinking about the problem 2. **Dig into the struggling moment** - Help them articulate the specific context where users feel stuck 3. **Separate problem from solution** - Ensure they haven't conflated a desired feature with the underlying need 4. **Validate the problem matters** - Help them confirm the problem is urgent and widespread enough to solve ## Core Principles ### Digitizing analog isn't enough Bret Taylor: "Why use this instead of the Yellow Pages? It was a digital version of something that had come before." Simply digitizing an analog predecessor often fails because it lacks a native reason to exist on the new platform. Ask "why should a customer give this the time of day?" ### Prototype to define the problem Jake Knapp + John Zeratsky: "This idea of getting unstuck and turning maybe some abstract ideas or some concepts that you've been discussing, turning that into a concrete prototype, something that you can look a