Many first-time founders know they should talk to users, but the conversations often produce soft feedback rather than usable evidence. The issue is usually not effort. It is interview design.
At StratSchool, founder interviews are treated as a method for reducing uncertainty. That means the goal is not to impress the user, validate the founder's ego, or collect compliments. The goal is to understand whether the problem is real, painful, repeated, and specific enough to justify further work.
What a good founder interview should reveal
A useful interview should tell you what happened, when it happened, how the person handled it, what it cost them, and why their current workaround is not good enough.
- What triggered the problem the last time it happened.
- What workaround they tried first.
- What part of that workaround is painful or inefficient.
- How often this problem shows up in real life.
- What a better outcome would actually change for them.
Start with stories, not opinions
Founders often ask questions like “Would you use this?” or “Do you think this is a good idea?” Those questions are easy to answer politely and hard to learn from. People are generous in conversation and unreliable in prediction.
A better approach is to ask for a recent story. Ask, “Tell me about the last time this happened.” Stories create detail. Detail creates evidence. Evidence is what helps a founder decide what to do next.
Questions that usually produce better signal
- Walk me through the last time you faced this issue.
- What did you try first, and why?
- What was frustrating or expensive about that process?
- How often does this happen in a typical month?
- Who else is involved when you try to solve this?
- What would make you switch from the current way you do it?
These questions move the conversation toward behavior and decision-making. That is where real founder insight comes from.
What to avoid during customer interviews
- Do not pitch the product in the first five minutes.
- Do not ask leading questions that push the person toward agreement.
- Do not interpret politeness as proof of demand.
- Do not talk to people who are too close to you unless you can control for bias.
- Do not stop after two or three conversations if patterns are still unclear.
How many interviews are enough at the start
There is no magical number, but most founders need enough conversations to hear repeated language and repeated pain points. Ten strong interviews in a narrow audience often teach more than forty vague conversations across a broad market.
The important thing is not volume alone. It is pattern strength. When the same friction shows up repeatedly, in similar words, with similar workarounds, the founder is getting closer to a problem worth solving.
What to do immediately after the interview
Interview learning decays fast if notes stay messy. Right after each call, write down the problem context, key phrases, pain frequency, current workaround, and one thing that surprised you.
After five or ten calls, look for repeated phrases. Those phrases usually belong in your problem statement, landing page, or MVP positioning. Good interviews do not just inform product thinking. They improve founder language.
Bottom line
Customer interviews are not a ritual. They are a filter. Done well, they keep a founder from building around weak assumptions. Done badly, they create false confidence.
If you want stronger startup decisions, ask better questions, talk to a narrower segment, and keep listening until the signal is undeniable.
