The Paradox of the "Non-Transformational" Game


If you’ve ever tried to get a straightforward answer from a four-year-old, you know their way of thinking can be a bit hard to pin down. They notice so much, but don’t always have the words to tell you how they actually see the world. That’s precisely where our project for this semester, in Game-Based Assessment, or GBA, comes into play. My team and I are busy building digital environments for a project we call SoKids. We use tablet games there to figure out how young children, specifically those between three and six years old, perceive the social groups and individuals around them.


So, what exactly is a non-transformational game?

The real puzzle in this kind of work isn't just making a game kids will want to play—it’s about creating one that leaves them unchanged. In nearly every other part of the gaming world, "transformation" is the ultimate goal. We want players to pick up a new skill, improve their character, or perhaps even walk away with a totally new perspective. But when your main aim is to measure what a child already believes, transformation actually works against you. If our game teaches them a lesson, or nudges them toward what we consider "correct" behavior, then we're no longer seeing their true reality. Instead, we're simply measuring how well they can follow our instructions.


This challenge has led us to a design philosophy that feels almost upside down: non-transformational design. We need to build a space that’s captivating enough to hold a preschooler’s attention, yet so neutral it doesn't leave any mark on their own way of thinking. It’s a bit like digital birdwatching, in a way. We just want to observe how kids naturally move through the world—who they choose to interact with, or how they decide to share things—without the game itself tipping the scales.


To manage this, we actually have to strip away many of the things that typically make a game feel like a "game." Most games rely on feedback loops—those gold stars, "Great Job!" animations, or triumphant sound effects—to let the player know they’re succeeding. In our specific work, that kind of feedback becomes a huge source of bias. If a child makes a choice and the game celebrates it, we've inadvertently told them that was the "right" answer. Every choice they make after that will be swayed by that reward, rather than coming from their own true instinct. Our systems, then, need to be silent observers, offering just enough sensory feedback so the child knows the screen is responding, but never enough to suggest what they should be doing.


Designing for this particular age group also means we have to be incredibly mindful of how much influence even the simplest interface choice can have. For a young child, something like a character's color, the speed of an animation, or even the order in which items appear on screen can subtly guide them toward a specific choice without us intending it. Our focus is on making the interface as invisible as possible. If a child has to struggle with a button or a menu, the data we collect ends up reflecting their tech frustration, not their genuine social understanding.


Ultimately, this whole idea of designing without transforming is about creating a clearer, more honest window into the human mind. We aren't trying to shift how these kids think, and we're certainly not trying to teach them a lesson. We're simply working to make sure that when we peer through this digital lens, we see them exactly as they are, with the game staying entirely out of the way. By taking the "instruction" out of the interaction, we can finally let the play truly speak for itself.