What product feedback means
Finding what people wish your product did — feature requests, comparisons that name a missing capability, and the workarounds people build because something is absent.
Medium · Product feedback
Monitor Medium for product feedback
Considered write-ups explaining what a tool got wrong — few, slow, and read by everyone who searches your category afterwards.
[01] THE JOB/ PRODUCT FEEDBACK
What it looks like on Medium
A Medium post about your product is almost always a retrospective, and retrospectives are where the most detailed feedback lives. Someone who used your tool for six months and then wrote fifteen hundred words about it has produced better feedback than any survey, and the specific value is that it is structured: what they expected, what happened, what they did instead. The cost of not knowing about one is that it ranks, and every prospect reads it before you get a chance to respond to anything in it.
What Medium will not give you
Volume is low and the signal is slow — this is not a platform where you reply within the hour. It matters because the content lasts, not because it moves.
What FishOut collects from Medium
Articles from Medium’s own search, with the publication attached where there is one. Responses are not searched.
[02] WHAT TO TRACK/ KEYWORDS
Keyword shapes for product feedback on Medium
A keyword tuned for this job on another platform is usually silent here, because the same person writes differently in each place. The example beneath is read the way FishOut reads one: a relevance bar and the label it would carry.
keywords · medium
your product name
Volume is tiny, so a bare name catches everything and everything is worth reading.
category plus retrospective language
"we chose", "six months with", "lessons from", "why we moved". The vocabulary of the posts that carry real feedback and rank.
your name alongside a competitor
A post naming both is a comparison a prospect will read, and its criticisms of you are the ones you will be asked about.
Medium80
Six months with AcmeMail: what worked, what did not, and the two features we ended up building ourselves
Feature request · your label[03] HOW TO SET IT UP/ VIEWS & ROUTING
The configuration that works here
A relevance floor of 50 — near-open, because volume is negligible and every post is worth a read. Route it to product and marketing together: the feedback goes to the roadmap, and the fact that it ranks goes to whoever owns what prospects find when they search your name.
And what to do with what arrives
Labelled and collected rather than answered immediately — describe a label such as "Feature request" and the AI applies it, then save the view. This is the one job where the value is in the aggregate rather than the individual mention.
[04] THE COMMON MISTAKE/ AVOID THIS
Arguing in the comments
A retrospective that ranks is answered by better information, not by a rebuttal underneath it. Replying at length under someone's honest six-month write-up reads badly to exactly the audience you are worried about, and it raises the post's profile. Fix what it is right about and publish your own accurate material on the same ground.
Questions
Other jobs on Medium
Product feedback on other platforms
Reddit
GitHub
YouTube
TikTok24 of a possible 40. A job and a platform only make a page when the intersection has something true of it alone.