Reducing Waste

A journey for automated Game Releases

Everyone's journey to becoming a product manager is unique, and mine is no exception. For me, it has always been about identifying opportunities to make things better—often by creating solutions that didn't exist yet.

One of the most rewarding projects I worked on was the development of a release management tool at Spil Games (now part of Azerion).

Spil Games specializes in casual mobile games for iOS, Android, and Amazon stores. These games are free-to-play and monetized through a combination of ads and in-app purchases. The intricacies of free-to-play strategies are fascinating, but that's a story for another day.

I joined Spil Games as a Release Manager, a role within the Project Management team. My job (shared with one other colleague) was to oversee the release of games. This involved more than just pushing a button to make a game available on app stores.

We had to coordinate with stakeholders to ensure marketing assets and development work were ready on time, educate teams on compliance rules, review assets, and collaborate with Game Producers on the rollout strategy for each release.

It didn't take long for me to notice significant inefficiencies in the release process. There was too much back-and-forth communication and no reliable way to track the process history, making it difficult to identify areas for improvement.

When I shared my observations with my peer, he mentioned his own ideas for improvement, specifically around automating tasks prone to human error. He had already done some great research and found an open-source tool called Fastlane, but hadn't had the time to turn it into a business case.

With the two of us working together, it became more feasible to carve out time for process improvements. We could also challenge each other's ideas and build on our different experiences to create a stronger proposal.

Flowchart showing the release process and communication around it

We gathered feedback from our colleagues about the current process and discussed our team's OKRs with our manager. Together, we built a proposal to integrate Fastlane into a proprietary release management tool. This tool would provide the entire organization with visibility into the release process, identify bottlenecks, and maintain a history to refine release strategies.

While it sounds fancy, the product itself was quite simple. Working with the lead developer, we mapped out the existing process and highlighted the pain points. We then designed a new process and validated it with all stakeholders.

We built a straightforward UI that initiated the release process and logged each completed step, sending notifications and reminders to relevant parties along the way. Some technical checks, previously performed by the Release or QA teams, were automated, and we enabled direct pushes to the app stores from our Release Management application.

It might not have been the kind of product development that makes headlines, but it was significant for us. It brought much-needed transparency to the process and freed up our team members from mundane tasks, allowing them to contribute more value to the organization.

This experience planted a seed for me—I realized that product management was something I was passionate about and might actually be the best way for me to make an impact.