<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Alexander Rådahl Benz</title>
    <description>The latest articles on DEV Community by Alexander Rådahl Benz (@alexanderbenz).</description>
    <link>https://dev.to/alexanderbenz</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F683604%2F07ebc6e2-eb32-4f79-a9e8-8063215a0cd7.png</url>
      <title>DEV Community: Alexander Rådahl Benz</title>
      <link>https://dev.to/alexanderbenz</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/alexanderbenz"/>
    <language>en</language>
    <item>
      <title>A podcast guest brief you can copy before recording</title>
      <dc:creator>Alexander Rådahl Benz</dc:creator>
      <pubDate>Thu, 27 Aug 2026 22:23:29 +0000</pubDate>
      <link>https://dev.to/alexanderbenz/a-podcast-guest-brief-you-can-copy-before-recording-44kj</link>
      <guid>https://dev.to/alexanderbenz/a-podcast-guest-brief-you-can-copy-before-recording-44kj</guid>
      <description>&lt;p&gt;Most bad interview prep starts by writing 20 questions.&lt;/p&gt;

&lt;p&gt;I’d rather decide six things first. They give the host direction without deciding the guest’s answers in advance.&lt;/p&gt;

&lt;h2&gt;
  
  
  Podcast guest brief
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Audience&lt;/strong&gt;&lt;br&gt;
Who should care about this episode? Be narrow enough that the host can picture one listener.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Angle&lt;/strong&gt;&lt;br&gt;
What tension, argument, or useful question is the interview actually about?&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Run of show&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;00:00 to 05:00: context and stakes&lt;/li&gt;
&lt;li&gt;05:00 to 15:00: guest experience&lt;/li&gt;
&lt;li&gt;15:00 to 30:00: examples and ideas&lt;/li&gt;
&lt;li&gt;30:00 to 40:00: tradeoffs, mistakes, or objections&lt;/li&gt;
&lt;li&gt;40:00 to 45:00: takeaway and close&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Questions&lt;/strong&gt;&lt;br&gt;
Write 4 to 6 anchor questions. Treat them as places to start, not a list you have to finish. The best follow-up is usually hiding inside the guest’s last answer.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Clip targets&lt;/strong&gt;&lt;br&gt;
Write down the kinds of moments worth listening for: a method someone could steal, a specific example, a strong correction, or a useful before/after. Don’t write the quote before the guest says it.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Guest prep&lt;/strong&gt;&lt;br&gt;
Send the audience, premise, topic areas, examples worth preparing, boundaries, and recording logistics. I’d keep the host’s follow-up notes private so the conversation still has somewhere to go.&lt;/p&gt;

&lt;p&gt;I build Mato, and we turned this structure into a free &lt;a href="https://heymato.com/resources/podcast-guest-brief-template/" rel="noopener noreferrer"&gt;copy/paste guest brief template&lt;/a&gt; and a &lt;a href="https://heymato.com/tools/podcast-guest-brief-builder/" rel="noopener noreferrer"&gt;browser-based guest brief builder&lt;/a&gt; if you want the structure without starting from a blank page.&lt;/p&gt;

&lt;p&gt;If the host already knows exactly what the guest will say, the brief went too far.&lt;/p&gt;

</description>
      <category>interview</category>
      <category>podcast</category>
      <category>writing</category>
    </item>
  </channel>
</rss>
