The Balance Problem: Why Games Are Never Really "Finished"
The success of a game depends, in part, on balance, and designers spend countless hours trying to get it right. Even the most brilliant mechanics or story can fall flat if the experience feels unfair or inconsistent. A gorgeous world with broken combat is a world nobody wants to stay in. A deep narrative built on a trivially easy system is a book with extra steps.
Balance is hard to get right and easy to get wrong. You can't "add more balance" any more than you can "add more fun." It is a property, not an ingredient - it emerges from the relationships between every system in your game, which means you can never work on it directly. You work on the pieces and hope balance appears. Because systems are interconnected, fixing one imbalance often shifts half a dozen others, which is why patch notes for live games read like archaeology: "We nerfed this because last patch we buffed that because the patch before that we changed something else that we thought was unrelated."
Think of balance like swapping a gear in the center of a machine. You are not tuning one component in isolation - you are affecting every connected system around it. Increase a class's damage by 5% and suddenly their best weapon is broken, their worst weapon is viable, their counter-class is unplayable, and three PvE encounters have new speedrun strategies.
If you ask 100 designers what balance is, you will get 90 different answers - and the other 10 will tell you it's a trap question. Balance is, first and foremost, a feeling, and you know it when you feel it:
"That boss battle was way too easy."
"This weapon is way overpowered."
"This character class was nerfed too much."
"Bloodborne is super challenging, and it's supposed to be."
"Betrayal at House on the Hill is a lot of fun. Totally unbalanced, but fun."
Notice the last two. "Challenging but fair" and "totally unbalanced but fun" are both compliments. Balance isn't the same as difficulty, and it isn't the same as symmetry. A perfectly balanced game can feel sterile. A wildly lopsided one can be a classic. The target you're aiming for isn't "equal" - it's "right for this experience." And that target moves.
Balance Is Contextual
Game balance is a gray area. What one designer or player considers balanced, another may not. The same mechanic - say, permadeath - is a feature in roguelikes and a disaster in a casual family game. Genres change expectations, and within a genre, modes change them again. What is right for an RTS might be wrong for a roguelite. What is right for an RTS's ranked mode might be wrong for that same RTS's campaign.
There is no single answer that rules them all. "Balanced" can refer to individual cards in a deck-builder, character classes in an MMO, units in an RTS, or the overall feel of an entire game. It can mean "every option is equally viable" (competitive Starcraft's ideal), "no option is clearly dominant across all situations" (Magic: The Gathering's ideal), or "the player always feels challenged but never helpless" (Dark Souls' ideal). Those are three completely different problems with completely different solutions, and calling all three "balance" is a big part of why designers end up talking past each other.
This is also why "balance patches" mean wildly different things in different games. A balance patch in League of Legends might nerf two champions and move on. A balance patch in a single-player RPG might mean re-tuning enemy HP across 60 hours of content. A balance patch in a co-op board game might mean reprinting cards. Same word, different planets.
Balance as Metaphor
Balance is a metaphor we borrow from scales, but you can't weigh monsters on one side and loot drops on the other to know whether the experience is right. The scale metaphor suggests symmetry - two equal weights - and symmetry is almost never what you actually want.
Single-player and co-op games that feel balanced often tilt slightly in the player's favor, even as mastery increases. The player should usually win, but winning should usually feel earned. Spelunky doesn't give you a fair fight - it gives you a death trap that you can eventually beat if you get good enough, and the slight tilt toward "the game is trying to kill you" is exactly what makes victory mean something. Meanwhile, God of War tilts hard the other way: Kratos is a god, the fantasy is power, and if the fights were "fair" the whole tone would collapse.
Competitive PvP games are where the scale metaphor comes closest to fitting - but even there, pro players will tell you that perfect symmetry makes for boring matches. Chess is technically balanced but white has a small advantage. Street Fighter tournaments are balanced overall but every character has matchups they dread. The scale is never quite level, and the tiny tilt is often where the interesting strategy lives.
Balance as Interdependency
Change the metaphor from a scale to an engine. If the gears run perfectly and you enlarge one gear, the others fall out of sync. That's why designers constantly revisit systems they thought were finished - new changes ripple backwards.
World of Warcraft has been running this engine for over 20 years, and every expansion is a story of gears falling out of sync. A new tier of gear drops and suddenly raids from two expansions ago trivialize in seconds. A new class gets added and the roster of dungeon roles reshuffles. A mount gets a small speed buff and PvP map timings change. None of these were bugs. They were the inevitable consequence of touching one gear in a machine with a thousand of them.
If player characters start too powerful, every other system may need to adjust to that lesser starting state. The enemy HP curves. The loot drop rates. The pacing of ability unlocks. The emotional arc of the story - because "becoming strong" is hard to feel if you were already strong on day one. Balance is a dance of give and take until the whole experience feels right.
Why Balance Is Never "Done"
Here's the uncomfortable truth every live-service team learns: balance isn't a state you reach. It's a process you commit to.
A single-player game that ships in 2025 is balanced for the players of 2025 - their skill levels, their expectations, their familiarity with the genre. Five years later, those players have played a hundred more games, learned a hundred new tricks, and the same game feels different. Dark Souls was considered brutal in 2011. The same game, unchanged, is widely considered medium-difficulty now, because an entire generation of players grew up on its DNA.
For multiplayer games the problem is even worse, because the playerbase isn't just getting better - it's actively collaborating against the designer. The Reddit threads, the YouTube breakdowns, the Discord meta discussions, the pro players live streaming optimizations to 50,000 viewers. Every week the community gets smarter about your game. Every week the "correct" strategy shifts slightly. Balance decays on its own just from being observed.
This is why the designers who handle balance best aren't the ones with the cleanest spreadsheets. They're the ones who accept that balance is a relationship with their players, not a property of their game. They ship, watch, adjust, watch, adjust again. They build tools that let them change numbers without rebuilding systems. They read patch notes from other teams to see what went wrong and why. And they accept, deep down, that the game is never actually done - just done for now.
The Takeaway
Balance is the invisible architecture of every game that feels good to play. You notice it most when it breaks, which is ironically the one time designers get credit for it - when they fix what their previous patch broke. The rest of the time it's just called "the game."
If you're designing one, the best advice isn't a formula. It's a disposition: stay curious, stay humble, assume every change will ripple further than you expect, and build systems that are easy to tune, because you'll be tuning them for as long as anyone is playing.