User Need vs User Want - What You Need to Know

Your users are lying to you. Not on purpose. But they are.

Here's the thing. People say they want one thing. But actually need something completely different. That gap? That's where bad design lives.

Someone says "I want more filters on Zomato." But what they actually need is to find good food, fast, without overthinking it. More filters = more decisions = more stress. The want and the need are literally opposites here.

This happens everywhere. On IRCTC, people say they want a better-looking app. But what they need is to book a ticket without wanting to throw their phone. Two very different problems.

So why does this matter for you?

If you design for the want, you're just decorating. If you design for the need, you're actually solving something. That's the difference between a pretty app and a useful one.

User need is the real problem underneath what someone says. It's the "why" behind the request. When someone says "make the button bigger," the need is probably "I can't find what to tap." Dig deeper. Always.

And to find that need, you use user empathy - basically, you stop assuming and start actually understanding what the person is going through. Not just what they click. What they feel before, during, and after.

Zomato's designers didn't just listen to "we want more options." They understood that people are hungry, impatient, and slightly lazy at 8pm. That empathy shaped everything.

Quick ways to catch yourself:

• Ask "why" three times before designing anything
• Watch someone use your app. Don't explain. Just watch.
• If a user request sounds too specific, zoom out

The best designers aren't the ones who give users what they ask for. They're the ones who figure out what users actually need, and make it feel like exactly what they wanted.

Takeaway: Next time someone gives you feedback, don't open Figma yet. Ask why first.