Lessons Learned As A First-Time Game Producer (So Far…)
I knew launching a game studio was going to be hard work, but I did not anticipate some of the challenges encountered along the way.
For nearly seven years, I have been producing immersive VR and AR experiences for clients. When we decided to launch a game studio, I knew it was going to be hard work; still, with my background in immersive technology production, I did not anticipate some of the challenges we have encountered along the way. As our first game approaches its early access release, I thought now was a good time to check in and share what I’ve learned with other first-time game producers, especially those doing things independently.
Plan, plan and plan some more.
Looking back at Loam’s pre-production, I wish we had started with a more defined plan. We do this for our clients, so why wouldn’t we do this for ourselves? Since we were in the middle of a pandemic, I wanted to start the project with prototyping and creative freedom.
This was good for morale, however, without a strong initial plan, we spent too much time spinning our wheels and lacked a long-term vision apart from a general “gardening game” label. Once we started designing and documenting prior to development, things started running more smoothly and at a quicker pace.
Your timeline will be pushed back.
Looking back on it, our original launch date was highly unrealistic. We were ambitious and excited, but due to the type of game we are producing (garden simulation), many elements took more time to implement than originally anticipated. We also allowed controlled scope creep to occur when we found something new that just HAD to be in the game.
The team has gotten better at recognizing unnecessary launch features and understanding why we cannot add them in at this time. We also realized that we only have one chance to make a first impression as a game studio, and we would rather launch the right game at a later date than the wrong game early.
Remember your game is a business.
This is probably the number one thing I need to remember when judgment gets clouded. Indie game development is full of passion, excitement, and personal opinions, but to sustain a studio — salaries, benefits, software licenses, hardware, etc. — the business side of the game must take high priority. Just like any other project, the ultimate decision comes down to time, budget, effort, and quality. While that may knock the wind out of some peoples’ sails, it brings me comfort. It is a guiding force that helps me maintain focus and drive. If we execute this well as a business, we get to do more of it which is worth it (even when I have to be the bad guy).
Know everyone’s strengths.
I know my team well. Most of us have been together for years and have encountered quite a bit together, but I learned so much more about everyone throughout this process. Doing an independent internal production allowed us to branch out of our typical roles and take on new ones in a true all-hands-(and many hats)-on-deck situation. For example, I am the executive producer, but I am also a composer and have been using those skills to compose the background music for the game. A couple of people were required to step up into leadership positions, and those are strengths that were previously held inside as well. Others who were in development and marketing have stepped up to manage playtesting processes and sessions. Instead of just assigning roles, I have learned to ask if I have an opportunity if anyone is interested. By learning more about each other and our hidden strengths, it’s made us stronger as a team.
Have a long-term goal, and then add more.
When we started development, our long-term goal was to release a game. Plain and simple, right? Wrong! The goalposts kept moving, sometimes narrowing and sometimes expanding, but that is 100% normal. Now, we have a series of goals that stretch from the initial player experience to the third game update. By verbalizing our goals and sharing them with the team, we can work with unity (hehe, no pun intended). Everyone shares the vision, has the power to contribute to the vision, and we work together to make it happen. I am happy our goalposts keep moving and evolving, but we also need to remember to look back on all that we have accomplished. And that brings me to my last lesson…
Celebrate the wins and recognize progress.
This is something that we all struggle with. We celebrate wins when they are obvious (i.e. someone completes a major task or crushes a pesky bug), however, we often forget all of the little things that add up over time.
For years now, we have been creating a weekly “list of good things” where we write down at least three good things that happened recently. If I ever need a reminder of how far we have come, I look back on that list (which now goes back about three-and-a-half years) and get a jolt of energy. I highly recommend reminding yourself of all you have accomplished as well as verbalizing that to your team; it can go a long way and shows you’re paying attention.
This article is just a shortlist of all I have learned so far, but I hope to publish an update in the future after Loam has officially released. Thank you all for your support in this process — it is not by any means easy, but it is one of the most rewarding professional endeavors I have tackled.
