Abstract
Problem: Developers often receive feedback telling them something is "bad" or "good," but without understanding why someone feels that way, the feedback is nearly useless for making improvements.
Approach: Tim uses an extended movie analogy — a film that tests poorly despite universal praise from its creators — to demonstrate how missing context can make feedback misleading, then connects this to game development and the broader question of whether "bad games" truly exist.
Findings: The movie's poor reception wasn't because it was bad — it was because critical story details depended on whispered dialogue and tiny visual cues that only front-row viewers could perceive. Once the viewing context changed (smaller room, closer seats), approval jumped from 5–10% to 95%. The what of the feedback ("I didn't like it") was the same, but the why ("I couldn't follow it") completely changed how to address it.
Key insight: Understanding why someone dislikes something is just as important as knowing what they dislike — the context behind feedback determines whether you need to fix a feature, remove it, or simply accept that it's not for everyone.
The Movie Theater Analogy
Tim opens with an extended hypothetical: you're making a movie, and during production everyone loves it — the script writers, actors, crew, cinematographer, and editor all agree it's fantastic. You do a focus test screening for 400 people. Only 5–10% like it.
You're stunned. You run another test with questions — same result. The small minority who love it praise the plot, characters, and cinematography. The 90% majority say they couldn't follow it at all.
Discovering the Root Cause
For the next screening, you go inside and watch the audience instead of the movie. You notice something striking: only people in the first row or two are engaged — leaning forward during dramatic scenes, laughing at jokes. Everyone else is checked out.
You sit in the back row yourself and realize the problem: a huge chunk of the movie's context depends on whispered dialogue and tiny visual details — an object on a desk in the background, text written on the side of a book, subtle movements. From the back of a 400-seat theater, these details are invisible.
You make the next focus group smaller, everyone sits up front — suddenly 95% love it.
Lessons from the Analogy
It's Already Too Late (It's Really About Money)
By the time you discover the problem, the movie is finished. You can re-record the whispered dialogue at higher volume (ADR), but reshooting scenes to make background details more visible? That's not happening. Tim connects this directly to game development: you should have made a prototype, a vertical slice, or a "beautiful corner" and tested it with people during production — not after the whole thing is built.
It's Not a Bad Movie
The people who did catch the details loved it. This leads to Tim's recurring philosophy: "There are no bad games, just bad games for you." If you disliked a game that others loved, maybe you missed details that would have made it click — or maybe you just needed to play past the first hour or two.
Broad Appeal vs. Niche
Developers can design for broad appeal through familiar characters, tropes, and settings. But some players specifically love niche games and feel special for appreciating them — broad appeal would actually drive those players away. If you're targeting a 90% approval rate, broad appeal is the path. But you'll lose the niche audience.
Context Beyond the Product Itself
Tim identifies several external factors that affect how a game or movie is received, none of which have anything to do with its quality:
- Marketing: A great product that wasn't marketed well may be discovered later (on video/streaming) and find its audience
- Competition: Releasing an RPG at the same time as a bigger RPG means the bigger one gets all the money, eyeballs, reviews, and attention — yours looks lesser by comparison even if it's good
- Timing/Season: A Christmas movie in spring, a beach movie in winter — wrong context for reception
- The Bloodlines Example: Vampire: The Masquerade – Bloodlines launched poorly and wasn't well-liked, but grew a devoted following over time. Yes, bugs were fixed, but the things people ended up loving were always there. Was it a bad game?
Games That Age Poorly
The reverse is also true: beloved games can be looked back on 10–20 years later and dismissed for "old school mechanics" and "bad graphics." Tim asks: is it still a good game? Did it become bad? Or are people just applying a modern lens to an old product?
The Core Message
When someone gives you feedback — "I didn't like this feature" — you now know what isn't liked. But why they don't like it determines everything about how you respond:
- If 5% of players dislike something but 95% love and seek it out, you can't really "fix" it. Accept that 5% won't buy your game because of that feature.
- If players don't like a feature but their reason points to something fixable without removing the feature, that's a completely different situation than cutting and replacing it.
The why behind feedback is just as important as the what. Context changes everything.
References
- Tim Cain. YouTube video. https://www.youtube.com/watch?v=0wBEMGov0HY