Product
The Difference Between Feedback, Advice, and Validation
, Community Leader
11 minutes
Feedback helps you improve something you've already built. Advice helps you make better decisions by learning from someone else's experience. Validation tells you whether you're solving a real problem before investing more time and resources.
Although these concepts are often used interchangeably, they answer different questions. Understanding the distinction will help you ask better questions, collect more useful information, and make better startup decisions.
If you want to... | You need | Ask |
|---|---|---|
Confirm that a problem is worth solving | Validation | Potential customers |
Improve something you've already built | Feedback | Users or experienced founders |
Learn from someone who's solved a similar challenge | Advice | Experienced founders |
Many founders simply ask for "feedback" whenever they need input. In reality, feedback is only one type of input. Sometimes what they really need is validation from potential customers. In other situations, they need advice from founders who have already faced similar challenges. Treating all three as the same conversation often produces plenty of opinions but very little clarity.
The distinction matters because each type of conversation has a different objective. Feedback helps improve execution. Advice broadens your perspective by sharing experience. Validation reduces uncertainty by testing assumptions. Choosing the right one is often the difference between making steady progress and spending months optimizing the wrong thing.
Why founders confuse feedback, advice, and validation
The confusion usually comes from the fact that all three involve talking to other people. Whether you're speaking with customers, experienced founders, mentors, or investors, you're trying to gather information that will help you build a better business. From the outside, these conversations look almost identical, even though they should produce completely different outcomes.
Consider a simple example. You've just designed a new pricing page for your SaaS product. You ask another founder whether the messaging is clear and whether anything feels confusing. You're asking for feedback. You ask how they introduced pricing changes in their own company. You're asking for advice. You show the page to potential customers to understand whether the value proposition resonates strongly enough that they would seriously consider paying for the product. You're seeking validation.
The pricing page hasn't changed, but the purpose of the conversation has. Feedback evaluates what already exists. Advice shares experience that may help you make a decision. Validation tests whether your assumptions are correct. Once you understand these differences, it becomes much easier to recognize which conversation you actually need to have.
This distinction becomes especially important in early stage startups, where every experiment consumes time and resources. Improving a feature before validating that customers actually need it can waste months of development effort. Following advice that worked for another founder may lead you toward a strategy that doesn't fit your market. Asking for feedback when you really need validation often results in dozens of suggestions but very little evidence that people will buy your product.
Feedback vs Advice: why they solve different problems
The difference between feedback and advice is subtle, which is why founders often confuse the two. Both can improve your business, but they do so in different ways. Feedback focuses on evaluating something that already exists. Advice focuses on helping you decide what to do next.
A useful way to think about feedback is that it begins with observation. Someone reviews your landing page, onboarding flow, sales email, or product demo and describes what they experienced. They point out what was clear, what caused confusion, and what could be improved. Effective feedback is grounded in what the person actually saw or used, making it directly applicable to your current work.
Advice comes from experience rather than observation. An experienced founder might recommend focusing on one acquisition channel before expanding to others, delaying enterprise sales until the product is more mature, or experimenting with annual pricing. Those recommendations can save a significant amount of time, but they are still shaped by the context in which that founder built their company.
This is why advice should not be treated as evidence. A pricing strategy that worked for one SaaS business may fail in another market with different customers, competitors, or pricing expectations. Advice helps you explore possible directions. It does not prove that a particular direction is right for your business.
The simplest way to remember the distinction is to focus on your objective.
Your objective | What you need |
|---|---|
Improve something you've already created | Feedback |
Learn from another founder's experience | Advice |
Confirm that your assumptions are correct | Validation |
If you're clear about what you're trying to accomplish before starting a conversation, you'll ask better questions and receive answers that are far more useful. That clarity also makes it easier to decide who you should be talking to in the first place.
What validation is and when you need it
If feedback helps you improve a solution and advice helps you make decisions, validation answers an even more fundamental question. It tells you whether you're solving a problem that's worth solving in the first place.
This is why validation should happen before you spend weeks refining features, redesigning your landing page, or optimizing your pricing. None of those improvements matter if customers don't actually care about the problem you're trying to solve.
One of the biggest misconceptions among early stage founders is believing that positive reactions are the same as validation. They're not. Someone telling you that your idea is interesting doesn't mean they'll pay for it. Even experienced founders can't validate your product on behalf of your target customers. They can offer valuable advice, but only potential customers can confirm whether your assumptions are correct.
Real validation comes from evidence. It comes from customer interviews, preorders, signups, purchases, or repeated requests for a solution. The stronger the commitment, the stronger the validation.
This is... | Not validation | Validation |
|---|---|---|
Customer reaction | "That's a great idea." | "I'd pay for this today." |
Product interest | Likes and comments | Demo requests or signups |
Market demand | Positive opinions | Customers changing their behavior |
Confidence | Encouragement | Evidence |
A useful way to think about validation is that it reduces uncertainty. Every experiment should answer a specific question. Do customers recognize the problem? Do they understand the value proposition? Are they willing to pay enough to make the business viable? Until those questions have evidence behind them, you're still operating on assumptions.
What effective feedback actually looks like
Once you've validated the problem and started building a solution, feedback becomes far more valuable. At this stage, you're no longer asking whether you should build something. You're asking how to make it better.
Unfortunately, many founders ask for feedback in a way that almost guarantees vague answers. Questions like "What do you think?" or "Any feedback?" invite general opinions instead of useful observations. Most people respond with broad statements because they don't know what kind of feedback you're looking for.
Effective feedback starts with a focused question. Instead of asking whether someone likes your landing page, ask whether the value proposition was immediately clear. Instead of asking whether your onboarding feels good, ask where they hesitated or became confused. Narrow questions produce specific answers, and specific answers are much easier to act on.
The same principle applies when reviewing product demos, pricing pages, emails, or marketing copy. The more precisely you define the problem you're trying to solve, the more actionable the feedback becomes.
Instead of asking... | Ask... |
|---|---|
What do you think? | What was unclear? |
Do you like it? | What would stop you from using it? |
Any feedback? | Which part created the most confusion? |
Does this look good? | What would you improve first? |
How to ask for feedback effectively
Before asking anyone for feedback, decide what decision you're trying to make. If the answer is unclear in your own mind, it will be unclear to everyone else as well.
It's also worth thinking about who is best positioned to answer your question. Existing customers can explain where they struggled while using your product. Experienced founders can point out weaknesses in your positioning or pricing strategy. Designers can evaluate usability. Each group sees different problems because each brings a different perspective.
The most productive feedback conversations also provide context. Rather than sharing a landing page without explanation, briefly describe your target customer and the objective of the page. Rather than asking someone to review your onboarding, explain where users typically drop off. Context allows people to evaluate your work against the outcome you're trying to achieve instead of relying on personal preference.
Finally, resist the temptation to defend your decisions while receiving feedback. If someone misunderstood your messaging, explaining what you intended to say doesn't change what they experienced. Their confusion is often the most valuable insight you can receive because future customers are likely to have the same reaction.
A simple rule to remember
Validation tells you whether to build.
Feedback tells you how to improve.
Advice helps you decide what to try next.
Why advice is often misunderstood
Advice can dramatically shorten your learning curve, but только when you understand its limitations. Every piece of advice comes from a specific company, market, product, and point in time. Even founders who faced similar challenges may have reached different conclusions because their circumstances were different.
This is why advice should expand your thinking rather than replace it. If several experienced founders recommend testing annual pricing, that's a good experiment to consider. It isn't proof that annual pricing is the right choice for your business. The only way to answer that question is to test it with your own customers.
The most valuable advice usually explains why a decision worked, not just what decision was made. Understanding the reasoning allows you to decide whether the same conditions exist in your business. Without that context, advice easily turns into copying someone else's playbook.
How to know whether you need feedback, advice, or validation
Before asking anyone for help, take a moment to identify the decision you're trying to make. Most conversations become more productive once that objective is clear.
If you're unsure whether customers have a meaningful problem, you're looking for validation. If you've already built something and want to improve it, you're looking for feedback. If you're choosing between different approaches and want to learn from someone who's already been there, you're looking for advice.
A simple question before every conversation can save a surprising amount of time:
"Am I trying to prove an assumption, improve a solution, or learn from someone else's experience?"
The answer usually tells you exactly what kind of input you need.
If your goal is... | Ask for... | Best source |
|---|---|---|
Test an assumption | Validation | Potential customers |
Improve execution | Feedback | Users or experienced founders |
Learn from experience | Advice | Founders who've solved a similar problem |
Common mistakes founders make
Once you understand the distinction, many common startup mistakes become easier to spot.
The first mistake is asking for feedback before validating the problem. Founders spend weeks polishing onboarding flows, pricing pages, or user interfaces without knowing whether customers actually need the product. Better execution cannot compensate for solving the wrong problem.
The second mistake is asking experienced founders to validate an idea. Experienced founders can often predict risks, suggest alternative approaches, and share lessons from similar situations. What they cannot do is tell you whether your customers will buy. Only your target market can provide that answer.
The third mistake is treating every opinion equally. A casual comment on LinkedIn, detailed feedback from an existing customer, and advice from a founder who has built a similar business all have different levels of relevance. Collecting more opinions doesn't automatically lead to better decisions. Choosing the right source of information matters much more.
Finally, many founders stop at positive reactions. Compliments feel encouraging, but encouragement is not evidence. The goal isn't to hear that your product looks promising. The goal is to understand whether people will actually change their behavior by using or paying for it.
Common mistake
Founders often ask for feedback when they actually need validation. As a result, they improve ideas that should have been tested before they were refined.
Final thoughts
Building a startup means making hundreds of decisions with incomplete information. No framework can remove uncertainty completely, but asking the right question is one of the easiest ways to reduce it.
Feedback, advice, and validation are not interchangeable. Each serves a different purpose, each should come from different people, and each creates value at a different stage of building a business. Understanding that distinction helps you spend less time collecting opinions and more time making progress.
The next time you're about to ask someone for feedback, pause for a moment. Think about what you're really trying to learn.
If you need to know whether a problem is worth solving, seek validation.
If you want to improve something you've already built, ask for feedback.
If you want to learn from someone who's already solved a similar challenge, ask for advice.
Choosing the right conversation is often more important than choosing the right answer.
