Reassessing Epizo Zero

Introduction

This article extends back to the first time when a nascent endeavor and audience had the chance to meet in the online space. Considering the content of the first podcast episodes, the set of articles looking back to the time of inception (summer of 2020) targets a different audience compared to a typical article.

Episode Zero Specialties

You can easily guess from the title that Episode Zero is intended both introductory and emphasizes that it is more than an essential part of the show because it details some crucial differences compared to other content.?

Target Audience of this Article

Episode Zero both sets goals for the author and the community of the show so that achievements can be followed, while as expected from an introductory chapter, details what kind of content to expect.

Because of the above, the minor difference in the target audience is that it also targets people who want to know more about the #entrepreneurial side, still serving as a starting point for reassessment for all the affected parts of the #programmer community.

Most Essential Findings and Undertakings by the Show’s Inception

In-the-making Session

Firstly, I would recommend that everyone with their nascent venture create some Episode Zero-like content because it does open the gates to effective community building before the significant part of the show starts.

In-the-making session, also referred to as Immense brainstorming about the ideal podcast, introducing various intended audiences was a huge undertaking. For clarification, this was organized via LinkedIn messaging, and as a result, ProScala Podcasts listeners have a LinkedIn group ( https://www.dhirubhai.net/groups/8951149/ ) of more than 100 people and various lead lists.

My personal finding is that it is worth organizing something between Episode Zero and the major part of the show.

What’s the Goal of the Topics, and What Shall Be Covered?

The goal of the topics is to build up a general knowledge regarding Functional programming, Scala, architectural design, and related topics to a level that can make you able to take part in software migration and/or pet project development both if you are a developer or on the business side.

Season 1 succeeded in covering the general aspects of these, providing some evergreen content we can go back to over and over again as a means of repetition.

What Changed Regarding the Audience’s Behaviour?

I get fewer responses if send out messages but remain on the lists and listen to what I say. My two cents are that more people shall be reached by the show, and more exciting content (including written content) shall be provided.

What are the Author’s Long-term Plans?

Even though it's tough to go on with ProScala Podcasts, I’ve got more ambitious. The show can be produced at a slower pace, but meanwhile, I can create different content that can be monetized in different ways.

Regarding the podcast, I have good experience with something I’d call evergreen content. I’d refer to Season 1, which includes tech stories that can be distributed to audiences not just on the spot but later on. I’d stick to that format.

Summary

To summarize my most important clues, I found that only a quality-over-quantity monetizing model works both for me and both for the show. Not surprisingly, the brainstorming behind the scenes turned rather into market research with some community-building elements.

Being in a preparation phase for Season 2, I treat this period as the period for reassessment, but it would be great to hear about others who also had a beginner venture about their personal experience.