Videos into Companion Posts

Every podcast episode I publish and most of the live streams I do end up with a companion blog post on this site. If you have poked around here, you have seen them: a short writeup that sits alongside the video, gives you the gist, and tells you whether the full thing is worth your time. People sometimes ask why I bother, since the video already exists. Here is why, and here is how I actually do it.

The why is the easy part. A video is a wall. You cannot skim it, you cannot search it, and you cannot tell from the thumbnail whether the forty minutes inside are worth your afternoon. A companion post fixes all of that. It gives the episode a front door. Someone lands on it from a search, reads three paragraphs, and decides in thirty seconds whether to hit play. It also does things the video simply cannot. It is searchable, so the episode surfaces when someone looks up the topic months later. It is linkable, so I can point to a specific idea instead of a timestamp nobody will scrub to. And it gives the episode a life beyond the platform it was published on, which matters, because platforms come and go and my own site does not.

There is also a selfish reason, which is that writing the post forces me to actually understand what we talked about. It is very easy to host a conversation, nod along, and walk away with only a fuzzy sense of what was said. Sitting down to write a few clear paragraphs about it makes me pin down the actual point. More than once, writing the companion post is where I realized what the episode was really about, which was not always what I thought going in.

Now the how, because this is the part that used to take me way too long before I got a system for it. The mistake I made early was treating the companion post as a transcript, trying to capture everything that was said in order. That is miserable to write and worse to read. A companion post is not a transcript. It is a distillation. Nobody wants the whole conversation in text form, they want the shape of it and the one or two things that made it worth having.

So the first thing I do is find the spine. Every good episode has one real thread running through it, even when the conversation wandered. For the bootc episode with James Harmison, the spine was “what does this actually look like when someone runs it every day, not just tries it once.” I write that down first, in one sentence, and everything in the post hangs off it. If a detail from the episode does not support the spine, it does not go in the post, no matter how interesting it was in the moment.

Then I pull the two or three moments that mattered. Not every topic we touched, just the parts a reader would remember. The surprising claim, the concrete example, the thing that made me go huh in real time. This is where the timestamps I jotted down during recording pay off, because I am not relistening to the whole thing hunting for the good parts. I noted them while they happened, so I can go straight to them. That habit, writing down the moment when it lands, is the single biggest time saver in the whole workflow.

I write the post the same way I write anything else here. A hook that earns the next paragraph, usually a specific detail from the episode rather than a topic sentence. A body that walks through the spine and the key moments in prose, grounded in the actual things that were said. And a close that steps up a level to why the whole thing matters, followed by a plain link to go watch it. I keep the posts short on purpose, usually a few hundred words, because their job is to get you to the video, not to replace it.

The thing I have learned is that the companion post is worth far more than the effort it takes, especially once you have a system that makes it fast. The video is the thing I made. The post is the thing that helps people find it, understand it, and decide to watch it. Skipping the post is leaving most of the value of the work sitting on the table.