TRANSKRIP 🔗
WEBVTT
00:00:00.080 --> 00:00:06.639
Okay, so for this quick cast, I wanted to talk about a blog that was shared internally in the company chat.
00:00:06.639 --> 00:00:12.720
It was written by Tom Raftery, who is a Buzzsprout podcaster and a listener of Buzzcast.
00:00:12.720 --> 00:00:14.240
Yeah, super fan.
00:00:14.240 --> 00:00:17.440
He's a host of Resilient Supply Chain and Climate Confident.
00:00:17.440 --> 00:00:22.960
And he wrote about his podcasting workflow after 800 episodes.
00:00:23.120 --> 00:00:24.239
Yeah, 800 episodes.
00:00:24.239 --> 00:00:25.120
What an accomplishment.
00:00:25.120 --> 00:00:26.160
That's that's massive.
00:00:26.480 --> 00:00:33.039
So, I mean, his podcast is about like supply chain, and you know, you you got to make sure that everything's like running really smoothly.
00:00:33.039 --> 00:00:43.920
And it's so interesting reading through his process of podcasting and also his like philosophy of podcasting, like when it's working through that lens of like supply chain.
00:00:43.920 --> 00:00:46.560
And he kind of like taught ties it all in.
00:00:46.560 --> 00:00:50.399
So he he wrote, I think of the workflow as a media supply chain.
00:00:50.399 --> 00:01:00.719
They're inputs, quality gates, dependencies, production steps, packaging, hosting, publishing, feedback loops, and a constant search for the next bottleneck.
00:01:00.880 --> 00:01:01.359
I love it.
00:01:01.359 --> 00:01:02.320
That's great.
00:01:02.320 --> 00:01:03.039
Yeah.
00:01:03.359 --> 00:01:07.599
So some of my favorite takeaways from his experience, I read through this, I'm gonna link to it in the show notes.
00:01:07.599 --> 00:01:08.879
I highly recommend that you read through it.
00:01:08.879 --> 00:01:10.159
It's it's so well written.
00:01:10.159 --> 00:01:13.280
Um, Tom's got a great voice in his writing.
00:01:13.280 --> 00:01:20.159
Um, but one of the things I really enjoyed, uh, he said, consistency happens when you remove as many pain points as possible.
00:01:20.159 --> 00:01:25.920
And I think a lot of us kind of assume that we're going to be consistent with our podcasting.
00:01:25.920 --> 00:01:30.719
We're gonna stay consistent just through like pure grit.
00:01:30.719 --> 00:01:34.560
And he's saying, like, no, actually, that's a good way to burn out.
00:01:34.560 --> 00:01:42.640
And the best way to continue podcasting and make sure that you are continuing is by making it as easy as humanly possible on yourself.
00:01:42.959 --> 00:01:44.159
Isn't almost everything like this?
00:01:44.159 --> 00:01:51.040
Like you can white knuckle your way through a few workouts, you can force yourself to a diet for a short period.
00:01:51.040 --> 00:01:56.959
You anything you're like, I really want to do this, I'm going to do it, you can do it for a couple days.
00:01:56.959 --> 00:02:08.560
And it's when anything goes slightly off plan that you're like, oh gosh, my two workouts every day plan actually is going to be kind of tough when we're on vacation.
00:02:08.560 --> 00:02:12.080
I have no clue how to solve this, and it all unravels.
00:02:12.080 --> 00:02:17.919
And like podcasting fits into this group, like you can force yourself to do a few episodes, no matter what.
00:02:17.919 --> 00:02:23.120
You know, you're no matter how bad the supply chain, the media supply chain is.
00:02:23.120 --> 00:02:38.400
But at some point, you need to have like smoothed it out so that it kind of is happening naturally, like the equivalent of laying out the gym clothes the night before, so that you can just wake up and go rather than having to like figure it out on the fly every single day.
00:02:38.719 --> 00:02:47.599
One of the things that he mentioned is a bottleneck that I've personally been encountering in my podcasting experience too, which is probably why it resonated so much with me.
00:02:47.599 --> 00:02:49.280
And I included it in this list.
00:02:49.280 --> 00:02:55.360
He said that your pre-record needs to be like completely bulletproof, foolproof.
00:02:55.360 --> 00:03:00.719
And if you do that, that will ensure that the rest of the podcast runs so much more smoothly.
00:03:00.719 --> 00:03:08.479
And so he says, like, you need to make sure that you're vetting your guests, you know, and making sure that they're a good guest for your podcast.
00:03:08.479 --> 00:03:10.800
You need to always be prepared.
00:03:10.800 --> 00:03:14.639
So make sure that you have like backups and contingencies.
00:03:14.639 --> 00:03:19.680
Um, he says to include like recording details and the calendar invite, which I love.
00:03:19.680 --> 00:03:23.680
This is a big one, coaching guests on audio and video.
00:03:23.680 --> 00:03:35.039
The thing is, is I've encountered, especially with uh our podcast, Happy to Help, the people that we have on as guests, they're not podcasters, like the vast majority of the time.
00:03:35.039 --> 00:03:35.680
They're not.
00:03:35.680 --> 00:03:37.120
They don't have experience with that.
00:03:37.120 --> 00:03:41.280
They might be doing like some Zoom calls and consultancy kind of things.
00:03:41.280 --> 00:03:48.479
And I think that Tom uh often encounters the same thing where the people he's interviewing for his podcast, like they're not podcasters.
00:03:48.479 --> 00:03:52.319
And so he has to kind of like coach them and get them comfortable on the camera.
00:03:52.319 --> 00:03:57.840
And so one of the things that really helps with that is doing like a pre-recording warmup, which I love doing this.
00:03:57.840 --> 00:04:11.759
It's it's great to um just kind of like chat with people about something that they're passionate with and it makes them a little bit more comfortable in front of the camera and they feel like, okay, I'm at ease, like I can do this interview now because this is a friendly encounter.
00:04:11.759 --> 00:04:28.079
But I've I've totally had things where I wish that I did the painful thing and had like a tough conversation with a
Load full transcript
guest, you know, because there's been so many times where I kind of like white knuckle through a recording, even though I know it doesn't sound quite right.
00:04:28.079 --> 00:04:31.040
And I'm like, I could, I know I can fix it in post.
00:04:31.040 --> 00:04:36.240
Like, I know I can, but really that makes so much extra work for me in the long run.
00:04:36.240 --> 00:04:39.680
And then I start like dreading editing this episode, right?
00:04:39.920 --> 00:04:40.879
It's it's a great point.
00:04:40.879 --> 00:04:47.519
The the stuff that he's listing here, I think, is the stuff that when it goes wrong, it's not insurmountable stuff.
00:04:47.519 --> 00:04:58.959
Like if you have a guest on your show and they're uncomfortable on camera, like you can grind through that, but it's removing a lot of the joy and it's removing a lot of the polish that you work so hard for in your episodes.
00:04:58.959 --> 00:05:11.680
If you have a guest who's like talk talking off topic or they're whatever, like you see a lighting change that they could make that would be an easy adjustment, but now you're into the recording and you don't want to mess up with stuff right in the middle of the recording.
00:05:11.680 --> 00:05:18.240
These are little things that steal the joy and the craft, or maybe what makes your show unique and different.
00:05:18.240 --> 00:05:28.319
And uh getting it right up front, I think, is a great protection measure to protect your joy, to protect your time, and protect sort of maybe the brand or the style of your podcast.
00:05:28.319 --> 00:05:33.199
And so I I I love this as a checklist, and I think everyone could have their own version of that for sure.
00:05:33.519 --> 00:05:38.079
I like these little things like recording details are in the calendar invite.
00:05:38.079 --> 00:05:47.759
And I think I'm always the stickler for these in my own life, where I'm like, okay, we're gonna use the same Google Meet Room every time, no matter what.
00:05:47.759 --> 00:05:54.319
And over time, like you just it gets a little bit easier because you don't sit there and go, hey guys, you got the got a room, got a link for us?
00:05:54.319 --> 00:05:55.839
It's always the same room.
00:05:55.839 --> 00:05:59.360
And so everybody knows where they're how to get there.
00:05:59.360 --> 00:06:01.920
The room is always in the calendar invite.
00:06:01.920 --> 00:06:06.000
The calendar is always the same time unless we want to change it.
00:06:06.000 --> 00:06:12.319
And each of those, like it's already decided, just takes one of the things off the table.
00:06:12.319 --> 00:06:20.160
So that when there inevitably are I'm running 10 minutes late, it's not the third inconvenience, it's just the one tiny one that doesn't really matter.
00:06:20.399 --> 00:06:21.600
Yeah, that's a huge one.
00:06:21.600 --> 00:06:25.920
And especially because you want to keep the energy up during the recording.
00:06:25.920 --> 00:06:32.079
And so if your pre-recording is painful, it's gonna be like, oh gosh, okay, it took us forever to get in here.
00:06:32.079 --> 00:06:37.120
We had to do like troubleshooting, and you know, I had to ask for this thing like a million times and they didn't respond.
00:06:37.120 --> 00:06:39.120
And now I'm not excited about the recording.
00:06:39.120 --> 00:06:45.680
And so, yeah, there's there's so many advantages to making sure that everything runs really smoothly.
00:06:45.680 --> 00:06:46.240
All right.
00:06:46.240 --> 00:06:49.120
So I I have a third one here that I love.
00:06:49.120 --> 00:06:54.480
And this is, I mean, I don't want to say this is like my favorite part, but it's pretty close to my favorite part.
00:06:54.480 --> 00:06:57.279
So and you'll see why.
00:06:57.279 --> 00:07:06.720
Tom talked about how instead of being like loyal to like your tool set, ask yourself like what part of the workflow keeps breaking and improve your tool stack from there.
00:07:06.720 --> 00:07:14.240
And in this point, he talks about how important it is that a company has support.
00:07:14.240 --> 00:07:18.959
And so he talks about how he uses BuzzSprout to host both of the podcasts.
00:07:18.959 --> 00:07:26.560
And he said that support is easy to undervalue until something breaks, which is so true.
00:07:26.879 --> 00:07:28.720
All right, can I tell a story on this point?
00:07:28.720 --> 00:07:31.600
I think I'm a huge Airbnb advocate.
00:07:31.600 --> 00:07:33.279
And it's always so smooth.
00:07:33.279 --> 00:07:34.720
You can find a great place.
00:07:34.720 --> 00:07:38.720
I come from a big family, so if we all get together, it we need a big house.
00:07:38.720 --> 00:07:41.439
And Airbnb is the best way to do it.
00:07:41.439 --> 00:07:48.639
And we've stayed in tons of Airbnbs over the years to the point that like we don't look for hotels, we look for Airbnbs.
00:07:48.639 --> 00:07:54.720
And so when I went to this wedding a couple weeks ago, we got a really bad Airbnb.
00:07:54.720 --> 00:08:00.639
And it wasn't Airbnb's fault, but there were a bunch of bugs in it and it was bad.
00:08:00.639 --> 00:08:05.839
So we just message him and go, hey, we you know, we can't stay here, it violates the policies, we got a hotel.
00:08:05.839 --> 00:08:09.839
And then the support was so bad for a few days.
00:08:09.839 --> 00:08:15.600
And I was talking to my wife, and I was like, I'm not upset that we lost the money from this Airbnb.
00:08:15.600 --> 00:08:22.079
If that's the result, what I'll be really upset about is that we'll lose Airbnb because there's no way I can do this again.
00:08:22.079 --> 00:08:30.800
Like I can't commit to, you know, if we went on a big vacation to Italy or something, like you can't get an Airbnb under that scenario if they don't solve this.
00:08:30.800 --> 00:08:35.120
And I'm like lamenting this and going, I don't think they're gonna pull it out.
00:08:35.120 --> 00:08:39.600
And then like the next day, my wife's like, let me step in, I'll I'll
email them.
00:08:39.600 --> 00:08:51.759
And she sends them one message and she got the right person because they go, Oh, I'm sorry, our mistake, we refunded it, everything's taken care of, tickets closed, and it had been like five days.
00:08:51.759 --> 00:08:53.679
I was like, Oh, wow.
00:08:53.679 --> 00:08:55.200
It's good to get that money back.
00:08:55.200 --> 00:09:00.399
But the big part was as soon as you lose your trust in a product, it's like gone.
00:09:00.399 --> 00:09:11.919
It and it stinks for everybody, stinks for the company, but it also stinks as the user because then you don't feel like even if it works 99% of the time, I'm just kind of waiting for the other shoe to drop.
00:09:11.919 --> 00:09:12.639
Does that make sense?
00:09:12.879 --> 00:09:22.639
Yeah, there's a lot of products that I have stopped using because it's impossible to find their like support email.
00:09:22.639 --> 00:09:28.799
You'll you'll go through all the help articles and they have like a ton of like unhelpful help articles that maybe are like outdated.
00:09:28.799 --> 00:09:31.039
It was for like previous versions or something like that.
00:09:31.039 --> 00:09:34.879
And then you're like trying to find, like, okay, no, how do I just like talk to somebody?
00:09:34.879 --> 00:09:42.000
And then the chat just like keeps sending you to like these help articles that weren't helpful in the first place, and like you just never reach a person.
00:09:42.000 --> 00:09:47.840
And those kind of things can definitely sour my relationship with a company big time.
00:09:48.000 --> 00:09:57.759
Yeah, there's something too you you just want to know at the end of the day, even if the AI chat bot was really smart and the help article was well written and everything helped.
00:09:57.759 --> 00:10:04.480
Like, I kind of want to just know at the end of the day, at the end of the path, I can go to a person and say, Do you understand?
00:10:04.480 --> 00:10:09.279
Like this stinks, even if you're not gonna give me the money back or you can't solve this bug or whatever it is.
00:10:09.279 --> 00:10:12.320
Like, you kind of still want that human connection in there.
00:10:12.559 --> 00:10:16.000
And I think that Tom, like in his writing, he really reflects that.
00:10:16.000 --> 00:10:20.960
He said that when you publish every week, support is part of the resilience architecture.
00:10:20.960 --> 00:10:30.159
And if an upload fails, a feed behaves strangely, or metadata issue appears just before publication, you do not want to shout into a ticketing void.
00:10:30.159 --> 00:10:34.000
You want people who understand podcasting and respond with clarity.
00:10:34.000 --> 00:10:39.440
And he says BuzzSprout's own customer support podcast, happy to help, is a useful signal here.
00:10:39.440 --> 00:10:45.440
It is hosted by Priscilla Brooke, Buzzsprout's head of podcaster success, and focuses on making customer support better.
00:10:45.440 --> 00:10:52.159
And a company willing
to talk publicly about support usually understands that support is part of the product.
00:10:52.159 --> 00:11:03.840
And I love this so much because I really truly feel in my heart that our support, the support that Buzzbro has is a feature.
00:11:03.840 --> 00:11:05.279
It is absolutely part of the product.
00:11:05.279 --> 00:11:09.039
It is like one of like the most shiny things that we have.
00:11:09.039 --> 00:11:15.600
I just love that one of our customers feels that, like that, they understand that and they see it.
00:11:15.919 --> 00:11:18.320
Yeah, we could we could do a whole episode on support.
00:11:18.320 --> 00:11:20.799
I think we have done partial episodes at least.
00:11:20.799 --> 00:11:34.720
Priscilla's been on the podcast a few times, but it's it's it's such a difficult balance to strike between you want every customer to experience your support at some level, especially when it's really good and you really care and you love connecting with people and interacting with them.
00:11:34.720 --> 00:11:40.480
Again, but you and then again, you don't necessarily want them to because that means something probably they're struggling somewhere.
00:11:40.480 --> 00:11:41.279
Something went wrong.
00:11:41.279 --> 00:11:45.200
The majority of our support tickets are not necessarily because something is broken.
00:11:45.200 --> 00:11:50.240
It's usually the result of a misunderstanding or um I don't know how to do something.
00:11:50.240 --> 00:11:56.080
And I love that when people get to interact with us, you know, just because they want clarity around something or they want to do something better.
00:11:56.080 --> 00:11:58.159
I hate it when it's the result of something breaking.
00:11:58.159 --> 00:12:05.600
But either way, uh, I love it when people get to experience our support because our team, we only hire people who really do care about helping people succeed.
00:12:05.600 --> 00:12:08.559
That's why we renamed the team from support to success.
00:12:08.559 --> 00:12:14.399
Um, again, I don't want to go on and on about it, but I I do love the fact that Tom wrote about that.
00:12:14.399 --> 00:12:29.120
And it is a good part or an important part of being able to run a successful and consistent production is making sure you have a team around you and not necessarily meaning like a co-host and a producer, but also like the software that you're using, the team behind those products being a part of your team.
00:12:29.600 --> 00:12:37.360
One thing I would add to this, Jordan, that I really like from this episode was he treats the finished episode as a metadata factory.
00:12:37.360 --> 00:12:43.440
And the idea is at the end of the episode, you're trying to make sure that you're not losing value after you record.
00:12:43.440 --> 00:12:47.840
You've got titles, guest profiles, transcripts, thumbnails, all these extra pieces.
00:12:47.840 --> 00:12:56.159
You need to make sure that your flow of your podcast is easy enough that you have energy at the end to still optimize the episode somewhat.
00:12:56.159 --> 00:12:56.399
Yeah.
00:12:56.399 --> 00:13:08.159
And make sure you're writing a title and you're not just burned out, so you don't you just skip all these extra steps that he's basically optimized it so there's still energy at the moment of publication.
00:13:08.159 --> 00:13:12.799
And so there's this one quote if I can send us off with one quote from Tom.
00:13:12.799 --> 00:13:15.600
Heroics are a poor operating model.
00:13:15.600 --> 00:13:23.039
If a publishing system depends on repeated last-minute rescue missions, it's not a system, it's theater with a deadline.
00:13:23.039 --> 00:13:30.960
Surprise for me is that podcasting has taught me as much about supply chains as supply chains have taught me about podcasting.
00:13:30.960 --> 00:13:40.720
Flow matters, bottlenecks matter, quality control matters, consistency matters, support matters, resilience is built before the disruption arrives.
00:13:41.039 --> 00:13:41.600
I love it.
00:13:41.600 --> 00:13:46.240
I I told you, like it, the writing in this whole blog is just amazing.
00:13:46.240 --> 00:13:47.759
It's it's a really fun read.
00:13:47.759 --> 00:13:57.360
I think that there's a lot of wisdom in here from Tom's experience, you know, in supply chain, and then also as a podcaster for 800 episodes, which is incredibly impressive.
00:13:57.360 --> 00:13:59.200
And so I highly recommend that you read it.
00:13:59.200 --> 00:14:02.240
I will leave a link to this in the show notes.
00:14:02.240 --> 00:14:05.919
And until next time, thanks for listening and keep podcasting.