Authority Without Responsibility

tim-cain game-development management leadership production team-dynamics

Abstract

Problem: In game development, people in positions of authority (directors, VPs, executives) often push features into games they have no responsibility for — taking credit when things go well, and disappearing when they don't.

Approach: Tim Cain describes the pattern from decades of firsthand experience across multiple studios, detailing the exact tactics used and the outcomes for those on the receiving end.

Findings: This "authority without responsibility" dynamic is pervasive across the entire industry (and likely others), has existed for decades across all generations, and has no clean solution. It acts as a counterbalance to the developer caution problem Cain discussed in earlier videos.

Key insight: The only thing you can control is yourself — push back on bad features, support good ones, and always do what you think is best, even when authority figures try to override you.

1. Context

This video is Tim Cain's response to the popularity of his earlier "caution" videos, where he argued that developers are too cautious — over-polishing, overestimating timelines, and shipping games with fewer or less interesting features than they could have. Those videos were well-received but drew criticism that he was "punching down" at team-level developers. This video, he says, is about "punching up."

2. The Pattern

Authority without responsibility follows a predictable three-step escalation:

2.1. Step 1: The Direct Approach

Someone in a position of authority (a lead's lead, a VP, someone in administration) approaches the team lead and suggests a feature that isn't in the design doc. When the lead pushes back with concrete reasons — "we considered this, it causes these problems, other games had these issues" — the authority figure dismisses the concerns: "I don't think it'll cause that problem" or "I'm sure you can fix that." When told to solve the problem themselves, they don't like the pushback and may remind you of their position.

2.2. Step 2: The End-Run

If the direct approach fails, the authority figure goes to individual team members and lobbies them directly. They use fear-based arguments: "Other games have this feature," "We'll look old-fashioned," "People will wonder where this is." Once team members are convinced, they come to the lead themselves — and now it's no longer the manager's request, it's the team's. There's strength in numbers, and it becomes very hard to resist.

2.3. Step 3: The Order

If lobbying fails, some managers will simply order someone on the team to implement the feature, bypassing the lead entirely. They may even say "don't tell anyone" — though, as Cain notes, he always finds out eventually.

3. The Credit-Blame Matrix

The outcome of this dynamic follows a perfectly asymmetric pattern:

Feature ships and does well: The authority figure tells everyone — the company, the publisher, interviewers — that it was their idea, that they pushed it through against resistance, and they're glad everyone likes it.

Feature ships and does badly: They say nothing. They don't lie or deny it — they just stay silent while the game director, lead, team, or publisher takes the blame from reviewers and fans.

Feature doesn't ship, game does well: They shrug it off. "Oh well, I tried, the game's good anyway."

Feature doesn't ship, game does poorly: They tell everyone the game would have been much better if people had just listened to them, and leverage this for future influence.

4. The Executive Producer Problem

Cain draws a parallel to the "Executive Producer" credit in games, film, and TV. The role is so poorly defined that it can mean anything from someone who genuinely kept a project on track and true to its vision, to someone who simply ordered the credit because they were in a position to do so — or even donated money. The ambiguity is the point: because some EPs genuinely earn it, the ones who don't can hide behind the title.

He references the Futurama joke: "I hereby promote you to Executive Delivery Boy." "Executive?" "It's a meaningless title, but it helps insecure people feel better about themselves."

5. Not a Generational Issue

Cain is emphatic that this is not new and not generational. He has seen it throughout his entire career — from the 1980s to the present — at every company he's worked at, including his own. The only common factor is that the person doing it held a position of authority: director, lead, VP, or administrative role.

6. Personal Consequences

Cain shares that resisting these dynamics earned him a reputation for being "hard to work with." When he gave in, the features caused problems and he — as the lead or director — took the blame. Sometimes there was time to fix things before shipping; sometimes there wasn't, and the game shipped with features he'd argued against while he took the public blame. He has "famously walked" from positions a couple of times when this dynamic became too much.

7. No Solution

Cain admits he has no solution to this problem. His only advice: "Do what you think is best. The only person you control is you." Push back on features you believe are bad. Support features you believe are good. But recognize that the authority-without-responsibility problem is pervasive, has been there forever, exists in every industry, and acts as a counterbalance to the developer caution problem he discussed previously.

Source: Authority Without Responsibility — Tim Cain (YouTube)

8. References