A Practical Guide to Problem Interviews for First-Time Founders

This is the guide I wish I had handed myself before my first product. It is not a framework, it is not a methodology, it is not a research doctrine. It is the smallest set of practices that, in my experience, separate first-time founders who validate well from first-time founders who think they are validating but are mostly seeking encouragement.

If you read all the way through, you will have everything you need to start this week.

Step One: Define Who You Are Trying to Learn From

Before you talk to anyone, decide who counts. Not in marketing-persona detail. Just two clean filters: a job-or-role and a recent behavior.

For example: "Solo SaaS founders who shipped a product in the last twelve months," or "Operations leads at small agencies who manage their own schedules," or "Course creators who launched a paid course in the last year." Two filters, both verifiable.

This matters because it constrains your sample. If you talk to anyone willing to chat, you will get noise. If your two filters are tight, the patterns show up faster, with fewer interviews.

Step Two: Find Fifteen of Them

You need fifteen because the patterns require ten to fifteen calls to surface, and not everyone you contact will reply. So plan to send forty to sixty short, specific outreach messages to land fifteen calls.

The best places to find candidates depend on the audience. For founders, Twitter and LinkedIn work well. For specific professions, niche Slack and Discord communities. For consumers, Reddit subreddits matched to the topic. For B2B operators, LinkedIn search by job title plus company size. Cold email works if your message is short and you can demonstrate you actually understand their world.

The message itself should be three sentences. One sentence about why you are reaching out specifically to them. One sentence about what you are researching and that you are not selling. One sentence asking for thirty minutes. Done.

Step Three: Build a Three-Question Spine

Have a script, but a small one. Three questions you will definitely ask, and the rest left open for follow-up.

Question one is a story prompt about the last time the problem came up. Question two is about workarounds and what they have tried. Question three is about money and time already spent. Those three give you an event, an effort signal, and a willingness signal in any order, and they leave plenty of room for you to follow your nose.

Write the questions on a sticky note next to your computer. Glance at it during the call. Otherwise, listen.

Step Four: Run the Call

Open with a low-stakes intro. "Thanks for the time, I am researching how people handle X right now, I am not selling anything, I just want to learn from people who have lived through it." Then ask question one and shut up.

Your job during the next twenty-five minutes is to keep them telling stories. The most useful sentence you can say is "Tell me more about that." The second most useful is silence. After they finish a thought, count to three before responding. Most of the time, they will keep going, and the second half of what they say will be more honest than the first.

Avoid describing your idea. If they ask what you are building, deflect: "I am exploring a few directions, which is why I am asking these questions. Can we come back to that at the end?" They will say yes, and you can save the last three minutes for that conversation if you want.

Step Five: Take Notes That Matter

Type or write notes during the call. Capture exact phrases when they say something specific, vivid, or unexpected. Your future self will thank you. Paraphrasing throws away signal.

After the call, spend five minutes writing a short summary at the top of the notes. Three things: what was the situation that triggered the problem, what did they actually do about it, and what surprised you. The third one is the most important. If nothing surprised you, you might not have been listening hard enough.

Step Six: Look for Patterns Across Calls

After every five interviews, sit down with all the notes and look for repetition. The same workaround coming up. The same vocabulary used by different people. The same trigger that starts every story. The same complaint, even if expressed differently.

Patterns mean signal. Idiosyncrasies are interesting but not actionable. The story you can write a one-paragraph summary of, that holds true across at least five out of fifteen calls, is the story your product should be designed around.

Step Seven: Decide What You Have

After your first ten or fifteen interviews, ask yourself three questions. Is the problem real, frequent, and painful enough that people are already doing something ugly to handle it? Is the audience reachable - can you find them, and would they actually talk to you again? Is the workaround you observed expensive enough in time, money, or stress that something better could plausibly earn money?

If yes, yes, and yes: you have warranted confidence. Build the smallest possible thing and put it in front of the same fifteen people. If any of those is no, you have learned something equally valuable. Adjust your filters, switch the audience, or rethink the problem.

Common Failure Modes

You talked to the wrong people. The pattern is clean but the audience is not the audience you wanted. Solution: rerun with the right filter.

You pitched too much. The interviews were polite, the answers were warm, you learned little. Solution: do five more, with strict no-pitch discipline.

You stopped at the surface. People said it was annoying and you wrote down annoying. Solution: practice the "tell me more about that" reflex, and aim for at least three follow-ups per question.

You did three calls and called it validated. Solution: a single conversation is a data point, not a verdict. Get to ten before you draw any conclusion you bet on.

Why This Works

None of this is clever. It is just consistent. The reason this set of practices outperforms more elaborate frameworks for first-time founders is that elaborate frameworks rarely get done. The practical guide is one you actually finish, repeatedly, and the doing is where the value lives.

Five people, three questions, one notebook, fifteen calls, then synthesize. Start now. The first one is the hardest. By the fifth, you will know more about your customer than you knew before you began, and you will start to feel something rare for a first-time founder: warranted confidence about what to build next.