Need vs want

People want a humidifier, but what they need is to control the room’s humidity.

People want a humidifier, but what they need is to control the room’s humidity.

People want a headphone, but what they need is to listen to the music privately.

People want a luxury watch, but what they need is prestige.

People usually express what they want. But our job, as product practitioners, is to figure out what they really need. Then, together with the team, we must figure out the best solution for that need. A solution that works for the users that fit with the product’s strategy, yet aligns with the company’s mission.

Try this: When you hear a specific feature request, ask yourself, is that a want or a need?

---

Related posts

• Outcomes, not outputs

• Problem solving principles

• Next month, I’ll quit my job

• How to scope product design work

• See more on the table of contents