How to run an indie game studio: Part 3, Dealing with issues
So far in this series, we've looked at how to define what your studio is and what it stands for , and how to set goals that give your studio direction on both a long-term and short-term horizon . This week, we're getting into something a little less exciting, but just as important: the problems. Read more
In this article, the focus is on dealing with issues within an indie game studio that go beyond typical development process challenges. These complex problems, such as team tension, stalling publishing deals, or unclear game loops, require more nuanced solutions since they don't have a clear owner or straightforward answer. To address these issues, the author suggests creating a shared, visible list where any team member can contribute open issues that hinder studio performance.
This list, akin to a backlog for the studio rather than individual games, ensures that all problems are on the table and can be addressed.
The author also emphasizes the importance of dedicating specific time during regular team meetings to tackle these studio issues, rather than relegating them to the end of meetings or allowing them to be ignored. To prevent unproductive debates that often occur, a structured discussion format called IDS, standing for Identify, Discuss, Solve, is recommended.
Before diving into solutions, it's crucial to correctly identify the underlying problem. This requires asking "What is the problem underneath the problem?" until the root issue is uncovered. By taking this systematic approach, studios can effectively manage their issues, leading to improved performance and reduced risk of derailment.
Written by urgent.news from GamesIndustry's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
