Handling Feedback From Your First Visitors

The first people to try your product will tell you things your friends will not. They are not trying to be kind, and they do not know your intentions. They simply meet the product as it is, and their reactions, spoken or silent, show you what it really looks like from outside.

That is a gift, and it can also feel like a weather event. This guide helps you collect feedback, make sense of it and use it without being knocked over by it.

Why early feedback matters so much

Early feedback is the cheapest research you will ever do. A change made now costs an afternoon. The same change after a thousand people have built habits around the old way costs far more. Early visitors also reveal the gap between what you think you built and what people think they are seeing, which can be wide.

Product Hunt's launch guide makes a similar point about comments: they let makers gather feedback and often open the door to networking, partnerships and even funding. The conversation is where the value lies.

Make it easy to give

People will not go out of their way. Remove effort.

• A visible feedback link on the product and in your emails.
• A short question at a natural moment: "Was this clear?" after the first task.
• A direct email address that reaches a human.
• Replies to comments that invite more: "What did you expect to happen?"
• A quick call offered to a few people who seem engaged.

Avoid long surveys. Three questions get answered. Twenty do not.

Ask better questions

How you ask shapes what you hear.

Weak: "Do you like it?" (Invites polite yes.)

Better: "What were you trying to do when you came here?"

Better: "What nearly stopped you?"

Better: "What did you use before?"

Better: "If this disappeared tomorrow, what would you do instead?"

Past behaviour is a stronger guide than opinions about the future. "Would you pay for this?" produces optimism. "What do you pay for now?" produces facts.

Hacker News's comment guidance suggests asking genuine questions instead of interrogating, and offering constructive alternatives instead of criticism. That is good advice for the people giving feedback and for you when you respond.

Watch what people do

Words are only half of feedback. Behaviour is the other half.

• Where do people click first?
• Where do they stop?
• What do they ignore?
• How long do they spend?
• Do they come back?

Simple analytics can show these. Better still, watch a few people use the product in front of you, in silence, as they would at home. You will see confusion that no one would think to report.

Sort what you hear

After a week, you will have a pile of comments, emails and observations. Sort them into three groups.

Bugs. Things that do not work. Fix the serious ones fast.

Confusions. Things that work but are not understood. These are copy and design problems, often cheap to fix.

Requests. Things people would like added. Handle these with care.

A simple spreadsheet works: date, source, what was said, group, how many times.

Look for patterns

One comment is a data point. Several comments pointing the same way are a pattern.

• Count. How many independent people said it?
• Check who. Are they the people you are building for?
• Look for the problem under the request. "Add a calendar view" may really mean "I cannot see what is due this week".
• Notice what is missing. If nobody mentions the feature you are proudest of, that is a message too.

Do not give equal weight to every voice. A paying customer's detailed complaint is worth more than a passing remark.

Handle harsh feedback

Some feedback will sting.

1. Pause. Do not reply immediately.
2. Read it again for facts. Strip the tone. What is the observation?
3. Thank the person. They took the time.
4. Ask if it is unclear. "Could you tell me what you were trying to do?"
5. Do not defend. If you disagree, explain once, calmly.
6. Act, or explain why not.

Some comments are not worth engaging. Abuse can be ignored and reported. But hard feedback delivered bluntly is often the most honest, and if you can look past the tone you will learn something.

Respond so people want to help again

The way you respond decides whether the person ever writes again.

• Reply quickly, at least to acknowledge.
• Be specific. "Thanks, I have noted the export problem and we are fixing it this week."
• Close the loop. When you fix something, tell the person who reported it.
• Credit them, with permission.
• Never promise what you cannot deliver.

People who see their feedback acted on become allies.

Decide what to build

You will never have time to do everything. Choose using a few filters.

1. Does it serve the core purpose? The reason someone uses the product.
2. How many people want it, and how badly?
3. How much will it cost to build and maintain?
4. Does it fit the audience you are aiming for?
5. Is there a simpler way to meet the underlying need?

Pick the top three and write them down. Do those first. Explain publicly what you chose and why, and mention what you are not doing yet.

Saying no kindly

You will decline most requests. Do it with respect.

"Thanks, I can see why that would help. We are keeping the product small for now, so I do not plan to add it soon. Here is a workaround that might help in the meantime."

Honest refusals build more trust than vague promises.

Share what you learn

Telling your audience what you learned, and what you changed, reinforces the relationship. A short update: "You told us the sign-up was too long. We cut it from five steps to two." Show that the conversation went somewhere.

Google's helpful-content guidance emphasises creating work for people and evidence of real expertise and care. A visible record of listening and improving is one way to show it.

Common mistakes

• Collecting but not acting.
• Acting on everything.
• Asking only friends. They will be kind.
• Defending the product in the thread.
• Treating feedback as a verdict on yourself.
• Ignoring silent users.
• Forgetting to say thank you.

A weekly feedback routine

Spend an hour each week: read all new feedback, update your spreadsheet, pick the top three themes, reply to anyone you owe a reply, and write one line on what you will change. After a month, you will see patterns clearly, and your product will already be better for it.

On this site

The comments on your entry are a place for early feedback. The submit page begins a listing, with a launch entry currently $5. The launch calendar is where early visitors are likely to find you. The people who run the site are named on the about-founders page.

A worked example of sorting feedback

Suppose you launched a small budgeting app and, after a week, you have twenty-three pieces of feedback. Sorting them reveals the following. Four people said the sign-up asked for too much before showing anything; that is a confusion, and it is cheap to fix by delaying the questions. Three people reported that the monthly chart showed the wrong total when a transaction was edited; that is a bug, and it comes first. Five people asked for a bank connection; that is a request, and it is expensive and carries risk, so you ask each of them what they currently do instead. Two said the colours were hard to read; that is a design confusion with an accessibility angle, and it rises quickly in priority. Nine comments were praise with no detail, which you thank people for and use to ask follow-up questions.

The top three actions are therefore the chart bug, the sign-up order and the colour contrast. The bank connection goes on a list with notes from the five conversations. Notice that the most numerous request did not win, because cost and risk mattered, and that the small accessibility point jumped the queue because it affected who could use the product at all.

Keeping a feedback diary

A short diary of feedback kept over the first three months becomes a precious record. Note the date, the source, what was said and what you did. When you review it, you can see which fixes actually reduced complaints, which requests faded and which grew. It also helps you write honest accounts of your progress later, because you can show what people told you and how you responded. Founders who keep such a record tend to make steadier decisions, since they are working from evidence rather than from the memory of the loudest recent comment.

The takeaway

Make feedback easy to give, ask questions about behaviour, watch what people do, sort what you hear, look for patterns and respond with thanks. Then change something and tell people. That cycle, repeated, is how a first impression becomes a good product.