Validation is not asking whether people like your idea

Many entrepreneurs believe they are validating when they show their idea to someone and receive a positive reaction.

“Sounds good.”
“I would use it.”
“That seems interesting.”
“It makes sense.”
“It could work.”

That kind of response is reassuring.

But it rarely validates anything important.

Because validation is not asking whether people like your idea.

It is not, because saying an idea sounds good costs almost nothing. It is not, because liking something does not mean using it. It is not, because finding something interesting does not mean it solves a relevant problem. And it is not, because a kind opinion does not reduce the uncertainty that truly matters when building a business.

This mistake is very common in early-stage phases. And it is also expensive. Because it leads many founders to interpret as a market signal what was actually just politeness, curiosity or a superficial conversation.

The direct answer

Validation is not about collecting positive opinions about your idea. It is about checking, through real signals, whether there is a relevant problem, for a specific profile, with enough intensity to trigger action.

The key word here is action.

Not enthusiasm. Not approval. Not sympathy. Not friendly feedback. Action.

Because an idea can be liked and still not matter. It can seem useful and still not be a priority. It can sound logical and still fail to generate any real behavior.

The core mistake: looking for confirmation instead of evidence

When someone has an idea, it is normal to want to test it.

The problem is that, many times, they are not looking for contrast. They are looking for relief.

They want to hear that they are on the right track. They want to reduce the discomfort of uncertainty. They want a quick sign of encouragement. They want confirmation that they are not wasting their time.

And then they ask questions like these:

Do you think this is a good idea?
Would you use something like this?
Would you pay for this?
What do you think of this app?
Does this sound interesting to you?

These questions have a design problem.

They invite hypothetical, polite and low-commitment answers.

In other words, they generate conversation, but not validation.

Why asking whether people like it produces weak answers

It is not just that those questions are soft. It is that they unintentionally push the other person to answer poorly.

1. Because people want to be kind

Most people do not want to discourage you.

Even less if you are a friend, acquaintance or someone who is clearly excited about a project.

So they soften their response. They encourage you. They say it looks promising. They answer politely.

That does not make the answer a lie. But it does make it a very weak signal.

2. Because giving an opinion is cheap

Saying “I like it” costs nothing.

It does not mean changing a habit. It does not mean dedicating time. It does not mean paying. It does not mean trying anything. It does not mean taking any risk.

And in business, what matters is not how easy it is to say yes. What matters is how hard it is to act accordingly.

3. Because the question is answered in the abstract

When someone gives an opinion about an idea in the abstract, they usually imagine an ideal version.

They do not think about the real context. They do not think about priorities. They do not think about current alternatives. They do not think about adoption friction. They do not think about whether they would actually change any part of their behavior.

That is why positive answers can sound promising and still have little predictive value.

4. Because it confuses superficial interest with real need

Something can seem curious without being important.

And in validation, that difference changes everything.

A business does not emerge because an idea briefly catches attention. It emerges when it solves something the market experiences as sufficiently relevant.

What you should actually validate

If your goal is not to feel better, but to make better decisions, then validation should focus on much more specific questions.

1. Whether the problem exists

Before validating the solution, you need to validate the problem.

You need to understand:

Whether it really happens.
How often it appears.
Who it affects.
In what context it happens.
What consequences it creates.

If the problem does not exist clearly enough, everything else loses meaning.

2. Whether the problem matters

It is not enough for something to happen.

It has to be annoying, costly, frequent or frustrating enough to deserve attention.

Many founders detect inconveniences. Far fewer detect real priorities.

And a business needs the second much more than the first.

3. Whether there is a profile that suffers it intensely

Validation does not improve when you speak to “many people”. It improves when you speak to the right people.

You need to know who experiences the problem with the greatest pain, urgency or exposure. That is usually the best entry point for an early-stage proposal.

4. How it is solved today

If someone already has a way of living with the problem, that matters a lot.

They may use:

A spreadsheet.
A manual process.
An imperfect tool.
An agency.
An internal team.
An improvised combination.

Your idea does not compete against nothing. It competes against what already exists today, even if it is mediocre.

5. Whether there are behavioral signals, not just opinions

This is the core of the matter.

Useful signals are those that involve some form of action.

For example:

Spending time explaining the problem in detail.
Asking for more information.
Wanting to try a solution.
Accepting a demo.
Leaving their contact details.
Writing back to you.
Sharing the problem with urgency.
Paying for a test.
Committing to a next step.

That is when it starts to look like validation.

What to ask instead of “do you like my idea?”

The difference is not just about stopping yourself from presenting the idea. It is about changing the type of conversation.

Instead of asking for opinions, investigate past behavior

Instead of asking:

“Would you use this?”

It is better to ask:

How do you solve this problem today?
When was the last time this happened to you?
What did you do then?
Which part was most frustrating?
What was the cost of not solving it properly?
Have you looked for any alternative?
What have you already tried?
Why are you still doing it this way?

These questions are not looking for praise.

They are looking for reality.

Instead of selling, try to understand

When you show an idea too early, you contaminate the conversation.

The other person starts reacting to your frame, your energy and your narrative. That reduces the quality of the signal.

At the beginning, it is usually more useful to understand the problem without pushing your solution.

First the market. Then the proposal. Then the reaction.

Instead of listening to nice words, observe real friction

A kind phrase means little if it is not accompanied by something more.

Pay attention to things like these:

How long they have been living with the problem.
How much effort they dedicate to it.
What solutions they have already tried.
What frustrations they repeat.
Whether they are actively looking for another way to solve it.
Whether they have budget, urgency or authority to act.

That is usually where the most useful truth appears.

The most misleading answers

There are phrases that many founders interpret as validation, but they are not necessarily validation.

“I would use it”

It can mean politeness. It can mean curiosity. It can mean “in theory”. It can mean “maybe someday”.

Without context or action, it is worth little.

“It seems like a good idea”

That only indicates that the idea does not sound absurd.

It does not tell you whether the problem hurts. It does not tell you whether they would change their behavior. It does not tell you whether they would pay. It does not tell you whether you are the right solution.

“That is needed”

Sometimes yes. Sometimes no.

Many people say something “is needed” without ever having tried to solve it, without prioritizing it and without showing any behavior consistent with that supposed need.

“I would pay for that”

Said in a conversation, it is worth almost nothing.

Actually paying you, booking a call, leaving a deposit or committing to a test is worth much more.

What signals are more valuable than a positive opinion?

If you want to validate more seriously, pay more attention to this.

1. Repetition of the problem

When several people describe the same friction in similar words, you start to see a pattern.

2. Emotional or specific language

When someone describes the problem with detail, fatigue, frustration or concrete examples, there is usually more truth than when they answer in the abstract.

3. Previous attempts to solve it

If they have already tried things, that is a good signal. It indicates that the problem has enough weight to move behavior.

4. Visible cost

Lost time. Frequent errors. Wasted money. Slow processes. Confusion. Delays. Dependence on third parties.

When there is cost, there is a higher probability of real need.

5. Commitment to a next step

This is one of the best signals.

If someone accepts a test, leaves their details, schedules a call, wants to see a demo or asks you to notify them when it is ready, you are no longer only in the territory of opinion.

The real role of a validation interview

An interview should not be used to get people to tell you whether your idea is good.

It should help you better understand:

How a real person experiences the problem.
What they do today to solve it.
What frustrates them about that process.
What alternatives they know.
How much priority this has compared with other things.
What signals would indicate that there is room for a better solution.

That changes everything.

Because it shifts the focus from “I want people to like it” to “I want to understand”.

And building well requires much more of the second than the first.

What happens when you validate poorly

Poor validation does not only give you mediocre information. It also pushes you toward worse decisions.

1. It gives you a false sense of progress

Because you receive positive answers, you believe there is a market.

And that pushes you to build too early.

2. It reinforces your biases

You hear what you wanted to hear. You interpret sympathy as a signal. You read enthusiasm where there was only kindness.

3. It delays important learning

While you celebrate superficial feedback, you are not discovering real objections, true priorities or adoption barriers.

4. It makes correction more expensive later

The more you build on weak validation, the harder it becomes to change when reality arrives.

How to validate better in practice

It does not need to be complicated. It needs to be done with better judgment.

1. Start with the problem, not the solution

Before presenting what you want to build, understand properly what is happening in the market.

2. Speak with specific profiles

Do not validate with just anyone. Validate with people who truly fit the problem you want to study.

3. Ask questions about facts, not future hypotheses

Look for past and present behavior, not imagined promises.

4. Look for patterns, not isolated anecdotes

One promising conversation is not enough. What matters is the repetition of signals.

5. Measure interest through small but real actions

A test. A call. A registration. A later reply. An introduction to another person. A payment.

That is worth more than many favorable opinions.

The sentence worth remembering

Validation is not checking whether your idea is well received. It is checking whether the market moves in response to a real problem and a meaningful proposal.

That is the difference.

What Foundeia ultimately stands for

Foundeia does not understand validation as a ritual for feeling emotionally safe about an idea.

It understands it as a process for reducing uncertainty before investing more.

That means changing the logic:

From opinion to evidence.
From idea to problem.
From sympathy to behavior.
From enthusiasm to real signal.
From pleasant conversation to better-informed decision.

Because a founder does not need to be told that people like their idea.

They need to know whether it is worth moving forward, reformulating or discarding.

Conclusion

It is easy to look for emotional validation when you have an idea.

It is human.

It is also dangerous.

Because if you confuse approval with evidence, you will end up building on a fragile foundation.

And that is not always noticeable at the beginning. It becomes visible later, when the market does not respond as expected.

That is why it is worth remembering from day one:

That people like your idea is not enough. That it sounds good is not enough. That people smile when you explain it is not enough.

What matters is something more uncomfortable and much more useful: understanding whether there is a real problem that moves behavior and whether your proposal has the ability to generate an equally real response.

Frequently Asked Questions

Does asking whether people like my idea help validate it?

Not really. It may work as an initial conversation, but it does not validate the problem, the priority or the real willingness to act or pay.

What should I validate first in a business idea?

The first step is usually to check whether the problem truly exists, who suffers it most intensely, how it is solved today and whether it creates enough friction to justify a new solution.

What type of questions are better in a validation process?

Questions that explore real behavior, context, frequency, current alternatives, frustrations and action signals are better than hypothetical opinions about the future.

What signal is more valuable than “I like it” or “I would use it”?

Any signal of real commitment, such as accepting a test, leaving contact details, scheduling a call, following up or paying for an initial version.