> For the complete documentation index, see [llms.txt](https://www.designreference.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.designreference.xyz/ux-methods/discovery/problem-statements.md).

# Problem Statements

{% hint style="info" %}
AKA User Need Statements, Needs Statements, Point-of-View Statements, PoV Statements, How Might We Statements
{% endhint %}

There is also a separate page for How Might We Statements here:

{% content-ref url="/pages/HBHPNXKATYTuh1unbzvi" %}
[How Might We](/ux-methods/ideation/how-might-we.md)
{% endcontent-ref %}

Problem statements are concise descriptions that highlight a specific issue, challenge, or opportunity that needs to be addressed.

They provide a clear and focused articulation of the problem to be solved or the goal to be achieved. Problem statements typically define the gap between the current state and the desired state, emphasising the impact or significance of the problem. They help teams and stakeholders understand the problem's context, scope, and implications. 

By formulating problem statements, organisations can align efforts, prioritise initiatives, and guide decision-making. Problem statements serve as a foundation for problem-solving, innovation, and planning, enabling teams to develop targeted strategies and solutions that directly address the identified problem or opportunity.

#### Further Reading

{% embed url="<https://www.nngroup.com/articles/problem-statements/>" %}

{% embed url="<https://medium.com/@uxsurvivalguide/why-i-ditched-user-need-statements-created-the-cmbat-framework-67c37b3e2716>" %}

{% embed url="<https://www.nngroup.com/articles/user-need-statements/>" %}

{% embed url="<https://productcoalition.com/defining-requirements-while-building-0-to-1-e2d1c4a4c1bc>" %}

{% embed url="<https://tvsnext.com/blog/uncovering-user-needs-statement-is-50-of-solving-define-in-design-thinking/>" %}

{% embed url="<https://www.ibm.com/design/thinking/page/toolkit/activity/needs-statements>" %}

{% embed url="<https://medium.com/nextuxdesign/how-to-define-users-needs-statement-ff5ee945fed9>" %}

{% embed url="<https://www.uxpin.com/studio/blog/problem-statement/>" %}

#### Further Viewing

{% embed url="<https://www.youtube.com/watch?v=kT0ZqwdPYRM>" %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://www.designreference.xyz/ux-methods/discovery/problem-statements.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.