Why You Shouldn't Delegate Customer Interviews to Non-Researchers

One of the easiest ways to lose money in product work is to hand customer interviews to people who are not trained researchers or experienced product thinkers.

I keep seeing founders do exactly that. They ask sales reps, assistants, engineers, support specialists, or copywriters to run qualitative interviews because, on paper, the idea sounds sensible enough.

“They already talk to customers.”

“They are underutilized.”

“Everyone in the company should hear the customer.”

“Let them learn.”

“They want to become product managers anyway.”

If the goal is education, that is fine. Seriously. Let people learn. Let them sit in on interviews. Let them try. Let them develop product sense.

But then we should be honest about what those conversations are. They are training interviews, not decision-grade research.

That distinction matters more than most teams think.

Qualitative research is not just a list of questions

A lot of companies treat customer interviews as if the job is simple: write a guide, ask the questions, collect answers, paste them into a spreadsheet, and call it research.

That is not how good qualitative research works.

Running a strong interview is a professional skill. It takes training, deliberate practice, and enough hours in the chair to recognize when a conversation is drifting, when a respondent is performing, and when your own expectations are quietly steering the result.

A good interviewer knows how to:

• avoid leading the respondent;
• separate real past behavior from polite future speculation;
• stay curious without becoming suggestive;
• notice when a person is rationalizing instead of remembering;
• push gently for specifics without turning the conversation into an interrogation.

That is a real craft. We do not usually question this in other domains. Nobody asks a developer to draft legal contracts. Nobody asks a salesperson to write production code. Nobody asks a marketer to design a tax strategy.

And yet, for some reason, research is still the function many teams assume anyone can pick up in an afternoon.

Why non-researchers usually bring back bad data

The problem is not that these people are careless or incapable. The problem is that customer interviews are extremely easy to bias, especially when the interviewer wants a certain answer or thinks the company wants one.

For almost any statement an interviewer expects to hear, there is a sequence of questions that will get them something close enough to it.

If an employee believes the founder wants proof that customers love the product, they will usually come back with proof. They will attach the recording. They will fill in the notes. They will highlight the quote where the customer sounds excited.

And still, the insight can be worse than useless.

Sometimes the bias is obvious. The question is leading. The tone is leading. The framing is leading. But more often it shows up in softer, more familiar language:

• “What if we built…”
• “Under what conditions would you consider…”
• “Let’s imagine you had…”
• “Would this be useful if…”

That is how teams end up confusing politeness with demand and hypothetical interest with real buying behavior.

The interview sounds positive. The spreadsheet looks clean. The conclusion feels reassuring. Then the company makes a product decision on top of it and learns, a few expensive weeks later, that the market never said what the team thought it said.

”They already talk to customers” is the wrong logic

This is probably the most common argument for delegating customer interviews inside a startup, and it is also one of the weakest.

Sales calls are designed to persuade. Support calls are designed to solve. Founder calls often drift toward validation. Customer research interviews are designed to learn.

Those are different jobs.

Someone can be excellent with customers and still be a poor research interviewer. In fact, that is normal. Strong communicators often want to help, explain, reassure, pitch, or rescue the conversation when there is silence. In research, silence is often useful. Not rescuing the respondent is useful. Letting the person finish the thought they were about to abandon is useful.

So no, “they already talk to customers” is not enough. The context of the conversation changes the quality of the information you get.

When it is actually fine to let the team run interviews

There is one important exception here.

If your goal is to teach someone, then yes, let them do interviews.

Let the salesperson learn how discovery feels when you are not selling. Let the assistant hear how messy customer language really is. Let the junior PM practice. Let the engineer sit in and ask a few questions.

But do not confuse that with reliable qualitative research.

If beginner interviews are being used for learning, they need proper scaffolding:

• training before the interview;
• feedback after the interview;
• review from someone more experienced;
• clear boundaries on how the data can be used;
• mentorship over time, not one-off encouragement.

Without that support, people usually learn bad habits while the company gains false confidence.

And without that distinction, teams start making business decisions from educational exercises. That is where the trouble starts.

What founders should do instead

If you want customer interviews that are actually useful, there are two sensible options.

Founders should do more of the interviews themselves

Yes, founders are often not trained researchers either. That part is true.

But at an early stage, learning from customers is a core founder job. It is not admin. It is not optional. It is not something to casually hand off just because the calendar is full.

You do not need ten interviews a week to get value. Even two solid hours a week is enough to keep one meaningful hypothesis moving each month. For an early-stage company, that is not trivial. That is strategy.

And the operational parts can still be delegated. Someone else can recruit respondents, manage scheduling, send reminders, confirm attendance, and organize notes. That is good delegation. The interview itself is where the signal gets made or distorted.

If the decision is expensive, the founder should stay close to the evidence.

Bring in professional researchers when the stakes are real

The second sensible option is to work with an external researcher.

That might be an agency. It might be a freelancer. It might be an independent specialist with a strong qualitative background. The exact format matters less than the competence.

What matters is that the person running the interview understands methodology, knows how to reduce bias, and can tell the difference between a clean signal and an answer that only sounds convincing.

Yes, you can make mistakes in research. Yes, you can make mistakes in product strategy too. That part never goes away.

But extracting reliable evidence from a customer conversation is not some mysterious dark art anymore. We know how to do it well enough. This is one of the worst places to gamble on amateur execution.

The real cost of bad customer interviews

Bad research is not neutral.

It does not simply waste a few hours and disappear. It creates false confidence. And false confidence is expensive.

A team hears what it wanted to hear, rewrites the messaging, builds the wrong feature, chases the wrong segment, or keeps investing in a product story that was never really there. By the time reality corrects the mistake, the company has already paid for it in time, attention, and momentum.

That is why I push back so hard on casual delegation here. Weak interviews do not just produce low-quality notes. They produce bad decisions with a research-shaped justification attached.

FAQ

Can sales reps run customer interviews?

They can help with recruiting, context, and follow-up. But unless they are trained in qualitative research, sales-led interviews usually introduce persuasion bias and make the findings less reliable.

Should founders conduct customer development interviews themselves?

In early-stage companies, usually yes. Founders are closest to the product bets, the positioning questions, and the cost of getting the signal wrong.

When should you hire an external user researcher?

When the decision matters, the team lacks qualitative research depth, or previous interviews have produced vague, overly positive, or contradictory insights.

Can junior team members still be involved in user research?

Absolutely. They should just be involved in a way that is clearly educational, reviewed, and supported, rather than treated as a substitute for professional research.

If your team needs customer interviews that lead to usable decisions rather than comforting fiction, that is exactly the kind of work Glasgow Research is built for.