Mighty Kingdom Play Test Pipeline
The Problem
The lack of structured play testing at Mighty Kingdom was failing to provide insights and actionable outcomes for our game designers
TLDR
We collaborated with the team to set up a play testing pipeline that helped them gain insights and guide design decisions. It was difficult but it led to actionable outcomes and a scalable play testing blueprint.
Context
In 2020 when I arrived at Mighty Kingdom the play testing process was a chaotic hybrid of internal testing and product showcasing. There was no scientific method to the madness, nobody was championing it and actionable data was being lost due to a lack of structure. In short, it was a huge missed opportunity.
Problem
Play testing data was not being captured in a measurable way. This meant that it also did not help inform design decisions. We needed a way to allow the data to be captured, analysed and communicated to the development team so they could iterate effectively.
Research
In our analysis, we examined the play testing pipelines of our competitors and engaged in discussions with game designers to understand their specific requirements for the system. Additionally, we conducted research to determine the optimal stage in the development cycle where the system would provide the greatest benefits. Furthermore, we performed were sure to test and iterate on our play testing solution to assess its functionality and ensure it performed as anticipated.
Solution
We developed a comprehensive solution that involved consulting with designers to understand their research objectives and designing specific player tasks to test those objectives. Our technical setup enabled anonymous observation of players and provided a mechanism for recording and storing videos. We were able to easily review the recorded videos, carefully noting how players performed in relation to the testing objectives. The collected data was then compiled and presented to the team, empowering them to leverage the objective insights gained from the play testing process. And finally, after each play test we conducted a retrospective to see how we could continue to improve on the process for future tests.
Regular play testing led to more meaningful iteration. Game designers also gained a deeper understanding of how people played their games.
100+
Play Tests Completed
Impact
The implementation of the new system brought about significant improvements. Designers gained the ability to iterate more effectively, finding solutions and measuring results through re-testing their ideas. The inclusion of player feedback began shaping the development process, providing valuable insights. Furthermore, the system proved scalable, accommodating both small-scale and large-scale testing needs. As a result, the value of UX became evident, contributing to an overall increase in the company's UX maturity. The team adopted a stronger UX mindset when approaching projects, leading to enhanced collaboration across all teams. The testing system itself could be repeatedly utilised for both short and extended play tests without compromising team efficiency.
