problem-statement

To frame user problems with empathy, you articulate a user-centered problem narrative by capturing persona, outcomes, barriers, root cause, and emotions. This approach aligns product teams around user outcomes rather than features before solution development begins.

Empathy-driven problem framing is a technique that structures problem validation around a user's emotional context and barriers. You should use it during product discovery to guide stakeholder alignment and ensure teams address root causes instead of surface-level symptoms.

Write a problem statement using jobs to be done and empathy mapping by providing a user persona and context. The framework guides you through structured capture of outcomes and emotional framing to produce a concise final problem statement with contextual constraints.

Yes, you can use this empathy-driven problem framing framework for stakeholder alignment across product teams. It generates a concise final problem statement plus context and constraints that align stakeholders on user outcomes before feature development.

The best way to structure a user narrative for product discovery is to apply an empathy-driven framing framework. This involves capturing the persona, expected outcomes, barriers, root cause, and emotional context to produce a validated problem narrative.

Yes, you need to provide a user persona and context to draft a problem framing narrative. A defined persona serves as the foundation for capturing outcomes, barriers, and emotional framing required to produce the final problem statement.