Skip to main content
Why asking users directly what they want is a bad idea and what you should do instead.
- July 24, 2026
You sit at your desk in Surat after a long week of user interviews. You asked twenty people exactly what features they want in the new app. They all gave you a huge list of complex ideas. You spent a whole month designing every single thing they asked for. You launch the app and absolutely nobody uses those new features. You feel completely confused and angry because you did exactly what they told you to do.
I know how much this hurts.
But let me tell you a harsh truth over our coffee today. Humans are terrible at predicting their own future behavior. If you ask a user what they want, they will lie to you without even realizing it.
Why asking direct questions is a dangerous trap and what you must do instead.
Users ask for control but actually want magic
Imagine you are designing a new smart home app for 2026 AR glasses. If you ask users what they want, they will ask for fifty different buttons to control every single light bulb. If you build that, the screen becomes a total mess.
They do not actually want fifty buttons. They just want the lights to turn off automatically when they fall asleep. Stop asking them what buttons they want. Ask them to describe the last time they felt frustrated before going to bed. Design the invisible AI magic that solves that specific frustration.
Users say yes just to be polite to you
Think about testing a new financial feature for an app like Cred. You show a user a new voice-activated payment button. You ask them if they would use it every day. They will smile and say yes because they do not want to hurt your feelings.
But when they are alone in a crowded cafe, they will never speak their bank password out loud. Never ask a user about the future. Always ask them to show you exactly how they paid their last bill yesterday. Past behavior is the only truth.
Users ask for complex features but only use the basics
Look at a massive music app like Spotify. If you run a survey, users will loudly demand complex audio equalizer settings. But data shows that ninety-nine percent of people never open the settings menu.
They just want a smart Agentic AI DJ to play good songs while they drive. When a user asks for a complex feature, do not just build it. Ask them why they think they need it. You will usually find a much simpler problem hiding underneath their request.
Common Mistakes to Avoid
Stop ruining your research sessions. Avoid these massive mistakes today.
Asking leading questions.
Do not ask users if they like your new fast checkout screen. Ask them to buy a product and watch silently where their fingers get stuck.
Believing their feature ideas.
Users are not designers. When they give you a solution, ignore the solution. Only write down the underlying pain they are trying to fix.
Showing perfect designs too early.
If you show a user a beautiful and polished Figma prototype, they will only talk about the pretty colors. Show them ugly black and white wireframes so they only focus on the actual problem.
The Final Word
Your job as a designer is not to be a waiter taking orders from a menu. Your job is to act like a smart doctor. A patient tells the doctor their stomach hurts. The doctor does not ask the patient what surgery they want. The doctor runs tests, finds the root cause, and prescribes the exact right medicine. Stop asking users what they want and start watching what they actually do.
