problem-statementlisted

## Purpose Articulate a problem from the user's perspective using an empathy-driven framework that captures who they are, what they're trying to do, what's blocking them, why, and how it makes them feel. Use this to align stakeholders on the problem before jumping to solutions, and to frame product work around user outcomes rather than feature requests. This is not a requirements doc—it's a human-centered problem narrative that ensures you're solving a problem worth solving. ## Key Concepts ### The Problem Framing Framework Based on Jobs-to-be-Done and empathy mapping, the framework structures problems as: **Problem Framing Narrative:** - **I am:** [Describe the persona experiencing the problem] - **Trying to:** [Desired outcomes the persona cares about] - **But:** [Barriers preventing the outcomes] - **Because:** [Root cause of the problem] - **Which makes me feel:** [Emotional impact] **Context & Constraints:** - [Geographic, technological, time-based, demographic factors] **Final Problem Statement:** - [Single, concise, empathetic summary] ### Why This Structure Works - **Persona-centric:** Forces you to see the problem through the user's eyes - **Outcome-focused:** "Trying to" emphasizes desired results, not tasks - **Root cause analysis:** "Because" pushes past symptoms to underlying issues - **Emotional validation:** "Makes me feel" humanizes the problem and builds empathy - **Contextual:** Constraints acknowledge real-world limitations ### Anti-Patterns (What T