Start with the problem, not the profile
Two people of the same age and income may choose a product for entirely different reasons. One might want the fastest way to finish a task; the other might want reassurance that they will not make a mistake. Demographic details can help describe an audience, but they do not always explain what someone needs from an experience. Needs-based segmentation starts with the job a person is trying to get done and the difficulty standing in their way.
A need is more specific than a broad preference such as “convenience.” Ask what convenience means in context. Does the person need to compare options quickly, avoid repeating information, or complete a purchase without help? Also distinguish the problem from a proposed solution. “I need an app” names a possible tool; “I need to keep track of changes while I am away from my desk” describes a problem that could be solved in several ways.
Collect evidence in the context of a decision
Choose a clear decision to guide the research, such as improving a sign-up process or explaining a service to first-time buyers. Then define whose needs matter for that decision. A segment set built for onboarding may differ from one built for choosing a provider, even when both involve the same people. Stating the scope early keeps the exercise from becoming a collection of vague customer types.
Interviews can reveal how needs arise. Ask participants to describe a recent occasion when they faced the problem: what prompted it, what they tried, what felt difficult, and how they decided what to do next. Look for concrete accounts rather than asking people to select labels for themselves. A survey can then explore how commonly particular needs appear among a broader set of respondents, provided its questions use plain language and do not assume everyone has the same options or priorities.
Record context alongside each response. Time pressure, familiarity with the task, available support, and the consequences of a poor choice may all affect what matters most. These details help you interpret an answer without treating a need as a permanent trait.
Build groups that are distinct and useful
Review the evidence for recurring patterns in the problems people describe and the trade-offs they make. For example, one group may prioritize a quick, good-enough decision, while another needs enough detail to feel confident explaining its choice to someone else. Give each proposed group a short name that describes its need, not a stereotype about its members.
A useful segment should be recognizable in the evidence and meaningfully different from the others. Write a short definition for each group: the situation that triggers the need, the main obstacle, the outcome sought, and the trade-off the person is willing to make. If two groups would respond to the same product change and the same message, combining them may be more useful than keeping both. If one group contains people with conflicting priorities, examine whether it needs to be split.
People may have more than one need or move between groups as their circumstances change. You can identify a primary need for a specific decision without claiming it defines the person. Keep ambiguous responses visible rather than forcing every case into a tidy category.
Check the segments before using them
Test whether someone who did not create the groups can assign new responses using the definitions. When assignments differ, inspect the wording and the evidence: are the boundaries unclear, or do the responses reveal a need you missed? Compare the proposed groups with the original interview accounts as well as any survey results. A memorable label is not a substitute for a pattern that holds up across responses.
Check practical value, too. Ask what the team would do differently for each group. Could a clearer comparison help people seeking confidence, while a shorter route through routine steps helps those facing time pressure? If the segments do not lead to different, feasible choices, refine the groups or reconsider whether segmentation is needed for this decision.
Use the map without mistaking it for the territory
Turn each segment into a brief decision aid that includes its need, supporting evidence, and possible response. Use it to review product features, instructions, or messages against the problems people actually described. Avoid assuming that an individual belongs to a group based on appearance or demographic information; where possible, let people signal their current goal through their actions or choices.
Revisit the segments when the product, audience, or task changes. Needs-based segmentation is a working model, not a permanent classification. Its value lies in making decisions more attentive to the problems people want solved while leaving room for people to be more varied than any set of labels.
