The producer path

What good looks like at every stage

I’ve been on both sides of the conversation: the producer asking “what does it take to get promoted around here?”, and the manager awkwardly trying to articulate why someone who is technically very capable... isn’t quite there yet. It’s a frustrating conversation to have, for everyone involved, because the games industry does a pretty poor job of defining what “good looks like” at any given point in the production career.

So let me try to do that. Not as a formal rubric, certainly not as a checklist, but as an honest description of what I’ve seen work, what I’ve seen not work and some of the lessons I picked up along the way in trying to help clarify progression for producers.

What a producer actually is

A producer’s job is to create the conditions in which a team can make their best game. Not to coordinate tasks, not to run meetings, not to be the person who knows where everything is in Jira. Those things might be part of the work, but they are not the work itself.

Producers manage forward. What that means is that they see where the production is heading before everyone else does. Not in some oracle-like way, but just by paying attention: where is risk accumulating, what decisions have been deferred past the point of safety, what team dynamic is progressively degrading. They manage the space between people, the gaps in communication, the unspoken tensions, the creative alignment that tends to drift when no one is actively working to maintain it. And they manage clarity, making sure the team knows what they’re building, why, what phase they’re in and what success looks like right now.

It took me years to really understand that production is not fundamentally a coordination problem but a people problem. The spreadsheet is not the job. The people filling it in are actually the job. If you confuse those two things, you’re already on the wrong path.

On the producer / product manager distinction: this typically comes up in larger studios, mobile studios and anything built around live services. A product manager, broadly speaking, owns the “what”: the product vision, the feature roadmap, what gets built and in what order, grounded in player behavior data and business objectives. A producer typically owns the “how”: the execution, the team, the health of the production day to day. In very simple terms, you want a product manager asking whether you’re building the right thing, and you want a producer asking whether you’re building the thing right, and increasingly, whether the people building it have what they need to do it well.

That last part is easy to lose sight of early on because studios tend to ask for the coordination work first and loudest: the Jira board, the milestone tracking, the status reports, clear processes, sensible artifacts. It satisfies a kind of organizational anxiety in a way that people work doesn’t. Human dynamics are also just harder than process systems and the instincts take longer to develop. So most producers start by getting good at what’s asked of them most visibly and they stay there perhaps longer than they should. There’s nothing wrong with being rigorous about processes. There’s something wrong with mistaking it for the real job.

On title inconsistency: "producer" is the most common title for the role, but it's not universal. In some studios, particularly larger ones with technology or platform roots, you'll see "program manager" or "development director" doing essentially the same work. Some studios use "project manager." The titles vary enough that when you're evaluating a job posting or a resume, it's worth reading the actual responsibilities rather than anchoring on the title. What I'm describing here applies regardless of what it's called.

The levels and what they actually mean

Most studios have this progression in some shape or form: associate, mid-level, senior, lead or principal, director, and somewhere above that, executive producer or VP. Larger studios often have more steps: a “staff” level between senior and lead, or an “associate director” between lead and director. That additional granularity is typical for organizations where clear level distinction matters for compensation bands and organizational design. It’s not always meaningful in practice. Whether your studio has four levels or seven, the underlying shape of the progression is the same.

What's less consistent is what each level actually requires in terms of demonstrated capability and experience. I've seen "senior producer" mean three years in the industry and no shipped titles, and I've seen the same title mean a decade of complex project experience and real P&L exposure. Read the responsibilities, not the label.

There’s also a somewhat meaningful fork that opens at the lead or principal level, but only in larger studios. More on that below.

Associate producer

This is the entry point and the job at this level is deceptively simple: find mentorship, learn to do the coordination work well, foster visibility as much as possible, develop instincts for where things are drifting and begin to understand the studio, team and game deeply enough to make useful contributions to the conversations that matter.

In practice, an associate producer is typically supporting one team or one content area within a larger production. They own a slice of the backlog, run standups, track dependencies, flag blockers, and write meeting notes that are hopefully useful. The scope is narrow and the stakes are contained. That’s by design. The priority at this level is building foundational habits: rigor in tracking, discipline in follow-through, early development of that sense that something is about to go wrong before it does.

What differentiates a strong associate from an average one is not how clean their Jira board is but whether they’re starting to read the room. Do they notice when a developer’s energy has shifted? Do they bring problems with a proposed path forward rather than just flagging that there’s a problem? Are they curious about the game beyond their immediate slice of it?

In a corporate environment, an associate producer usually has a clear manager, structured onboarding and regular feedback. In a small indie studio, the same person might be doing administrative coordination, scheduling, QA facilitation and a slice of game design simultaneously, with minimal guidance. Both are valid, but the indie version requires more self-direction earlier and the margin for confusion about what the job is tends to be higher.

Typical experience at this level: zero to three years in the industry. Often the first professional production role, sometimes a transition from another discipline. Scrum Master certification is common and mildly useful. More useful is any experience organizing complex work with other people under time pressure, as well as a solid mentorship relationship.

Mid-level producer

The jump from associate to mid-level is largely about independence. A mid-level producer owns a meaningful production area without needing significant oversight to do it well. They can run a small team’s production end-to-end: milestone planning, sprint structure, risk management, stakeholder updates, etc. They’re starting to have real opinions about what the work systems should look like and those opinions are occasionally right.

At this level, the producer is typically interfacing with discipline leads (design, engineering, art) on a daily basis. This is where interpersonal skills start to visibly differentiate people. A mid-level producer who can build genuine trust with technical and creative leads is dramatically more effective than one who can’t, even if the less trusted producer has more polished “process skills”.

The mistake I see most at this level is a producer who has gotten very good at the visible work (clean board, timely reports, milestone dates tracked with precision, all that), and underneath that, a team that's slowly falling apart, a lead burning out, a developer who's lost the thread, a director who still doesn't know the scope won't fit. The process looks healthy on paper. The people are not.

At mid-level, the work is starting to ask you to care about which one is actually true, and to have the conversations the process can’t have for you. Those conversations are uncomfortable. Developing the willingness to have them, at this level, is a very large part of the job.

In indie studios, a mid-level producer at a ten-person shop might be the only dedicated production person on the team. Which means they’re also doing some of what a senior producer does in a larger studio: interfacing with external partners, contributing to milestone planning across the full project, supporting leadership decisions. The title doesn’t change. The scope does.

Typical experience: three to six years, more or less. One or two shipped titles, or meaningful live operations experience. Beginning to develop a production philosophy rather than just production habits.

Senior producer

This is where the work starts to substantially change. A senior producer is no longer primarily about execution within a defined area. They’re increasingly about judgment, risk management, organizational influence and leadership.

In a larger studio, a senior producer is typically running end-to-end production for a significant feature team or an entire module of a game. They’re managing producers below them and partnering as peers with discipline directors. They own their production area’s success with real accountability, which means they’re not just flagging when things are at risk but actively doing something about it: reprioritizing, renegotiating scope, realigning teams, collaboratively making hard calls about what gets cut and what gets protected.

The decision quality here starts to matter in a different way. A senior producer is being called on to make judgment calls with incomplete information, usually with meaningful downstream consequences. They’re the ones sitting in the room when scope has to be negotiated, when a feature has to get cut close to launch, when a team is in conflict and someone has to verbalize what’s actually happening. The ability to read a room, hold their own in those conversations and stay calm when the situation is genuinely difficult. That’s what separates senior producers who advance from senior producers who don’t.

External partnerships also start to appear in scope at this level. Third-party vendors, outsourcing partners, co-development studios, platform relationships. A senior producer needs to be able to manage dependencies that don’t run through the internal org chart.

At the senior level, most producers begin to encounter leadership in a more intentional way, even if it doesn't fully land yet. Some of it comes from proximity: working closely with a director or studio head who models something different from what they've seen before, someone who leads with context rather than directives, who makes decisions and elicits something in people in a way that's worth studying. Some of it comes from formal exposure: a leadership training program, a recommended book, a conversation with a mentor that reframes something they'd been doing on instinct.

What often starts to crystallize at this stage is a distinction between management and leadership, that managing is about the work and the systems, and leading is about the people and the direction, and that being good at one doesn't automatically make you good at the other. A senior producer who is technically excellent at running a production can still struggle to inspire trust, hold a team through uncertainty, or build genuine followership. That gap doesn't always become visible until the senior producer is asked to lead other producers or step into a higher-stakes organizational moment. But the good ones start sensing it earlier, not necessarily reading Kouzes and Posner or Brené Brown cover to cover, but developing a sort of awareness that the next phase of the career is going to demand something different from them than the current one does.

In an indie context, a senior producer at a small studio often has some version of executive responsibility by default. There’s no one above them in production. That can accelerate development if the person is genuinely capable, or create a dangerous gap if they’re being given a senior title they haven’t fully grown into yet. I’ve seen both, and the gap tends to show up around crunch time when the production decisions have real consequences.

Typical experience: six to ten years, with meaningful variation by studio. Has experienced at least one significant full production lifecycle, ideally also including post-release. And has managed others, even informally.

Lead and principal producer: the fork

At the lead or principal level, in studios large enough to have this distinction, there’s a somewhat meaningful split in career path.

A lead producer is primarily a people leader. They’re managing a team of producers, setting standards for how production is done across that team, coaching junior and mid-level producers, handling performance conversations and operating as a production leader at the organizational level. Their leverage comes from making other producers (and other developers) more effective. The best lead producers I’ve worked with had a particular quality that’s hard to put into words but easy to recognize: they made everyone around them better without making themselves the center of everything.

A principal producer is more of a craft or technical leader. They’re the person who defines what great production looks like, sets the methodology and process standards for the studio, consults on the hardest production problems and brings depth of expertise rather than width of management. They’re often the person a director calls when a production is struggling and they need someone who can diagnose what’s actually wrong. They don’t necessarily manage a large team of producers, but their influence on how production runs across the studio is significant.

The Venn diagram of those two roles is, quite frankly, enormous. Most people operating at this level are doing a mix of both things. The distinction matters more as a signal of developmental trajectory than as a rigid job description: where do you want to grow from here? Toward broader organizational leadership or toward deeper craft mastery? Both paths are legitimate and oftentimes mirrored in other game development disciplines (where they arguably make more sense than in production). Not everyone needs to manage people to have a meaningful senior career in production.

This split mostly exists in larger studios. In a twenty-person indie studio, there’s one senior production person and they’re doing all of it.

At the lead level, that quiet leadership awareness developed over the past few years becomes something more active. The producer is now responsible for other producers (their development, their performance, their growth) and that accountability has a way of forcing the questions that were easy to defer at the senior level. You can't lead a team of producers without developing a real point of view on what good leadership actually looks like, because they're going to reflect whatever you model for them, good and bad.

The abstract understanding that leadership and management are different things starts to show up in concrete daily decisions: how you run a one-on-one, how you give feedback that lands without shutting someone down, how you hold someone accountable while keeping the relationship intact. Many lead producers at this stage become more deliberate about the learning itself, reading more intentionally, seeking out mentors with genuine leadership depth, reflecting on their own patterns in a way that goes beyond professional performance. The frameworks that felt like theory at the senior level start to feel applicable, because now there's a specific person or situation to map them onto. And there's usually at least one hard moment (a producer on the team who isn't growing, a conflict that requires real courage to address, a situation where the technically correct production call and the right leadership call are not necessarily the same thing) that does more to internalize the lesson than any book or training ever could.

Typical experience: ten or more years. Has shaped how production works at an organizational level, not just within a team. Has navigated at least one genuinely hard production situation (a project in trouble, a team falling apart, a major scope crisis) and come out the other side with something to show for it.

Director and executive producer

This is where the scope becomes organizational rather than project-specific. A production director or EP is accountable for the delivery health of a full game or a studio’s full slate. They’re operating at the strategy layer - profit & loss statements, portfolio planning, go-to-market, organizational design, executive alignment, greenlight and cancellation decisions - while simultaneously staying close enough to the production reality to know when something is actually in trouble.

The stakeholder map also changes substantially. A director or EP is regularly in conversation with the publisher, platform holders, investors, creative executives, the board, external partners. They’re not managing the day-to-day anymore. They’re managing the conditions under which the day-to-day can succeed.

Hiring becomes a core responsibility at this level in a way it isn’t at lower levels. An EP who can’t build a great team and develop a strong production leadership bench will eventually hit a ceiling regardless of their individual capability. The output is the team. The judgment that matters most is often about people: who to bet on, who needs support, who is in the wrong role, and what the organization needs in order to do its best work.

Budget ownership is real at this level. P&L literacy is not optional. Not because an EP needs to be a CFO, but because decisions about scope, staffing, milestone timing, project health and release window have very real financial consequences.

What I didn’t fully understand until I was actually operating at this level is how much of the job is holding organizational stability when things are truly tough. Productions that are genuinely at risk generate a kind of organizational anxiety that is contagious. An EP who can’t stay grounded in that environment and project reasonable confidence without pretending everything is fine... well, the team picks that up immediately. It changes how they work, often for the worse.

At the EP level, leadership is no longer a competency you're developing but the primary medium through which you do your job. The game doesn't get made by your hands. It gets made by the culture you've built, the leaders you've grown, the standards you've modeled and the judgment you've brought to every hard decision people watched you make.

That cascading effect is real and it runs in both directions: an EP who leads well creates conditions where good producers become great ones, where the team feels safe enough to raise problems early, where the studio develops a kind of institutional resilience that outlasts any single project. An EP who leads poorly, who is technically excellent but emotionally unavailable or who optimizes for delivery at the expense of people, tends to produce studios that perform in the short term and slowly hollow out over time. By this point, the work of leadership is less about learning new frameworks and more about continued self-awareness, about knowing your own patterns well enough to catch the moments where your instincts might be working against the people depending on you.

In the indie space, an executive producer at a fifteen-person studio is often also doing some mix of COO, studio director and technical coordinator depending on what the team needs and what the gaps are. The title reflects seniority and scope of accountability. The specific work adapts to the context.

Progressing deliberately

So many producers I’ve known, especially early in their careers, approached progression the way you approach a performance review: do the job, get the feedback, hopefully advance. That’s passive and it works slowly and inconsistently.

The producers I’ve seen develop fastest, and who helped their direct reports develop fastest, had a different orientation. They thought about what great looked like at the next level before they were there and they pursued the specific experiences and competencies that would close that gap. Not abstractly, not just by reading books, but by deliberately seeking the situations that would require them to grow.

That means asking for the uncomfortable assignment, the production that’s in trouble, the team with the dynamics problem, the milestone no one thinks can be hit. It means working with leads and executives who are better than you at the things you’re trying to develop and paying real attention to how they operate. It means retrospectives on your own decisions, not just the project’s: where did your judgment fail, what did you not see coming, what would you do differently?

It also means being honest about which competencies are actually weak. Most producers have strong process skills. Fewer have strong people skills. Fewer still have strong strategic thinking skills: the ability to see where the organization is heading, what decisions need to be made at the portfolio level, how the current production maps onto the studio’s long-term health. That last one typically only develops through exposure to executive conversations, and it’s worth seeking that exposure earlier than most people do.

The “framework lite” I’d leave you with is this:

1. Know what good looks like at the next level in terms of competencies, experience and behaviors

2. Align with your manager on that

3. Close the gap in a concerted manner

4. When you get there, reset the horizon

---

If this was useful, you might also like:

What makes a great game producer?

The team is everything