problem-statement

A user problem statement summarizes core user pain points by structuring personas, goals, barriers, causes, and feelings into a concise sentence for stakeholder communication. It captures relevant context and constraints to improve team alignment and solution focus.

A human-centered problem statement accurately reflects user pain points and needs based on research data. You need one during product discovery to foster team alignment and ensure solution focus before development begins.

Structure user research data by organizing personas, goals, barriers, causes, and feelings into a structured narrative. Include geographic, technological, or demographic constraints to synthesize a concise statement that aligns stakeholders.

Yes, you can generate an empathetic problem statement from raw user interview data by providing user insights to the process. It formulates the data into human-centered statements that articulate user emotions and contextual barriers.

The best way to document user constraints is to capture relevant geographic, technological, or demographic limitations influencing the problem. This contextual documentation is structured alongside personas and barriers to improve team understanding.

Teams lack alignment on user pain points when they fail to synthesize user research into a shared, human-centered problem statement. Structuring personas, barriers, causes, and emotions into a concise narrative ensures everyone understands the core issue.