Claude Prompts for Podcast Outlines

A podcast host running a weekly interview show once recorded a 90-minute conversation and cut it down to 20 usable minutes in editing — not because the guest was bad, but because the conversation wandered with no structure to pull it back. The fix wasn't a better guest. It was claude prompts for podcast outlines used before recording, not after.

The Problem This Host Faced

He was booking genuinely interesting guests but going into every interview with a loose list of "topics to cover" rather than an actual arc. Episodes felt shapeless, listener retention dropped noticeably past the 15-minute mark according to his hosting platform's analytics, and editing took hours because there was no clear through-line to cut around.

The Wrong Approach

His first attempt at using Claude just asked for questions:

Give me 10 questions to ask a guest about [topic].

The questions were fine individually, but a list of 10 disconnected questions isn't a structure — it's still up to the host to sequence them live, under the pressure of an actual recording, which is exactly the skill that was failing him.

The Correct Prompt

I'm interviewing [guest, one sentence on their background/expertise]
about [specific topic]. Design a 5-segment episode arc, not just a
question list:
1. Opening hook — a specific, surprising angle related to their
   expertise that isn't the obvious "tell us about yourself"
2. Origin/context segment — how they got into this specific work
3. Core insight segment — the 2-3 ideas listeners should walk away
   understanding, sequenced from foundational to advanced
4. Tension/nuance segment — where their view differs from
   conventional wisdom, or a genuine tradeoff in their work
5. Closing — a forward-looking question and a clear sign-off

For each segment, give me 2-3 possible questions, not a script —
I still need to listen and follow up live.

What this does: Structuring by segment and purpose, not just topic, is what gives the host something to actually navigate back to when a tangent runs long — he can feel when he's in the "core insight" segment and knows it's time to move toward "tension" before wrapping. The explicit "not a script" instruction also matters — it keeps the conversation live rather than turning into a guest reading prepared answers to prepared questions.

Results and What Changed

Using this structure for the next batch of episodes, his average usable-recording-to-final-cut ratio improved dramatically — closer to 45 usable minutes out of a 55-minute recording, instead of 20 out of 90. Editing time dropped correspondingly, since there was a clear arc to cut around instead of a transcript to mine for the good parts.

⚡ Pro tip: Send the "opening hook" and "core insight" segments to your guest ahead of time (not the full outline) so they know the shape of the conversation without over-rehearsing. This noticeably improved guest comfort without sacrificing spontaneity.

⚠️ Common mistake: Treating the generated questions as a script to read verbatim. The segment structure is meant to be a map you glance at, not a transcript you follow — the best moments in an interview usually come from following up on something unscripted the guest just said.

How to Apply This to Your Situation

For solo/narrative episodes instead of interviews:

I'm doing a solo episode about [topic]. Structure it in this arc:
hook, why this matters now, the main argument broken into 3 clear
points, one likely objection and my response to it, and a specific
call to action for the close. Give me a one-sentence summary of
each section, not a full script.

Scenario: B2B marketing podcast host planning a themed season A B2B marketing podcast host used the segment-arc structure across an entire themed season on a single topic, deliberately varying which segment got the most time episode to episode so the season didn't feel repetitive despite covering related ground each week.

Scenario: True crime podcaster restructuring a two-part episode A true crime podcaster used the arc structure to plan where to place a cliffhanger between part one and part two of a two-episode story, treating the "tension/nuance" segment as the natural place to end part one.

Scenario: Internal company podcast host interviewing cross-functional leaders An internal comms lead running a company podcast used the interview arc structure to interview leaders across different departments consistently, giving the show a recognizable shape episode to episode even as the specific guests and topics varied widely.

Next Steps

The fix here generalizes past podcasting: structure before you record, not after you edit. Once you've built a segment-arc prompt that fits your show's format, save it in PromptABCD so every new episode starts from a proven shape instead of a loose topic list and hope.