How to Run a Customer Discovery Interview Across Languages (Questions + Debrief Template)

Target query: how do I run a customer discovery interview when my customer and I do not share the same language?

Yes, you can run a strong customer discovery interview across languages, but you have to optimize for clarity instead of speed.

The simplest way to do it is:

1. decide the exact learning goal before the call
2. ask short, concrete questions instead of broad abstract ones
3. repeat back what you heard in plain language
4. capture the takeaways in writing right after the interview

If you skip those steps, cross-language interviews can sound polite on the surface while still giving you bad product signal underneath.

This guide gives you a practical way to get useful answers without making the conversation feel robotic.

---

What goes wrong in cross-language discovery calls

Most bad interviews are not failing because of translation alone. They fail because:

• the interviewer asks long multi-part questions
• the customer answers politely instead of precisely
• both sides think they understood the same word, but they did not
• the team writes down conclusions that were never actually stated

In a same-language call, those problems already exist. Across languages and cultures, they get amplified.

So the goal is not "perfect fluency." The goal is clean signal.

---

Step 1: define one learning goal for the call

Before the interview, write one sentence:

By the end of this call, I want to understand whether [customer type] currently solves [problem] often enough to care about changing it.

That keeps you from drifting into a vague chat.

Good discovery goals:

• understand how a multilingual support team handles escalations today
• learn how an international sales team shares meeting follow-ups after client calls
• find out where cross-language handoffs break in a global operations workflow

Bad discovery goals:

• "learn everything about their workflow"
• "see if they like the idea"
• "get feedback on our product"

Discovery is about the customer's current behavior, not your pitch.

---

Step 2: send 3 topics in advance

If the conversation will happen across languages, structure helps a lot.

Send a short note before the call:

Thanks again for taking the time. To make the conversation easy to follow, I plan to ask about:

1. how your team handles this today
2. what is frustrating or slow
3. what happens after the meeting or handoff

This lowers anxiety and makes the answers better.

---

Step 3: ask shorter questions than you think you need

Cross-language interviews break when the interviewer bundles too much into one prompt.

Avoid:

Can you walk me through how your team currently handles customer calls, follow-ups, internal notes, and whether language differences make that harder across markets?

Ask instead:

• "Can you tell me about the last time this happened?"
• "Who was involved?"
• "What happened next?"
• "Where did it get confusing?"
• "How did your team follow up after that?"

Those questions travel better across languages because they are:

• concrete
• time-bound
• easier to translate
• harder to answer with generic opinions

---

Step 4: bias toward real examples, not hypotheticals

If you want useful product insight, keep pulling the customer back to a real event.

Useful phrases:

• "Can you use the most recent example?"
• "What tool did you use in that moment?"
• "Who wrote the follow-up?"
• "Did anyone misunderstand the decision?"
• "What happened after the call ended?"

Hypotheticals get even less reliable across languages because people tend to give socially acceptable answers.

Real behavior is what you build around.

---

Step 5: use repeat-back constantly

This is the highest-leverage habit in multilingual interviews.

After an important answer, say:

Let me check I understood correctly: your team can handle the live conversation, but the real problem starts after the call because the notes and next steps are scattered. Is that right?

Why this works:

• it catches translation errors early
• it gives the customer a safe way to correct you
• it creates cleaner notes for your team

Do this multiple times during the call, not just at the end.

---

Step 6: separate "pain" from "preference"

In cross-language conversations, customers often say something would be "nice" because they are being polite.

Your job is to find out whether the issue is expensive, frequent, or risky.

Follow-up questions:

• "How often does that happen?"
• "What happens when it goes wrong?"
• "Who feels the impact most?"
• "Are you solving it manually today?"
• "What does that cost in time?"

This keeps you from mistaking friendliness for urgency.

---

Step 7: end with a 60-second summary

Before the call ends, summarize:

• the main problem you heard
• the current workaround
• the consequence of the problem
• what you still need to clarify later

Example:

Let me summarize to make sure I have it right. Your team can get through multilingual client calls, but after the meeting the action items live in different chats and people remember different things. That creates delays and sometimes missed follow-ups. Your current workaround is one person manually rewriting notes in English for the rest of the team. Correct?

If the customer says yes, your notes just became much more trustworthy.

---

A simple question set you can copy

Use these in order:

Warm-up

• "Can you tell me your role?"
• "How often do these conversations happen?"
• "Which languages are usually involved?"

Current behavior

• "Tell me about the most recent example."
• "How did the conversation start?"
• "Who joined?"
• "What tools did you use?"

Friction

• "Where did it become difficult?"
• "Was the problem during the live call, after the call, or both?"
• "What got misunderstood?"
• "What slowed the team down?"

Follow-up and memory

• "How were notes captured?"
• "Who owned the next steps?"
• "Where were decisions saved?"
• "Did anyone need to translate or rewrite the recap?"

Severity

• "How often does this happen?"
• "What is the cost when it goes badly?"
• "Have you tried to fix it before?"

---

Debrief template for your team

Right after the interview, write this while the memory is still fresh:

1. What happened

• customer type:
• use case:
• languages involved:
• real example discussed:

2. Core pain

• main problem:
• where it shows up:
• current workaround:
• cost of the problem:

3. Evidence

• direct phrases worth preserving:
• repeated themes:
• anything the customer corrected:

4. Product implications

• what we learned:
• what we still need to validate:
• what not to assume yet:

This step matters even more in multilingual research because your team will otherwise fill in the gaps with interpretation.

---

Common mistakes to avoid

Mistake 1: using the call to impress the customer

Discovery gets worse when you over-explain your product. Keep the focus on their workflow.

Mistake 2: trusting smooth conversation too much

A polite, flowing conversation can still hide weak understanding. Verify key points.

Mistake 3: translating everything literally

Sometimes the right move is not word-for-word translation. It is restating the meaning in simpler language and confirming it.

Mistake 4: forgetting the post-call workflow

For many international teams, the biggest pain is not the live meeting. It is what happens after: notes, decisions, handoffs, and follow-ups spread across languages and tools.

---

Where Leyo fits

If you regularly talk to customers, partners, or teammates across languages, the hard part is not just understanding the live conversation. It is preserving the meaning afterward.

Leyo is built for that broader communication workflow:

• Leyo Meet helps you run multilingual conversations with captions and translation support
• shared meeting memory helps your team keep one record of what was actually said, decided, and assigned
• cross-language follow-ups make it easier to turn a conversation into clean next steps for teams and clients in different languages

That is especially useful in discovery work, where one small misunderstanding can send product decisions in the wrong direction for weeks.

---

Quick takeaway

If you only change one thing, do this:

Ask shorter questions and repeat back what you heard before moving on.

That single habit will improve the quality of your multilingual customer interviews more than trying to sound more fluent.