Improving and delegating more of my podcasting process
Posted: - Modified: | delegation, podcastingI'm interested in videocasting/podcasting as a richer and more interactive way to get stuff out of people's heads and into other people's heads. I've come to terms with the fact that most people don't write anywhere near as much as I do, but that they know all sorts of things that they might not have realized yet. Talking to people seems to be a good way to help them share that, because many people find it easier to answer questions than to share on their own. Likewise, podcasts recorded live make it easier for me to bring in other people's questions (bonus: I learn more in the process!). So, podcasting, even though actually talking to people is hard. Maybe if I do enough of it, I'll get desensitized to the anxiety and I'll get better.
Along those lines, I've been doing a weekly show for Google Helpouts providers. It's a community of maybe a thousand people, which is a tiny niche in the Internet. I used to have co-hosts, but they're on hiatus for various personal/business reasons. I did my first solo show the other week, and my second was last week. So far, I have managed to survive. I like it because Google Helpouts is a new platform and everyone's still figuring things out. I'm fine with talking tech and maybe a little online marketing/customer service, but other people know so much more than I do about business and education, so interviews are a natural fit. I'm getting settled into a decent workflow involving Hangouts on Air, the Q&A module, MP3s, and even drawing sketchnotes while the conversation progresses.
Sketchnoting is oddly calming. I had done it from the very first show, when I had a co-host handle all the niceties of reaching out to people, introducing them on air, and asking questions. For a kick, I tried seeing if I could do it even when hosting solo, and it worked out fine. You'd think adding one more thing to do during the show would drive me crazy from multi-tasking, but actually, drawing keeps me not-stressed-out enough to listen well, ask follow-up questions (since I have my notes handy!), and help people follow along with the conversation or catch up afterwards. Besides, it's a good excuse to swap out my webcam image for the screenshare, so I don't have to be “on” all the time.
So the interview itself is fine, and it will get better as I pick up more experience.
Then there's all the rest of the processes around that. I typically stay up about two hours after the end of the show. I chat with participants off-air for 30-45 minutes (this is usually the most fun segment!) and then handle all the post-work, since I like it when the resources are posted right away. That way, I don't have to go back and work on it again. Although it's certainly possible to just let the video be automatically posted on my YouTube channel and be done with it, I like putting together the video, my visual notes, an MP3 download (for the people who prefer to listen to the podcast while, say, doing chores or walking around), and eventually a transcript. If I'm going to do something, I might as well use it as an opportunity to explore what awesomeness look like. =)
That said, wouldn't it be awesome to be able to document my processes so that I can do them without worrying about missing a step, and so that other people could take care of making things happen? I'd love to worry less about identifying, inviting, and coordinating potential guests, too. Someday.
Since many of the things I do involve my Google account, this probably means building trust carefully. I was thinking about what sequence of activities might make sense in terms of trust.
Come to think of it, I can improve my post-podcast process by parallelizing some of the tasks that take a long time to do. Maybe I'll even figure out how to automate some of those tasks, like perhaps getting the ID3 information from a spreadsheet.
Here's a list that's roughly in order of trust:
- Typing
- If there are visual notes, type in the text of the images and send them to me.
- Create transcripts suitable for copying and pasting into the blog posts.
- Tech
- Make sure the podcast shows up correctly in popular directories.
- Add the text from 1 and 2 above to the blog posts for greater searchability.
- Write the blog posts with the video, audio, images (if any), and additional resources; update the redirection in WordPress.
- Create the announcement in WordPress.
- Update the WordPress redirection information for the event.
- Download the video from YouTube and extract the MP3; add metadata and upload it to archive.org
- Create and share the Google+ event for the upcoming podcast.
- Copy the event to Google Calendar.
- Start and manage the Google Hangout. (Including starting the Q&A module, setting up the YouTube URL, etc).
- Connecting
- Draft or send invitations to possible show guests. Coordinate acceptance and schedule.
- Do research on the scheduled guest. Compile a short report with their bio and possibly interesting questions to ask.
- Research and suggest potential guests, including reasons why.
The biggest risk, I guess, is that someone goes rogue with my Google Account. Goodness knows enough people have had that kind of problem with people breaking into their accounts. Working with assistants I pick myself (since I work with people who have a good reputation) and making an effort to be an excellent client could lower that risk. I've also separated my domain administration account from my regular e-mail account. At some point, I'll just have to trust (and verify).