Research Governance

User Need

A user need is an evidence-based statement of what a user must understand, decide, access, provide, or accomplish in order to complete a task or receive value from a service.

Concept facts

A user need is an evidence-based statement of what a user must understand, decide, access, provide, or accomplish in order to complete a task or receive value from a service.

Also known as
Need statement, service need, user goal, user-centered need.
Used in
UX research, service design, product discovery, public-service design, requirements framing, roadmap planning, and usability evaluation.
Interpret with
Research finding, UX insight, problem statement, user requirement, service standard, task success, and outcome metric.

Plain-language explanation

A user need describes what matters to the user in context. It is not the same as a feature request or stakeholder preference. A good user need helps teams understand what the service must support before deciding how to design or build it.

Why it matters

User needs create a bridge between research evidence and delivery decisions. Without clear user needs, teams may build features that satisfy internal assumptions but do not solve the real user problem. In public-service, health, finance, education, telco, and development-sector systems, poorly understood user needs can cause access failure, wrong submissions, support burden, operational delay, or weak adoption.

Use contexts

  • translating research findings into product or service direction
  • defining the problem before requirements are written
  • planning public-service or civic-tech journeys
  • reviewing whether a feature supports real task completion
  • prioritising roadmap items
  • preparing design, content, or service recommendations
  • evaluating whether a service standard is being met

Application guidance

Write user needs from evidence. Use interviews, field research, usability testing, analytics, support tickets, service data, and operational observations where appropriate. Make the need specific to a user, context, and task. Keep the need separate from the solution and link it to service consequences.

Practical example

A development-sector cash assistance programme asks beneficiaries to check payment status through a mobile portal. Field staff report repeated calls from beneficiaries who do not know whether a payment is delayed, rejected, or pending verification. A user need states: “Beneficiaries need to understand their payment status and next action without contacting field staff.” The UX consequence is service access, trust, reduced field-staff burden, and fewer avoidable follow-up visits.

Interpretive boundaries

A user need is not a demographic description, feature request, business goal, or requirement specification. User needs may conflict with business rules, policy constraints, or technical limitations, and those tensions should be made visible rather than hidden.

Applied at Userhub

Userhub uses user needs to connect research findings with design, content, service, and roadmap decisions. In UX Lab work, user needs help clients move from evidence to clearer requirements, prioritisation, and service improvement.

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

Sources and references

Government Digital Service. (n.d.). Service Standard. GOV.UK Service Manual. https://www.gov.uk/service-manual/service-standard

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

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

Cite this entry

APA

Userhub. (2026). User Need. UX Reference. https://userhub.com.bd/reference/user-need/