problem-statement

To write a user problem statement for a PRD, frame the narrative around the persona, their desired outcomes, barriers, root causes, and emotional context. This ensures teams align on the actual user problem before exploring solution implementations.

Framing user problems using jobs-to-be-done involves capturing who is blocked, what they are trying to do, why it matters, and how it feels. This method integrates persona data and JTBD insights to create a grounded, empathy-driven problem narrative.

Structure a problem statement for stakeholder alignment by following a persona-driven narrative format: I am, Trying to, But, Because, Which makes me feel. This synthesizes user constraints and context into a concise, shareable final problem statement.

Yes, you need interview data and persona references to create an empathy-driven problem statement. The problem framing process guides context gathering through interviews and JTBD insights to ensure the final narrative accurately reflects real user constraints.

Centering the user instead of the solution during problem framing ensures the team addresses the actual barriers and root causes users face. Articulating a user-centered narrative captures why the outcome matters before jumping to specific feature solutions.

Yes, you can use a problem framing narrative for roadmap planning. The process produces a concise final problem statement derived from persona data and emotional context, making it highly suitable for direct integration into roadmaps and stakeholder alignment documents.