How to Interview an Expert Who Knows More Than You


To interview someone who knows far more than you, stop trying to match them. Sit in the translator's chair: your job is to ask the question your listener is too embarrassed to ask, request an analogy whenever an answer goes abstract, and turn jargon into plain English in real time. You are not the second-smartest person in the room. You are the only person in the room speaking for the audience.
Most hosts get this backwards. Faced with a brilliant guest, they over-prepare, drop a few field terms to prove they belong, and then nod through answers they don't fully follow because admitting confusion feels like losing. The episode comes out impressive and useless, two people talking past the listener. The fix isn't more reading. It's a stance and five repeatable moves that convert expertise into something a beginner can actually use. Here's the toolkit.
How do you interview someone who knows more than you?
You interview someone smarter than you by reframing your job entirely. You are not there to debate the expert or to demonstrate parity, you are there as the listener's stand-in, asking what they'd ask if they had the mic. That means asking the basic question out loud, slowing the expert down when they accelerate into jargon, and checking after each answer that a non-specialist would understand it.
The relief in this is real: you don't have to know the field. You have to know your listener and you have to be unembarrassed. A host who confidently says "explain that to me like I've never heard the term" is doing more for the audience than one who pretends to track every acronym. Curiosity beats credentials in this seat. The guest is the authority; you are the bridge, and a good bridge is honest about where it starts.
Prepare enough to ask the right dumb question
Sitting in the translator's chair is not a license to wing it. You prepare differently from how you'd prepare to argue with the expert. You're not memorizing their field, you're learning enough to ask precise, basic questions and to know when an answer skipped a step the listener needed. Aim for the shape of the topic, not mastery of it.
Spend your prep building three things: a one-line plain-English summary of what this person is famous for, a short list of the three or four terms they'll definitely use that your audience won't know, and the two or three questions a smart beginner would actually have. That's it. If you try to learn the whole subject, you'll arrive intimidated and start performing knowledge instead of asking for it. A focused 90 minutes beats a panicked week, there's a full method in how to research a guest in under 90 minutes. The goal of prep here is confidence to be confused, not the elimination of confusion.
The five moves that translate an expert in real time
When the mic is live, the work happens in the gaps between the expert's answers. These five moves are the whole toolkit. Each one converts something dense into something a beginner can hold, and none of them requires you to know more than the guest, only to know your listener and stay unembarrassed.
The dumb question is the most valuable thing you'll say all episode, and the hardest to make yourself say. When a term flies past, stop and ask what it means, not "as you know" or "for some of our listeners," just "back up, what is that?" Own the question. Every listener who didn't know either just exhaled. The host who fakes understanding to protect their ego robs the whole audience.
The analogy request is how you make abstract concrete. When an answer goes theoretical, ask: "What's that like for someone who's never seen it?" Experts often have a great analogy ready and never get asked for it. If their first one is still too technical, ask for another, "give me the version you'd use at a dinner party." This is the move that produces the line people remember.
The jargon swap turns you into an active translator instead of a passive nodder. You take a swing at restating their point in plain words and invite the correction: "So in plain terms, that's basically X, am I close?" A nervous host asks the expert to simplify; a confident one attempts the simplification and lets the expert fix it. The correction is usually sharper than anything you'd get by just asking again. This is the engine of the whole interview, and it pairs with the follow-up question, which is where the episode actually lives.
The so-what check drags expertise back to the listener's life. After a precise, correct, and slightly inert answer, ask why a normal person should care, what changes, what they should do differently, what they'd get wrong without this. Experts default to what is true; your job is to pull them toward what it means for you.
The one-sentence recap lands the plane. After a long answer, summarize it in a single sentence and check it: "So the whole thing comes down to X." If you nailed it, you've handed the listener a clean takeaway. If you missed, the expert sharpens it. Either way you get a tidy, quotable line, and those clean summaries are frequently the most shareable moments in the episode.
What an expert answer looks like, before and after
The five moves are easier to trust when you see what they do to a real answer. Here's a typical expert reply, dense and accurate, and the same point after a host asked for an analogy and a so-what.
The left answer isn't wrong. It's just built for peers, not for an audience. The host didn't need to understand quantization to get to the right side, they only needed to ask "what's that like for someone outside the field, and why would a normal user notice?" The expertise was always there. The translation was the host's to draw out.
Common mistakes when interviewing an expert
- Faking understanding to save face. The worst habit on this list. You nod through a term you didn't catch, and now the listener is lost and you can't ask a real follow-up. Admitting "I don't follow, say that again simpler" is a strength, not a flaw. This is also basic host etiquette that makes a guest feel useful, not interrogated.
- Performing your own knowledge. Dropping field terms to prove you belong turns the episode into a two-expert conversation the audience can't enter. Spend your credibility on better questions, not on showing off vocabulary.
- Letting jargon stack. One unexplained term is survivable; three in a row and the listener has tuned out. Stop at the first one. The cost of interrupting for a definition is far lower than the cost of losing the audience for the next five minutes.
- Debating instead of drawing out. When you do know a little, the temptation is to argue. A few sharp challenges are great; a sparring match is not, the guest is the authority and the audience came to learn from them, not to watch you fence.
- Skipping the recap. Long expert answers need a landing. Without your one-sentence summary, a brilliant explanation evaporates by the next question. Recap, confirm, move on, and you'll have a clean takeaway every time.
Why the translation is the whole job
The reason this matters beyond the recording: the clips that travel from an expert interview are almost never the technically deepest moments. They're the analogy, the plain-English recap, the "so what this really means for you is" line, the exact moments your five moves produce. 57% of listeners now rely on social media for podcast recommendations, the first time that source passed friends and family (InsideRadio). When you steer an expert into a sentence a beginner can repeat, you've made the one thing that spreads. The translation pays twice, once for the listener in the room, once for the listener who finds the clip later. That listening discipline is its own skill, covered in active listening for hosts who are busy thinking.
Frequently asked questions
How do you interview an expert without sounding stupid? Reframe "stupid" as "the listener's representative." The questions that feel basic to you are the ones your audience needs answered, and asking them clearly is a skill, not an embarrassment. Prepare enough to ask precise basic questions, then ask them with confidence: "Explain that to me like I've never heard the term." Curiosity reads as competence; faked expertise reads as bluffing.
How much should I prepare before interviewing a subject-matter expert? Enough to ask the right basic questions, not enough to debate the guest. Build a one-line plain summary of what they're known for, a short list of terms your audience won't know, and the two or three questions a smart beginner would have. That's a focused 90 minutes, not a week, see how to ask questions that get real answers for turning that prep into a question list.
What do I do when a guest uses jargon I don't understand? Stop at the first unexplained term, not the third. Ask "back up, what does that actually mean?" and then attempt your own plain restatement so they can correct it: "so in normal terms, that's X?" Letting jargon stack is what loses the audience. One clean definition is worth more than five minutes of nodding through terms.
How do I get an expert to give a simple answer? Ask for an analogy and a so-what. "What's that like for someone outside your field?" pulls a household comparison; "why should a normal person care?" pulls relevance. If the first analogy is still too technical, ask for the dinner-party version. Experts usually have a simple answer ready, they're just rarely asked for it.
Is it okay to challenge an expert if I'm not an expert myself? Yes, on behalf of the listener, and sparingly. A few honest "but wouldn't someone object that…" questions sharpen an interview and keep it from being a press release. A sustained debate, though, turns the episode into a contest the audience didn't come for, and it's worth knowing the unwritten etiquette guests expect from a host. Challenge to clarify, not to win.