What is a User Need?

TL;DR

• A user need describes what a person is trying to achieve, avoid, understand, or improve.
• A need is not automatically a requested feature.
• Strong needs are grounded in evidence and context.
• One need can support several possible solutions.
• Product teams should understand the need before committing to the feature.

What does a user need look like?

A customer says, “Add CSV export.”

The feature request is CSV export. The underlying need could be reporting to a manager, moving data into finance software, creating a backup, or satisfying compliance requirements.

Those are different needs and may lead to different solutions.

User need vs. feature request

A feature request describes a proposed solution. A user need describes the progress or outcome the person is trying to achieve.

Good product discovery asks why the request matters before treating it as a requirement.

How do teams identify user needs?

• user interviews
• support conversations
• behavioral analytics
• usability tests
• field observation
• sales and customer-success evidence

What makes a useful need statement?

It should be specific enough to guide design but open enough to allow multiple solutions.

Weak: Users need better analytics.

Stronger: Team leads need to understand which onboarding step causes the most drop-off before deciding what to improve.

Common mistakes

Confusing what users ask for with what they need

Requests are evidence, not final requirements.

Writing needs too broadly

“Users need an easy experience” gives little design guidance.

Inventing needs without research

Needs should come from evidence, not personas built from assumptions.

The bottom line

A user need asks: what meaningful progress is this person trying to make, independent of our favorite solution?

Related terms

Pain point · Problem statement · Jobs to be Done · User research

Relevant Figr resource

Read User Research Methods for techniques to uncover needs.