Handling Criticism in Public Threads
Community · 8 min read ·
Public criticism of your product or your work is painful and useful. A calm routine for reading, responding, learning and deciding when to step away.
It might be a comment under your update, a reply in a community thread, a review of your product or a post that mentions your name. Somebody has said that what you built is bad, or that you were wrong, or that you cannot be trusted. Your stomach drops. You start composing a reply in your head, and it is not a good one.
Every founder who shares their work will face this sooner or later. Handled well, criticism can improve your product and your reputation. Handled badly, it can cost you both. This article offers a calm routine for the moment.
First, do nothing
The first rule is to wait. Close the tab, stand up, walk around the block, make a drink. Replies written in the first ten minutes tend to be defensive, sarcastic or too long. A short pause costs nothing and changes the result.
If the comment appears to be urgent, for example a claim that your service has exposed someone's data, reply briefly to say you have seen it and are looking into it, then investigate. Otherwise, wait.
Read it properly
When you are calmer, read the comment again, slowly. Ask:
- What exactly is being said?
- Is there a specific complaint, or is it a general opinion?
- Is there a question hidden inside it?
- What is the person feeling: frustrated, disappointed, scared, unfairly treated?
- Is it addressed to me, or about me?
Often the first reading makes a comment seem worse than the second.
Sort it
Criticism comes in different kinds, and each deserves a different response.
Legitimate feedback
A specific, fair point about your product or work. "The export loses formatting." "The pricing page does not explain what happens after the trial." This is a gift, even when delivered clumsily.
A misunderstanding
The person has misread something, or lacks information. "You do not support Android" when you do. These need a calm, clear correction.
A disagreement
The person has a different opinion about a choice you made. "I think it is wrong to charge for this." You do not have to agree, but you can explain your reasoning.
A complaint about an experience
Someone had a bad time, perhaps with support or billing. Empathy and action matter most.
Unfair or inaccurate claims
Statements that are false or misleading. Handle with facts and restraint.
Abuse
Insults, harassment, threats or discrimination. This is not feedback. It is behaviour that breaks community rules.
Decide whether and how to respond
You do not owe a reply to everyone. Replying can help when:
- There is a specific point you can address
- There is a question you can answer
- Others may be reading and benefit from your response
- The person has had a bad experience you can fix
Staying silent, or only responding privately, can be better when:
- The comment is purely abusive
- The thread has turned into an argument among others
- A reply would only prolong a pointless exchange
- The matter involves private information
When in doubt, a short, courteous reply is usually better than silence, because other readers see how you behave.
How to reply
Google's advice on replying to reviews of a business is a good template for public replies in general. It recommends being professional and polite, keeping responses concise, addressing the person by name, acknowledging what they said and responding promptly. For negative comments in particular, it suggests showing empathy, acknowledging mistakes honestly without accepting blame for things outside your control, apologising sincerely where warranted and offering to continue offline for complex issues. It also advises against promotional language in replies.
Here is a simple structure.
- Thank them or acknowledge them. "Thanks for telling us."
- Show you understand. "I can see why a missing export would be frustrating."
- Give facts or explain, briefly. "That field is not included in the current version."
- Say what you will do. "I have added it to our list and will update you here."
- Offer a next step. "If you would like, email me and I will help you move the data manually."
Keep it short. Avoid sarcasm, even mild. Avoid capital letters. Avoid defensiveness: phrases like "as we already said" or "you clearly did not read" rarely help.
When you are in the wrong
Sometimes the critic is right. Say so. "You are right, we made a mistake. I am sorry. Here is what happened and what we have done about it." A straightforward apology is disarming, and it earns respect from everyone reading. Do not add excuses to it.
If the mistake caused harm, act as well as apologise. Fix the problem, tell people affected and explain what will change.
When you are not
If the comment contains a factual error, correct it politely and once. "To clarify, we do not store card numbers. Payments are handled by our payment provider. Here is the page that explains it." Provide evidence if you can. Then stop. Do not keep arguing, because the person you are trying to persuade is often not the critic but the silent readers.
When it is abuse
Abuse is not criticism. Do not engage. Use the tools the community provides: report, mute, block. Wikipedia's description of online communities notes that they depend on norms and moderation to stay healthy, and that moderators enforce rules and manage content. If you are a moderator yourself, apply the rules fairly and consistently. If you are not, trust those who are, and keep a record of anything serious.
If you receive threats, contact the platform and, where necessary, the police. Look after yourself.
Look for the signal
After the sting fades, mine the comment for what is useful.
- Is there something you can fix quickly?
- Is there a pattern: have others said the same thing?
- Is there a misunderstanding that suggests your messaging is unclear?
- Is there an unmet need hiding in the complaint?
Keep a simple log of criticisms and what you did about them. After a few months, you will see which themes recur, and you can prioritise.
Close the loop
When you act on feedback, tell the person. "We have fixed the export issue. Thank you for flagging it." People remember being heard, and often change their view of you. Critics can become your best advocates when they see you take them seriously.
Protect your energy
Public criticism can eat your day and your confidence. Take care of yourself.
- Limit how often you check comments, especially at night.
- Have a friend or peer you can show harsh comments to for perspective.
- Remember that one person's view is one view.
- Take breaks from the platform if needed.
- Do not read the comments when you are already tired or upset.
Prepare in advance
You can make criticism easier by setting things up before it happens.
- Write down your values for how you respond: polite, honest, brief.
- Draft a few templates for common situations, such as a bug report or a pricing complaint, and adapt each one personally.
- Agree with your team who responds and how.
- Keep your documentation clear so you can point to it.
- Have a support route so that complaints can move to private channels.
A worked example
A founder posts an update about a new pricing structure. A commenter writes, "This is a cash grab. You used to be free and now you want money for basic features."
She waits twenty minutes. She reads it again and sorts it: a disagreement, with a hint of a complaint about change. She replies: "Thanks for saying so, Jordan. I understand that a change like this is frustrating. The free plan still includes the core features, and the new plan adds team sharing and history, which cost us more to run. I am sorry that the announcement did not make that clear. I have added a comparison table to the pricing page. If it still does not suit you, email me and I will help you export your data."
Jordan does not reply, but two other people thank her for the explanation, and one asks a question about the free plan. She updates the announcement to make the difference clearer and adds a note about it. The criticism led to a better page and a calmer thread.
Common mistakes
- Replying immediately.
- Arguing point by point.
- Taking it personally.
- Deleting criticism that is fair. Unless it breaks rules, removing it looks defensive.
- Ignoring everything.
- Letting one comment spoil your week.
Frequently asked questions
Should I remove negative comments from my own posts? Only if they break the community rules. Removing fair criticism harms trust.
What if a competitor is the critic? Respond to the substance politely, and let readers judge.
How do I get better at this? Practice, and reflect afterwards on what went well. The more you do it, the less it stings.
The about-the-founders page shows a plain introduction of two founders, and the contact page shows how people can reach us privately when a matter needs more than a thread.
Questions and answers
- Should I reply to every critical comment?
- Not necessarily. Reply to those that raise real points or questions, ignore those that are only abusive and never reply while angry.
- How quickly should I respond?
- Promptly enough to show you are listening, but only once you are calm. A short acknowledgement can buy time for a considered answer.
- What if the criticism is unfair or wrong?
- Correct facts politely and briefly, give your evidence and then stop. Readers judge you by tone as much as by content.
- When should I involve moderators or step away?
- When comments are abusive, harassing or breach the rules, or when the exchange is no longer constructive.