What Changed My Mind About Problem Interviews (First-Time Founders)

I used to skip problem interviews. I thought they were a thing methodology people wrote about to look rigorous. I had ideas, I had energy, I had tools, I could just build. Talking to strangers about their week sounded slow and faintly humiliating.

Several wrong builds later, I changed my mind. Here is what actually did it. None of the standard arguments. The standard arguments did not move me at the time, and they probably will not move you either.

It Was Not the Failed Launches

Failed launches did not change my mind. I rationalized them. The marketing was wrong, the timing was off, the audience was distracted. There was always a story that did not require me to interrogate the underlying premise.

If you have only ever shipped one thing that flopped, you can probably explain it the same way. The denial is comfortable and works for a while.

It Was Not the Books

I read the books. I knew the arguments. I could quote The Mom Test at parties. None of it changed my behavior, because reading about a discipline is not the same as adopting it. I treated the books as theoretically true and personally optional.

If you have read this kind of post and not done a single interview, you are in the same place I was. Do not be embarrassed. Reading is the easy part.

What Actually Did It

One conversation. With one person. About a product I had been building for two months and had not shipped yet.

I had agreed to talk to a friend-of-a-friend who fit the target audience. It was supposed to be a quick chat. I had no plan to call it a problem interview. I just wanted feedback on what I was building.

I started describing the product. He politely told me he did not actually have the problem the way I was describing it. He had a related problem - similar enough that my idea was vaguely interesting, different enough that what I was building would not solve it.

Forty-five minutes later, I had filled three pages with notes. The product I had been building was aimed slightly off the actual workflow. Not by a lot, but by enough that nobody would have used the version I was about to ship.

The Specific Realization

The thing that flipped me was a small one. He used a phrase I had never used. He said, "the part that always breaks is X." X was a thing I had not built around. I had built around Y, which was an adjacent thing.

That single phrase rearranged my product. Not because the conversation was magical, but because no amount of solo thinking would have surfaced X. I would have shipped something that handled Y nicely and ignored X. He would have looked at it, said "this is cool but not for me," and walked away. I would have rationalized that as "wrong audience."

Instead, because we talked, I rebuilt the core flow over the next week. The shipped product was about X with Y as a secondary feature. People used it. Not in huge numbers, but in real ones, and the people who did use it stayed.

The Cheaper Version of That Realization

I got lucky that the conversation happened. It easily could not have. The lesson, in retrospect, was that I should have engineered ten of those conversations on purpose, before building anything, instead of stumbling into one accidentally after two months of work.

That is, exactly, problem interviews. Engineered conversations with people who plausibly have the problem, run before the build. The realization that changed my mind was not that interviews are good. It was that the conversation that saved my product was reproducible on demand, and I had been refusing to reproduce it.

What I Did Differently After

Every project since: I run at least ten interviews before starting to build anything substantial. Some have killed the idea. Some have rearranged it. A few have confirmed it. None have been wasted, even when the conclusion was "do not build this." Especially when the conclusion was "do not build this."

I am not better at interviews than I used to be. I am just willing to do them now. The willingness is the entire skill, and it shows up only after you have paid the cost of not having it.

What This Means for You

If you are a first-time founder reading this, you do not yet have the scar. The arguments above will not move you the way the scar would. I am not going to tell you they should. I will tell you the scar arrives, sooner or later, and it is much cheaper to take the lesson on faith now than to pay the tuition.

One conversation. With one person. Before you ship anything. That is the threshold of trying. The first one is the hardest. After that, the practice tends to install itself.