How To Receive Criticism

tim-cain game-development criticism feedback advice soft-skills

Abstract

Problem: How should game developers handle criticism of their work?

Approach: Tim Cain draws on decades of experience shipping games like Fallout, Arcanum, and The Outer Worlds to share his philosophy on receiving feedback — both from professional reviewers and players.

Findings: The core advice is deceptively simple: listen. Don't deflect, don't hide behind how hard the work was, and don't dismiss critics for not being developers themselves. Aggregate feedback, look for patterns, and act on recurring complaints.

Key insight: Effort does not equal greatness. You can appreciate someone's hard work while still acknowledging the result needs to be fixed.

Source: https://www.youtube.com/watch?v=Gtcl1ZbWyX8

1. No Game Ships Perfect

Tim opens by acknowledging that none of his games shipped in the state he wanted. This isn't just about bugs — crash bugs, slowdowns, quest-blockers — but also design problems he recognized but couldn't fix before release. Examples include the spell cost system in Arcanum (which never got a balancing pass), EA registration in Fallout, and the Temple of Trials in Fallout 2 (which he didn't want at all).

1.1. Why Games Ship With Known Problems

Three reasons things ship in a state the designers don't like:

  1. Priority and money — You run out of time, which really means you run out of money. When the deadline approaches, you prioritize crash bugs, then quest-blocking bugs, then everything else. Design polish often doesn't make the cut.
  2. Scale blindness — Games are so large that even after 16 playthroughs (as Tim did with The Outer Worlds), you still don't see everything. Items, dialogue lines, icons, names — the sheer volume means things slip through.
  3. Shared authority — No developer has 100% final approval on everything. Every game Tim made had something in it that someone else put in or insisted on keeping, against his wishes.

2. The Core Advice: Listen

Tim's advice on receiving criticism is one word: listen.

Read all the reviews. Read Steam comments and forum posts. You don't have to follow every piece of feedback — not all criticism is good or accurate. Some people are having a bad day, some are viewing the game through a lens that distorts its intent. But if you see the same criticism appearing frequently about a specific feature, there's probably something genuinely wrong.

2.1. Players Smell Problems Even If They Can't Fix Them

Tim echoes a point from his companion video on giving feedback: players may not know how to fix a problem, but they can certainly identify that something feels off. Reviews also often mention what they liked, giving developers a balanced picture of what's working and what isn't.

3. "Effort Does Not Equal Greatness"

Tim recounts being pulled aside by a superior and told not to critique a colleague's feature because "that guy worked really hard on it." His response: effort does not equal greatness. You can appreciate the effort while still insisting the result needs to be fixed. The idea that hard work should be immune from criticism simply doesn't hold up.

3.1. The "Game Development Is Hard" Deflection

Tim criticizes developers who respond to reviews with "I'd like to see this reviewer make a game" or "he's never made a game before in his life, how dare he review mine." This is a mistake. Reviewing products is what reviewers and customers do. Similarly, some developers deflect by citing how hard the work was, how bad the design spec was, or any other excuse to avoid confronting that the final product isn't good enough.

4. Stating Opinions as Facts

Tim notes that some people — both developers and commenters — state their opinions as if they were engraved in stone. His observation: you don't come across as a thoughtful person when you do this, and you will be rightfully critiqued for it. Even Tim's own channel advice is explicitly narrow: it's for people who want to make nonlinear RPGs, not universal law.

5. Summary

The video distills to a simple framework: listen to criticism, aggregate it, look for patterns, and act on recurring issues. Don't let ego, effort, or authority shield you from legitimate feedback. Not every critique deserves action, but persistent ones almost certainly do.

6. References