Turning a Creator's Public Journey Into Lessons You Can Actually Use
Following a creator's work for years gives you something a textbook never can: a visible record of decisions, experiments, and course corrections made in public. Todd Michael's projects, games, podcast, shop, and personal story at toddmichael.tv offer that kind of record. The value is not in admiring the outcome. It is in reconstructing the reasoning behind choices so you can test whether the same logic fits your own situation. This article describes a method for doing that. It is general guidance for any builder, not a summary of Todd's specific business strategy, and it avoids assuming details that are not spelled out on the site.
Start With the Decision, Not the Result
Most people read a creator's story backward. They see a finished game, a running podcast, or an established shop and work out a tidy narrative about how it must have gone. That narrative is usually cleaner than reality. A better starting point is to pick one decision you can observe: a choice to make a particular kind of project, to publish on a schedule, to organize a shop around certain items, or to talk openly about a personal experience.
Write the decision in one sentence and then list what you can see about the context at the time. What problem might it have solved? What constraints were likely in place, such as budget, time, skills, or audience size? You will rarely have complete information, and that is fine. The goal is to separate what is documented from what you are guessing, so your lesson stays honest about its own limits.
Separate Transferable Principles From Personal Circumstances
Some lessons travel well. Clear communication with an audience, building in small releases before large ones, and letting feedback shape the next iteration are principles that apply across industries. Other lessons depend heavily on the person: their voice, their network, their tolerance for risk, or the specific niche they grew up in. A creator who built a following through personal storytelling has a different starting asset than someone entering a crowded market with a product idea.
A useful test is to ask whether the lesson would still make sense if the creator's name, medium, and audience were swapped out. If it would, it is probably a principle. If it only works because of the creator's particular advantages, treat it as an observation and look for the underlying mechanism instead. For example, 'the creator answers audience questions directly' is a behavior. The principle might be 'trust grows when people see how you think,' which you can pursue in your own way.
Map the Business Model Behind the Visible Work
Creators often present several outputs at once: entertainment, community, products, and personal narrative. Each one may serve a different role in the overall operation. A podcast can build familiarity that makes a shop easier to visit. A game can give people a reason to return to the broader body of work. Trying to map these relationships helps you understand why a portfolio of activities exists, rather than admiring each piece in isolation.
Draw a simple diagram with the public-facing outputs in boxes and arrows showing which ones seem to feed others. Mark where you see direct revenue, where you see audience-building, and where you see creative expression with no obvious financial return. Be cautious about assigning exact financial figures, since they are rarely public and guessing them leads to false confidence. The structure of the diagram is the useful part.
A Practical Checklist for Extracting Lessons
Use the following questions each time you study a creator's public work. First, what specific decision am I examining, and when did it appear to happen? Second, what was the likely goal, and what evidence supports that reading rather than a different one? Third, what constraints might have shaped the choice, and which of those apply to my situation? Fourth, is the lesson a transferable principle or a circumstance-dependent tactic? Fifth, what would I need to see to know whether this approach works in my own context?
Sixth, what is the smallest version of this idea I could test within a month? Seventh, what would failure look like, and how would I notice it early? Writing answers to these questions turns passive admiration into a working experiment. Keep the notes in a single document so you can compare lessons across several creators over time and notice patterns that recur.
Keep Your Own Judgment in the Loop
The final step is the easiest to skip: deciding what you will actually do. Public stories are edited, and even honest accounts omit the boring parts, the failed attempts, and the luck involved. Treat any single creator as one data point, not a template. Compare their experience with others in similar fields, and with your own results when you run a small test.
Above all, remember that your goals may differ from the creator's. Someone building a hobby project and someone building a full-time business need different lessons from the same story. Define what success means for you first, then use a creator's public journey as a source of questions rather than answers. The most valuable outcome of studying Todd Michael's work, or anyone else's, is a sharper set of questions you can bring to your own decisions.