There is a humbling moment in every product development cycle when you put something you have been building for months into the hands of real people and discover that half of your assumptions were wrong. For us, that moment came during our first organized playtesting sessions. We thought we knew what wedding guests would want from an arcade game. We were right about some things and spectacularly wrong about others. This post is about those lessons — the surprises, the corrections, and the insights that fundamentally changed how we design our games.
The Setup
Our early playtesting was scrappy. I set up the game on a screen at friends' gatherings — no arcade cabinet yet, just a monitor, a controller, and a willingness to watch quietly while people interacted with the games for the first time. There was no formal research lab or one-way mirror. The watching part turned out to be far more valuable than any questionnaire we could have designed.
I quickly learned that what people say about a game and what they actually do while playing it are often two different things. In post-play conversations, people would tell me the game was "fun" and "easy to pick up." But observation told a more nuanced story — I could see the exact moments where someone hesitated, where their eyes flicked from the screen down to the controls, where they leaned in with focus or leaned back with frustration. Those micro-moments became our real data.
Lesson One: Shorter Rounds, Better Energy
The initial game builds had round times between five and seven minutes. In solo development sessions, this felt right. But watching friends play in informal testing sessions told a different story. Five minutes was too long — people's attention drifted, conversations interrupted, and the energy that builds during a round would dissipate before the next player could capitalize on it.
We cut round times to the two-to-four-minute range and the difference was immediate. Players finished a round and wanted to go again. The pacing started to feel right — quick enough to stay exciting, long enough to feel complete.
As game builders, we wanted to create deep, layered experiences. As wedding entertainment designers, we needed quick, punchy, endlessly replayable moments. Playtesting showed us exactly where that balance needed to be.
Watching real players interact with our games taught us more than any survey ever could
Lesson Two: Couples Want to See Themselves Immediately
With Honeymoon Hustle, the personalization — pixel art characters customized to match the actual couple — is the core selling point. We assumed gameplay would be the first hook. We were wrong. The moment that consistently generated the biggest reaction was the instant guests saw the couple's pixel art likenesses on screen.
In early testing, the title screen showed a generic splash graphic before loading into personalized gameplay. Guests would walk up, see a standard-looking game, and sometimes walk away before ever seeing the custom characters. Once we redesigned the attract screen to feature the couple's pixel art front and center, foot traffic to the cabinet increased significantly. People would point from ten feet away — "Is that Sarah and Mike?" — and walk straight over to play.
Personalization is not just a feature, it is the hook. It needs to be visible before a guest even touches the controls.
Lesson Three: Simpler Controls for Wider Appeal
The early prototypes for Ring Run used a joystick and three buttons per player. In my own testing, this worked fine — I am comfortable with game controllers and naturally mapped the buttons without thinking. But watching less experienced players in testing sessions told a different story.
People who do not play games regularly were visibly hesitant with three buttons. They would look down at the controls, press one tentatively, and if the result on screen did not match their expectation, disengage rather than experiment. The goal is wedding guests of all ages and gaming backgrounds — that input barrier was too high.
I stripped the controls back to a joystick and one button. It meant reworking mechanics I had spent weeks building. But with one button, every tester — regardless of age or gaming experience — was playing comfortably within seconds. Grandparents, young kids, guests who "never play video games" — all engaged and having fun almost immediately.
The same principle applied to Altarbound and Frost & Found. Every game in our lineup now follows a strict simplicity rule for controls. If a guest cannot understand how to play within the first five seconds without any instruction, the design needs more work.
Lesson Four: Watch, Do Not Ask
Perhaps the most important meta-lesson was methodological: observation beats interrogation every time. When we asked players for feedback, the responses were uniformly positive and vague. "It was fun." "I liked it." Nice to hear, nearly useless for improvement.
The gold was in watching. We could see the exact second a player lost interest. We could see when someone's eyes went to the controls instead of the screen, the body language shift when a round went on too long — the subtle lean back, the glance over the shoulder. These observations gave us specific, actionable data that polite surveys never would have.
I now build observation into every testing session. Rather than asking for feedback, I watch — tracking where players look, how they hold the controls, and exactly when their engagement peaks and dips.
Better Games Through Honest Feedback
Every one of these lessons made our games better. Not incrementally better — fundamentally better. The products being built today are substantially different from the original designs, and every major change was driven by watching real people interact with real prototypes in real settings. I am deeply grateful to the early players and friends who gave their time and their honesty.
Playtesting is not a phase of development that ends. It is a continuous practice, and we intend to keep doing it with every new game and every new feature we build. If you are curious about the games that emerged from this process, take a look at Ring Run, Altarbound, and Frost & Found — each one shaped directly by the players who tested them first.