Fan Ritual, Builder Routine: Turning a Podcast Listen Into a Weekly Practice
Most people who follow a builder's public work share a common experience. They finish an episode feeling energized, nod along to a story about systems or reinvention, and then return to their week unchanged. The motivation was real, but it had nowhere to land. This article takes a different angle: how to treat a podcast or a creator's media home as raw material for a small, repeatable routine. The goal is not to copy anyone's life. It is to convert listening time into decisions, experiments, and records you can review later. The examples below refer to ToddMichael.tv, the media home of Todd Michael Gori, which publishes The Todd Michael Podcast, a free browser-game arcade, merch, and a Book a Call page. The same method works for any creator whose work you follow.
Start by Sorting What You Consume
Before you can build a routine, you need to know what kind of content you are actually taking in. Podcast episodes, arcade games, book excerpts, and merch pages each serve different purposes. An episode about systems or automation is instruction-shaped. A story about reinvention is reflective. A game is recreation and sometimes a useful break from screens. Treating them all as motivation is what makes most media feel the same and fade quickly.
Try a simple sort for one week. Each time you finish an episode or visit the site, write a single line labeled idea, story, or pastime. Ideas are claims you could test. Stories are context about how someone else worked through a problem. Pastimes are rest. At the end of the week, count them. Most listeners discover they are heavy on stories and light on ideas, which tells them where to focus their attention.
Extract One Testable Idea Per Episode
Motivation fades because it has no object. An idea has one. When an episode discusses systems, AI, automation, ecommerce, or ownership, pick the single most concrete claim and rewrite it as a question you can answer about your own situation. For example, a point about building systems in public becomes: which part of my current work would be easier to follow if I wrote it down each week?
Keep the test small. One question, one week, one artifact. A short note, a checklist you tried once, or a conversation you had with a colleague all count. The discipline is in finishing the cycle, not in the size of the experiment. Over a month, these small tests will tell you more about what works for you than any amount of inspiration.
Build a Weekly Review, Not a Feed
A feed rewards constant intake. A review rewards reflection. Set one fixed slot each week, perhaps thirty minutes on a quiet morning, to look back at what you consumed and what you did with it. Use three prompts: what did I learn that changed an action, what did I start and not finish, and what would I want to repeat next week.
Keep the review short enough that you will actually do it. A paper notebook or a single document works better than a complicated tool. The value is not the tool but the habit of asking whether listening produced any output at all.
Ask the Right Questions About Any Creator's Public Work
Following a builder in public is useful partly because it shows you the messy middle, not just the finished result. To get the most from that, ask questions of the material rather than accepting it whole. Useful questions include: what problem is this project solving, who is the audience, what would count as the project failing, and what did the creator decide to stop doing. These questions help you read a project update as a set of decisions rather than a highlight reel.
Be careful with claims about outcomes. Public updates describe what the creator chose to share. They do not tell you the full financial, operational, or personal picture, and they should not be treated as guarantees for your own work. Keep your own standards for evidence.
A Practical Checklist for the Week
Use this sequence as a starting template. First, sort what you consumed into ideas, stories, and pastimes. Second, choose one idea and write it as a testable question. Third, design the smallest action that could answer that question within seven days. Fourth, record what happened in one or two sentences. Fifth, during your weekly review, decide whether to repeat, modify, or drop the experiment.
If you want outside input on a specific project, the Book a Call page on the site offers a one-hour conversation with Todd Michael covering strategy, creator work, ecommerce, or automation. Prepare a short written summary of your situation beforehand so the time goes toward your actual question rather than background.
Motivation gets you to the first step. A routine is what carries you through the tenth. Treat your favorite creator's media as a source of questions, not a substitute for them, and the listening time will start to show up in your work.