Lessons Learned From Building Our First Games

When we built our first games, we thought we knew what we were doing. In some ways, we did. In many ways, we didn’t.

One of the biggest lessons was that simplicity is harder than complexity. It’s easy to add features. It’s much harder to know when to stop. Early on, we sometimes tried to do too much, when what the game really needed was clarity and confidence.

We also learned how important communication is across disciplines. A great idea can fall apart if it’s not understood the same way by design, development, art, and math. Alignment matters more than brilliance.

Testing taught us humility. Players don’t behave the way you expect. Features you love may be ignored. Small frustrations become big ones quickly. Listening to feedback changed how we approach everything.

If I were starting again, I’d still take risks, but I’d trust iteration more. Games aren’t finished when you think they are. They’re finished when they feel right.

Those first games shaped our studio culture. They taught us patience, respect for the process, and the value of teamwork. Most importantly, they reminded us why we started doing this in the first place.