Was that feedback real, or just polite?
Somebody told you they would use it, or that they loved it. Before you build anything on top of that sentence, five questions about that exact conversation will tell you whether it was evidence or good manners.
Everything runs in your browser. Nothing is sent anywhere, and the answer gets its own link you can send to your team.
About this check.
How do I know if user feedback is real or just polite?
Four things separate evidence from good manners: whether they said it before you showed your solution rather than after, whether they already have a workaround they dislike, whether they have done the thing again without you in the room, and whether you can name a second person who asked unprompted. Enthusiasm after a demo, with no workaround and no repeat use, is a no in better clothes.
Why do users say they like something and then never use it?
Because in a demo they’re reacting to your effort, not to their problem. Being encouraging is the socially correct response to somebody showing you something they made, and “that’s interesting” is what a considerate person says instead of “no”. It is indistinguishable from real interest at the moment it happens, which is what makes it expensive.
What questions should I ask in a user interview?
Ask about the last time the problem happened, in detail, before you describe your solution, or ideally without describing it at all. What did they do, what did it cost them, what did they try first. Past behaviour is checkable. Any question about the future, including “would you use this”, produces a polite guess rather than information.
Is it free, and where do my answers go?
Free, with no account and no email. Everything runs in your browser, nothing is sent to a server, nothing is stored, and I never see what you clicked.
Other checks.
-
Why is nobody using your product?
Which of the five you’re in, why the other four are not it, and the cheap test that confirms it.
-
Is this feature worth building?
Build it, build a smaller version, wait, or say no — with the reason behind it.
-
Should you decide this now, or think longer?
How much of your time this decision deserves, and the one check to run before you commit.
-
Can you charge for this yet?
Whether you’re ready to charge, and what to fix first if you’re not.
-
Why does your team keep redoing the same work?
Which of four things is causing it, and the smallest change that stops it.