Media Appearances / WP-Tonic
Kurt von Ahnen had a duffel bag of photography equipment in his garage. He'd started podcasting on a phone in the car, bought lights and other gear, and discovered the lights bothered him while he talked. By our conversation, he was using a simpler arrangement.
I returned to WP-Tonic with Kurt and Jonathan Denwood to talk about podcasting on purpose. Kurt also caught me making years of experience sound obvious. A beginner still needed the decisions I'd skipped over.
Those are related problems. You can buy a lot of equipment, install the tools and still need to decide what useful answer you're there to record. Start with the problem someone can recognize, then let the next purchase or archive project solve a limitation you've actually found.
Kurt points out decisions I skip over that a beginner still needs explained. Jonathan asks about a feed he cannot get removed. Watch our WP-Tonic conversation for both discussions; the show covers the WordPress and podcast work around them.
The Question You Find Obvious May Be a Good Episode
I started as a programmer making websites. WordPress made building them easier, but a working website still needed a way to make money. That led me into membership software, then list building and webinars as I worked on getting people to find what I'd built.
Interviews grew out of another practical problem. I'd meet someone at a networking event, exchange business cards, and need a reason to continue the conversation. Inviting them onto a recorded Skype call gave us that reason. I could ask about their work and their successes, then put the audio on a webpage we could both share.
Kurt heard me describe that progression and pointed out how much experience I was compressing into a casual explanation. He recognized it from his own website work. An experienced professional can make something sound easy while leaving out the decisions a beginner needs help making.
That's the expert's curse, and it's one reason I like the back-and-forth of a conversation. You explain something, the other person asks a follow-up, and you find a simpler way to say it. The useful moment may come from a question you wouldn't have thought to ask yourself. If you only record rehearsed answers, you can miss those moments.
When we discussed AI, I used the example of Jonathan and Kurt talking through WordPress learning-management plugins. Ask a writing tool for a generic list of the best plugins and it has none of their reasoning to work with. Give it a transcript of that discussion, and it can draw from their explanations and organize the useful points.
Record an Answer to a Problem You Solved
When Jonathan asked how someone should get started, I suggested grabbing a phone, sitting in a parked car, and recording three minutes. I'm comfortable with doing something awkwardly the first time. You can practice explaining one idea before you've figured out your entire podcast setup.
Give each minute a job. First, name a problem in your industry that bothers you. Then explain how you solved it for yourself. Finally, describe how you helped someone else with the same problem, when you have an appropriate real example.
I used the frustration of installing a WordPress theme that adds a bunch of plugins you didn't ask for. Now you're dealing with a confusing interface when you wanted a working website. If you've solved that problem, explain what you changed and why you chose that approach. You have a specific question to answer, so you can leave the complete history of WordPress for another recording.
A client example can show how you applied the solution in another situation. Use details you have permission to share, or anonymize the case where needed. If you're illustrating what someone could do, make that clear rather than presenting it as a completed project.
Once you've finished, give the recording a title that names the problem it addresses. Add a relevant next step, such as trying the approach or reading a fuller explanation on your site.
Buy Equipment to Fix a Problem You Can Hear or See
Jonathan wanted to know when someone should move beyond recording on a phone. He cared about sound quality, but he also wanted equipment he could use without making the setup complicated. My answer was to make some recordings first. Once you've outgrown something, you'll have a better idea of what needs replacing.
Maybe your sound is unclear, your lighting makes you difficult to see, or setting up has become such a nuisance that you avoid recording. Those are problems you can identify and work on. Buying an entire studio before you've started gives you more equipment to learn without much experience to guide the purchase.
I understand the appeal. The box arrives, you unpack it, and buying the equipment feels like an accomplishment. That's why I suggested treating upgrades as rewards for completing episodes. Record consistently, learn what bothers you, then improve that part of the setup.
Presentation still matters. If someone has to strain to hear you or can barely see you, fix that. Once they can comfortably follow the conversation, keep recording and improve the setup as you discover what bothers you. You might need a different microphone, or you might just need to move a light.
Check What a Podcast Import Will Publish
I imported my podcast feed into YouTube while video interviews were already on the channel. The import created audio-only versions with still images, leaving duplicates. I removed the imported versions and put the existing videos into a podcast playlist.
Jonathan described a separate WP-Tonic feed he'd spent years trying to remove. He wasn't sure where it had originated. Both problems make the same preparation worth doing: identify which service controls the recording, feed, website and video listing before connecting another one.
Before an archive import, identify what it will create alongside the episodes you already have. Check where each recording, feed and listing is controlled. If you're moving hosts, use the chosen providers' current migration and redirect instructions for that job.
Understand the Audio File, Feed, Website and Video
Jonathan and I also worked through the publishing setup. I wanted a video version available on YouTube and an audio version people could subscribe to through a podcast app. Those destinations didn't have to contain identical kinds of files.
In the WordPress arrangement I described, the episode page contained the written notes and a player, while the audio file could live with the podcast host. The feed carried the episode information used for distribution. The page, audio host, feed, and YouTube channel were related parts of the process, with different places to make a correction.
That was why the duplicate import mattered. Connecting two existing systems could create another version rather than recognize the recording I'd already published. Before changing an archive, identify which service controls the file and which listing you want the audience to find. The historical fix I described is a useful example of checking the result, rather than a current set of menu instructions.
Send the Guest a Link and Something to Share
Once the full episode is available, give someone a useful way into it. Jonathan said his interviews often ran close to an hour or longer, and he hadn't been regularly cutting them into shorter pieces. A short excerpt lets someone hear one complete answer before deciding whether to watch the rest.
It also gives your guest something specific to share. Send them a clip that makes sense to their audience, and they can see what they're inviting someone to watch. I've discovered podcasts through short clips myself. A good explanation gives me a reason to look for the rest.
Keep the handoff manageable. Select one strong moment, watch the surrounding discussion to check its meaning, and choose a cut that preserves the complete thought. Correct the captions, give the guest a usable video file, and include the original episode link so viewers can continue.
I used a transcript to find promising passages, then checked the recording before editing a clip. We discussed several tools, but Kurt had already found a practical reason to compare what his subscriptions actually covered.
Kurt had already encountered subscription overlap. He liked using Opus, but reconsidered renewing when he realized Descript covered work he needed done. As he said, "I don't want to double dip on all the same tools."
Choose What You Want to Find in the Archive
Kurt asked whether material from five or six years earlier was worth revisiting. My answer depended on the material. An explanation of a defunct service might be a poor choice. A clear answer to a continuing problem could still help someone who had never found it.
I described keeping a folder of fourteen hundred transcripts and guest biographies at that point. Going back through them could produce more than new clips. I could prepare clearer descriptions, keyword tags, titles, and a one- or two-sentence synopsis of what an episode actually contained.
Those summaries also helped me look across the show. Which subjects kept appearing? What did the archive tell me about the kind of show I was making? Where might there be a new question or a person worth inviting? The records could inform the show's description or an article plan instead of remaining a pile of files I never opened again.
You can divide that work into manageable passes. Find a useful answer or guest excerpt first. Improve its thin description and links next. Then look across the reviewed summaries for recurring subjects and gaps. Keep the original URL and timestamp with the new notes so another person can check the evidence.
I also liked revisiting a particular interview when I wanted to reconnect with its guest. A fresh, accurate clip gave me something specific to send. That was a reason to return to the recording, rather than trying to manufacture another generic check-in message.
Record One Answer or Finish One Old Episode
Choose a beginner's question and check whether an existing episode answers it. Finish one useful output: a clearer page, a self-contained clip, or a short recording supplying the missing step. Try it as someone who doesn't know your tools.
The DFY Podcast production page explains the help available after you make that recording. My team can handle the edit, notes and supporting material. Use the first episode to decide whether the sound or picture actually needs an equipment upgrade.
About Robert Plank
Robert Plank hosts Marketer of the Day and runs DFY Podcast, helping business owners turn recorded conversations into finished podcast episodes. His background includes programming, membership software, and webinars.
Original Conversation and Resources
Robert joined Jonathan Denwood and Kurt von Ahnen as a returning guest on WP-Tonic for episode 976, "We Discuss The Power of Podcasting In 2025."
