Idea Battles

Abstract

Problem: How should game development teams handle passionate disagreements over creative decisions, and what makes these debates productive vs. destructive?

Approach: Tim Cain reflects on decades of "idea battles" across Fallout, Arcanum, Carbine/WildStar, and The Outer Worlds, sharing specific examples of debates won, lost, and derailed.

Findings: Productive idea battles require psychological safety, separation of ideas from personal attacks, and willingness to lose gracefully. When someone resorts to personal attacks, they've run out of ideas. The best debates sometimes produce outcomes nobody originally proposed.

Key insight: The moment someone personally attacks another person in a creative debate, they've already lost — they have no ideas left to defend, only egos to protect.

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

The Nature of Idea Battles

Tim Cain defines "idea battles" (a term he adopts from the viewer who asked the question) as passionate debates where team members advocate strongly for their creative ideas. These aren't fights where people are upset — they're discussions where people "go to bat" for their ideas. He's been having them for decades without ever naming them.

Fallout: The Ending That Almost Wasn't

The Original Happy Ending

Fallout originally had a straightforward ending: you retrieve the water chip, defeat the mutant army and the Master, return to the vault, there's a party, game ends. Then Leonard Boyarsky came in with a different idea — the player gets kicked out of the vault.

Losing Gracefully

Cain's first reaction was "What? No, we can't do that." But Boyarsky argued passionately for it, and ultimately won. Cain says this was the first time he experienced a meeting where someone passionately wanted something and had to convince him against his initial resistance. He lost that argument, and he's glad he did — it became one of Fallout's most iconic moments.

Fallout's Early Development Culture

The early Fallout team had evening meetings (since nobody officially worked for Cain yet) where they'd throw out ideas freely. For a while, the game was going to be a "time-traveling dinosaur game." These meetings worked because everyone was collaborative, nobody expected immediate decisions, and people were genuinely open. Cain didn't realize at the time how special that dynamic was.

Arcanum: The One-Point Fiasco

The Cost Debate

Arcanum originally used a scaling cost system — higher-level skills and spells cost more points. Players earned multiple points per level, and the highest abilities required saving across multiple levels. Cain liked this system because it created anticipation and meaningful choices.

Cain vs. Everyone

Every other person on the team wanted a flat one-point-per-rank system. They shipped with the one-point system. Cain still believes it has balance problems — if a level-five spell costs the same as level one, why wouldn't you just rush to the top of a spell college? It made generalist builds less interesting. He admits the community largely likes the one-point system, making this a battle where he may be on the wrong side.

The Passion Problem

Arcanum taught Cain an uncomfortable lesson. He wasn't invited to the tech schematics design meeting. He later learned that his passionate arguing style was off-putting — not because people thought he was wrong, but because they felt they couldn't win against someone who presented arguments so animatedly. People worried their quieter advocacy would always lose to his excitement, regardless of idea quality.

Cain reflects that he wishes he'd asked for the same accommodation people ask for today: "This is just how I am. If you want to make games with me, this is how I am." When he's excited about your design, you'll love it. When he's excited about his own and you disagree, you'll hate it.

Temple of Elemental Evil and Vampire: Bloodlines

These two Troika games had essentially no idea battles. Temple of Elemental Evil was made so quickly there was no time for major design meetings — a programmer and artist designed the excellent turn-based UI independently, showed it to Cain, and it went straight in. For Vampire: Bloodlines, Cain joined so late that all decisions were already made; he primarily wrote AI code.

Carbine and WildStar: When Battles Turn Toxic

The Personal Attack

At Carbine, during a discussion about game design, someone came into Cain's office and said: "I hear you're a really bad designer. I hear you suck at design."

The Revelation

This moment crystallized a key insight: when someone makes a personal attack during an idea battle, it means they're completely out of ideas. Their idea isn't strong enough to defend on its merits, so they attack the person instead. Cain sees the same pattern online when people call designers or writers "stupid" — they've run out of substantive criticism.

The Hard Rule

Cain now enforces a strict policy: if someone insults another person during a brainstorm, they're asked to leave. They can email their ideas later, but they're cut from the live discussion. This isn't just about protecting himself — it's about ensuring everyone else feels safe contributing ideas without fear of personal attack.

The Lasting Damage

Carbine left Cain so "shellshocked" and "traumatized" that he avoided inserting himself into design discussions for most of his time at Obsidian. When working on Pillars of Eternity with Josh Sawyer, Cain told him: "If I have an idea and you don't like it, I won't bring it up again." He broke that rule exactly once, revisiting one idea — Sawyer still didn't like it, and it didn't go in.

The Outer Worlds: Healthy Battles Return

Co-Directing with Boyarsky

Idea battles resumed on The Outer Worlds because Cain was co-directing with Leonard Boyarsky. They'd discuss ideas in their shared office, working through problems on a whiteboard. Obsidian staff thought they were arguing, but they were actually stress-testing ideas: "Will this break that system? Do we have time? If it's your idea, you figure out the problems."

The Ownership Principle

Cain's rule for idea advocates: if you propose an idea, you own fixing its problems. He'll help if he likes your idea better than the current one, but you can't propose something and expect him to solve all its issues. If you're trying to convince him, your idea better not have major unsolved problems — or you better have a plan to fix them.

Companion Diversity

At one point, all companion submissions except the robot and the priest were LGBT. Cain pushed back — not against representation, but against homogeneity. The same way he didn't want all companions to be sarcastic or all to have amnesia, he didn't want them all to share one trait. They picked Parvati, and the rest were adjusted.

The Encumbrance Debate

Someone proposed removing encumbrance entirely. Cain outlined the cascading problems: encumbrance was tied to an attribute, had associated perks, and removing it would require solving infinite inventory UI — effectively shifting player complaints from one system to another.

The Ammo Debate and Respecting Different Minds

A designer proposed making all ranged weapons ammo-less. Cain disagreed because ranged weapons already had major advantages over melee. But what struck him most was how differently this designer thought about games. His ideas weren't opposite — they were orthogonal. Cain told him: "This isn't what I'm thinking for this game, and because I'm director, I win. But I want to play a game where you're the lead designer, because I'd like to see what that game looks like."

Lessons from Decades of Idea Battles

Personal Attacks Signal Defeat

The clearest signal that someone has lost a creative argument is when they attack the person instead of the idea. This applies equally in professional settings and online discourse.

Passion Is a Double-Edged Sword

Animated advocacy can inadvertently silence quieter voices. People may assume the louder argument will always win, even if the quieter idea is better.

Losing Can Be Winning

Cain's best example: losing the Fallout ending debate to Boyarsky produced one of gaming's most memorable moments.

Different Thinking Has Value

Ideas that are orthogonal to your own aren't threats — they're windows into games you'd never make yourself. Respecting fundamentally different design philosophies enriches the whole industry.

References