Real-Time Sweetspot: The Multiple Meanings of Game Company Playtests

This paper examines how game companies use playtesting, focusing on a single "Sweetspot" balancing test conducted in March 2006 for a real-time strategy game at a medium-sized Swedish studio, part of an international entertainment conglomerate. Drawing on interviews and observations of playtest sessions from March 2006 to February 2007, the author argues that playtesting carries multiple meanings beyond its conventional role in usability and design iteration. Within the company, playtests function as a tool for achieving clarity in an evolutionary, biweekly build-based development process, while also serving as a means of communicating project status to outside actors such as the publisher and parent company. The study situates these practices within a broader industry shift away from milestone-driven production toward iterative approaches that acknowledge the emergent properties of gameplay.

The Sweetspot test illustrates these dynamics concretely. Eight playtesters rated four builds varying unit hit points and reinforcement tempo, and the lead designer implemented changes overnight, with the subsequent build confirming his balancing decision. The study also documents the interpretive complexity of playtest data: quantitative ratings, a summary Test Index Value, and written feedback often conflicted, and the consumer testing manager gave particular weight to outlier scores that prompted follow-up questions. Quantitative figures were valued for setting priorities but were recognized as abstractions that could mislead when read without context.

The research also reveals that the test group was predominantly male and hardcore, and that some playtesters used participation as a route into employment at the company. The company's CEO acknowledged these sources of potentially "tainted" data and the risk that numerical reports could be misread by the parent company. The author concludes that playtesting cannot achieve scientific objectivity, that increasing quantification risks turning playtests into progress milestones for outside stakeholders, and that companies must remain clear about what they hope playtesting will accomplish.