User Need

A user need is what people actually need from the product to succeed. Glare uses 20 standard needs in five groups: Basics, Trust, Personal, Impact and Feelings. Every need the team names maps to one of them.

For example, new SecondBank cardholders ignore the rewards tab. Talking to them shows they need to see what their points are worth. That's the Valuable need, in the Impact group. They also need to find the rewards in the first place, which is Findable, in Basics.

Why it matters

When needs aren't named, teams build what people ask for instead of what they need. Customers ask for a faster horse; what they need is to travel faster. Requests pile up, features ship, and the real problem stays unsolved.

Naming the need, using a shared list of 20, keeps the team focused on the problem and makes needs comparable across products. It also connects design work to outcomes leaders track, because every need maps through user, product and business outcomes to a business goal.

Name the need in plain words, map it to one of the 20, say who has it, and mark whether it's a stated want or a confirmed need.

How we write one

Every user need is written as one sentence that names the need, its group, who has it, and what they need to do:

A need (its category): an audience needs to reach an outcome.

Valuable (Impact): new cardholders need to see what their points are worth.

Leading with the standard need makes needs easy to compare and count, and the outcome keeps it concrete enough to design and test against.

How it differs from similar ideas

  • A want is what someone asks for, such as "show me a points calculator". A user need is the underlying problem. A want is stored as a user need with the status Want until evidence confirms the need behind it.

  • An opportunity is the gap between a need and how well it's met today. The user need is the need itself.

  • A situation describes what people are doing. A user need explains what they need, which the situation points to.

  • A business goal is what the business wants. A user need is what the user wants, and the two connect through outcomes.

A good user need

  • Maps to one of the 20 user needs

  • Names a specific audience

  • Describes an outcome, not a feature

  • Says whether it's a want or a confirmed need

  • Is backed by evidence from customers or participants

  • Can be measured with a UX metric

What happens to it

  1. Stated as a want. Someone asks for something, and Ray records the need behind it as a Want.

  2. Identified. Ray or the team names the need from research or behavior.

  3. Confirmed. Evidence from customers or participants backs it, and it becomes a Need.

  4. Addressed. An opportunity, test or concept is working on it.

  5. Met or retired. A user outcome shows it's met, or the team decides it no longer matters.


For Ray

This part tells Ray how to find user needs in an input, such as an interview transcript, a support ticket export, survey comments, a research report or a feature request list, and how to store them.

How to find one

  1. Mark statements of need and request. Read the input and mark what people say they want, struggle with, or can't do.

  2. Look past the request. For each want, ask what problem it would solve. Write the outcome, not the feature.

  3. Map it to one of the 20. Match it to a need and its category: Basics (Useful, Usable, Findable, Accessible), Trust (Credible, Secure, Reliable, Intuitive), Personal (Inclusive, Adaptable, Connected, Insightful), Impact (Valuable, Sustainable, Scalable, Efficient) or Feelings (Desirable, Delightful, Engaging, Empowering).

  4. Find the audience. Identify who has the need and link the audience.

  5. Set want or need. Mark it Want if it rests only on what people asked for. Mark it Need if behavior or test evidence backs it.

  6. Link the situation. Connect it to the situation that points to it.

  7. Write the sentence. Use the format: [Need] ([category]): [audience] needs to [outcome].

  8. Fill the record, score it, link it and store it using the rules below.

Cues to look for

  • Struggle language: "I can't tell", "I didn't know", "I couldn't find", "it's confusing"

  • Requests: "I wish it", "can you add", "it would help if"

  • Workarounds people describe, such as using a spreadsheet or calling support

  • Behavior in data that shows people stopping, skipping or giving up

What doesn't count

<table xmlns="http://www.w3.org/1999/xhtml" style="min-width: 50px;"><colgroup><col style="min-width: 25px;"><col style="min-width: 25px;"></colgroup><tbody><tr><th colspan="1" rowspan="1"><p>If the statement...</p></th><th colspan="1" rowspan="1"><p>Store it as</p></th></tr><tr><td colspan="1" rowspan="1"><p>Names a feature or fix</p></td><td colspan="1" rowspan="1"><p>User Need with status Want, plus a Concept for the feature</p></td></tr><tr><td colspan="1" rowspan="1"><p>Describes the gap between a need and today</p></td><td colspan="1" rowspan="1"><p>Opportunity</p></td></tr><tr><td colspan="1" rowspan="1"><p>Describes behavior without saying what's needed</p></td><td colspan="1" rowspan="1"><p>Situation</p></td></tr><tr><td colspan="1" rowspan="1"><p>Says what the business wants</p></td><td colspan="1" rowspan="1"><p>Business Intent or Business Goal</p></td></tr><tr><td colspan="1" rowspan="1"><p>Can't be mapped to any of the 20</p></td><td colspan="1" rowspan="1"><p>Nothing yet; add it to the review digest</p></td></tr></tbody></table>

The record

<table xmlns="http://www.w3.org/1999/xhtml" style="min-width: 75px;"><colgroup><col style="min-width: 25px;"><col style="min-width: 25px;"><col style="min-width: 25px;"></colgroup><tbody><tr><th colspan="1" rowspan="1"><p>Field</p></th><th colspan="1" rowspan="1"><p>What to fill in</p></th><th colspan="1" rowspan="1"><p>Values</p></th></tr><tr><td colspan="1" rowspan="1"><p>Statement</p></td><td colspan="1" rowspan="1"><p>The one-sentence need</p></td><td colspan="1" rowspan="1"><p>[Need] ([category]): [audience] needs to [outcome].</p></td></tr><tr><td colspan="1" rowspan="1"><p>Need</p></td><td colspan="1" rowspan="1"><p>Which of the 20 user needs</p></td><td colspan="1" rowspan="1"><p>One of the 20 user needs</p></td></tr><tr><td colspan="1" rowspan="1"><p>Category</p></td><td colspan="1" rowspan="1"><p>Its group</p></td><td colspan="1" rowspan="1"><p>Basics, Trust, Personal, Impact, Feelings</p></td></tr><tr><td colspan="1" rowspan="1"><p>Audience</p></td><td colspan="1" rowspan="1"><p>Who has it</p></td><td colspan="1" rowspan="1"><p>Link to Audience</p></td></tr><tr><td colspan="1" rowspan="1"><p>Outcome</p></td><td colspan="1" rowspan="1"><p>What they need to be able to do</p></td><td colspan="1" rowspan="1"><p>Short text</p></td></tr><tr><td colspan="1" rowspan="1"><p>Want or need</p></td><td colspan="1" rowspan="1"><p>Whether evidence confirms it</p></td><td colspan="1" rowspan="1"><p>Want, Need</p></td></tr><tr><td colspan="1" rowspan="1"><p>Stated want</p></td><td colspan="1" rowspan="1"><p>The original request, if there was one</p></td><td colspan="1" rowspan="1"><p>Quoted text, or blank</p></td></tr><tr><td colspan="1" rowspan="1"><p>Situation</p></td><td colspan="1" rowspan="1"><p>The situation that points to it</p></td><td colspan="1" rowspan="1"><p>Link to Situation</p></td></tr><tr><td colspan="1" rowspan="1"><p>Source</p></td><td colspan="1" rowspan="1"><p>The input and exact passage</p></td><td colspan="1" rowspan="1"><p>Link to Input</p></td></tr><tr><td colspan="1" rowspan="1"><p>Status</p></td><td colspan="1" rowspan="1"><p>Where it stands</p></td><td colspan="1" rowspan="1"><p>Identified, Confirmed, Addressed, Met, Retired</p></td></tr><tr><td colspan="1" rowspan="1"><p>Confidence</p></td><td colspan="1" rowspan="1"><p>How well evidence supports it</p></td><td colspan="1" rowspan="1"><p>High, medium, low</p></td></tr></tbody></table>

A need starts as Want when it rests only on requests. Ray moves it to Need only when customer behavior or test evidence backs it.

Scoring confidence

Confidence measures how well the evidence supports the need and its mapping, not how often people ask for it.

<table xmlns="http://www.w3.org/1999/xhtml" style="min-width: 50px;"><colgroup><col style="min-width: 25px;"><col style="min-width: 25px;"></colgroup><tbody><tr><th colspan="1" rowspan="1"><p>Level</p></th><th colspan="1" rowspan="1"><p>When to use it</p></th></tr><tr><td colspan="1" rowspan="1"><p>High</p></td><td colspan="1" rowspan="1"><p>Backed by customer or participant behavior, and maps clearly to one of the 20</p></td></tr><tr><td colspan="1" rowspan="1"><p>Medium</p></td><td colspan="1" rowspan="1"><p>Backed by what customers or participants said, or the mapping is between two needs</p></td></tr><tr><td colspan="1" rowspan="1"><p>Low</p></td><td colspan="1" rowspan="1"><p>Raised only by the team or stakeholders, or inferred from a single request</p></td></tr></tbody></table>

If any part of the record can't be filled from the source, leave it blank and lower confidence by one level.

Linking

  • Check for duplicates first. If an existing need has the same need type, audience and outcome, add the new source to it instead of creating another.

  • Link to the audience that has it and the situation that points to it.

  • Link to opportunities it grounds, and to any concept created from a stated want.

  • Link through the mapping chain to the user outcome and design KPI that will show it's met.

  • Link related needs. When one input reveals two needs, such as Findable and Valuable, store both and link them.

When to store and when to ask

  • Store automatically when confidence is high and it maps to one of the 20.

  • Add to the review digest when confidence is medium or low, when it can't be mapped, or when it contradicts a confirmed need.

When to flag

  • A decision is based on a Want that hasn't been confirmed

  • A need has no audience linked

  • A need has no UX metric or user outcome to show when it's met

  • A concept or bet has no user need behind it

  • A need rests only on internal voices

Worked example

Input: a customer interview transcript, session 2 of 6.

Cardholder: "I see I have 4,200 points, but I honestly have no idea if that's a lot. Is that a free coffee or a flight? I wish there was a calculator or something. Honestly I only found the rewards tab last week."

What Ray finds:

  • "No idea if that's a lot" shows the person can't see what points are worth: Valuable (Impact).

  • "I wish there was a calculator" is a stated want. Ray records it and creates a Concept for the calculator.

  • "Only found the rewards tab last week" points to a second need: Findable (Basics), stored separately.

  • The speaker is a new cardholder, so Ray links the Customers audience.

  • This is one stated account, so the need starts as Want until behavior backs it.

Stored record:

<table xmlns="http://www.w3.org/1999/xhtml" style="min-width: 50px;"><colgroup><col style="min-width: 25px;"><col style="min-width: 25px;"></colgroup><tbody><tr><th colspan="1" rowspan="1"><p>Field</p></th><th colspan="1" rowspan="1"><p>Value</p></th></tr><tr><td colspan="1" rowspan="1"><p>Statement</p></td><td colspan="1" rowspan="1"><p>Valuable (Impact): new cardholders need to see what their points are worth.</p></td></tr><tr><td colspan="1" rowspan="1"><p>Need</p></td><td colspan="1" rowspan="1"><p>Valuable</p></td></tr><tr><td colspan="1" rowspan="1"><p>Category</p></td><td colspan="1" rowspan="1"><p>Impact</p></td></tr><tr><td colspan="1" rowspan="1"><p>Audience</p></td><td colspan="1" rowspan="1"><p>Customers: new cardholders, first 30 days</p></td></tr><tr><td colspan="1" rowspan="1"><p>Outcome</p></td><td colspan="1" rowspan="1"><p>See what their points are worth</p></td></tr><tr><td colspan="1" rowspan="1"><p>Want or need</p></td><td colspan="1" rowspan="1"><p>Want</p></td></tr><tr><td colspan="1" rowspan="1"><p>Stated want</p></td><td colspan="1" rowspan="1"><p>"I wish there was a calculator or something"</p></td></tr><tr><td colspan="1" rowspan="1"><p>Situation</p></td><td colspan="1" rowspan="1"><p>New cardholders rarely open the rewards tab, so earned points go unused</p></td></tr><tr><td colspan="1" rowspan="1"><p>Source</p></td><td colspan="1" rowspan="1"><p>Customer interview transcript, session 2, October 2026</p></td></tr><tr><td colspan="1" rowspan="1"><p>Status</p></td><td colspan="1" rowspan="1"><p>Identified</p></td></tr><tr><td colspan="1" rowspan="1"><p>Confidence</p></td><td colspan="1" rowspan="1"><p>Medium: stated by a customer, not yet backed by behavior</p></td></tr></tbody></table>

Next step: added to the review digest; the concept test on point value can confirm it and move it from Want to Need.

Edge cases

  • Feature as need. "Users need a calculator" names a feature. Store the calculator as a Concept and write the need as the outcome it serves.

  • Between two needs. If a need fits two types, such as Valuable and Insightful, pick the one closest to the outcome and note the other.

  • Two needs in one quote. Store each need separately and link them, as with Valuable and Findable above.

  • Many requests, no behavior. Volume of requests raises confidence to medium at most. Only behavior or test evidence confirms a need.

Identify where decision quality breaks down

The Glare Design Assessment helps teams spot weak validation, stakeholder friction, alignment gaps, and assumptions that scale without measurable learning—so you have a clearer starting point for improvement.

About 5 minutes · Team-based · Diagnostic snapshot you can act on

Take the Design Assessment
User Need | Glare