Your Customers Already Know What Your Podcast Should Be About: Turn Buyer Questions Into Useful Episodes
Casey Cheshire has an uncomfortable exercise for marketers: name seven customer companies, then name seven individual customers. The second question can produce a longer pause.
In our conversation about customer connections, Casey described the risk of building campaigns around assumptions instead of understanding people. I think podcast planning has the same problem. We can keep finding impressive guests while missing the question a customer asked this morning.
Your inbox may contain a better episode idea than another brainstorming session. The useful work is capturing that question, finding the decision behind it, and choosing an explanation that will help the next person asking it.
Start a small question file, then review it monthly
Keep the customer's original wording privately, along with enough context to remember why they asked. Once a month, review the questions from appropriate sales, onboarding, support, and follow-up conversations. Group related concerns and choose a few that deserve attention.
This doesn't require a new content platform. Use a document or spreadsheet your team can already find. The file should help you choose a conversation, not become another system you organize instead of recording.
I'd preserve a phrase such as "Am I going to have to redo all this work?" rather than immediately relabel it "implementation concerns." The first version contains a worry. The second could mean almost anything.
Here is a completed editorial illustration. The customer and situation are hypothetical, but the row shows the information worth retaining:
| Field | Example entry |
|---|---|
| Customer's question | "How quickly can we install the new system?" |
| Situation underneath it | The manager is worried about employee training while ordinary work continues |
| Decision to explain | What should a small team prepare before changing its workflow? |
| Evidence | One illustrative concern, not proof that the entire market has this problem |
| Best speaker and format | An employee-training specialist in a focused interview |
| Episode promise | Explain preparation, responsibilities, and common handoff problems |
| Publication checks | Verify factual claims and keep private employee or client details out |
| Follow-up | Share the finished explanation with relevant people and ask what remains unclear |
That row is more useful than a topic called "Efficiency Tips." You know who needs the answer, why it matters, and what the guest must help explain.
- 1. Capture the wordsRecord the original question and its context privately.
- 2. Find the decisionAsk what the person needs to understand or do next.
- 3. Choose the explanationSelect a qualified guest, your own answer, or a shorter resource.
- 4. Publish and listen againShare the finished answer appropriately and note what remains unclear.
Ask one more question before deciding what the episode is
A person asking how quickly software can be installed may be worried about something installation instructions won't solve. In our hypothetical example, their manager already has too much to do and doesn't know who will train the employees.
You discover that by asking what prompted the question, what they've tried, or what a satisfactory result would look like. You don't discover it by assigning an episode on installation speed before listening to the concern.
The same question can expose a business problem as well as a content opportunity. If customers repeatedly ask who handles training, your onboarding explanation may need to say so more clearly. Recording an interview shouldn't become a way to avoid fixing confusing service information.
Keep customer service first. Someone reporting an access problem or billing error needs help, not an impromptu research interview. Save the appropriate detail after dealing with the actual issue, and follow your business's privacy practices.
Also separate the record from your interpretation. "This customer asked who trains the staff" is an observation. "Our whole market is afraid of training" is a conclusion you haven't established. More conversations may reveal a pattern. One vivid conversation alone doesn't prove it.
Choose the speaker after choosing the job
Steve Gordon discussed using clients, experts, prospects, and solo episodes for different purposes. You can use that flexibility when deciding how to answer a customer question.
A customer interview is useful when someone has firsthand experience they can appropriately discuss. Ask what happened, which choices they considered, what surprised them, and what they'd do differently. The purpose isn't to guide them toward praising your company.
An expert interview makes sense when part of the answer is outside your knowledge. For our workflow example, a training specialist may offer more useful guidance than another software demonstration. You can contribute through your questions without pretending to be qualified in every connected subject.
A solo episode works when you can explain the answer responsibly yourself. Walk through the process, show an appropriate example, and identify the limits. It doesn't need an invited guest simply because your last ten episodes had one.
Some questions don't need an episode at all. "Where do I update my billing information?" is usually better served by a direct answer or short help page. A recording calendar isn't a reason to turn a small instruction into thirty minutes of content.
Group by the decision, not every variation of the wording
One customer asks how long onboarding takes. Another asks when the team will be fully operational. Someone else asks how much work employees must do during the first month. You may have one useful episode covering the timeline, responsibilities, and common delays rather than three repetitive recordings.
Robert Ingalls discussed this opportunity for law firms. Professionals already hear many of the questions prospects bring to an appointment. His suggestion of identifying 20 or 30 common questions illustrates the supply of useful material, not a quota every show must fill.
Before scheduling, write one sentence saying what the listener should understand afterward. If the episode is about choosing a provider, should someone be able to compare options, gather information, or ask a better question? Choose the result you can actually deliver in the conversation.
The title should reflect that result. A broad discussion can be interesting, but a practical title creates a practical obligation. Spend enough of the recording answering what you promised rather than retelling the guest's biography.
Prioritize consequence as well as frequency
Recurrence is useful evidence. Frank Husmann described regularly talking with clients and prospects to understand the problems behind content decisions. That habit is more reliable than deciding you've finished learning what buyers need.
But the most frequent question doesn't automatically win. Suppose seven people ask how long setup takes and one asks who owns a handoff between departments. Those hypothetical counts could point to two different issues. The handoff may be less common but consequential enough to deserve investigation.
Consider how often the question appears, what decision is at stake, whether you can explain it confidently, and whether a useful answer already exists. If the answer depends on changing technical or regulatory information, verify it before recording or publication.
A promising question can stay in the queue while you find the right expert. You're not obliged to publish speculation simply because someone asked something important.
Keep the original customer problem connected to the eventual recording.
Give the guest a worthwhile reason to participate
Casey contrasted asking a customer for a promotional case study with offering time, attention, and a platform for their experience. I like that distinction. An invitation to discuss a decision can serve the guest and listeners without requiring an endorsement.
Explain the subject, audience, recording arrangement, and intended publication. Make sure the person is comfortable sharing the relevant material. A private customer conversation doesn't become a public story just because it would make a good episode.
If someone doesn't want to appear, their question may still reveal an issue you can explain in general terms. Use an appropriate hypothetical or your own expertise while keeping identifying details out. Don't put words in the customer's mouth to preserve a story they didn't agree to tell.
Related conversations and resources
Put one useful answer on the calendar
For a first pass, review ten questions you're entitled to use, group the related concerns, and choose one. Ten is a manageable exercise, not a research requirement. Write the episode promise and identify the best speaker.
Prepare a few prompts about the situation, what was tried, what proved difficult, and what the listener needs to understand. After publication, ask a relevant recipient whether the explanation addressed the concern. A more specific question gives you somewhere useful to go next. It doesn't automatically establish a sale.
If you'd rather have someone conduct the conversations under your brand, our hosted interview option is a relevant alternative. The customer question should still guide what gets recorded.
If useful conversations already exist but production keeps them off the calendar, bring one recording and its customer question to our podcast production page. At DFY Podcast, we handle the editing and publishing work so the answer doesn't remain another good idea buried in your inbox.