Abstract
Problem: What is the biggest lesson Tim Cain learned across decades of game development?
Approach: Tim reflects on his career experiences with teams — from D&D in high school to engineering school to professional game studios — sharing specific stories of deception at every organizational level.
Findings: The hardest lesson is brutally simple: people lie. Employers, employees, and peers all lie — sometimes knowingly, sometimes to themselves first. Yet paradoxically, the most fulfilling part of game development is the very same teamwork that produces these betrayals: collaborating to create something no individual could make alone.
Key insight: "Trust but verify" — always get things in writing, ask direct questions, and check the evidence, while still embracing the creative magic of team collaboration.
The Lesson: People Lie
Tim's biggest lesson, learned and relearned over decades, is two words: people lie. He's been told repeatedly by industry colleagues that he's "naive and optimistic" because this keeps catching him off guard.
The Forms of Lying
People lie in several ways:
- Direct fabrication — looking you in the eye with a smile and stating something completely false
- Lying by implication — carefully constructing statements where nothing is provably false, but leading you to a false conclusion, then claiming "I never actually said that"
- Lying to themselves — people who genuinely believe their own lie, so they're not consciously deceiving you — they've deceived themselves first and are passing it along "by proxy"
Red Flag: Verbal Only
If someone won't put something in an email but will only tell you verbally, they're probably lying. They want deniability.
Examples From Tim's Career
"I'm On Top of This"
One of the biggest lies Tim encountered: people claiming they're making progress on work they haven't even started. They'd say "yep, it'll be done on time" when they hadn't written a single line of code, drawn a single pixel, or typed a single word. In the era of Perforce and managed check-ins, Tim could verify — "you say you've started, but I see no check-ins for a month." The response: "I'm doing research... it's in here" (pointing to their head).
Promises to Stay
Employees would promise to finish a project and then leave. They'd look Tim (or their boss) in the eye and commit to staying, with seemingly good reasons. In every case Tim describes, they left anyway — not because schedules changed, but because they simply lied about their intentions. One person stayed only long enough to get their name in the credits, then parlayed that credit into a better job elsewhere.
The Counter-Offer Betrayal
Tim watched someone receive a counter-offer from their company that met and exceeded the competing offer. The employee asked for it in writing — then took that written offer to the other company, got an even better deal, and quit anyway. Tim notes he's not saying people shouldn't negotiate, but there are consequences: "If people don't believe you anymore after this, that's a consequence."
The "Experiment" Firing
Tim was told a level-building experiment — with different teams trying different approaches — was purely experimental. "No one's going to get fired over this." He was excited; no company he'd worked at had done anything like it. One team was a clear winner. Ironically, they didn't adopt that winning team's approach. Instead, Tim was ordered to fire someone deemed "redundant" based on the results.
Tim told his boss he would never do that again, and threatened to quit on the spot if ordered to repeat it. After Tim left that company, his boss told the fired employee that Tim had wanted him gone and that the boss had saved his job — a complete inversion of the truth. Tim believes the boss realized the employee was actually good and wanted to keep him, so he rewrote history.
People Accept Lies Too
Beyond the liars themselves, Tim observes that many people are eager to accept lies without verification: "Your lie coincides with what I believe, so I'm not even going to try to verify it." Confirmation bias makes the problem worse.
The Counterweight: The Joy of Creating
Despite this harsh lesson, Tim says the most fulfilling thing about game development is the act of creating — specifically, building a new IP from scratch with a team.
- Fallout was super fun
- Arcanum was the deepest and most intense creative experience (because Leonard Boyarsky handled most publisher relations, freeing Tim to focus entirely on the game)
- Wildstar, Pillars of Eternity (to a lesser extent), and The Outer Worlds were all gratifying
Tim thinks this is why he tends to move on after each game rather than pursue sequels — "the most amazing part was just done."
What Makes Team Creation Special
- You make something bigger than any one person could have made alone
- Someone else might have a better idea than yours that improves the game
- Others have technical or artistic skills to realize ideas you couldn't execute yourself
- In great brainstorming sessions, ideas emerge from the group — no single person can claim ownership
- Intense joint debugging sessions that he remembers decades later — finding an egregious bug and suddenly the game runs 10 FPS faster
The Paradox
The same source — working in teams — produces both Tim's hardest lesson (people will lie to you) and his most fulfilling experiences (creating something amazing together). He wouldn't trade the collaboration despite the betrayals.
His practical advice: trust but verify, ask for things in writing, and keep your optimism while staying vigilant.
References
- Tim Cain. YouTube video. https://www.youtube.com/watch?v=GqNcNtxHU6E