Stop asking "Would you use this?" Ask these 4 questions instead

Jaskaran Singh — Tue, 03 Nov 2026 06:35:37 +0000

You've heard it before: "Yeah, I'd totally use that." Then you build the feature, ship it, and almost nobody touches it.

The problem isn't your users. It's the question. Here are the three takeaways up front:

Opinions are free. People say yes to be polite, and it costs them nothing.
Behavior costs something, so it is the only validation signal worth trusting.
Ask about the last time the problem happened, not about a future you're hoping for.

Why "Would you use this?" fails

When someone answers "Would you use this?", they are imagining a hypothetical version of themselves with free time, free money and perfect discipline. Saying yes costs them nothing, and saying no feels rude. So almost everyone says yes.

Real behavior is different. It takes time, effort, money or a change of habit. That is why behavior is the signal that counts.

The 4 questions to ask instead

"How did you solve this the last time it happened?" This forces a real story instead of an opinion.
"What did you try first?" It shows what they already believe a solution looks like.
"What did it cost you, in time, money or effort?" If the cost was tiny, the problem may not be worth solving.
"What did you do next?" It reveals whether they kept going or gave up.

How to read the answers

Real signals

A messy workaround they built themselves (a spreadsheet, a chain of scripts, a pile of sticky notes)
Money or time they already spent on the problem
They keep coming back to the problem again and again

Warning signs

"I'd probably use it" with no story about the last time it happened
No workaround and no spend, because the problem hasn't hurt enough yet
Enthusiasm about the idea, but none about the problem

An example (illustrative)

Weak: "Would you use an app that tracks your freelance invoices?" → "Sure, sounds useful!"

Strong: "How did you handle your last late invoice?" → "I have a spreadsheet and I chase people on WhatsApp every Friday. It takes me about an hour."

The second answer gives you a workaround, a cost and a habit. That is a product brief.

A checklist before you build the next feature

Can I name three people who hit this problem recently?
What did each of them do about it?
What did it cost them?
Am I building from a story, or from compliments?

Conclusion

Swap the opinion question for a behavior question, and build only what past behavior proves is needed. Opinions are free, and behavior takes time.

I turned this into a short reel and carousel for founders if you prefer a visual version: https://www.instagram.com/p/DfRB5jHRpqM/

I'm Jaskaran, a full-stack developer who helps early-stage startups turn ideas into products. What's the worst validation answer you've gotten? Tell me in the comments.