Right Mistake-Making

1. The Passage from Lord of Light

Tim opens by reading a passage from page 253 of Roger Zelazny's Lord of Light, a book he first read in 1987 while in graduate school at UCI — four years before joining Interplay and a full decade before Fallout shipped. In it, the character Sam dismisses the idea that destiny guided his involvement in great events, attributing his role instead to "an accidental social conscience and some right mistake-making."

Tim explains that something in this passage spoke to him long before he understood why. Years of game development gave him the framework to decode it.

2. An Answer, Not The Answer

Tim has never shipped a game he considers perfect. Every game he's released contained something he didn't want — compromises forced by time, budget, or capability. Rather than viewing this as failure, he frames each shipped game as "an answer, not the answer."

The pursuit of a perfect crystallization of every idea is futile. There will always be things that don't work, things the team doesn't know how to do yet, problems that only get solved years later by someone else. Waiting for perfection means never shipping. The discipline is recognizing when you have an answer that's good enough to put in players' hands.

3. Being Near Lightning

Tim describes Fallout as "lightning in a bottle" — the right people, right place, right time, right backgrounds, right opportunity. None of it was planned. The game was nearly cancelled multiple times and went through significant personnel shifts.

After Fallout shipped, an angry former colleague called Tim to say: "I hope you realize you will never do anything like Fallout again. You were associated with this game being great, but you're not the cause of it."

Tim is grateful he didn't listen. That could have been his "give up moment." Instead, he went on to be associated with Arcanum, Vampire: The Masquerade – Bloodlines, Tyranny, Pillars of Eternity, and The Outer Worlds. He doesn't claim to be the cause of any of these games' quality, but after enough data points, the pattern becomes hard to ignore — he was a cause.

4. The Catalyst and the Lightning Rod

Tim connects this to his concept of the "catalyst" team member — someone whose presence, personality, or skill set makes everything around them work better. They aren't necessarily the designer, the lead programmer, or the producer, but the project is measurably better because they're involved.

Using the lightning metaphor: the lightning rod isn't the energy, but it draws the energy to where it needs to go. Tim believes he served as that lightning rod on several of his projects — not the sole source of creative power, but someone who helped channel and focus it.

He first noticed this trait in other people before recognizing it in himself: "I'm so glad we have that person here. Things are going way better because of that person."

5. Right Mistake-Making

The core concept: many of Tim's mistakes turned out to be great mistakes that led to better features and better games than would have existed without the error. This is "right mistake-making" — failing in ways that produce unexpected value.

Tim's advice is direct: don't be afraid to fail. You will fail, and you'll fail a lot. If fear of failure stops you after your first few attempts, you'll never continue. If it doesn't stop you but makes you miserable, you'll miss the lessons your failures are trying to teach you. Some of those failures will become your greatest successes.

6. References

• Tim Cain. YouTube video. https://www.youtube.com/watch?v=OVYAvMYrAlE