problem-statement
User-centered problem framing that captures who is blocked, what they're trying to do, why it matters, and how it feels.
- Structures problems around five dimensions: persona, desired outcomes, barriers, root causes, and emotional impact—ensuring you solve problems worth solving, not feature requests
- Includes a fill-in template, quality checks, and anti-patterns to avoid solution smuggling, generic personas, and symptom-level diagnosis
- Designed for discovery alignment, stakeholder buy-in, and PRD framing before solutioning begins
- Works best when grounded in user research; includes guidance on gathering context, validating with users, and iterating based on feedback
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:
More from deanpeters/product-manager-skills
prd-development
Build a structured PRD that connects problem, users, solution, and success criteria. Use when turning discovery notes into an engineering-ready document for a major initiative.
1.7Kuser-story
Create user stories with Mike Cohn format and Gherkin acceptance criteria. Use when turning user needs into development-ready work with clear outcomes and testable conditions.
1.7Kroadmap-planning
Plan a strategic roadmap across prioritization, epic definition, stakeholder alignment, and sequencing. Use when turning strategy into a release plan that teams can execute.
1.5Kcompany-research
Create a company research brief with executive quotes, product strategy, and org context. Use when preparing for interviews, competitive analysis, partnerships, or market-entry work.
1.3Kproduct-strategy-session
Run an end-to-end product strategy session across positioning, discovery, and roadmap planning. Use when a team needs validated direction before committing to execution.
1.2Kprioritization-advisor
Choose a prioritization framework based on stage, team context, and stakeholder needs. Use when deciding between RICE, ICE, value/effort, or another scoring approach.
1.1K