Skip to content
Course contents

Lesson 19

Asking Clarifying Questions

4 min read

Why this matters

Misunderstandings are expensive. If you misunderstand a requirement, you can spend a week building the wrong feature. Many non-native speakers don't ask because they're afraid of looking slow. But native speakers ask clarifying questions all the time. It's a sign of a careful developer, not a weak one.

The core skill

When you didn't hear or catch something

In fast meetings or bad calls, you'll miss words. Ask for a repeat, and be specific when you can.

Sorry, I didn't catch that. Could you say it again?
Sorry, you cut out for a second. What was the deadline?
Could you speak a bit more slowly, please?

Catch here means "hear and understand". Cut out means the audio stopped on a call.

When you heard it but don't understand

Ask about the specific part you don't understand. That's faster than "Can you explain again?"

What do you mean by "real-time"? Within a second, or within a few minutes?
When you say "all users", does that include admins?
Could you give me an example?

Checking your understanding

Repeat what you understood in your own words. This is called paraphrasing, and it's the best way to find misunderstandings early.

So, if I understand correctly, we need the export by Friday, but only
for the admin dashboard, not for regular users. Is that right?

Just to confirm: the new API replaces the old one, and we remove
the old one in January?

Asking about requirements

Before you start a task, these questions save the most time:

What problem are we trying to solve?
Who is going to use this?
What does "done" look like?
Is there a deadline?
What should happen if the data is missing?

These are especially useful when a ticket has only one line.

Useful phrases

Asking for a repeat

  • Sorry, I didn't catch the last part.
  • Could you repeat the version number?
  • Sorry, you broke up there. (= the audio was bad)

Asking for meaning

  • What do you mean by "soon"?
  • Could you clarify what "fast" means here?
  • Could you give me an example?

Paraphrasing

  • So, if I understand correctly, …
  • Just to confirm, …
  • Let me make sure I got this right: …
  • So what you're saying is …

Checking details

  • Does that include mobile users?
  • What should happen if the payment fails?
  • Who should I ask about the design?

Common mistakes

"Can you repeat again?" Repeat already means "say again", so again is extra: "Can you repeat that?"

"What means 'idempotent'?" In questions with what as the object, you need does: "What does 'idempotent' mean?"

"Sorry, I didn't understand nothing." English uses only one negative here: "Sorry, I didn't understand anything." Even better, say which part: "Sorry, I didn't understand the part about the tokens."

Saying "yes" when you didn't understand. This is the most expensive mistake. If you're not sure, say: "I'm not sure I followed. Could you explain the last part again?"

Formal vs. casual

  • Meeting with a client: "Just to make sure I've understood correctly: you'd like users to receive the report every Monday, and only managers should be able to see the totals. Is that right?"
  • Chat with a teammate: "So reports every Monday, managers only for totals, right?"

Exercise

Take a ticket or task from your current work. Write:

  1. Three clarifying questions you could ask about it.
  2. One paraphrase that starts with "So, if I understand correctly, …"

Then actually send one of your questions to the person who wrote the ticket.

Hint: look for vague words like fast, simple, all, soon or real-time. They are usually the best things to ask about.

Recap

  • Ask for a repeat with Sorry, I didn't catch that.
  • Ask about the exact word or part you don't understand.
  • Paraphrase to confirm: So, if I understand correctly…
  • Ask about the problem, the users and what "done" means.
  • Never say "yes" when you didn't understand.