Abstract
Problem: Why is informal conversation between co-workers so important in game development, and what happens when teams minimize it?
Approach: Tim Cain draws on decades of experience at Interplay, Troika, and Obsidian to explain the many forms workplace conversation takes and the tangible benefits it produces.
Findings: Conversation improves understanding of design issues, builds cross-discipline empathy, creates social bonds that prevent misunderstandings, and surfaces bugs before they reach QA. People who dismiss its value are often doing so to promote remote work, which Tim sees as disingenuous.
Key insight: Nobody benefits from zero interaction with co-workers — conversation isn't everything, but it's far from nothing, and even small amounts of informal talking dramatically improve project outcomes.
1. Tim's Relationship With Talking
Tim opens by acknowledging the irony: his "secret weapon" is talking, which isn't very secret given that his entire YouTube channel is him talking. He notes that a friend once compared him to a "babbling brook" rather than a "babbling idiot" — comforting in its own way.
Despite appearances, Tim is neither introvert nor extrovert. He scored essentially zero on introversion/extroversion tests twice. He describes having an "extrovert battery" — he can talk and engage, but when the battery runs out, he's done. At conferences he retreats to his hotel room or a speaker lounge to recharge.
2. Why Conversation Matters
2.1. Understanding Design Issues
When a co-worker — designer, programmer, or artist — asks questions about a design, it forces the designer to confront gaps. If a colleague doesn't understand something, players probably won't either. These conversations lead to better explanations and better designs.
2.2. Cross-Discipline Empathy
Tim has watched programmers gain genuine understanding of artists' workflows by sitting with them and observing tool usage. This leads to better tools, automated repetitive tasks, and eliminated friction points — improvements that would never surface from just looking at output files.
2.3. Social Bonds Prevent Conflict
When you know someone personally, you read their emails in their voice and give them the benefit of the doubt. Without that bond, people jump to the most negative interpretation of messages and start "flaming" each other. Tim has watched this pattern repeatedly: strangers clash over Slack and email, while people with even a small personal connection work things out smoothly.
3. The Many Forms of Conversation
3.1. Desk Drive-Bys
Some of the best problem-solving Tim witnessed came from five-minute chats at someone's desk. A quick "Hey, can I ask you about this quest?" could prevent a bug that would otherwise languish in QA for weeks.
3.2. Meetings (Yes, Really)
Tim acknowledges the "meetings are terrible" sentiment but pushes back. Don't throw the baby out with the bathwater. A 10-15 minute weekly meeting that forces people into the same room has real value, even when the content could technically be an email. The proximity matters.
3.3. Lunch and After-Work Activities
Sitting down with people over lunch — not talking about work — is where bonding happens. Tim admits he often skipped this because he had pets to care for at home, but recognizes its importance. After-work activities at Interplay included tabletop RPGs, computer games, and movies. Obsidian had clubs and a softball team that mixed departments, connecting people who would never otherwise interact.
4. Tim's Personal Examples
4.1. The Dog Walk at Troika
Tim's dog Chester came to the office daily, and the daily dog walk became an institution. Some people joined for the spectacle (Chester had what people called a "poop posse" — he would deliberately make eye contact with different people while doing his business). Others saw the walk as a chance to get 20 minutes alone with Tim.
One colleague used a solo dog walk to discuss a sensitive personnel issue — something he didn't want to bring up in Tim's office behind a closed door where everyone would notice and speculate.
4.2. Chocolate Meetings at Obsidian
Every day at 3 PM, people would gather in Tim's office for 10 minutes to eat chocolate. Artists, designers, and programmers came on different days, but the informal mixing created connections across departments. Tim ate more chocolate than his doctor recommended, but considered it worthwhile.
4.3. Racquetball at Interplay
The best racquetball player turned out to be from accounting — someone Tim would never have interacted with otherwise. They played weekly, and it became one of Tim's favorite workplace connections.
5. The Remote Work Tension
Tim directly addresses people who minimize the value of co-worker interaction, arguing they're usually doing so to promote remote work. While he supports remote work (and has a separate video on it), he pushes back on the extreme position. Anyone who is 100% for or against something is "usually trying to sell you something."
His core claim: nobody is better off with zero interaction. People need it to varying degrees, but the floor is not zero.
6. Conversation Has Limits
Tim balances his argument by acknowledging that talking has its limits. At some point you need to stop talking and start doing. Ideas are great, but until you implement one, it's just "nebulous."
He invokes the philosophical concept of qualia: experiencing something teaches you far more than any description of it. Holding, smelling, and eating an apple teaches you more about apples than any amount of reading or conversation. The same applies to game development — you have to actually do it, not just discuss it endlessly.
7. The Takeaway
Talk to your peers, co-workers, and friends about game development. It will help your work. It isn't everything. It won't solve all your problems. But it's not nothing.
8. References
- Tim Cain. YouTube video. https://www.youtube.com/watch?v=int5XZHsgiU