Skip to main content

Podcasting About Mental Health in Tech For Over a Year: What I Learned

·9 mins

Sooooooooooo… I’ve been wrestling with this retrospective for two months now. I wanted it out by the end of January, but, welp, here we are. After 3 4 5 completely different drafts I couldn’t settle on a single, perfect structure, so I rolled back to a pretty basic flow: first my personal reflections, then the practical stuff on how to create a podcast. Enjoy!

and if for some reason you are here without knowing what debug:mind is, please check it out and subscribe on YT 😘


Part 1: Looking Back, How Do I Feel? #

…I think I’m happy with how “debug:mind” turned out.

I did it for two reasons: first, I felt we needed more open conversations about mental health in tech and wanted to play my part in destigmatizing the topic. Now that I look back, I can say I’ve left a small imprint on something that matters. Second, I challenged myself to release an episode every month in 2024. Despite everything else going on in my life, I managed to pull it off - which feels very rewarding.

The numbers section #

Now, if we look at the numbers, there were 14 full episodes and 64 shorts, with around 18.3K total YouTube views and 217 subscribers. That might not wow everyone, but as a fresh YouTube account with 0 subscribers, it’s not bad. The pilot episode—released on World Mental Health Day 2023—hit 830 views, which is still the highest to date. But more than the stats, I’m especially proud of the diversity in our conversations and guests. Of the 14 episodes, five featured people from underrepresented groups in tech, which is still fairly good, though I wish I could’ve done more. We also covered a wide range of mental health experiences—from PTSD and autism to ADHD and depression—and while a few episodes fell through when guests pulled back or never replied, I did my best to keep things inclusive overall.

Side note: I recently ran across a BBC article that points out most YouTube videos get fewer than 500 views—4% never see a single play. That perspective makes me feel even better about where I landed, even if my numbers aren’t massive in the grand scheme.

Two quick spicy takes #

1️⃣ During the last year and a half, I’ve been trying to stay more tuned-in to mental health conversations in tech, but it never feels like enough. It’s not fun or clickbaity content; it’s often difficult and sad, and you need people who are willing to open up and be vulnerable. That’s not exactly a majority mindset in this space. But after 10+ years in tech, I just keep seeing more and more people struggling (burnout, depression, you name it) all the time, and I wish we did more to address it.

2️⃣ If you’re trying to get your name out there in the tech world, I highly recommend skipping the whole podcast route—do open source instead. I’ve been in open source for years, and it’s night-and-day compared to the “exposure” you get from a podcast. Open source is more impactful, builds actual stronger credibility, and opens doors in a way that a scrappy podcast just can’t. Make your podcast a fun side project if you really want to, but if your main goal is to grow your profile, open source is where it’s at.

All in all #

Sure, maybe the name “debug:mind” wasn’t the best for SEO. Sure, I’d probably tweak a few things if I started again. But overall, I’ve done something I believe in: I’ve put a spotlight—however small—on mental health in our industry. And that’s enough for me.

I’ll keep the door open for a possible Season 2 if there’s enough demand—or even a chance to step into a producer role for other projects (do reach out if you have a podcast and would like me to help out).

For now, I’m just happy this project happened, and it will now exists as-is out there in the wild.


Part 2: The Practical Bits. If You Want To Podcast, Do This #

I learned a lot in the past year and a half, and I’m trying to condense here all the strategies. Of course, it’s not a size-fit-all and, in general, podcasting is a marathon, so set a sustainable approach and don’t be afraid to adapt and evolve over time.

Now, let’s get started:

0) Define Your Purpose and Format #

  • Know Your Why: Before doing anything else, you need a clear goal for your podcast—that’s what will keep you going even when things get tough. Pick a focus you’re passionate about—mine was mental health in tech—and that commitment will help you push through.
  • Choose Your Format: Decide if you’ll stick to audio-only or tackle video. Video can look more polished-that’s kind of what all the big shots are doing now- but typically involves higher costs (gear, studio rental, dedicated softwares or apps) and a narrower guest pool.
  • Nail the Name: Just like in programming, naming is a big problem. Keep it short, avoid punctuation or numbers, and if you can lock it down before Episode 1, you’ll spare yourself a world of trouble.

1) Pre-Production #

  • Build a Pipeline and Stay Organized: Scheduling guests, choosing topics, editing, and distributing episodes can get messy fast. Use a central planning tool (like Notion) to track guests, topics, and release dates. I maintained multiple Notion databases to handle long-form and short-form content separately—short-form entries referenced the corresponding long-form ones. This DB also tracked guests and each production stage so nothing fell through the cracks.
  • Frequency and Buffer: Pick a target release schedule (weekly, monthly, etc.) and keep one or two episodes completed in advance to avoid scrambling. Ex. If it’s month #2, try to have episode #3 fully finished and ready to go.
  • Finding Guests (If You Want Them): Start with people you already know who fit your show’s theme. Don’t take it personally if they say no. You can also cold email or message folks outside your network, but be prepared for many to ignore you. Keep multiple leads; guests can drop out at any point. Some may need workplace permission—especially in larger companies—so ask early.
  • Working with Guests: Once someone agrees, host a quick pre-recording call to finalize topics and expectations. Use a shared doc (like Google Docs) to coordinate asynchronously and gather discussion points. If you’re recording remotely, encourage guests to capture their own audio (and video) locally for higher quality. Always keep a backup plan for cancellations.
  • Plan Titles & Visuals Early: Algorithms can be unforgiving, so don’t wait until post-production to think about thumbnails, titles, and descriptions. Brainstorm them with your outline so you can tailor your conversation, angles, or visuals as needed. Strong visuals, strategic keywords, and concise copy can significantly boost engagement.
  • Gear and Budget: Start with a decent microphone—audiences can forgive less-than-stellar video but rarely bad audio (I used an Elgato Wave:3). If you plan to record in person, factor in possible studio costs. Above all, aim for clarity and consistency in your setup.

2) Production #

  • Episode Structure: Strive for a consistent length. Open with a quick intro and outline of what’s coming, then dive into the main conversation. Wrap up with clear calls to action—asking listeners to subscribe, leave comments, or share. A predictable format makes your podcast more approachable.
  • Use a Shared Outline: Reuse your prep doc during recording to keep track of key points, opening lines, and any must-say phrases. If you’re on video, consider printing the outline or placing it out of frame so you’re not constantly glancing off-screen.
  • Guest Setup Guidelines: Provide simple instructions for guests on camera framing, mic positioning, and audio checks. Even if you know your own gear, your guests might be new to recording. A short “how-to” guide can dramatically improve overall quality. If you’d like to see an example, reach out!
  • Session Timing: Schedule the recording to be longer than the final episode. Spend 10–15 minutes warming up, testing audio, and getting everyone comfortable. After you wrap, allow time to chat off-record—thank them, ensure they had a good experience, and confirm next steps.

3) Post-Production & Distribution #

  • Editing and Tools: Editing often takes longer than expected. I used DaVinci Resolve for my full video edits and to produce an audio-only version from the same project. If you’re going purely audio, simpler tools like Audacity or GarageBand should work well. For short clips, I’d pull selected segments from the final episode and assemble them in the CapCut webapp, rather than importing the entire project. Keep your workflow simple at first (especially if you are not experienced with the tools), then refine as you go.
  • Distribution: Use platforms that suit your audience. YouTube is great for discoverability, while Spotify and similar outlets covers the audio crowd (Spotify for Podcasters offers a free tool to distribute across multiple platforms, so I used that). Consider short-form clips on Instagram, TikTok, or YouTube Shorts to expand your reach. You can also use a scheduling tool like Buffer to keep posts consistent.
  • Interaction with Your Audience: Build dedicated social media accounts for your podcast on relevant platforms. At least announce new episodes, and if you want to go the extra mile share behind-the-scenes tidbits, and respond to comments or questions. Encourage listeners to subscribe, comment, and share your content—genuine engagement fosters a sense of community and helps you stand out (yes, it’s redundant and generic AF but honestly the algo is your worst enemy).
  • Consider a Website: If you have extra funds, consider building a simple podcast website for credibility and an easy reference point. This can also serve as a hub for show notes, additional resources, or behind-the-scenes content, rounding out your overall online presence. (s/o to Adam Ridovics for making a super cool design for the debug mind website!)

One final note: if you made it this far, thank you for joining me on this ride—whether you watched every episode, shared a short, or just followed from afar. Your support kept me going whenever things got tough, and I can’t thank you enough. And one final-final massive thank you to Roberto, Nathan, Jamie, Matt, Sara, Rachel, Mike, Anisha, Kitze, Andrei, Aleks, Emad, Alex and Parul - without whom this would have not happened.

And as always, take care of yourself.

Lorenzo 'kelset' Sciandra
Author
Lorenzo ‘kelset’ Sciandra
Lorenzo Sciandra is a Senior Software Engineer and mental health/open-source advocate. From 2018 to 2024, he served as a core maintainer of React Native, and spent four years at Microsoft driving its adoption both internally and across the wider community. More recently, he contributed to open-source sustainability at the Sovereign Tech Fund. Currently taking time to recharge, but always happy to open a call and chat.