Abstract
Problem: How do game developers grow from their failures, and why might failures teach more than successes?
Approach: Tim Cain reflects on his career — spanning Fallout, Arcanum, Temple of Elemental Evil, and The Outer Worlds — examining specific failures and what each taught him about writing, team vision, taste, reputation, and self-awareness.
Findings: Success can mask weaknesses because you don't know which parts you "got lucky" with versus which parts you were genuinely good at. Failure forces you to confront specific shortcomings: misidentified strengths, fractured team vision, the subjectivity of taste, the fickleness of reputation, and the universal bias of being the hero in your own story.
Key insight: When you do something right, you don't always know why it's right — but when you do something wrong, you get a much better idea of how to do it right.
1. Success Masks Your Weaknesses
After Fallout's success, Tim believed he was a good writer because the Ron Perlman "War never changes" intro was so well-received. It wasn't until Temple of Elemental Evil got panned for its characters and dialogue that he realized there was a critical nuance: he writes short, directed, specific text well (cinematics, lore entries, manual sections), but dialogue and character writing are not his strength.
This distinction took years to identify. Fallout's success never forced him to examine it — only Temple's failure revealed it.
2. Team-Wide Vision Alignment Is Hard
On Fallout, the team naturally "gelled" around a shared vision. Tim assumed this would always happen. It didn't.
During Arcanum — made with many of the same people — major arguments erupted because team members had different ideas of what game they were making. The lesson: having a vision is not enough. Getting that vision communicated to and agreed upon by everyone is extremely difficult, and you can't take alignment for granted just because it happened once before.
By The Outer Worlds, Tim was much better equipped to actively communicate the vision to designers, programmers, and artists.
3. "Success Has Many Fathers, but Failure Is an Orphan"
Tim cites this ancient expression as a career truth. When a game succeeds, everyone wants credit — even people you've never met claim involvement. When a game fails, those same people vanish and prefer not to be mentioned.
He notes the irony: he learned far more about making good games from his "bad" ones, yet those are the projects nobody wants to be associated with.
4. Taste Is Subjective
Tim emphasizes that taste is subjective, and developers need to internalize this — not just acknowledge it intellectually. When someone says a game is "objectively bad" because it crashes, but another player saves frequently and loves the experience, neither is wrong. The game isn't universally bad just because it has a measurable flaw.
He compares it to walking into an ice cream parlor with 31 flavors and declaring only three are "good" — the other 28 exist because people genuinely enjoy them.
5. You're Only as Good as Your Last Game
After Arcanum underperformed relative to Fallout, publishers negotiated from a position of strength. After Temple's poor reviews, Tim stepped back from design entirely on Vampire: Bloodlines, telling co-owners Leonard Boyarsky and Jason Anderson he'd just handle code and HR.
This pattern repeated throughout his career: recruiters, publishers, and peers judged him almost exclusively on his most recent project, ignoring decades of work.
6. The Right People Make All the Difference
Different teams produce different results. When someone deeply cares about a specific aspect of a game — animations, lighting, dialogue, level layout — that part of the game feels distinctly polished and "cared for." Games made by different teams will naturally excel in different areas, reflecting the passions of the people who made them.
7. Not Everyone Will Like You
No matter how you act or how good your work is, some people will never like you and some will always support you. Often this has less to do with you than with them. Tim learned to accept this continuum rather than trying to win everyone over.
8. Everyone Is the Hero in Their Own Story
Leonard Boyarsky crystallized this insight for Tim: everyone is the hero in their own story. People naturally talk up their contributions, downplay their mistakes, and frame themselves as having always made the right call.
Tim combats this bias in several ways:
- Keeping detailed notes since his Interplay days, using them to ground his recollections in facts
- Reporting what people did, not why — avoiding speculation about others' mental states or motivations
- Taking blame openly for his own mistakes across multiple videos
- Being suspicious of "blameless" narratives — when someone never admits to doing anything wrong, that's a red flag
- Bringing other people on his channel (like Leonard Boyarsky and JT) to provide alternative perspectives on shared events, since even two people leaving the same meeting can have completely different interpretations of what happened
9. References
- Tim Cain. YouTube video. https://www.youtube.com/watch?v=Kh5JMp5_5nQ