Five Traits In A Good Producer

tim-cain production game-development leadership management

Abstract

Problem: What qualities make someone a good producer in game development, and what should aspiring producers focus on?

Approach: Tim Cain draws on decades of experience working with producers across multiple studios to identify the five essential traits, illustrating each with concrete examples from real game development pipelines.

Findings: The five traits are: (1) good communication — especially with introverts and diverse stakeholders, (2) being highly organized — tracking complex interdependent pipelines, (3) knowledge of game development — understanding how assets and features actually get made, (4) being proactive — anticipating problems before they become crises, and (5) mastery of deadlines — setting, managing, and enforcing them across publisher, press, and internal needs.

Key insight: A producer isn't someone who simply does what the director says — they're the person who tells the director "you're out of time, out of money, decide now," and that requires a rare combination of toughness, organization, and deep understanding of how games get made.

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

1. The Producer's Role

Tim opens by clarifying a common misconception: most people think the game director sits at the top of the chain, but in many ways it's the producer. Producers handle everything — interfacing with publishers, localization teams, external art studios, and managing assistant producers. They're the ones who sometimes have to tell the game director: "You're out of time, you're out of money, that person isn't available anymore. Either you're happy with this feature or we're cutting it. Decide."

If you can't imagine yourself doing that, production might not be for you.

2. Trait 1: Good Communication

This sounds obvious, but Tim emphasizes how genuinely hard it is. Game development is full of introverted people, and a producer must learn to work with every flavor of introversion. Tim describes real colleagues who:

  • Only want to be contacted via email or Slack, never in person
  • Want you to Slack them to schedule a time to talk
  • Only accept visitors during certain hours
  • Hang an object on their monitor meaning "don't bother me" — and sometimes forget to take it down

Tim shares a personal example: when he's programming, he builds a complex mental structure. Even when he pauses typing, an interruption collapses that structure and costs 15 minutes to rebuild. This is why he started putting zzz comments in his code at interruption points — and later noticed bugs always clustered within a few lines of those markers.

The point isn't that people are being difficult. It's that different work requires different communication protocols, and the producer is the person who negotiates those systems with every team member. Beyond developers, producers also communicate with publishers, press, and company management — all requiring different approaches.

3. Trait 2: Being Organized

A producer must be the most organized person on the project. Modern game development has enormous numbers of moving parts: half-finished assets in the game for testing, features in various pipeline stages, and complex dependencies between people.

The critical insight here is about invisible deadlines. A producer must recognize that if Person A doesn't finish by Friday, Person B can't start their part, and Person C can't do theirs after that — meaning a deadline months away is actually at risk right now. It can seem strange to tell someone "you must be done Friday" when the final deadline is next month, but the producer is the only person who sees the full dependency chain.

4. Trait 3: Knowledgeable on Game Development

Tim pushes back hard on producers who say "we might as well be making shoes." You absolutely need to understand how games are made.

He walks through the 3D asset pipeline as an example:

  1. Modeling — polygons shaped in 3D software (needs to know size, shape)
  2. Texturing — surface appearance (needs to know environment context, whether it should stand out or blend in)
  3. Rigging — adding bones for movement (needs to know which parts move — a creature's face may not need the same rigging as a human's)
  4. Animation — creating movement sets (needs to know what animations are required — maybe no death animation if it's never attacked, or multiple death animations for different damage types)

The key producer question: can any of these stages happen in parallel? If you see rigging and texturing scheduled simultaneously on the same model, you need to know whether that's possible. The lead artist should catch this too, but the producer owns the schedule.

5. Trait 4: Being Proactive

Don't wait for problems to happen. Constantly scan the schedule for:

  • Choke points — bottlenecks where work piles up
  • Personnel gaps — someone planned for a task is on vacation, on leave, or just quit
  • Cascading delays — a missing person next month means you need to start hiring now

Tim stresses the timeline: finding a replacement means posting a job, reviewing applicants, interviewing, making a hire, onboarding, and getting them up to speed. That's months of lead time. The moment you realize you need an asset from someone who's gone is far too late.

6. Trait 5: Mastery of Deadlines

Producers must be excellent at figuring out, setting, and enforcing deadlines. These come from multiple sources:

  • Publisher deadlines — budget milestones, demo dates, vertical slice deliveries
  • Press deadlines — media visits requiring stable builds and walkthrough-ready regions with specific features
  • Localization deadlines — text must be locked before translation begins; if narrative designers are still writing dialogue or quests are being redesigned (changing "go north" to "go south"), that all needs to settle first
  • Internal deadlines — ones nobody imposes on you, but a good producer identifies and sets them anyway

7. Path Into Production

Tim notes that assistant producer is the natural entry point. Some are hired directly; others transition from QA, art, programming, or design. Coming from another discipline gives you the game development knowledge (Trait 3) for free. But many of the best producers Tim has worked with wanted to be producers from the start because they were naturally strong at organization and communication — the first two traits. Just don't forget you still need the other three.

8. References