problem-statement

To write a problem statement for a PRD that aligns stakeholders, frame an empathy-driven narrative capturing persona, desired outcomes, barriers, root cause, and emotional impact, then distill it into a single concise sentence.

The best way to frame a user problem during product discovery is structuring the narrative around jobs to be done, keeping the outcome focused on user goals rather than features, and documenting real-world constraints that shape feasibility.

Problem framing using jobs to be done improves stakeholder alignment by articulating who is blocked, what they are trying to do, why it matters, and what prevents progress, ensuring teams agree on the real objective before solutioning.

Yes, you can use a persona and jobs to be done structure to document product constraints. The framing process explicitly captures real-world limitations and context that shape what is and isn't feasible for the user.

You need empathy-driven problem framing when you must clarify the underlying user problem behind a set of feature requests, ensuring product, design, and engineering teams agree on the real objective before building solutions.

A limitation of drafting a single-sentence problem statement is that it requires sufficient persona research notes and context upfront to accurately capture emotional impact and root cause without oversimplifying the barrier.