The feedback form nobody fills out.

Process · 4 min read

Every app has one. A little "Give Feedback" button tucked away in the settings menu or buried in the navigation. It's there because it feels responsible. It says "we care what you think." And almost nobody taps it.

When someone does use it, the feedback falls into one of two categories. Either it's vague and unhelpful, something like "it's good" or "I like it." Or it only comes when something is broken. "This doesn't work." "I can't log in." "Where did my data go?" You end up with a feedback channel that's either empty or full of complaints. Neither gives you the insight you actually need to improve the product.

The feedback you're ignoring is already there

The real feedback isn't in a form. It's in the data. Which screens do people spend the longest on? Where do they drop off? What features do they open once and never return to? What do they do immediately after opening the app? That implicit feedback is more honest than any survey because people can't lie with their behaviour. They just do what makes sense to them.

I've seen this play out with clients. A client built a feature they were proud of, a detailed analytics dashboard for their users. They spent weeks refining it. Usage data showed that less than 8% of users ever opened it. Nobody complained about it. Nobody said "remove this." They just quietly ignored it. That silence was the feedback. It told us more than a hundred survey responses could have.

Jakob Nielsen put it simply back in 2001: "The first rule of usability is don't listen to users." Not because their opinions don't matter. But because what people say they want and what they actually do are often completely different. If you ask users what they want, they'll describe an ideal that doesn't match how they behave. Watch what they do instead.

Behaviour tells you what words won't

A user who opens your app, goes straight to one feature, finishes their task, and closes the app is telling you something important. That feature is the reason they're here. Everything else is secondary. If you spend your next sprint improving a different feature, you might be polishing something nobody cares about while neglecting the thing that keeps people coming back.

Look at the path users take, not the path you designed. If they're skipping your onboarding, it's too long. If they're tapping the wrong button, the label is confusing. If they're searching for something that's already on the screen, it's not visible enough. Every confused tap, every abandoned screen, every repeated action is feedback. It's just not wrapped in a tidy form submission.

That doesn't mean the feedback button is useless. Keep it. Some users will use it, and the occasional detailed response can be gold. But don't rely on it as your primary source of insight. The best product decisions come from combining what users say with what they do, and leaning heavily toward the latter when the two don't match.

Build the listening into the product

Instead of waiting for feedback, design your app to generate insight automatically. Simple analytics that track screen views, feature usage, drop-off points, and session length will give you a steady stream of behavioural data. You don't need to ask "what do you think?" when the data is already showing you what people think through their actions.

The feedback form nobody fills out is still telling you something. It's telling you that passive feedback channels don't work. So stop waiting for users to talk and start watching what they do.

Sources
First Rule of Usability: Don't Listen to Users (Nielsen, 2001, Nielsen Norman Group) - What users say they want and what they actually do are often completely different. Observe behaviour, not opinions.

Related blog posts:

Your app's first usability test should embarrass you →

The default matters more than the option →

Your app should know more than your user →