Research Governance

Problem Statement

A problem statement is a clear description of a user, service, product, or operational problem that explains who is affected, what is happening, why it matters, and what consequence needs attention.

Concept facts

A problem statement is a clear description of a user, service, product, or operational problem that explains who is affected, what is happening, why it matters, and what consequence needs attention.

Also known as
Problem framing, design problem, challenge statement, problem definition.
Used in
UX research synthesis, product discovery, service design, requirements planning, design strategy, and stakeholder alignment.
Interpret with
Research finding, UX insight, user need, opportunity area, assumption mapping, user requirement, and recommendation prioritization.

Plain-language explanation

A problem statement defines the issue before the team decides what to build. It helps teams avoid jumping from evidence directly to a preferred solution. A strong problem statement makes the problem understandable, bounded, and useful for decision-making.

Why it matters

Teams often begin with solutions too early. A clear problem statement helps product owners, designers, developers, service managers, and stakeholders align around the issue to solve. In high-friction services, poor problem framing can waste resources and leave the real access or operational problem unresolved.

Use contexts

  • synthesising research findings
  • preparing discovery or strategy work
  • defining product or service improvement scope
  • aligning stakeholders before requirements writing
  • framing design challenges
  • deciding whether a proposed feature addresses the real problem
  • documenting why a roadmap item matters

Application guidance

Base the problem statement on evidence, not assumption. Name the affected user or role, explain the situation and consequence, and avoid solution language. Keep it specific enough to guide action but broad enough to allow alternative solutions.

Practical example

A civic permit system receives repeated incomplete applications. Staff initially suggest adding more required fields. A problem statement reframes the issue: “Small business applicants cannot understand which permit category applies to their activity before submission, causing wrong applications, staff rework, and delayed approval.” The UX consequence is eligibility confusion, operational delay, and staff workflow burden.

Interpretive boundaries

A problem statement is not a research finding, requirement, acceptance criterion, or proposed solution. It may change as evidence improves and should not become a fixed slogan that ignores new data.

Applied at Userhub

Userhub uses problem statements to structure advisory, audit, and discovery work before recommending solutions. In UX Lab work, problem statements help clients connect user evidence with practical improvement decisions.

See Userhub UX Lab for applied UX research and evaluation context.

Sources and references

Government Digital Service. (n.d.). 1. Understand users and their needs. GOV.UK Service Manual. https://www.gov.uk/service-manual/service-standard/point-1-understand-user-needs

International Organization for Standardization. (2019). ISO 9241-210:2019 Ergonomics of human-system interaction — Part 210: Human-centred design for interactive systems. https://www.iso.org/standard/77520.html

Kolko, J. (2010). Abductive thinking and sensemaking: The drivers of design synthesis. Design Issues, 26(1), 15–28. https://doi.org/10.1162/desi.2010.26.1.15

Gothelf, J., & Seiden, J. (2021). Lean UX: Designing great products with agile teams (3rd ed.). O’Reilly Media.

Cite this entry

APA

Userhub. (2026). Problem Statement. UX Reference. https://userhub.com.bd/reference/problem-statement/