How Game Studios Can Learn from Classic Board Games When Building Player Retention

Eight years in game development and I’m still learning obvious lessons way too late.

Last Tuesday I’m watching our QA team test this mobile game we’ve been building for fourteen months. Pretty standard stuff, decent graphics, progression system we spent weeks balancing. Players are closing it after exactly 12 minutes. You know what app they opened next? A domino online game that looks like something from 2008 and has basically zero features beyond the actual game itself.

That messed with my head for days.

Why Your Expensive Game Loses to Simple Tiles

My natural instinct was to blame the players or make excuses about our marketing. But I’ve worked at enough studios across Europe to notice a pattern: games with tiny budgets and super simple mechanics regularly destroy our retention numbers.

I ran this experiment on myself. Played 47 domino matches over three weeks while trying to figure out what was hooking me. No grinding or paywalls or battle passes. Just gameplay that treats you like an adult with a functioning brain.

The Psychology Behind Tiles and Turns

Game developers love drawing flowcharts and mapping user journeys and calculating retention curves until we’ve got spreadsheets that would make an accountant weep with joy.

But sometimes we’re idiots about the basics.

I remember pitching a game concept in 2019 that got rejected for being “too simple.” The publisher wanted meta-progression and seasonal content and battle passes and everything that sounds good in a monetization meeting. Another studio eventually made that game, it completely flopped within six months, and probably cost someone around $340,000.

Meanwhile people still play dominoes. Have been for hundreds of years.

Here’s what your brain does during a good domino match: you’re making constant micro-decisions with incomplete information where you’ve got seven tiles and your opponent plays something and now you’re thinking three moves ahead while trying to remember what’s been played and managing risk versus reward. Pretty much identical to what we try creating in strategy games except dominoes does it with 28 pieces.

Rules take 90 seconds to learn.

What Retention Actually Looks Like

I’ve sat through way too many meetings where someone says “we need better retention” and the solution is always add more content, more levels, more characters, more events. But that’s not retention, that’s just delaying the inevitable moment when players realize they’re bored.

Real retention happens when someone closes your game and thinks about it three hours later. When they’re standing in line at the grocery store mentally replaying that move they should’ve made.

I asked 23 people in our office what games they actually play regularly outside of work. Seventeen mentioned word games or card games or board games. Only eight mentioned the big AAA titles everyone talks about at conferences.

Traditional games stuck around because they nailed something we constantly miss: immediate clarity of cause and effect where you play a tile and something happens and you understand exactly why. No hidden algorithms. No confusion about whether you won because of skill or because you spent money on gems.

Building Games That Don’t Need a Tutorial Video

I worked on a game in 2021 that required a seven-minute tutorial just to explain the basic combat system. Players still left reviews saying “I don’t get it” and our brilliant response was making the tutorial even longer.

Compare that to teaching someone dominoes where you say “match the numbers, can’t play means draw a tile, first person out wins” and you’re done. Three sentences total. But the actual strategy takes years to master and that’s where the magic lives.

Modern game development confuses complexity with depth constantly where we add systems because they sound impressive in design documents. But depth comes from meaningful choices, not from having 47 different currencies that all convert into each other at confusing rates.

You can play domino online right now and have a completely different strategic experience than me even though we’re playing identical rulesets. Some people play aggressively, some play defensively, both approaches work fine.

The Math Behind Simple Design

Our studio’s average development cost per hour of engaging gameplay is roughly $8,200. That’s what we spend creating content that keeps players interested for 60 minutes. Most of that content gets played once, maybe twice if we’re lucky.

Traditional games like dominoes figured out replayability accidentally because they didn’t have the option to add new content every season. The game had to be endlessly replayable with identical components. So the design focused on emergent complexity rather than scripted content drops.

I’m not saying we should all make domino clones. But we can steal the underlying principle: design systems that create different experiences through player interaction instead of through constant content updates that drain development resources.

When Players Become Students

You know what’s genuinely cool about watching people learn strategy games? They go through this visible progression where first they’re just trying to follow the rules, then they start seeing patterns, then suddenly they’re teaching other people advanced tactics they discovered.

I saw this happen with a junior developer on our team who’d never played dominoes before. She started playing during lunch breaks and within two weeks she was explaining probability strategies to people who’d been playing casually for years. The game rewarded her attention without requiring hundreds of hours of grinding.

That’s the learning curve that actually works. Gentle at first but with visible skill progression that players can feel happening. Not locked behind levels or purchases, just there in the gameplay waiting to be discovered.

Why We Keep Overcomplicating Things

Part of the problem is how we pitch games to publishers where you can’t walk into a meeting and say “it’s simple but deep” because that sounds like you haven’t done enough work. You need feature lists and monetization strategies and content roadmaps. The business incentives push toward complexity even when complexity hurts the actual game.

But players don’t experience feature lists. They experience moment-to-moment gameplay. And if those moments aren’t fun then no amount of meta-progression will save you from bad reviews and declining retention.

I’ve shipped four commercial games now. The one that performed best in terms of actual player satisfaction was the simplest. Had one core mechanic that we polished until it felt perfect. Everything else supported that mechanic. We cut probably 60% of our original design document and the game got better every single time we removed something.

The Business Case for Simplicity

Publishers want monetization opportunities and live service models and reasons to come back daily. But you can have all that without sacrificing clear engaging core gameplay that people actually enjoy.

Your monetization works better when the base game is genuinely fun. Players spend more when they’re enjoying themselves, not when they’re confused or frustrated or feeling manipulated. Seems obvious but I’ve watched studios design monetization first and gameplay second. Never works well.

The games that last aren’t usually the ones with the biggest marketing budgets or the most features. They’re the ones people actually want to play.

What I’m Doing Differently Now

Since my domino revelation I’ve been applying these ideas to our current project. We cut three entire systems that seemed cool in meetings but didn’t serve the core experience. We made the first match playable in under two minutes. We focused on making sure every decision feels meaningful instead of just filling time.

Simpler designs feel risky in pitch meetings where everyone expects elaborate feature presentations. But I’ve tested our current build with 31 people outside the studio and the average session length is 34 minutes. With zero meta-progression. No daily rewards. No login bonuses. Just gameplay that people want to keep playing.

I can’t promise this approach works for every genre. But I can tell you that forgetting the basics is a reliable way to build something nobody actually wants to play.

The next time you’re designing a game maybe spend an afternoon playing something that’s been around for centuries. Not for research necessarily. Just play it and notice what keeps you engaged. What makes you want another round. What feels satisfying about your decisions. Then ask yourself honestly if your current project has any of those qualities.

Because at the end of every design sprint we’re trying to create the same basic thing: an experience people choose to return to. And sometimes the best way forward is looking at what’s always worked.