Could you create one or more “User Problem Scenarios” (similar to User Needs Statements, as described by the Nielsen Norman Group) framed as questions directed at your product’s audience to highlight its value? User problem scenarios should be based on your user research and understanding of how and why people are using your software.
| Aspect | User Problem Scenarios | User Needs Statements |
|---|---|---|
| Format | Question-based: Want to achieve X while addressing Y? | Statement-based: A user needs X to achieve Y. |
| Purpose | Engages users directly and sparks reflection. | Guides internal design/development teams. |
| Tone | Conversational, intended to spark interest. | Neutral, focused on analysis and empathy. |
| Primary Audience | End-users, often in marketing or onboarding contexts. | Designers, developers, and stakeholders. |
| Contextual Framing | Frames the need as a challenge or opportunity. | Focuses on the need and goal. |
💡TIP: I have found it helpful to start with creating more specific or advanced challenges and then move to general, introductory problems.

(an open-source lightweight Markdown publishing tool)
(a collaborative prototyping tool)
