How to Write Interview Questions That Edit Well
A good interview question does two jobs at once. It gets the person talking, and it gets you a clip you can actually use. Miss the second job and you walk away with an hour of conversation and no usable moments. This guide covers what to do before you ask anything, how to warm a subject up, which core questions reliably produce strong answers, how to follow up in the moment, which questions quietly ruin an edit, and how to carry all of it into the cutting room.
Before You Ask
Know the story you're trying to find
Write your questions after you decide what the piece is about, not before. NPR's training team frames pre-interview prep as figuring out where a source fits into the story you're already building and what they might tell you that you don't expect yet, according to NPR Training's guide to preparing for an audio interview. That means research first: read what the person has already said publicly, understand the events you're asking about, and only then draft questions.
Terry Gross, longtime host of NPR's Fresh Air, goes further and treats the question list itself as a structural document. "I always write down questions beforehand because the interview isn't the raw material for me, but the final product," she has said. "I want it to have a shape. I want it to have a narrative, a beginning, middle and end, and I want each question to build on the one before," reported by Writer's Digest. That's worth sitting with. If you can't sketch the shape of the finished piece before you sit down, your questions will wander, and so will the answers.
Group your questions into 3 to 5 chapters, the way a producer builds a rundown: background, the central event or turning point, consequences, and reflection. Each chapter gets 2 to 4 questions. Anything beyond that and the subject starts repeating themselves, which is fine for them but expensive for you in the edit.
Send a short heads-up to the subject beforehand covering the topics you'll ask about, not the exact wording. StoryCorps recommends sharing your question list ahead of time so both people get more out of the time together, per StoryCorps' Great Questions guide. A person who knows roughly what's coming gives longer, more considered answers than one caught flat-footed.
Warm-up Questions
Spend the first two minutes on easy ground
Open with something the subject can answer without thinking hard: where they grew up, how they got into their field, what a normal day looks like for them. The content rarely makes the final cut. Its job is to get the person talking in full sentences and used to hearing their own voice on the recording, and to let you check levels without wasting a real question on it.
StoryCorps' published tip sheet is built around this idea directly, suggesting openers like "Where were you born?" or "Can you describe the first time we met?" before moving into anything substantial, per its Great Conversations guide. NPR's own training material makes a related point about equipment: acclimate the subject to the microphone early, because someone who is still self-conscious about being recorded gives shorter, more guarded answers.
Keep warm-up questions open-ended even though they're easy. "Where did you grow up?" beats "Did you grow up nearby?" A yes-or-no answer at minute one sets a bad pattern for the rest of the session, because subjects mirror the shape of the question. Ask short-answer questions and you train them to give you short answers all the way through.
Two to three warm-up questions is enough. Longer than that and you're burning the subject's energy and patience before you get to the material you actually need.
The Core Questions
Ask open, ask one thing, and ask them to restate
The single biggest lever on answer quality is whether a question is open or closed. "Walk me through the day you found out" produces a scene. "Were you surprised?" produces one word. Poynter senior scholar Roy Peter Clark's basics-of-interviewing guide puts open-ended, one-at-a-time questions at the top of the list, alongside doing enough research that the conversation feels like two people who already know the subject talking it through, according to Poynter's illustrated interviewing guide.
Ask for one thing per question. "What happened, and how did the team react?" invites the subject to answer only the second half, or to blend both into a sentence that can't be split apart later. Break it into two separate questions and you get two separate, independently usable answers.
Ask your subject to build your question into their answer. If you ask "When did you start the company?" and get back "2011," that clip is dead on arrival, useless without your question baked into the transcript next to it. Prompt instead with "Tell me when and why you started the company," or simply ask the person to answer in a full sentence. A subject who says "I started the company in 2011 because..." gives you a self-contained line that drops into any part of the edit without their original question attached to it.
Favor "how" and "why" over "what," since NPR's training notes those two words tend to pull description and reasoning out of a source rather than a flat fact, and description is what a scene is built from.
Order matters too. Save your hardest or most sensitive questions for the second half of the conversation, once trust has built up, a sequencing point Poynter's guide also makes. Asking the hard thing first, before the subject is warmed up, tends to produce a guarded, shorter answer than the same question asked twenty minutes in.
Follow-ups That Work
The best material rarely comes from the scripted question
Plan your core questions, then be ready to leave them behind. NPR's training team is direct about this: active listening lets you catch details, contradictions, or emotional shifts in real time that call for a follow-up your prepared list never anticipated, and that follow-up is frequently where the strongest material in the whole interview shows up.
The simplest follow-up in journalism is also the most underused: repeat a phrase the subject just used and ask what they meant by it. If someone says "it was chaos in there," don't move on. Ask "what did the chaos actually look like?" You're not introducing a new topic, you're asking them to zoom in on the one they already picked, which usually produces the most specific, most quotable version of the story.
Let silence do some of the work. Poynter's guide lists patience, not filling a pause with the next scripted question, as one of its core basics. A few seconds of quiet after an answer often prompts the subject to keep talking, adding a clarifying detail or an admission they hadn't planned to share, and that unplanned extension is frequently the strongest soundbite of the session.
When someone says something unexpectedly candid or emotional, don't immediately pivot to your next question. Acknowledge it, even briefly, then follow up on it. Treating a vulnerable answer like any other line item signals to the subject that it's safe to close back up, and the interview gets guarded from that point on.
Questions to Avoid
Cut anything that produces an unusable answer
Yes-or-no questions top the list. "Were you nervous?" gets you "yes." "Walk me through what you were feeling right before you went on" gets you thirty usable seconds. If a question can be answered in one word, rewrite it so it can't be.
Double-barreled questions are the second offender: two questions stapled into one sentence. "What went wrong, and what would you do differently?" forces the subject to either answer just one half or braid both together into a single tangled sentence you can't cut cleanly. Poynter flags this pattern specifically as a way subjects dodge the harder half of a question without appearing to. Split it into two questions, asked a beat apart.
Leading questions, where the answer is baked into the question itself, produce answers that sound like agreement rather than testimony. "That must have been terrifying, right?" invites a nod and a borrowed word. "How did that feel?" makes the subject supply their own language, which is almost always more specific and more usable than the word you handed them.
Jargon-loaded questions are a quieter trap. If your question assumes vocabulary the audience won't have, the answer will too, and you'll spend the edit either cutting around it or adding a lower-third to explain a phrase nobody outside the industry recognizes.
And skip any question you could answer yourself from public research. It wastes the subject's energy and the tape, and it signals you didn't prepare, which makes people guard their answers more, not less.
From Interview to Edit
The interview isn't done until the transcript is
Every technique above exists to produce one thing: a transcript full of complete, self-contained sentences you can pull out and rearrange without losing meaning. That's the actual test of a good interview question, not whether it sounded smart in the room, but whether the answer stands on its own six months later when you're staring at a rough cut.
This is where the editing side of the work actually starts, and it starts with reading, not scrubbing. Once the interview is transcribed, read it the way you'd read a script, the same approach we cover in our guide to building a paper edit: mark the lines that could stand as a scene on their own, and set aside the ones that only make sense next to the question that prompted them. If you followed the restate technique during the interview, most of your strongest answers will already read as complete sentences on the page.
Because ScriptCut times every word to the original recording, the lines you mark on the page stay linked to an exact point in the audio or video, so selecting a sentence in the transcript is the same as marking the cut. That matters most when a subject answers your core question well into a long, meandering response. You don't need to scrub back through the recording to find where the good line starts and ends; it's already sitting at the right timecode in the transcript, the same underlying idea behind how timecode anchors a transcript-first workflow.
Working from the page rather than the timeline also changes how you handle a subject who rambles. Instead of replaying a 20-minute answer three times to find the 15 usable seconds, you read it once, highlight the sentence that does the job, and move on, the same logic behind text-based editing generally. If you're conducting several interviews for the same piece, a shared, arranged transcript also makes it far easier to compare how two subjects answered the same core question, which is often the moment that becomes your strongest sequence.
Once you've selected the lines that survive, arranging them into a sequence and handing that structure to an editor is its own step, one journalists working from interview transcripts and documentary editors handle slightly differently, but the underlying habit is identical: build the story on the page first, then send a locked structure into the timeline rather than sorting it out live in the NLE. For editors cutting in Premiere Pro specifically, that structure carries over directly through a transcript-based Premiere workflow, and podcast producers running the same process across a full season of interviews can see how it scales in batch editing a podcast season.
If the interview is headed for a short vertical clip rather than a full-length cut, the same selected lines are the starting point for pulling social clips out of a longer sit-down, since a self-contained answer that works as a standalone moment on the page is exactly the kind of line that works as a standalone clip.
None of this replaces good judgment in the room. But a well-built question list, one that avoids closed and double-barreled questions, leaves room for the follow-up, and asks the subject to speak in complete thoughts, hands you a transcript that's already halfway edited before you've touched a timeline.
Sources
frequently asked questions
A question edits well when the answer can stand alone as a full sentence, without needing your question attached to make sense. Open-ended prompts that ask the subject to restate context in their answer produce clips you can drop anywhere in a sequence.
It means phrasing your question so the subject naturally repeats the key facts in their answer, for example asking 'tell me when and why you started the company' instead of 'when did you start the company.' You get a self-contained line like 'I started the company in 2011 because...' instead of a one-word answer that only makes sense next to your question.
They produce single-word answers with no usable narrative. Poynter's interviewing guide and StoryCorps' question guide both list open-ended phrasing, such as 'walk me through' or 'tell me about,' as a core basic because it hands the subject room to build a scene instead of a fact.
Treat them as separate. Two or three easy, open-ended questions at the start get the subject comfortable and talking in full sentences, but they rarely make the final cut. Their job is to set a pattern of longer answers before you ask anything that matters.
She has said the interview isn't raw material for her, it's the final product, so she builds her questions into a narrative with a beginning, middle, and end, each one building on the last. That structure is what lets a listener follow the conversation without ever hearing the questions edited out.
Group your topics into 3 to 5 chapters, such as background, the central event, consequences, and reflection, with 2 to 4 questions per chapter. StoryCorps found most people get through about 6 to 8 questions in a 40-minute session, so plan for depth on fewer topics rather than a long list you'll rush through.
Because every strong answer already reads as a complete sentence, you can select lines straight from the transcript instead of scrubbing through footage to find where a usable moment starts and ends. In ScriptCut, those transcript lines are timed to the exact word in the recording, so marking a sentence on the page marks the cut.
You might also like...
