Lessons From a Creator's Portfolio: Choosing Which Bets to Keep
Most people who follow a creator, or who build their own work, eventually face the same problem: there are more possible projects than there is time to finish them. Games, podcasts, shops, and personal storytelling can all compete for the same hours. The useful question is rarely "what is the best idea?" It is "which of these ideas deserves the next unit of effort, and how will I know when to stop?" This article uses the general shape of a multi-format creator's portfolio, the kind visible on toddmichael.tv, where projects, games, a podcast, a shop, and a personal story sit side by side, to walk through a method for making those decisions. The lessons apply whether you are a fan trying to understand how a body of work fits together or an entrepreneur deciding where your own resources should go.
Map the portfolio before judging any single piece
A portfolio is easier to evaluate as a whole than as a list of isolated items. Start by sorting each project into one of three roles: a bet that could grow into a main line of work, a supporting piece that makes the main work more visible or more useful, or an experiment whose purpose is to learn something cheap. A podcast often supports other projects by carrying ideas, interviews, and audience attention. A shop may turn attention into a direct relationship with buyers. A game or build log may be an experiment that tests whether a particular creative process holds up over months.
Once each piece has a role, the portfolio stops looking like scattered activity and starts looking like a system with dependencies. You can ask whether the supporting pieces are actually supporting anything, and whether the experiments are designed to produce answers rather than just output. This mapping step takes an afternoon and prevents a common error: judging a small experiment by the standards of a flagship project, or treating a flagship as if it were disposable.
Separate evidence of interest from evidence of viability
Creative work generates two different kinds of signal. Interest signals include comments, shares, repeat visits, and the enthusiasm of people who say they want more. Viability signals show whether the work can sustain itself: whether people buy, return to a paid offering, or keep engaging after the novelty fades. Public-facing creators tend to receive a lot of the first kind and much less of the second, and it is easy to mistake applause for a business.
When you review a project, write down which kind of evidence you actually have. If you only have interest signals, the honest conclusion is that the project is promising but unproven, and the next step is a test designed to produce viability evidence, such as a small offer, a limited release, or a specific request for a commitment. Do not treat that test as a final verdict in either direction. A single weak week is rarely decisive, and a single viral moment is rarely a plan.
Use a short checklist before committing time
Before adding a new project or expanding an existing one, answer these questions in writing. First, what specific problem does this project solve for its audience, and can you state it in one sentence? Second, what is the smallest version that would tell you something true, and how long will it take? Third, what will you stop doing to make room for it? Fourth, what result in the next 60 to 90 days would convince you to continue, and what result would convince you to pause? Fifth, who besides you has seen the idea and given a useful objection?
The fourth question matters most and is the one people skip. A project without a stated stopping condition tends to continue by inertia, consuming effort long after its evidence has turned negative. Write the threshold down before you start, when you are not yet emotionally invested in the outcome. This is not a financial formula; it is a discipline for keeping your judgment intact when the work becomes personal, which in creator-led businesses it almost always does.
Learn from the story, but extract the decisions
A creator's personal story is often the most engaging part of their public presence, and it can be genuinely useful. Yet stories are compressed. They highlight turning points and omit the many ordinary choices that led there. When you read a creator's history, look for decisions rather than outcomes: what they chose to build, what they chose to drop, how they handled a project that was not working, and what they did with the feedback they received. A narrative of success tells you little about repeatability; a detailed account of a hard decision tells you how someone reasons.
A practical exercise is to take one decision from any public story you follow and rewrite it as a question you would face in your own work. For example, a choice to launch a product before it felt finished becomes: what is my minimum acceptable version, and who will tell me if it fails to meet it? This converts admiration into method, which is the actual transferable asset.
Revisit the portfolio on a fixed schedule
Portfolios drift. A project that felt central in January may be quietly stalled by June, while a side experiment has become the most energizing thing you do. A fixed review cadence, perhaps quarterly, keeps these shifts visible. At each review, reassess every item against its stated role and stopping condition. Decide whether to continue, redesign, merge with another project, or retire it. Retiring a project is a legitimate outcome, and it frees attention for what is working.
Keep the review short and the record simple: a single page listing each project, its role, the evidence gathered since the last review, and the decision made. Over several cycles this document becomes more valuable than any individual announcement, because it shows how your judgment has actually performed. Fans reading a creator's public work can apply the same habit by following what gets finished, what gets quietly dropped, and what returns after a break, rather than reacting to every new launch.