Problem Interviews Without Methodology (Non-Technical Founders)

Methodology content overwhelms a lot of non-technical founders. Mom Test, jobs-to-be-done, customer development - the names alone make most founders close the tab. If that is you, here is the version stripped to the parts that actually do the work. Three rules.

Rule 1: Talk to People Who Have the Problem

Not your friends. Not your family. Not random Twitter followers. People who, recently, did the specific workflow you are thinking of changing.

Find them on LinkedIn by title and team size. In niche Slack and Discord communities. On Reddit subreddits matched to the topic. Cold message ten of them. Some will say yes. The mechanism is just asking, repeatedly, kindly, briefly.

Rule 2: Ask About Their Past, Not Their Future

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

Ask "tell me about the last time this came up." That is a question about a specific past event. People are good at remembering specific past events. You will get a story. Stories carry data. Hypothetical answers do not.

Rule 3: Do Not Pitch and Do Not Demo

Two failure modes wrapped into one rule. Do not describe what you are building. Do not show your no-code prototype. The moment you do either, the conversation tilts toward politeness and away from honesty.

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

What That Adds Up To

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

That is enough. Run ten interviews following those three rules and you will have more useful information than most non-technical founders ever collect.

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 system. You can skip the customer journey diagram. You can skip the synthesis workshop. None of those are bad in principle. They are scaffolding for teams running thirty interviews a week. You are running ten.

What You Cannot Skip

You cannot skip the calls. The reason all the methodologies exist is that the calls are the part that matters. 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, the trigger event, the workaround - are non-negotiable.

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. 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 their actual past. Do not sell. Do not demo. Take notes. Look for repeats. Stop when you can summarize the customer in three sentences.

That is problem interviews for people who hate complexity. The rest is decoration.