There is a humbling moment in building anything when you hand something you have worked on for months to another person and watch half of your assumptions fall apart in real time. I have hit that moment more than once while making these games — usually at a friend's kitchen table, watching someone who does not play video games try to figure out what I built. This post is about those lessons: the surprises, the corrections, and the things that changed how I design.
The Setup Was Scrappy
My early testing was about as low-tech as it gets. No arcade cabinet yet — just a monitor, a controller, and whatever gathering of friends and family I could talk into humoring me. There was no research lab and no one-way mirror. Just me, quietly watching people play for the first time and trying not to explain anything.
That watching part turned out to be worth more than any questionnaire I could have written. I learned fast that what people say about a game and what they actually do while playing are often two different things. In conversation afterward, people were polite — "fun," "easy to pick up." But while they played, I could see the exact moments they hesitated, glanced from the screen down to the controls, leaned in with focus or leaned back in frustration. Those micro-moments became my real data.
Lesson One: Shorter Rounds, Better Energy
The early builds had rounds running five to seven minutes. Alone in a development session, that felt right. Watching other people play told a completely different story. Five minutes was too long — attention drifted, side conversations started, and the little bit of energy that builds during a round would fizzle before the next person stepped up.
I cut rounds down to the two-to-four-minute range, and the difference was immediate. People finished and wanted to go again. As a game builder, my instinct is to create deep, layered experiences. As someone designing for a wedding reception, I needed quick, punchy, endlessly replayable moments. Testing showed me exactly where that line sat.
Watching people play taught me more than any survey ever could
Lesson Two: People React to Seeing Themselves
With Honeymoon Hustle, the personalization — pixel-art characters made to match the actual couple — is the whole point. I assumed the gameplay would be the first hook. Testing suggested otherwise. Even on a bare monitor with no cabinet, the biggest reaction I got was the instant someone recognized a personalized character on screen.
Early on, the title screen showed a generic splash graphic before loading into the personalized game. People would glance at a standard-looking title and lose interest before they ever saw the custom characters. So I redesigned the attract screen to put the couple's pixel-art likenesses front and center from the first frame. It is a small change that testing made obvious: the personalization is not just a feature buried in the gameplay, it is the hook, and it needs to be visible before anyone touches a control.
Lesson Three: Simpler Controls, Wider Appeal
The early Ring Run prototype used a joystick and three buttons per player. In my own hands, that worked fine — I map buttons without thinking about it. Watching people who do not play games regularly was a reality check. Three buttons made them visibly hesitant. They would look down, press one tentatively, and if the screen did not do what they expected, they would disengage rather than experiment.
The whole point is wedding guests of every age and background. That input barrier was too high. So I stripped it back to a joystick and a single button, which meant reworking mechanics I had spent weeks on. But with one button, nearly everyone I handed it to was playing comfortably within seconds — kids, grandparents, people who "never play video games." Every game in the lineup now follows the same rule: if someone cannot figure out how to play within about five seconds with no instructions, the design needs more work.
Lesson Four: Watch, Do Not Ask
The most useful meta-lesson was about method: observation beats interrogation every time. When I asked for feedback directly, the answers were uniformly kind and uniformly vague. "It was fun." "I liked it." Lovely to hear, nearly useless for making the thing better.
The gold was in watching. I could see the precise second someone lost interest, the glance at the controls instead of the screen, the small lean-back when a round dragged. Those observations gave me specific, fixable problems that a polite survey never would have surfaced. Now I build watching into every session — tracking where eyes go, how people hold the controls, and exactly when engagement peaks and dips — instead of relying on what people tell me afterward.
Better Games Through Honest Feedback
Every one of these lessons made the games meaningfully better — not incrementally, but fundamentally. What I am building today is substantially different from where I started, and nearly every major change traces back to watching a real person pick up a controller for the first time. I am genuinely grateful to the friends and family who gave their time and their honesty, even when their honesty meant more work for me.
Playtesting is not a phase that ends. It is a practice, and I intend to keep it going with every new game and feature — including, before long, with real couples at real weddings. If you are curious what has come out of this process so far, take a look at Ring Run and Honeymoon Hustle.