Problem Interviews for People Who Hate Complexity (First-Time Founders)

If you have read any post about customer discovery and felt like the methodology was bigger than the activity it described, this one is for you. Here is the lowest-complexity version that still works.

The whole thing fits in three rules.

Rule 1: Talk to People Who Have the Problem

Not your friends. Not your investors. Not random Twitter followers. People who have, or recently had, the specific problem you think you are going to solve.

How do you find them? Ask. Cold message ten of them on LinkedIn. Post a question in a niche community. Email five contacts who fit. The mechanism is not exotic. The discipline is just to filter for the right audience.

Rule 2: Ask About Their Past, Not Your Future

Do not ask, "would you use this." That is a question about a hypothetical future. People are bad at it. You will get polite garbage.

Ask, "tell me about the last time this came up for you." That is a question about the past. People are good at it because they remember it. You will get a story. Stories carry data.

That is the whole methodology. Ask about the past.

Rule 3: Do Not Pitch

Do not describe your idea during the call. The moment you do, the conversation tilts toward politeness and away from honesty. The customer starts saying nice things. You start hearing what you want to hear.

If they ask what you are building, say you are still figuring it out. That is almost always true anyway. They will accept it and keep talking about themselves, which is what you wanted.

What That Adds Up To

Three rules. Talk to people with the problem. Ask about their past. Do not pitch.

That is enough. Run ten interviews following those three rules and you will have more useful information than most first-time founders ever collect about their market.

What You Can Skip

You can skip the framework names. You can skip the persona doc. You can skip the affinity map. You can skip the tagging. You can skip the score. You can skip the synthesis workshop. You can skip the customer journey map.

Most of those things are not bad. They are useful for teams running dozens of interviews and trying to keep track of the volume. They are overkill for a first-time founder running ten.

What You Cannot Skip

You cannot skip the calls themselves. The reason all the methodologies exist is that the calls are the part that matters, and the methodologies are mostly scaffolding around the calls. Strip the scaffolding and the calls still do the work.

You also cannot skip writing things down. Even minimal notes - a few quotes, a one-paragraph summary - are non-negotiable. Otherwise the patterns evaporate before you can see them.

If You Want to Be Even Lazier

Do five calls. Just five. Use the three rules. Take messy notes. Write a one-paragraph summary at the end of each.

You will know more after five than you knew before five. That is the point. You can always do more later. The biggest mistake is doing zero because the methodology felt overwhelming, not doing too few because you got tired.

The Plain English Version

Find the right people. Ask them about something they already lived. Do not sell. Take notes. Repeat a few times.

That is problem interviews. The rest is decoration. If the decoration helps you, keep it. If it stops you, throw it out and just do the calls.