his post is inspired by a piece on the Itembase Dev's blog. I wanted to expand on the ideas there because they nail something designers wrestle with constantly.
Saying a game is "balanced" is about as precise as saying it's "fun." Everyone nods, nobody agrees on what it actually means. But there is a practical framework hiding behind the vagueness, and it starts with three dials.
The Three Dials
Every balance conversation, whether you're tuning a single boss fight or a full free-to-play economy, comes down to three variables:
Difficulty — Is it too easy, too hard, or just right? This isn't only about combat. It's the cognitive load of a puzzle, the pressure of a timer, the friction of a crafting loop. A game can be mechanically simple and still feel brutally difficult if the decision space is overwhelming.
Quantity - Are there too many or too few of something? Resources, enemies, loot drops, skill points, players in a lobby. Quantity problems are sneaky because they rarely announce themselves. They show up as boredom (too few meaningful choices) or paralysis (too many).
Timing - Are things arriving when the player expects them? A reward that lands three minutes late feels stingy. A difficulty spike that hits before the player has the right tools feels unfair. Timing is the dial that separates a game that "flows" from one that "drags."
These three dials interact with each other constantly. A generous quantity of healing items can mask a difficulty problem. Perfect timing on power-ups can make a brutal encounter feel fair. The art is in how they combine.
Dials Without Context Are Meaningless
Here's the part many balance discussions skip: the dials only work when you know what range to set them in. Three modifiers define that range.
Target audience. A family board game and a competitive strategy title can both be perfectly balanced, but for completely different pressure thresholds. What feels "just right" for a casual mobile player would bore a hardcore optimizer, and vice versa. Knowing who you're building for isn't a marketing question — it's a balance question.
Designer intent. A masocore platformer and a meditative exploration game should not share the same difficulty curve. The intended emotional arc dictates what "balanced" even means. Dark Souls is balanced. Animal Crossing is balanced. They have almost nothing in common mechanically.
Purpose. This is the uncomfortable one. Are you balancing for fun? For session length? For retention? For monetization? These goals overlap, but they also conflict. A system balanced for maximum monetization pressure will feel different from one balanced for pure player satisfaction. Being honest about your purpose keeps you from accidentally building something that feels manipulative.
Progression Is the Silent Test
Players might not articulate it, but they notice when difficulty flatlines. A common design baseline is something like "each level should feel roughly twice as demanding as the last." The exact ratio varies, but the principle holds: by the time a player finishes one challenge, they should be psychologically tuned for the next step up.
When progression stalls, the game feels "off" even if individual encounters are well-designed. Players describe it as the game getting boring or repetitive, but the real issue is that the difficulty-to-skill ratio stopped moving.
The Chess Problem
Is chess balanced? It's been played for centuries, and at elite levels, white has a measurable (possibly psychological) first-move advantage. This raises an interesting point: more skill can reveal more imbalance, not less. Experts exploit asymmetries that beginners never notice.
But in multiplayer games, skill itself can be a balancing mechanism. In Catan, experienced players instinctively refuse to trade with the leader, which reins in runaway advantages. Novices don't do this, so the same game feels less balanced at lower skill levels.
This means "balanced" isn't a fixed state. It's a moving target that shifts with the skill level of your players, which loops right back to knowing your target audience.
So How Do You Actually Know?
You playtest. Relentlessly. You watch where players quit, where they get stuck, where they skip content, where they stop spending (or start spending too much). You build dashboards that track the dials — difficulty curves, resource accumulation rates, time-to-reward — and you compare what you see against what you intended.
Balance isn't a destination. It's a practice. The dials are difficulty, quantity, and timing. The range is set by audience, intent, and purpose. Everything else is iteration until the feeling clicks.
Top comments (0)