“Happiness writes in white ink on a white page.”
— Henry de Montherlant
There are always more negative reviews than there are unsatisfied customers. This is as true for video games as it is for anything else.
There’s nothing surprising about this: we tend to be much more vocal when something bothers us, yet remain silent when we’re satisfied. But I’m not here to moralize — to call us all ungrateful, yapping babies. We might be, but that wouldn’t be a particularly useful conclusion.
Instead, I want to explore two practical questions about this tendency:
- Why are we like this?
- As reviewers and creators, should we do something about it?
Why (I Think) We Are Built This Way
Learning anything requires two signals: knowing what works and knowing what doesn’t. You need both — but here’s the tricky, often-overlooked part: these two signals aren’t symmetrical. It’s much easier to pinpoint what makes us uncomfortable than to articulate what brings us joy.
You can immediately tell that cilantro is ruining your guacamole. But describing what made last night’s taco tastier than the one you had the day before? That’s much harder. You can explain in precise detail why a game’s controls feel laggy — the input delay, the animation priority, the buffer window. But explaining why a game feels good? You’d have to somehow gesture at everything at once: the responsiveness, the pacing, the way the systems interlock, the mood, the sound design. “It just feels right” is the best most people can do, and it’s not because they’re lazy. It’s because they’re trying to describe something that resists compression.
The reason, I think, is dimensional. Badness is low-dimensional — a single broken element is enough to ruin the experience, and you can point straight at it. Goodness is high-dimensional — every component has to align, and the thing that makes it work isn’t any one part, it’s the relationship between all of them. A broken string is easy to identify. An orchestra playing in tune is something you can only hear as a whole.
This is why negative reviews write themselves. One-star Steam reviews are often detailed, articulate, and persuasive — “the hitboxes are broken, the camera fights you in tight spaces, the checkpoint system wastes your time.” Five-star reviews? “This game is a masterpiece. Just play it.” The negativity isn’t because people are ungrateful. It’s because what’s wrong is describable, and what’s right often isn’t.
So What Do We Do With This?
Here’s the thing: this asymmetry isn’t a bug. It’s genuinely useful. A negative review that says “the input lag makes combat feel unresponsive” gives a developer something to fix. A positive review that says “the combat feels amazing” gives them… a compliment. Negative feedback is more actionable precisely because it’s low-dimensional — it points at a specific thing that can be changed.
But it’s also incomplete. If all you have is negative feedback, you know what to stop doing — you never learn what to keep. You can patch every flaw your players identify and still end up with a game that lost whatever made it special, because nobody could tell you what that was. They just knew it was there.
This is the hard part. You can’t build a complete theory of why a beloved game works. You can only reason by subtraction — if this element were missing, people would love it less. But subtraction never gives you the full picture, because the thing that makes a game great isn’t any single element. It’s the relationship between all of them. Remove nothing, and you still can’t explain it. That’s what high-dimensional means in practice: the goodness lives in the configuration, not the parts.
So if negative feedback can’t tell you what’s working, and positive feedback can’t articulate it either — how do you protect the thing that makes your work good?
You learn to feel it first. Much of the path to making something great is intuitive — you play the games you love, you make your own, you develop a sense for what works through repetition and attention. That sense is real, and no theory can replace it.
But intuition alone is fragile. It’s how you find what works — but theory is how you keep it. How you protect it from being lost when the project grows, the team changes, or the scope expands beyond what any one person’s gut feeling can track. The two aren’t in competition. They’re sequential: feel it first, then write it down.
It’s okay if your players can’t perfectly articulate why they love your work. But if you can start to — even imperfectly — that understanding becomes something you can build on, share with collaborators, and check against when the pressure of a bigger project threatens to erode the very thing that made people love it in the first place.
Goodness writes in white ink. But that doesn’t mean you can’t learn to read it.