Podcasting for Speakers: Keep Useful Conversations Going
You finish a speaking engagement with a few business cards and several conversations you meant to continue. There was an event organizer who understood the audience, another speaker with an interesting perspective, and someone whose question deserved more time. Then you went home to client work and preparation for the next event.
A podcast gives you a specific invitation to send. You can ask one of those people to discuss a question your listeners care about. You're creating useful material while getting to know someone beyond the few minutes you shared at an event.
For a speaker, that can also become a way to examine your own ideas. Guests bring examples and objections you wouldn't find by delivering the same presentation again. The useful result is a finished conversation and a reason to follow through, with any referral or booking treated as a separate outcome.
Choose the Listener Before Choosing the Guest
Event organizers, executives, fellow speakers, and potential coaching clients may all be relevant to your business. They don't necessarily need the same show. Choose one main audience and one purpose so you can judge which conversations belong.
Imagine you're a leadership speaker teaching difficult conversations. A team leader could explain a performance issue, an organizer could discuss what corporate audiences need, and a business owner could describe changing how their company handles conflict. Those are hypothetical guest choices, but each has a connection to your subject.
Beside a potential guest's name, write the question you want them to answer. If you can't find one your listeners would value, an impressive title or a large following isn't enough.
Start with people you know from events, customers, peers, mentors, and other speakers. You can reach beyond that circle later. Several completed episodes will give a new guest something to examine when deciding whether the show fits them.
The name and description should make the audience and subject understandable. Say the name aloud and consider whether someone who heard it at your presentation could find the show. If you need the general setup steps, my business podcast starting guide covers those separately.
Give Preparation, Recording, and Follow-Up Different Jobs
I organize the work around three conversations. They don't all need to happen on the same day, and the third needs a reason beyond the guest having appeared on the show.
Three Conversations a Speaker Can Keep Distinct
- 1. Pre-callFind the audience problem, a useful angle, and stories to explore.
- 2. Recorded interviewFollow the guest's experience and finish something useful for listeners.
- 3. Optional post-callContinue a relevant relationship or discuss an introduction openly.
During a short pre-call, I ask who the guest helps, what they're working on, and what people misunderstand. An employee-retention consultant may reveal that their most interesting work involves managers who postpone performance conversations. That's more specific than asking for half an hour on leadership.
Save the complete stories for the recording. Note the experiences that sound promising, establish any subjects to leave out, and confirm the appointment and recording link. You need a direction, not rehearsed answers.
For the recorded interview, I use the biography to introduce the guest, then ask, "What did I miss in that introduction?" Sometimes their answer reveals a current priority that the prepared description didn't mention.
If there's a reason to continue after publication, suggest a separate conversation. One question I like is, "Who would be a useful introduction for you?" Sometimes I can help, sometimes they know someone I should meet, and sometimes there's no further action to take.
Make a business discussion explicit. A guest agreeing to an interview hasn't agreed to a surprise presentation about your services. Separate appointment types and clear invitations help the person understand what they're scheduling.
Ask for Experiences That Can Improve the Material
When a guest says, "We were struggling," ask what was happening. Was a manager avoiding a conversation? Were instructions unclear? What did the person decide to do, and what happened next? Those details give a speaker more to work with than another broad instruction to communicate better.
I keep Why, What, How-To, and What-If in mind. Why did the issue matter? What was happening? How did the guest respond? What would they do differently, or when might that approach fail? You can follow the actual answer instead of announcing a framework or forcing the questions into order.
Near the end, I like asking, "What question should I have asked you that I didn't know to ask?" It gives the guest room to contribute something my preparation missed. Then make the next step for listeners clear.
When a customer is the guest, I like the customer-as-hero idea in Donald Miller's StoryBrand framework. Ask what the customer wanted to accomplish, what got in the way, what they tried, and what happened. Your company can be part of the experience without making the interview a commercial about how wonderful you are.
For another hypothetical example, an event organizer might tell a leadership speaker that attendees need practical examples more than another motivational story. That gives the speaker something to investigate: which situations are they facing, what decisions are difficult, and what would an applicable example need to explain?
The conversation may never lead to a booking. You can still leave with a better understanding of the audience. If a guest's real experience could strengthen a presentation, discuss permission and attribution before using their story or customer details.
Record a Useful Conversation Without Creating a Studio Project
A quiet room, a usable microphone, clear video when needed, and a short test are a sensible starting point. Check that the recording software selected the microphone you intended. The hardware on your desk and the input actually being recorded can be different.
I use Riverside for remote interviews. Check the sound and picture together before the main conversation, and let the required uploads finish afterward. Give guests simple instructions about the link, expected duration, headphones, and a reasonably quiet place.
In person, test both speakers before starting. A phone arrangement that looks connected can still record from the wrong input or pick up clothing against a microphone. Listen to the sample instead of deciding from the equipment's appearance.
Have a fallback if something doesn't work. Audio-only may be a better use of the appointment than spending most of it fighting a webcam. You want a conversation you can publish, rather than a complicated setup that consumes the time reserved for it.
Finish the Episode and Give It Back to the Guest
For a speaker, an episode page gives organizers and prospective clients a place to see the subjects you explore and how you communicate. Give the interview a clear title, usable player, helpful summary, and relevant resource links.
Then choose a small amount of promotional material that represents the conversation. A complete short answer, an accurate quote, and a useful graphic can give the guest something worth sharing. Review the meaning and captions rather than publishing an automatic selection untouched.
Keep one production record through editing, review, publication, and guest notification. The podcast editing handoff checklist helps collect the recording, guest details, links, and instructions before the next person starts.
Send the guest the published page, the approved assets, and optional wording they can adapt. Check the access and links. A folder full of unexplained files creates another job, while a small, organized kit is something they can use.
Keep private relationship notes separate from approved public material. If you use a recording or AI notetaker for another conversation, explain that and obtain agreement. A personal goal mentioned in a post-call isn't automatically content for the next LinkedIn post.
Measure What Happened After the Interview
Downloads can tell you something about audience activity. They won't tell you whether you made the introduction you promised or learned something useful from an event organizer. For a speaking business, give those outcomes their own record.
| What you're tracking | What to record | Keep the distinction clear |
|---|---|---|
| Useful audience insight | A question, objection, or example to examine for a talk. | A useful idea isn't automatically proof of an improved presentation. |
| Follow-through | The resource sent or introduction completed. | A promise and a completed action are different states. |
| Speaking inquiry | Who asked, what event they described, and the next step. | An inquiry isn't a confirmed booking. |
| Client or referral opportunity | The relevant conversation and any agreed action. | Count paid work separately when it actually happens. |
A spreadsheet with the guest, last contact date, commitment, and next action is enough to begin. You don't need a sophisticated system to notice that someone asked for a resource and never received it.
Look for recurring audience problems across the interviews. Those may deserve a new talk, workshop, or longer project. Keep the podcast's immediate purpose clear before adding another production obligation.
The useful standard is whether you had worthwhile conversations, finished the episodes, and followed through. Any booking or client result belongs in the record when it happens, with its own context.
Turn One Event Contact Into a Specific Invitation
Pick someone from the event whom you'd like to understand better. Choose a question they could answer for your audience and invite them to a conversation around it. That is more useful than another vague promise to stay in touch.
If you can make those conversations happen but need the production work handled, visit DFY Podcast's production page. Bring the audience you want to reach and the schedule you can maintain so we can discuss the editing, episode pages, and supporting content that should follow each recording.