How to Run User Interviews That Actually Change What You Build

Most founders walk away from user interviews feeling good. The user was friendly, the conversation flowed, they said the product was "really useful." Then you look at your notes and realize you have absolutely nothing actionable to show for it.

That is the trap. User interviews are one of the highest-leverage activities in SaaS, but they are almost always done wrong. Not because founders are bad listeners. Because they are asking the wrong questions, talking to the wrong people, or treating the whole thing like a validation exercise instead of a discovery one.

Here is how to run interviews that actually move the needle on what you build.

Start With a Goal, Not a Script

Before you book a single call, get clear on what decision this interview is supposed to inform. Are you trying to understand why users churn in the first 30 days? Are you deciding between two features on your roadmap? Are you figuring out whether a new segment is worth targeting?

Without a specific question to answer, you will end up with a generic conversation. You need a thesis to test, not a chat to have.

Write it down before the call: "I want to understand why users who signed up last month never activated the core feature." That single sentence will shape every question you ask.

Talk to the Right People

This sounds obvious, but most founders default to interviewing their most engaged users. Those people love the product. They will tell you great things. They will not help you understand churn, drop-off, or hesitation.

For real product insight, you need a mix:

• Recently churned users. These conversations are uncomfortable and worth their weight in gold. Find out what broke down. Was it missing functionality, a confusing onboarding flow, or a competitor that offered something you do not?
• Users who signed up but never really activated. They saw enough to start. Something stopped them. That gap is your biggest opportunity.
• Power users. Not to feel good, but to understand the exact moment the product clicked for them so you can engineer that moment for everyone else.

If you are a solo founder or indie hacker running lean, even five to eight interviews across these groups will surface patterns you cannot get from saas metrics alone.

Ask About the Past, Not the Future

Here is the single most important rule in user research: never ask someone what they would do or what they would want. People are terrible at predicting their own behavior. They will describe an idealized version of themselves, not the actual one.

Instead, ask about what they have already done.

Bad question: "Would you use a feature that lets you export reports?" Good question: "Walk me through the last time you needed to share data with your team. What did you do?"

The second question reveals real behavior, real workarounds, and real friction. That is the raw material for good product decisions. Feature voting and a suggestion box can complement this, but they should never replace the texture you get from hearing someone describe their actual experience.

Shut Up More Than You Think You Should

Most founders talk too much in user interviews. You are excited, you want to explain what you are building, you want to respond to every comment with context. Resist every single urge to do this.

Your job in an interview is to create space. Ask a question, then wait. If they stop talking and there is silence, wait a bit longer. The most honest, revealing answers usually come after the first thing someone says. The first answer is often rehearsed or polished. The second or third layer is where the real signal lives.

A useful follow-up that works in almost every situation: "Can you tell me more about that?" It sounds almost too simple. It works every time.

Listen for Emotion, Not Just Information

Good feedback management is not just about cataloguing feature requests. It is about understanding what actually frustrates people, what worries them, what they feel embarrassed about when using your product.

Pay attention to the language users use. When someone says "it was kind of annoying" versus "it was honestly infuriating," that is not the same thing even if the underlying complaint is identical. Emotional intensity signals priority. You are doing informal sentiment analysis in real time.

When you hear something charged with emotion, dig in. "It sounds like that was frustrating. Can you walk me through exactly what happened?" You will get far more useful material than any survey score can give you.

Document Everything Immediately

Memory is unreliable. Even if you take notes during the call, write up a synthesis within an hour of finishing. Capture the direct quotes that hit hardest, the moments where the user seemed uncomfortable or uncertain, and your own read on what the interview revealed.

Over time, these summaries become an incredibly valuable asset. Patterns will emerge across interviews that you simply cannot see if you are just reviewing scattered notes weeks later. This is the foundation of a real user feedback collection system, one that connects directly to your product roadmap rather than sitting in a folder no one reads.

If you are building in public, these insights can also be shared (with appropriate anonymity) to show your audience how customer feedback is shaping your decisions. That kind of transparency builds trust and attracts the kind of users who want to help you build something great.

Turn Insights Into Decisions

An interview that does not change something is just a conversation. After each round of interviews, force yourself to write down:

1. The one thing I learned that surprised me
2. One assumption I had that turned out to be wrong
3. One concrete change to the product or roadmap I am going to make as a result

That last one is the whole point. Feature prioritization should be grounded in real user insight, not gut feel or whoever emailed you most recently. When you build based on what users have actually told you, you are doing product-led growth the way it is supposed to work. You are not guessing. You are responding.

Customer success starts before anyone talks to your support team. It starts with understanding, deeply and specifically, what your users are trying to do and where your product is getting in the way.

FlagUp helps SaaS teams track the feedback and signals that predict churn before it happens. Collect, organize, and act on what your users are telling you in one place. See how it works →