The Hardest Question In Game Development

The hardest call a game leader makes isn’t about features or art style; it’s deciding whether to build the game at all. We break down a practical framework that helps you pressure-test new ideas and late-stage projects alike, so you can protect your team, your runway, and the game’s chance to find real players.

First, we dig into passion—what it looks like when it’s real and how to tell it apart from polite compliance. You’ll hear how sustained commitment shows up in behavior, not slogans: problem-solving in the ugly middle, ownership beyond titles, and pride in quality when deadlines move. We share questions to ask across disciplines and what to watch for when early excitement fades into quiet disengagement.

Then we turn to resources, the pillar most leaders underestimate. Money is just one piece; time, tools, skills, leadership bandwidth, and emotional capacity matter just as much. We explore common blind spots—hidden tech complexity, QA and polish debt, marketing and distribution costs—and show you how to build buffers, map skills honestly, and cut scope without killing momentum. You’ll leave with tactics to avoid the trap of “we’ll figure it out later” that leads to crunch, burnout, and fragile launches.

Finally, we face market reality with clear eyes. Great games don’t sell themselves, and hoping that marketing will fix it later is a gamble you can’t afford. Learn how to define a precise target player, analyze comparable titles, and validate demand early with demos, wishlists, and community feedback. We connect the dots on why any two pillars are not enough and walk through scenarios where teams get burned by ignoring the third.

Throughout, we offer checkpoints, scoring methods, and habits you can use to revalidate passion, resources, and market at every milestone. Even when all three align, risk remains—so we show you how to navigate it without sacrificing your people or your credibility. Subscribe, share with a teammate, and leave a review to help more leaders build healthier teams and better games.

Transcript

SPEAKER_00 0:38

Hey there, Press Starters, and welcome to the Press Start Leadership Podcast, the podcast about game-changing leadership, teaching you how to get the most out of your product and development team and become the leader you were meant to be. Leadership coaching and training for the international game industry professional. Now, let me introduce you to your host, The Man, the Myth, the Legend, Christopher Miffstude.

Framing The Core Question

Pillar One: Real Team Passion

How To Assess Passion Honestly

Pillar Two: Resources Beyond Money

Scoping And Resource Reality Checks

Pillar Three: Market Viability

Validating Demand With Early Signals

SPEAKER_01 1:07

Hey there, Press Starters, and welcome back to another awesome edition of the Press Start Leadership Podcast. On this week's episode, we'll be discussing Should We Make It? The eternal question for leaders in the game industry. A practical leadership framework for evaluating team passion, available resources, and market demand before committing to a game project. The question that never goes away. No matter how experienced you become as a leader in the video game industry, one question never stops coming back. Should we make it? It appears at the start of a new idea during early prototypes, halfway through production, and sometimes uncomfortably late in development. It shows up in pitch meetings, budget reviews, creative discussions, and quiet late-night reflections. It is one of the hardest and most important questions a leader can ask. Because answering it honestly requires more than optimism or instinct. It requires responsibility. I have faced this question many times throughout my career. Sometimes the answer was an enthusiastic yes. Sometimes it was a hesitant yes. Sometimes it was a painful no. And sometimes the answer changed over time as circumstances evolved. What I learned is that the question itself is not the problem. The problem is when leaders stop asking it, or worse, avoid asking it honestly. In game development, passion runs high. Ideas feel exciting. Teams want to create. Leaders want to believe. But belief alone does not ship games, protect teams, or keep studios alive. Leadership means balancing creative ambition with reality, not to kill ideas, but to give the right ideas a real chance to succeed. Over time I found the most green-lit decisions can be distilled into three fundamental questions. Does the team have the passion to make it? Do we have the resources to make it? And do we have the market for it? Any two of these may feel convincing, but they rarely lead to sustainable success. All three do not guarantee success, but they dramatically improve the odds and put you on a healthier path forward. This podcast breaks down each question: why it matters, how to evaluate it honestly, and how leaders can use this framework not just once, but continuously throughout development. The first question: Does the team have the passion to make it? Passion is usually the easiest box to tick. Most game ideas begin with excitement. Someone believes deeply in the concept. The team rallies around it. The early days feel electric. This is often where leaders get fooled because early enthusiasm can mask deeper issues. Passion is not about liking an idea. Passion is about sustained commitment over time. Why passion matters? Game development is hard. It is long. It's filled with uncertainty, iteration, compromise, and moments where the game feels broken and unfixable. When deadlines slip or features get cut, passion is what keeps teams engaged rather than resentful. True passion shows up as willingness to solve hard problems, pride in quality and craft, resilience during setbacks, ownership beyond job descriptions, care for the final player experience. Without real passion, quality suffers first, then morale, then momentum. When passion is missing, sometimes teams agree to work on a project out of obligation, fear, or convenience, rather than belief. They may say yes, but their energy tells a different story. This usually appears later as minimal effort, low initiative, defensive behavior, quiet disengagement, corners being cut. Leaders often mistake compliance for passion. They are not the same. How to assess real passion. The most important insight I learned is that passion must be assessed honestly, not assumed. Leaders must be willing to ask uncomfortable questions and listen carefully to the answers. Actual steps to evaluate team passion. Ask why this project matters to the team. Listen for personal connection, not rehearsed answers. Look beyond the loudest voices. Passion must exist across disciplines, not just with one champion. Assess long-term commitment. Ask the team if they are willing to stay engaged when things get difficult. Watch behavior, not words. Passion shows up in effort, curiosity, and care. Be honest if passion is forced. The team is not excited, acknowledge it early rather than hoping it changes. Passion alone will not carry a project, but without it, the project is already in trouble. The second question. Do we have the resources to make it? This is the question leaders most often underestimate. Passion makes people optimistic. Optimism makes people assume resources will appear somehow. They rarely do. Resources are not just money, they include time, skills, tools, experience, leadership bandwidth, and emotional capacity. Why resources matter more than belief? You can have the most passionate team and the clearest vision in the world. But if you do not have the resources to execute the project, it will fail or damage the team trying. Resource gaps show up as endless delays, crunch becoming normal, burnout, quality compromises, leadership exhaustion, financial instability. Passion does not replace missing resources. It only hides the problem temporarily. Common resource blind spots. Leaders often underestimate the true length of production, hidden technical complexity, QA and polish time, marketing and distribution costs, team growth needs, leadership attention required. The most dangerous phrase in game development is we will figure it out later. Being realistic without killing momentum. Evaluating resources honestly does not mean killing ideas. It means shaping them responsibly. Sometimes the right answer is not no, but not yet, or not at this scale. Actual steps to evaluate resources. Create a realistic budget with buffers. Assume things will take longer than expected. Map available skills honestly. Do not assume people can simply learn critical skills mid-production. Assess leadership capacity. Ask whether leadership has time and energy to support the project properly. Identify critical gaps early. Missing one key skill can derail everything. Be willing to reduce scope. Smaller, well-executed games outperform ambitious, unfinished ones. If you do not have the resources, it does not matter how good the idea is. The idea deserves better than being set up to fail. Third question: Do we have a market for it? This is often the most uncomfortable question, especially for creative teams. It forces leaders to confront reality outside the studio walls. Making a good game does not guarantee players will show up. Why market matters? Games are products as well as creative works. There is no audience willing to buy or play the game. The project cannot sustain itself. Ignoring market reality leads to financial loss, studio instability, team layoffs, burn trust with investors or publishers. Leaders owe it to their teams to ask whether the game has a real chance to reach players. Common market myths. Some of the most damaging beliefs I've seen include: if it is good, players will find it. We just need the launch in hope. There's always an audience somewhere. Marketing will figure it out later. These beliefs shift responsibility away from leadership and towards the luck. What market validation actually looks like. Market validation does not require massive budgets or years of research. It requires curiosity, humility, and early signals. Actual steps to evaluate market viability. Define the target audience clearly. If you cannot describe the player, you do not know the market. Study comparable games. Look at performance, pricing, and audience size. Test early interest. Demos, wish lists, mailing lists, and community feedback matter. Separate personal taste from demand. Loving an idea does not mean others will buy it. Watch for weak signals early. Lack of interest early usually does not improve later. Market reality is not an enemy of creativity. Why any two are not enough? This is where many leaders get stuck. They have two strong pillars and convince themselves the third will work itself out. It rarely does. Passion and resources without market. Team is excited, the budget is secured, the game ships, no one buys it. The result is disappointment and financial damage. Passion market without resources. Players want it, team believes in it, but the studio lacks time or money. The project collapses under pressure. Resources and market without passion. The game is viable, the budget exists, but the team does not care. Quality suffers and the game and the game feels hollow. Actual steps for evaluating the full picture. Create a simple three-pillar checklist. Passion, resources, market. Score each pillar honestly. Weakness in one should pause the decision. Courage dissent. Invite team members to challenge assumptions. Delay decisions if needed. Waiting is better than committing blindly. Be willing to say no. Saying no protects the team and the studio. Two pillars can convince you. Three pillars give you a fighting chance. When you have all three and still might fail. Even when passion, resources, and market align, success is never guaranteed. Timing, competition, execution, and luck still matter. This is not pessimism, this is realism. The difference is that when all three pillars are present, failure teaches valuable lessons. Teams stay healthier. Studios remain more stable. Leaders remain credible. Actionable steps to manage risk, even with all three. Set milestone checkpoints. Revalidate the three pillars regularly. Build flexibility in the plans. Be ready to pivot or adjust scope. Monitor team health constantly. Passion fades when burnout rises. Track market signals continuously. Markets change quickly. Accept uncertainty. Leadership is about navigating risk, not eliminating it. Having all three dots does not remove risk. It makes risk manageable. Using the three questions as an ongoing leadership tool. The biggest mistake leaders make is treating these questions as a one-time gate. They should be revisited regularly throughout development. Passion changes, resources fluctuate, markets evolve. Actionable steps for ongoing use. Revisit the three questions quarterly. Make them part of leadership reviews. Encourage honest reassessment. Normalize changing direction. Communicate decisions transparently. Teams deserve clarity. Treat stopping a project as strategy, not failure. Ending the wrong project protects future ones. Document learnings. Every decision improves future judgment. Good leadership asks the right questions repeatedly, not just once. Final thoughts. Should we make it? This question is not a hurdle to creativity. It is a safeguard for teams, studios, and the future of the work. Leaders who ask it honestly protect their people from burnout, protect their studios from collapse, and protect ideas from being wasted. Passion matters. Resources matter. Market matters. Any two may feel convincing. All three improve the odds. None guarantee success. Leadership is not about believing harder, it is about seeing clearly and choosing responsibly. Sometimes the bravest leadership decision is to say no. Not because the idea is bad, but because the conditions are wrong. Better questions lead to better decisions. Better decisions lead to healthier teams. Healthier teams build better games. And that is ultimately what leadership in the game industry is about. Alright, and that's this week's episode of the Press Start Leadership Podcast. Thanks for listening, and as always, thanks for being awesome.