We had a great team conversation yesterday about User Needs, and I wanted to share how we’re thinking about them.
Most people think a User Need is just something a user says or does, a problem they have, or a feature they want. But a real User Need is more than that.
Fundamentally, user needs are a business concept that connects what someone is doing today with a better way your product can help them do it. When you meet that need, both the user and the business gain value.
Here’s what I tried to put together in the diagram
- User Need: What people expect or value before they use your product.
- Interaction: Where their expectations meet reality.
- Product: Where you see proof that the design actually meets those needs.
Here’s where I think this is cool: if you test in high volume, you can explore concepts without heavy builds. You learn faster from users and start spotting patterns that reveal what the real underlying need is.
Here’s an example:
A user might say, “I want a ‘Save for Later’ button.”
It sounds simple. They just want to come back later. But when you test a few quick concepts, you start to see the real story behind it.
What users are really saying is, “I need more time to decide before I buy.”
Why?
Because buying isn’t just about clicking a button. It’s about confidence. Users might want to compare prices, read reviews, check with a partner, or see if it fits into their budget. That extra time probably isn’t procrastination. It’s part of how people make decisions when they feel uncertain. They want some sort of reassurance.
So the deeper User Need isn’t “save my cart.”
It’s “help me feel confident in my decision.”
When teams understand this, we can design smarter solutions, like sending a helpful reminder email, showing social proof, or keeping their cart saved automatically. Those ideas go beyond the feature and meet the emotional need that builds real engagement and trust.
