problem-statement

A user-centered problem statement articulates who is blocked, what they are trying to do, why it matters, and how it feels. You frame it using an empathy-driven template covering persona, outcome, barriers, root causes, and emotional impact to align stakeholders before moving to solutions.

Problem framing in product management is the process of defining a user's barrier and emotional impact rather than jumping to solution ideas. It is needed during discovery and prioritization to keep product, design, and engineering teams grounded in empathy and align stakeholders around the actual user need.

You align stakeholders using a jobs-to-be-done framework by synthesizing interview insights into a single, empathetic problem statement. Documenting user constraints and emotional context ensures product, design, and engineering teams rally behind a shared understanding of the user's actual need.

Yes, you can use problem framing for PRD planning and constraint documentation. The process prompts you to record geographic, technological, time-based, and demographic factors before synthesizing an empathetic statement, ensuring your product requirements document is grounded in validated user context.

Common anti-patterns when creating a problem statement include jumping to solutions too early and lacking persona specificity. Quality checks help you avoid these pitfalls by ensuring your narrative includes measurable outcomes and is validated with proto-persona insights before stakeholder alignment.

You should not use a user-centered problem statement template when you lack interview insights or proto-persona data to populate it. Without research-backed context regarding who is blocked and their emotional impact, the resulting narrative will lack the empathy needed to accurately drive discovery or prioritization.