What I Would Fix First About Problem Interviews for First-Time Founders

If I had to pick one fix that would give first-time founders the biggest jump in interview quality, it would not be a better script, a better notetaking system, or a better tool. It would be this: stop talking about your idea.

That is the entire change. Most other problems with problem interviews dissolve once you make this one shift. Most other techniques become unnecessary, or at least less load-bearing, once the founder has truly committed to it.

Why This Is the Bottleneck

The moment a founder describes their idea inside a problem interview, three things happen at once. The other person becomes polite. The questions shift from "how do you handle this" to "how would you use my thing." And the founder, who is excited, tunes their listening to confirmation rather than discovery.

You can have the cleanest checklist, the best questions, the most thoughtful follow-ups, but if you have already pitched the product, the conversation is poisoned. Everyone is being polite. Nothing real comes out.

The Specific Fix

Decide before the call that you will not describe what you are building. Not in the intro. Not when they ask. Not even when it would feel natural to. If they ask what you do, say something true but vague: "I am exploring a few directions in this space and trying to learn how people actually handle it today."

That is enough. Most people do not press, because most people are happy to talk about their own work. The few who do press will accept the answer if you keep the conversation focused on them.

What You Lose By Pitching

You lose three specific things when you pitch inside a problem interview. First, you lose the ability to hear the actual problem in the person's own words, because their words become reactive to yours. Second, you lose the chance to discover an adjacent problem that is bigger than the one you came in with. Third, you lose any negative signal, because polite people do not say "your idea is bad" to your face.

Those three losses combine to mean almost every interview you do becomes confirmation theater. You walk away feeling validated and learning nothing. That is the worst possible outcome and it is the most common one.

How to Train Yourself Out of It

This is harder than it sounds. The urge to explain what you are working on is strong, partly because you are excited, partly because you want to sound like you know what you are doing. A few practical tactics help.

Tell a friend before each call that your single goal is to leave without describing the product. They will ask you afterward. The accountability matters.

Practice the redirect. When someone asks "so what does your thing do," have a stock answer ready: "Honestly, I am still figuring that out, which is why I am asking these questions. Can I keep poking at the problem first and we can come back to that at the end?" Almost everyone says yes.

Treat every interview as if the person is going to be a board member at your competitor. You would not pitch them. You would just learn from them. Adopt that frame and the discipline becomes easier.

What Comes Out the Other Side

Once you commit to not pitching, the interviews change shape. They become longer, because you ask more follow-ups instead of switching to demo mode. They contain more specific stories, because the person stays in their own world. They produce vocabulary you would not have invented, because the person is using their own words instead of reacting to yours.

And, occasionally, they produce the moment every founder needs and almost none get: the moment where you realize the problem is different from what you assumed. That moment is what saves you the wasted quarter. That moment is what makes problem interviews worth doing at all.

The One-Sentence Version

If you remember one thing from this post, remember this. The single highest-leverage fix for first-time founders running problem interviews is to talk about your product less, not interview better. Most of the rest follows from that.