Your Users Are Lying to You

You ask "would you use this feature?" They say yes. You build it. Nobody uses it.

This happens to almost every founder. And it is not your users being dishonest. It is how human psychology works. When you ask people what they want, they tell you what they think you want to hear. Or what sounds good in the moment. Or what they imagine they would do in theory.

None of that predicts real behavior.

Why People Cannot Predict Their Own Behavior

Humans are terrible at predicting what they will do in the future. We overestimate how much we will exercise, how often we will cook, and how many books we will read. The same applies to software. "Would I use this?" is a hypothetical question, and people answer hypotheticals with optimism.

Worse, people are polite. If someone shows you something they built with obvious enthusiasm, your instinct is to be encouraging. "Yeah, that sounds useful!" is the socially comfortable response. "I would never open that" is not.

The most expensive feedback is the kind that makes you feel good but leads you in the wrong direction.

Ask About the Past, Not the Future

Do not ask "would you use this?" Ask "when was the last time you tried to solve this problem? What did you do?"

Past behavior is the best predictor of future behavior. If someone has never tried to solve the problem you are addressing, they probably will not use your solution either. If they have tried three different tools and none worked, you have found someone with real pain.

• "How do you handle this today?" tells you whether a real workflow exists.
• "What is the most annoying part?" tells you where the pain actually is.
• "How much time do you spend on this?" tells you whether the pain is worth solving.

Look for Actions, Not Opinions

Not "do you think this is valuable?" but "have you paid for something like this before? How much?" Money is the ultimate signal. If someone has spent money trying to solve this problem, you are on the right track. If they have not, their enthusiasm costs nothing and means very little.

The same applies post-launch. If users say they love your product but do not open it, they do not love it. Usage data is truth. Surveys are opinions. When the two disagree, trust the data.

Ask Uncomfortable Questions

"What would make you stop using this?" "What almost made you cancel?" "What is the one thing that frustrates you the most?"

People are more honest about negatives than positives. Praise is generic. Complaints are specific. The user who says "I love everything" gives you nothing to work with. The user who says "I almost quit because of the export feature" just handed you your next priority.

The best feedback comes from people who have tried to solve the problem and failed. They are not imagining. They are remembering.

Collect Feedback Like Data, Not Validation

The purpose of user feedback is not to confirm what you already believe. It is to find out what you are wrong about. If every conversation makes you more confident, you are probably asking the wrong questions.

Good feedback should occasionally make you uncomfortable. It should challenge assumptions. It should sometimes make you think "well, that changes things." If it never does, you are running a confirmation bias machine, not a research process.

Feedback is data. But only if you collect it right. Ask better questions, and you will build better products.