problem-statement

Write a user-centered problem statement by applying the "I am / Trying to / But / Because / Which makes me feel" structure to articulate personas, desired outcomes, blocking barriers, root causes, and emotional impact from your interview insights.

Reframe vague feature requests into measurable user outcomes by synthesizing jobs-to-be-done insights into an empathetic narrative that names who is blocked, what they are trying to do, and why they are blocked before scoping your PRD.

Align stakeholders during product discovery by generating a single-sentence final problem statement alongside a context and constraints list, preventing solution smuggling and keeping prioritization strictly focused on user outcomes.

Yes, you can use jobs-to-be-done insights to document blocking barriers and root causes by mapping them into a narrative that specifies the persona, the attempted task, and the resulting emotional impact.

Validate a problem statement with users and stakeholders by applying a built-in validation checklist that reviews context, executes quality checks, and tests the finalized narrative against actual user needs and stakeholder constraints.

Yes, this problem framing approach works for PRD scoping and stakeholder alignment by transforming assumptions and metric-focused goals into a concise, empathy-driven context list that teams can validate before designing solutions.