Honeymoon Hustle is a two-player lane runner where the couple sprints through an airport to catch their honeymoon flight, dodging luggage carts and slow walkers and the general chaos of a terminal. It is simple, it reads instantly, and people seem to get it the moment they see it. What almost nobody would guess is that the airport was the last idea standing after I cut nearly everything else. This is the story of how the game got there, a story about doing too much, and then doing much less.
The Original Was an Epic
The first design was ambitious in the way first designs usually are. The concept was to take the couple through the whole arc of leaving their own wedding and getting away on their honeymoon. It was going to be a multi-stage journey:
- ✓ Stage one: Escape the reception. Slip out through a crowd of guests, dodge the well-wishers and the relatives who want just one more photo.
- ✓ Stage two: The getaway down the road, car and all.
- ✓ Stage three: Get home and pack the bags in a mad scramble before the clock runs out.
- ✓ Stage four: Finally, the airport dash to make the flight.
On paper it was a complete story. Four distinct stages, each with its own setting and its own mechanics, all tied together by the narrative of the newlyweds racing toward their escape. I was excited about it. It felt rich.
Where It Fell Apart
The trouble showed up as soon as I started actually building it. Every stage wanted to be a different kind of game. Escaping a reception crowd is a weaving-and-dodging problem. A car getaway is a driving problem. Packing a bag against a timer is a frantic sorting problem. The airport is a running-and-dodging problem. Four stages meant, in practice, four small games stapled together, four sets of controls to learn, four sets of rules to explain, four things that each had to be fun on their own.
That is a lot to ask of anyone. It is especially a lot to ask of a wedding guest who is two drinks in, has never played a video game, and is going to spend a grand total of a few minutes at the cabinet before someone else wants a turn. The whole point of these games is that you walk up and understand them instantly. My beautiful four-stage epic was the opposite of instant. It was a game you had to be taught.
The transitions were the worst part. Every time the game shifted from one stage to the next, it had to re-explain itself, and the momentum died right there. The pieces were not adding up to more than their sum. They were adding up to less.
What survived: one relatable stage, playable in seconds, personalized to the couple
Kill Your Darlings
There is an old piece of writing advice, "kill your darlings", about cutting the clever bits you are most attached to when they are not serving the whole. Design has the same rule, and I had to apply it here. Instead of asking "how do I make all four stages work," I started asking a better question: "if I could only keep one of these, which one earns its place?"
The answer was obvious once I let myself ask it. The airport. Almost everyone has run through an airport, or been terrified they were about to miss a flight. It is universal in a way the others are not. You do not need to have gotten married to feel it. Racing to a gate is instantly legible; the second you see it, you know what you are supposed to do. And it carries the emotional payload the whole game was reaching for anyway: two people, side by side, rushing toward the start of their life together.
So I cut the other three stages. All of them. Months of ideas, gone in one decision, and the game got dramatically better the moment they were gone.
What Focus Bought
Narrowing to a single stage did not shrink the game. It sharpened it. With one setting and one core mechanic, I could pour all my attention into making that one thing genuinely good. The two-player, side-by-side format got room to breathe, now it is the couple running together, which is the entire point. The controls collapsed to something anyone can grasp in seconds. And because there are no transitions to kill the momentum, a round stays fast and punchy from the first second to the last.
It also made the personalization land harder. When the whole game is one clear scene, the couple's customized characters are on screen the entire time, front and center, instead of buried inside one stage of four.
The Lesson I Keep Relearning
Every project I build teaches me some version of the same thing: the first idea is almost always too big, and the work is figuring out what to remove. Subtraction is harder than addition. Adding a feature feels like progress; cutting one feels like loss, especially when you are attached to it. But the airport version of Honeymoon Hustle only exists because I was willing to throw away three-quarters of a design I loved.
If you want to see where that focus ended up, take a look at Honeymoon Hustle. And if you are curious how the rest of the lineup came together, the product lineup is where the other games live, each one shaped by its own round of hard cuts.