Do the reading before you write the questions
Read their work, not their bio. Listen to two of their recent interviews and find the place where the good part stopped. Then write areas instead of a script. Six areas you want to reach gives you a conversation. Twenty numbered questions gives you a form to fill out on the air.
Their last few interviews tell you what they have already said out loud and which answer they clearly have memorized. That memorized answer is a landmark. Start the conversation just past it, and let your first question prove inside one sentence that you are not running the same script.
Look for the question their last ten interviews stepped around. Anyone with a public story has one: the year that gets summarized in half a sentence, or the decision nobody has asked them to defend. Ask about that, kindly, and you have an episode that exists nowhere else.
- Six to eight areas, written as topics rather than sentences. You ask them in whatever order the conversation earns.
- One question you are slightly nervous to ask. If nothing on the page makes you nervous, the episode will be pleasant and forgettable.
- Two specifics from their work that nobody would have found in a bio.
- The opening question, written word for word. It is the only one worth scripting.
- A hard stop, and the fact that you told them about it.
Keep all of it in one place rather than five. Pod Green Room gives every booked guest a prep page holding that guest's episode concept, your areas, and your reading notes right next to your guest tracking. The rest of the booking sequence is in the guide to booking podcast guests.
The first five minutes set the hour
Spend them off the record. Check levels, name the hard stop, tell them they can restart any answer, then talk about something ordinary until their shoulders drop. Most guests arrive braced for an exam. The recording gets better the moment they stop performing, and that usually happens before you press record.
The warm-up is where you tell them what will not happen. No ambush, and if they say something they regret, it comes out. That sentence costs you nothing, and it buys candor for the next hour.
Then open with a real question. "Tell us about yourself" hands someone a microphone and no direction, and what comes back is the resume they have delivered forty times. Ask about a specific moment instead, or about something they wrote that you want them to defend.
A good opener is narrow enough to answer in one sentence and interesting enough that nobody stops there. "You shut the product down on a Tuesday. What happened Monday?" Ten seconds in, the guest is inside a story, and anyone deciding whether to keep listening has already heard something.
Listening is the skill everything else sits on
The best question in an interview is usually one you did not prepare. It comes from a clause the guest dropped in passing, and you only catch it if you were listening instead of reading ahead. Prepared questions keep the episode on schedule. Follow-up questions are what people remember.
The discipline is small and hard: while the guest is answering, do not rehearse your next question. That rehearsal is why hosts ask about something the guest covered two minutes ago, and every listener hears it. Put the page down.
Let them finish, then wait a beat. Not a dramatic pause. One or two seconds after you think the answer is over. Guests fill that space more often than not, and the sentence they add is the honest one. The sentence before it was the prepared one.
Silence feels far longer in the chair than it does in the edit. A second of air that felt unbearable while recording is invisible to a listener. Be the person who does not rush to fill it.
The two hosts nobody finishes listening to
One interviews their own notes. The other talks more than the guest. Both are nerves wearing a professional costume, and both are audible inside four minutes. For a fast diagnosis, open the transcript of your last episode and look at whose words are on the page.
- The host who interviews their notes. Every question arrives in the order it was written, whatever the guest just said. Nobody in the episode was surprised. The fix is crossing off the questions an answer already covered, out loud if you have to.
- The host who talks more than the guest. Long setups, a personal story bolted to the front of each question, agreement noises over the top of the answer. The fix is asking the question and stopping. A question needing three sentences of context is two questions.
Both come from the same place, which is not wanting the silence to be your fault. The way out is preparation you trust enough to set down.
Steering without bulldozing
Part of hosting is ending things. When a guest is nine minutes into an answer, you are allowed to interrupt, as long as you interrupt into their content rather than away from it. Take the last concrete thing they said and turn it into the next question.
That sounds like "hold on, you said the board pushed back. Who on the board?" It does not land as a cutoff, because you are asking for more of what they were already saying. What you cut is the part they have said on four other shows.
The opposite problem is the guest who stalls. Do not repeat the question louder. Make it smaller. If "how did you build the team" produces nothing, try "who was the first person you hired?" One obvious answer usually gets them moving again.
Keep a running list of the things they say sideways. Guests drop their best material in subordinate clauses, on the way to whatever they think the point is. Two words in the margin is enough to come back later: "you mentioned you nearly quit that year." Three hundred episodes in, that move has produced more of my best segments than anything I planned.
Ask the hard question kindly
Ask permission, then be specific. "I want to ask about the layoffs. Is that open?" gives a guest half a second to prepare and rarely gets a no. Vagueness is the thing that feels hostile. A precise question about a hard subject reads as respect, because it proves you read the record.
What you do next matters more than the question. If the answer is thin, ask once more without heat: "can you say more about that?" If they decline a second time, move on and mean it. A guest who watched you let something go will give you more later than one you cornered.
Do not soften it into mush either. "Some people have said there were maybe concerns around the culture" is worse for everyone than "three people who worked for you told a reporter the culture was punishing. What would you say to them?" The second is harder to hear and easier to answer.
How you end is part of the interview
Two things belong at the end: a closing question you ask every guest, and a hard stop you honor. Finishing five minutes early is a gift to someone whose day is scheduled in blocks. Running twenty minutes long becomes a story your guest tells other people you wanted to book.
The closing question should be answerable in under a minute and impossible to answer generically. Ask the same one every time. Regular listeners start waiting for it, and you end up with a shelf of short, comparable answers that cut themselves into clips.
Before you stop recording, ask one more thing: is there anything I should have asked you? Some of the best two minutes I have ever recorded came after that question, from someone who had been waiting the whole hour for a door to open.
Then close the loop while the conversation is still warm. The thank-you, the assets they can post, the release date. That is where most shows leak, and it is exactly what a guest pipeline with follow-up nudges is for. Pod Green Room queues those touches against each booking, and the after-the-yes templates have the messages already written.