Needs and Wants
ニーズ・アンド・ウォンツ
Needs are essential requirements, while wants are the preferred ways people choose to satisfy those needs.
Needs describe fundamental problems or requirements that must be addressed, such as safety, health, or convenience. Wants are the specific solutions people prefer based on culture, budget, and context. Marketing separates needs from wants to design products that solve the underlying problem while choosing a form and experience that customers actually desire.
It guides product scope by separating core requirements from optional features. It influences positioning and messaging by focusing on the problem first. It shapes pricing and segmentation decisions based on different desired solutions.
- It guides product scope by separating core requirements from optional features.
- It influences positioning and messaging by focusing on the problem first.
- It shapes pricing and segmentation decisions based on different desired solutions.
- Identify the underlying need before designing the solution form.
- Map multiple wants that satisfy the same need to expand options.
- Use research to distinguish real needs from internal assumptions.
- Design tradeoffs around the need, not around flashy wants.
- Update definitions as customer context or budgets change.
A commuter needs a quick breakfast, but wants vary: some prefer a hot sandwich, others a protein bar. The team designs a simple menu that solves the speed need, then tests different formats and price points. By surveying commuters and observing purchase behavior, they find that portability matters more than variety. They adjust packaging and messaging around the need for speed, while offering two formats to match different wants.
Compare Needs and Wants with adjacent concepts before deciding. Needs and Wants | Current concept | Use when the team needs the primary decision lens Adjacent metric or framework | Supporting lens | Use when the team needs evidence or process detail General vocabulary | Broad explanation | Use only for orientation, not final decision-making
| Metric | Difference | Why read together |
|---|---|---|
| Needs and Wants | Current concept | Use when the team needs the primary decision lens |
| Adjacent metric or framework | Supporting lens | Use when the team needs evidence or process detail |
| General vocabulary | Broad explanation | Use only for orientation, not final decision-making |
- Needs and wants are not the same, even if customers use them interchangeably.
- Companies can shape wants but cannot create fundamental needs.
- A popular want does not always signal the most important need.
When should I use Needs and Wants?
Use it when the team needs to decide scope, priority, owner, or trade-off, not when it only needs a short definition.
What makes Needs and Wants useful in practice?
It becomes useful when it is tied to evidence, a decision owner, and a concrete next operating choice.
What should I avoid?
Avoid using the term as a label without clarifying assumptions, boundaries, and how success will be judged.