How to Handle Negative Feedback in Public
Negative comments on a listing or thread are permanent and indexed. How to respond, when to concede, when to correct, and when to say nothing.
Published 2026-09-27 · 4 min read
Public criticism of a product is permanent, indexed against the product name, and read by every future evaluator. How a founder responds is read alongside it, and a good response to bad feedback does more for the product than the feedback did against it.
This is the discipline, including the responses that feel right and cost the most.
The four types, and what each needs
| Type | Example | Response |
|---|---|---|
| Factually wrong | "It does not support CSV export" when it does | Correct it plainly, with where to find it. No triumph, no elaboration |
| True and fixable | "The onboarding is confusing" | Agree, say what you are changing, and follow up when you change it |
| True and a deliberate trade-off | "It is expensive for a solo user" | Agree it is true, explain the reasoning, and say who it is not for |
| Bad-faith or abusive | Insults, or criticism with no content | Nothing. Do not reply, do not delete unless it violates the platform's rules |
The response that works
- 1
Answer the substance first
Not the tone, not the framing, not the implied motive. The substance. Everything else in the reply is secondary and most of it should be cut.
- 2
Concede what is true, immediately and without qualification
"You're right, it fails on files over 50MB" is a complete sentence. Adding "but that's an unusual case" or "most users don't hit that" undoes the concession and reads as deflection.
- 3
Say what happens next, specifically
"We're looking at it this week" is better than "we'll look into it", and "fixed in the next release, out Thursday" is better than both. A vague commitment is worth nothing.
- 4
Keep it to three sentences
Longer reads as defensive. The length of a reply to criticism is inversely related to how confident it appears.
- 5
Do not apologise excessively
One acknowledgment is enough. Repeated apology reads as panic and invites further pressure.
- 6
Follow up when you fix it
Reply to your own comment weeks later: "this shipped." It is the single most credibility-building action available and almost nobody does it
What never works
- Arguing about tone. "You could have said that more nicely" may be true and is always a loss. The reader judges the exchange on substance.
- Questioning the critic's expertise. Even when they are wrong, this reads as deflection and invites the audience to side against you.
- Explaining why they misunderstood. Almost always a description of your own unclear communication. Fix the communication instead.
- Comparing to competitors. "At least we're not like X" makes the criticism about someone else's product, which is not what was asked.
- Deleting it. Unless it violates platform rules, deletion is visible, is resented, and turns a complaint into a story.
- Replying to every follow-up. One clear response, then stop. Continued exchange is a feud and feuds are what a product becomes known for.
When the criticism is correct and damaging
Sometimes a critic identifies a real failure and states it well. This is the hardest case and the one with the most upside.
- Agree completely and specifically. Not "we appreciate the feedback" but a description of the actual problem, in their terms.
- Explain the constraint honestly if there is one. "That requires a rewrite we cannot do before Q2" is more credible than a promise.
- Say what you are doing about it and when. A date you will meet beats an intention.
- Ask for their help if genuine. "If you hit it again, can you send the file?" converts a critic into a contributor more often than anything else.
- Then actually do it, and post the follow-up. This sequence — concede, commit, deliver, report — turns the most damaging criticism into the strongest evidence available about how the product is run.
The internal part
Public criticism of something you built is unpleasant, and responding well requires managing that before typing.
- Wait an hour. Nothing good is written in the first ten minutes after reading a criticism you think is unfair.
- Read it for the factual content only. Strip the tone mentally and ask whether the fact is true. Usually part of it is.
- Draft it somewhere private first. Then cut a third of it. The cut portion is almost always the part defending you rather than answering them.
- Have someone else read it if it matters. A second person catches the defensiveness you cannot see.
- Collect the criticism somewhere. Repeat complaints across platforms are your roadmap, and they are easy to lose when each one arrives as a personal affront.
Turning it into an asset
| Criticism | Becomes |
|---|---|
| A repeated complaint | A changelog entry, then a note in the description so the next person knows |
| A misunderstanding of what the product is for | A clearer first sentence on the landing page and every listing |
| A pricing objection | A line on the pricing page explaining what the price covers |
| A missing feature people assume exists | An FAQ entry stating plainly that it does not exist and whether it is planned |
| A well-argued criticism you agreed with | A quote on your site, with permission — the most credible marketing content available |
Nobody decides against a product because someone criticised it. They decide against it because the founder's reply made them look defensive, evasive or careless — and that is entirely within your control.
More in Community playbooks
- How to Find and Join AI Newsletter CommunitiesNewsletter authors and their reader communities are a reachable audience for a new AI product. How to find them, get on their radar, and get mentioned.
- Product Hunt Community: How to Engage Before You LaunchA launch-day platform rewards the people who were already there. How to build standing in a launch community in the months before you need it.
- How to Answer Questions in Public Without SellingThe helpful-answer channel: how answering strangers' questions builds an audience for an AI product, what a good answer contains, and where the line is.