Skip to the feed
BizHub
Post a launch

Giving Feedback That Actually Helps Another Founder

Community · 8 min read ·

How to give feedback on someone's product, page or pitch so that it is kind, specific and useful: ask first, describe, explain and suggest.

Illustration: Two speech bubbles linking: a question mark from one avatar and a lightbulb from another, soft pastel palette

Almost every founder wants feedback and almost every founder dreads it. The wanting is rational: fresh eyes spot what you cannot. The dread is human: you have put weeks into something, and now someone will say what is wrong with it. Giving feedback well is one of the most generous things you can do in a community, and one of the easiest to do badly.

This article sets out a simple way to give feedback that helps, and to receive it with grace.

Why feedback goes wrong

Most bad feedback fails in one of a few ways.

It is vague. "I did not like it" or "it feels off" gives the person nothing to act on.

It is about the person. "You clearly have not thought this through" attacks the founder, not the work.

It arrives uninvited. Unsolicited criticism, especially from strangers in public, is rarely welcome.

It prescribes. "You should do X" may ignore constraints the founder knows and you do not.

It lacks context. Without knowing who the audience is, you may criticise the wrong thing.

It is only negative. Without noting what works, a founder may change things that were fine.

Understanding these traps makes it easier to avoid them.

Ask before you give

A simple question changes the dynamic: "Would you like my honest thoughts on this?" If the answer is yes, you have permission. If they say no, you have saved yourself both trouble and time.

It also helps to ask what kind of feedback they want. "Do you want feedback on the wording, the layout or the whole idea?" "Is this a draft, or is it going live tomorrow?" "Who is it for?" The answers help you target what matters.

A simple structure: observe, explain, suggest

A reliable format has three parts.

1. Observe

Say what you saw or experienced, in neutral terms. "When I opened the page, the first thing I noticed was the large image. I could not find the pricing link for a few seconds."

This is a fact about your experience, not a judgement about quality. It is hard to argue with, and it shows the founder what a real visitor encountered.

2. Explain

Say why it matters, or what you felt. "I was looking for a price because I wanted to know whether this was for a team my size, and I nearly left."

Explanation gives the founder the reasoning so that they can decide whether it applies.

3. Suggest

Offer an idea, framed as an option. "You might try putting pricing in the main menu, or adding a line under the headline. I do not know which would suit you better."

A suggestion is a gift, not an order. The founder can accept, adapt or ignore it.

Say what works too

Mention what you liked, but be specific and sincere. "The two-line explanation under the headline made it clear immediately what the product does" is useful, and it tells the founder what to keep. Avoid the old "praise sandwich" in which compliments are used as padding around a criticism. People see through it. Genuine, specific appreciation is different: it is information.

Be specific

Compare these:

  • "The copy is confusing."
  • "In the second paragraph, I could not tell whether 'workspace' meant a folder or a team. I read it twice."

The second is something the founder can fix in a minute.

When you can, point to the exact place: a line, a screen, a step. Screenshots with notes help, as do short voice recordings of your first reaction.

Be honest and kind

Honesty and kindness are not opposites. The aim is to tell the truth in a way the person can hear.

  • Use "I" statements: "I got lost" rather than "this is confusing".
  • Separate the work from the person. "This page" not "you".
  • Avoid absolutes. "Never" and "always" provoke defence.
  • Do not soften the point until it disappears. If something is a real problem, say so clearly.
  • Consider timing. A founder hours before launch needs a different kind of feedback from one in early design.

Google's own advice for replying to reviews of a business offers a similar spirit: be professional and polite, keep responses concise, address the person by name, acknowledge specifics and, for negative points, show empathy. Those principles apply as well to giving feedback as to answering it.

Know your limits

State your perspective and what you do not know. "I am not a developer, so I cannot comment on the technical side, but as a customer I found..." Honest boundaries make your feedback more credible.

If you are a potential customer, say so, and say what would make you buy. That is gold for a founder. If you are a competitor, be transparent about it, and be careful to avoid advising in a way that could mislead.

Keep it proportionate

Do not list thirty problems. Choose the three that matter most. A long list overwhelms and risks burying the one change that would make the biggest difference. If you have more, offer to share them later.

Public or private?

Think about where to give feedback.

  • Public can help others learn and show support, but it can embarrass the person if it is critical.
  • Private lets you be more candid and gentler. For sensitive points, send a message.
  • Group settings such as feedback threads where people have agreed to receive comments suit open critique.

When in doubt, offer to discuss privately.

Receiving feedback well

Because you will be on the other side too, a few reminders help.

  1. Listen first. Resist the urge to explain or defend.
  2. Ask clarifying questions. "Which part was unclear?" "What did you expect to see?"
  3. Take notes. You will remember less than you think.
  4. Thank the person. Even if you disagree.
  5. Wait before deciding. Sleep on it.
  6. Look for patterns. One person's view is a data point. Several saying the same thing is a signal.
  7. Close the loop. Tell the person what you did with their advice. They will be more likely to help again.

Wikipedia's description of online communities notes that members need benefits to compensate for the costs of participation. Feedback that is received graciously is one of those benefits, because it rewards the person who took the trouble.

A worked example

A founder posts a landing page and asks for thoughts. A helpful reply might read:

"Thanks for sharing. I read it as someone who runs a three-person shop. What worked: the headline told me straight away what the tool does, and the demo video was short. What tripped me up: I could not find pricing, and I was not sure whether the free plan was permanent or a trial, which made me hesitate. You might try adding a pricing link to the top menu and a one-line note under the sign-up button saying what the free plan includes. I am not sure how it looks on mobile, as I only saw it on my laptop. Happy to look again after changes."

It is specific, kind, honest about its limits and actionable. It would take two minutes to write and could change the founder's week.

Make it a habit

Set aside a little time each week to give feedback to someone. It sharpens your own thinking and builds goodwill. Over months, you will be known as a person whose comments are worth having. The about-the-founders page names the founders of BizHub Launch, if you want an example of a plain introduction.

Common mistakes

  1. Giving feedback without being asked.
  2. Being vague.
  3. Being cruel for effect.
  4. Dumping a long list.
  5. Ignoring the founder's context.
  6. Forgetting to follow up.

Feedback on different kinds of work

The same method adapts to different situations. For a landing page, describe what you noticed first, what you thought the product was and what you would have wanted next. For a pitch or a story, say where your attention rose and fell and where you got lost. For a product demo, describe the moment you understood the value, or the moment you stopped following. For a pricing decision, share how it would look from a customer's chair without pretending to know their numbers. In each case, you are offering a single reader's honest experience, which is exactly what the founder cannot get from inside their own head.

Giving feedback in writing versus in conversation

Written feedback lasts and can be reread, but tone is easily lost. Reread yours before sending and remove any phrase that could sound sharper than you intend. In conversation, tone comes through naturally and the founder can ask questions, but details are forgotten. A good compromise is to talk, then send a short written summary of the two or three main points. That way, the warmth of the conversation and the clarity of the note both survive.

Frequently asked questions

What if the founder reacts badly? Stay calm, thank them and step back. You cannot control how people react.

Can I give feedback on a competitor's product? You can, openly and fairly, but be aware of how it looks. A neutral perspective is often better coming from someone with no stake.

Should I ask for feedback on my own work in return? It is natural to reciprocate, but do not make it a condition.

Questions and answers

Should I give feedback if nobody asked?
Usually ask first. Unsolicited criticism often lands badly, while an offer such as 'would you like my thoughts on this?' gives the person a choice.
How do I be honest without being harsh?
Describe what you saw and how it affected you, explain why, and suggest an alternative. Avoid judging the person.
What if I am not an expert?
Your reaction as a first-time reader is valuable. Say what you understood and where you got lost.
How should I receive feedback myself?
Listen without defending, ask clarifying questions, thank the person and decide later what to act on.

Sources

Related guides

Get help