Why product teams ignore feedback, and what gets heard
It is rarely that nobody cares. Feedback gets lost in ordinary ways, and the person writing it can fix most of them.
If you have ever written a long, careful message to an app's support team and got back a polite template, you know the feeling. It is easy to conclude that nobody reads feedback. Often the truth is duller than that. The message was read, by someone whose job was to close the ticket, and the useful part never reached the people who decide what gets built.
Most of the reasons feedback goes nowhere are ordinary, and the person writing it can fix most of them.
Where feedback ends up
Feedback arrives through many doors: support chats, emails, app store reviews, replies on social media, a sales call, a word with a delivery partner. Each door tends to be watched by a different person with a different job. A support agent is there to solve your problem today. A social media manager is there to keep things calm. Neither is usually the one deciding next quarter's work.
On the way from those doors to a planning meeting, feedback gets summarised. "User reports issue with payments" may be all that survives of your three paragraphs about the payment page timing out during a Tatkal booking. The detail that made your message useful is the first thing to go.
That is how the same request, sent ten times through ten channels, can look like ten unrelated messages. Nobody is counting them in one place.
Vague feedback cannot be acted on
Even when feedback reaches the right person, much of it is too vague to use. "The app is slow" could mean the home screen, the search, the checkout or the map. It could be the phone, the network or a real bug. A team that wants to help still has to guess, and guesses lose to work that is already clear.
Feedback a team has to guess at, and feedback they can use
Vague
Your app is so slow these days. Please fix it.
One person is easy to ignore
A single message, however good, reads as one person's preference. Teams are right to be careful with those, because building for one loud user can make a product worse for everyone else.
What changes the picture is the same request, in one place, with many people saying they want it too. Then it stops looking like a preference and starts looking like demand. It helps even more when those people say something about themselves: that they use the product, how often the problem happens to them, and whether they would pay for a fix.
Bundled requests work against this. A post asking for five changes splits the people who agree with it five ways, and a team cannot tell which change the votes were for. One request per post keeps the signal clean.
Quick question
A food delivery app's team reads these four messages on the same day. Which is most likely to lead to a change?
Teams have reasons you cannot see
Some good requests get turned down for reasons that are invisible from outside. A payments change may need a partner bank to agree. A feature may be held up by regulation. A screen may be about to be replaced, so fixing it now would be wasted work. Sometimes the request is good and the team simply has three better ones ahead of it.
None of that is your fault, and you cannot fix it. What you can reasonably expect is an answer. A clear "not planned" with a reason is a far better outcome than silence, because it tells you to stop waiting and maybe look at another product. And a team that explains its nos is easier to believe when it says yes.
What gets heard
Put together, the requests that get acted on tend to have four things in common. They are specific. They are in one public place. They have other people behind them. And they show some cost: time lost, money spent, a workaround someone keeps doing.
Make your feedback hard to miss
0/7How Suggst helps a request get heard
Suggst is built for the gap between the support ticket and the planning meeting. Each product has a public page where its requests collect in one place. People vote with I want this too, mark I use this product and I'd pay for this, and answer How often does this happen to you? with daily, weekly, monthly or rarely. Comments can be marked helpful, so the most useful detail is easier to find.
Product teams can claim their page by signing in with a work email at the product's domain. Once they have, they can reply to posts and set statuses: planned, in progress, shipped or not planned. Posts a team picks show Picked by with the product's name. If a team has not claimed its page, the page is still public, and the votes keep adding up where anyone can see them.
To widen the circle, make a group list of the requests that matter to your building, office or family and share one link in your WhatsApp group. Votes on the list go straight to the posts. You can also follow a product to get its new posts in a Monday email.
If you are about to write one, start with how to write a feature request. If you work on a product team, running a public roadmap covers the other side of this.
Post the request you have been sending to support, somewhere other people can back it.
Write a requestWritten by the Suggst team. Example requests about real apps are made up to show how to write them, not reports about those apps.