<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Testimonials - DFY Podcast</title>
	<atom:link href="https://www.dfypodcast.com/tag/testimonials/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.dfypodcast.com</link>
	<description>Podcast Production &#38; Editing</description>
	<lastBuildDate>Sun, 08 Nov 2026 00:51:55 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=7.1.5</generator>

<image>
	<url>https://www.dfypodcast.com/wp-content/uploads/2026/10/dfy-podcast-icon-20261015-32x32.png</url>
	<title>Testimonials - DFY Podcast</title>
	<link>https://www.dfypodcast.com</link>
	<width>32</width>
	<height>32</height>
</image> 
	<item>
		<title>How to Turn Customer Interviews Into Useful Case Studies</title>
		<link>https://www.dfypodcast.com/customer-interviews-into-case-studies/</link>
		
		<dc:creator><![CDATA[Robert Plank]]></dc:creator>
		<pubDate>Sun, 01 Nov 2026 17:00:00 +0000</pubDate>
				<category><![CDATA[Business Podcasting]]></category>
		<category><![CDATA[Case Studies]]></category>
		<category><![CDATA[Customer Interviews]]></category>
		<category><![CDATA[Podcast Marketing]]></category>
		<category><![CDATA[Testimonials]]></category>
		<guid isPermaLink="false">https://www.dfypodcast.com/?p=1764</guid>

					<description><![CDATA[<p>Get beyond generic praise by recording the customer's situation, the work, and what changed, then turn checked excerpts into a useful case study.</p>
<p>The post <a href="https://www.dfypodcast.com/customer-interviews-into-case-studies/">How to Turn Customer Interviews Into Useful Case Studies</a> first appeared on <a href="https://www.dfypodcast.com">DFY Podcast</a>.</p>]]></description>
										<content:encoded><![CDATA[<p>Imagine a customer leaves you a five-star review that says, "Great service. Highly recommended." You're glad they're happy. You'd certainly rather have five stars than one. But the next customer still doesn't know what you actually helped with.</p>
<p>A conversation can get you past that generic compliment. Ask what was happening before you worked together, what you did, and what changed. Your customer knows their experience. They shouldn't have to become a marketing writer to explain it.</p>
<p>That's one useful job for a podcast interview. You can give a customer room to discuss their business and successes, then find the specific statements that belong in an accurate case study. You may record 30 minutes and keep two sound bites. Those two statements can tell a prospective customer more than a page of praise.</p>
<h2>Invite the Customer to Tell Their Experience</h2>
<p>Choose someone who has enough experience with your work to discuss it and is comfortable being recorded. Explain the interview's purpose, where the episode will appear, and any case study or promotional use you have in mind. A customer can be happy with your service and still prefer to keep their business problems private.</p>
<p>Make the conversation about what they were trying to accomplish. They should have something useful to say beyond endorsing you. You might learn that the problem they cared about was different from the one you put on your sales page.</p>
<p>You also need to hear imperfect answers. Maybe the work helped with one recurring task but didn't solve a separate promotion problem. Maybe the process took longer than expected. Those details make the story understandable. Don't lead the customer toward a cleaner result than they experienced.</p>
<section aria-labelledby="dfy15-map-title" class="dfy-article-map" style=";background:#102c48;color:#fff;padding:24px;border-radius:12px;margin:32px 0;clear:both;">
<h3 id="dfy15-map-title" style=";color:#fff;font-size:24px;line-height:1.25;margin:0 0 18px;font-weight:700;">From Customer Conversation to Useful Case Study</h3>
<ol class="dfy-map-steps" style=";display:flex;flex-wrap:wrap;gap:12px;list-style:none;padding:0;margin:0;">
<li style=";display:block;box-sizing:border-box;flex:1 1 170px;min-width:0;margin:0;padding:16px;background:#fff;color:#102c48;border-left:5px solid #ee8432;border-radius:6px;font-size:16px;line-height:1.5;"><strong style=";display:block;width:auto;color:#102c48;margin-bottom:8px;font-size:18px;line-height:1.3;">1. Ask for the situation</strong><span style=";display:block;">Find the original problem and why the customer wanted to act.</span></li>
<li style=";display:block;box-sizing:border-box;flex:1 1 170px;min-width:0;margin:0;padding:16px;background:#fff;color:#102c48;border-left:5px solid #ee8432;border-radius:6px;font-size:16px;line-height:1.5;"><strong style=";display:block;width:auto;color:#102c48;margin-bottom:8px;font-size:18px;line-height:1.3;">2. Trace the work</strong><span style=";display:block;">Identify the decisions, help, and adjustments that mattered.</span></li>
<li style=";display:block;box-sizing:border-box;flex:1 1 170px;min-width:0;margin:0;padding:16px;background:#fff;color:#102c48;border-left:5px solid #ee8432;border-radius:6px;font-size:16px;line-height:1.5;"><strong style=";display:block;width:auto;color:#102c48;margin-bottom:8px;font-size:18px;line-height:1.3;">3. Check the change</strong><span style=";display:block;">Confirm the outcome and retain important limits.</span></li>
<li style=";display:block;box-sizing:border-box;flex:1 1 170px;min-width:0;margin:0;padding:16px;background:#fff;color:#102c48;border-left:5px solid #ee8432;border-radius:6px;font-size:16px;line-height:1.5;"><strong style=";display:block;width:auto;color:#102c48;margin-bottom:8px;font-size:18px;line-height:1.3;">4. Approve the story</strong><span style=";display:block;">Verify the excerpts and agree on the finished publication use.</span></li>
</ol>
</section>
<h2>Ask for Events Before Asking for Praise</h2>
<p>Start with "What was happening before we worked together?" Then follow the answer. What were they trying to do? What kept getting in the way? What had they already tried?</p>
<p>For example, imagine a podcast production customer. You might expect them to talk about sound quality, but they explain that the recordings were fine. The trouble was finding time to edit them. If you begin with "How much better does your podcast sound now?" you'll miss the problem they actually hired you to solve.</p>
<p>That is a hypothetical customer, not a claim about a client. The point is to leave room for an answer you didn't plan.</p>
<p>Once you understand the situation, ask how they made the decision. What concerned them? What did they compare? Then ask what happened during the work. "What happened first?" and "Was anything harder than you expected?" will usually get you further than "How great was our service?"</p>
<div aria-label="Questions that improve a customer case study" class="dfy-table-scroll" role="region" style=";overflow-x:auto;-webkit-overflow-scrolling:touch;margin:28px 0;max-width:100%;" tabindex="0">
<table style=";border-collapse:collapse;width:100%;min-width:520px;font-size:16px;line-height:1.5;">
<caption style=";text-align:left;font-weight:700;color:#102c48;padding:0 0 12px;caption-side:top;">Replace a request for praise with a request for detail</caption>
<thead>
<tr>
<th scope="col" style=";padding:12px;text-align:left;vertical-align:top;border:1px solid #c8d6df;background:#edf5f7;color:#102c48;font-weight:700;">Weak question</th>
<th scope="col" style=";padding:12px;text-align:left;vertical-align:top;border:1px solid #c8d6df;background:#edf5f7;color:#102c48;font-weight:700;">More useful question</th>
<th scope="col" style=";padding:12px;text-align:left;vertical-align:top;border:1px solid #c8d6df;background:#edf5f7;color:#102c48;font-weight:700;">What it helps you understand</th>
</tr>
</thead>
<tbody>
<tr>
<th scope="row" style=";padding:12px;text-align:left;vertical-align:top;border:1px solid #c8d6df;background:#edf5f7;color:#102c48;font-weight:700;">Were you frustrated?</th>
<td style=";padding:12px;text-align:left;vertical-align:top;border:1px solid #c8d6df;">What kept getting pushed back before we started?</td>
<td style=";padding:12px;text-align:left;vertical-align:top;border:1px solid #c8d6df;">The problem in the customer's own terms.</td>
</tr>
<tr>
<th scope="row" style=";padding:12px;text-align:left;vertical-align:top;border:1px solid #c8d6df;background:#edf5f7;color:#102c48;font-weight:700;">Why did you choose the best option?</th>
<td style=";padding:12px;text-align:left;vertical-align:top;border:1px solid #c8d6df;">What did you consider, and what worried you?</td>
<td style=";padding:12px;text-align:left;vertical-align:top;border:1px solid #c8d6df;">The actual decision, without assuming you were the obvious choice.</td>
</tr>
<tr>
<th scope="row" style=";padding:12px;text-align:left;vertical-align:top;border:1px solid #c8d6df;background:#edf5f7;color:#102c48;font-weight:700;">Was the process easy?</th>
<td style=";padding:12px;text-align:left;vertical-align:top;border:1px solid #c8d6df;">What happened first, and where did we need to adjust?</td>
<td style=";padding:12px;text-align:left;vertical-align:top;border:1px solid #c8d6df;">The work and any friction along the way.</td>
</tr>
<tr>
<th scope="row" style=";padding:12px;text-align:left;vertical-align:top;border:1px solid #c8d6df;background:#edf5f7;color:#102c48;font-weight:700;">How much did we improve things?</th>
<td style=";padding:12px;text-align:left;vertical-align:top;border:1px solid #c8d6df;">What can you do now, and how are you comparing it with before?</td>
<td style=";padding:12px;text-align:left;vertical-align:top;border:1px solid #c8d6df;">The outcome and the basis for a result claim.</td>
</tr>
</tbody>
</table>
</div>
<p>You don't need to march through a questionnaire. If the customer describes a moment when something started working, stay there. "Tell me more about that" is a perfectly useful follow-up.</p>
<h2>Find the Statements That Explain What Changed</h2>
<p>After recording, mark the passages that describe the original problem, the work, and the result. A transcript helps you locate them. Return to the audio or video before treating an automated transcript as an exact quotation.</p>
<p>Sometimes the two most useful sentences are 15 minutes apart. One explains the frustration and another explains the change. You can put those excerpts near each other, provided you preserve the meaning and don't manufacture a sentence the person never spoke.</p>
<p>Here's what that level of detail looks like in my own production experience:</p>
<p>Before I had a team, I'd let ten or twelve interviews pile up, then spend an afternoon working through them in batches. Following my production checklist kept me organized, but pulled me away from work that brought in revenue.</p>
<p>Now I export the interview from Riverside and drop it into our shared Google folder. My team checks daily and processes each recording without a reminder, although I still haven't let go of the export step.</p>
<p>Those details explain the old routine, the handoff, and the part I still do. "Having a team is great" would leave all of that out. This is my account of my own workflow, not a customer's endorsement, but it's the kind of specific experience I listen for in an interview.</p>
<p>For a customer, ask how they know the situation improved. If they say they save time, find out what they're comparing and whether they measured it. Don't turn an unmeasured feeling into a claim that you saved ten hours a week.</p>
<blockquote class="dfy-pullquote" style=";border-left:5px solid #ee8432;background:#f0f7f8;padding:18px 24px;margin:28px 0;font-size:21px;line-height:1.45;color:#102c48;">
<p>Specific doesn't always mean numerical. It means you can understand what actually changed.</p>
</blockquote>
<p>A customer who no longer spends weekends editing can describe that change without assigning it an unsupported dollar value. If the result is mixed, retain the distinction. Publishing consistently and finding an audience are different jobs.</p>
<h2>Build the Written Story Around the Customer's Problem</h2>
<p>Give the reader enough background to understand why the customer wanted help. Then explain the work and the change it produced. A company history and a list of every service usually get in the way.</p>
<p>Here's a compact hypothetical outline for the podcast production example:</p>
<ul>
<li><strong>Situation:</strong> The customer could record interviews but kept putting off editing, leaving finished conversations unpublished.</li>
<li><strong>Work:</strong> The customer and production team agreed on a shared folder, editing instructions, approval steps, and a publishing schedule.</li>
<li><strong>Change:</strong> Describe what the customer actually reports after using that process. Ask for the publication record or other support before adding a numerical result.</li>
</ul>
<p>The outline deliberately leaves the result open. In a real case study, the interview supplies it. You can't fill that space with what you hoped the service would accomplish.</p>
<p>Use the customer's exact words for a direct quotation. If the wording needs more explanation, use a short exact excerpt and paraphrase the surrounding context in your own prose. A paraphrase should not appear inside quotation marks.</p>
<p>Keep your role proportionate to what happened. The customer may have hired you while also changing their offer, staff, or promotion. Explain the work you contributed without taking credit for every improvement in their business.</p>
<figure class="dfy-video">
<div class="dfy-video-frame" style=";max-width:100%;"><iframe allow="accelerometer; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" allowfullscreen="" loading="lazy" referrerpolicy="strict-origin-when-cross-origin" src="https://www.youtube-nocookie.com/embed/4cUZa1FZv_U" style="aspect-ratio:16/9;width:100%;height:auto;border:0;width:100%;height:auto;aspect-ratio:16/9;display:block;border:0;" title="Robert Plank explains the hidden marketing value of podcast customer interviews"></iframe></div><figcaption>In <a href="https://www.youtube.com/watch?v=4cUZa1FZv_U">The Hidden Marketing Gold in Podcasting</a>, I discuss interviewing customers about their successes and the work that helped them.</figcaption></figure>
<h2>Review the Finished Use With the Customer</h2>
<p>Listen to the sentences before and after every excerpt. A positive comment about one part of a project shouldn't become an endorsement of the entire service. Keep any condition that changes the claim.</p>
<p>Confirm names, timelines, amounts, and reported results with the customer. Show them the proposed story and explain where you intend to use it. An interview appearing on a podcast and a quotation appearing in an advertisement are different uses to discuss.</p>
<p>Store the approved version, approval record, original recording, and source timestamps together. Give the folder a descriptive name based on the customer and problem. When a prospect raises that issue six months later, you'll be able to find the relevant story instead of searching every recording.</p>
<p>Choose formats based on the material. A clear spoken explanation can become a short clip. A complicated sequence may work better as a written page. A brief, precise statement may be useful on its own. You don't need ten assets if one approved story answers the prospective customer's question.</p>
<p>For video excerpts, use the <a href="https://www.dfypodcast.com/podcast-clips-for-social-media/">same clip-selection checks</a> you would use elsewhere: a complete thought, enough context, readable captions, and an edit that preserves the speaker's meaning.</p>
<h2>Choose One Customer and Start the Conversation</h2>
<p>Pick a customer whose experience you want to understand better. Ask whether they'd be comfortable discussing the original problem, the work, and what changed. Explain the publication plan before scheduling the interview.</p>
<p>Your first useful output is an approved customer story, not a predetermined list of compliments. If the conversation shows that the result was more complicated than you expected, that is useful information to learn before publishing.</p>
<p>If you can have those conversations but need help turning them into finished episodes and clear excerpts, <a href="https://www.dfypodcast.com/production/" style=";font-weight:700;">see how DFY Podcast handles production</a>. We can help with the recording's editing, publishing, and promotional materials while you concentrate on asking the questions only you know to ask.</p><p>The post <a href="https://www.dfypodcast.com/customer-interviews-into-case-studies/">How to Turn Customer Interviews Into Useful Case Studies</a> first appeared on <a href="https://www.dfypodcast.com">DFY Podcast</a>.</p>]]></content:encoded>
					
		
		
			</item>
	</channel>
</rss>
