Production 101 #1 - What Does a Producer Do?
The role is broader than most people expect, and that breadth is exactly what makes it hard to explain
A game producer owns the delivery of a game, from initial concept through to live operation, across every discipline involved.
The role splits broadly into internal production (running the team and the schedule) and external production (managing partners, platforms, and third parties).
Producers come from many different backgrounds: QA, design, development, marketing, and straight from adjacent industries entirely.
This is post #1 in the Production 101 series. Post #2 covers the specific job roles and levels you’ll find inside a studio.
If you ask ten producers what they do, you’ll get ten different answers. The variation is accurate. The role genuinely changes shape depending on the studio, the game, the team, and the moment in production you catch them in.
The honest answer to “what does a producer do?” is: a producer is responsible for getting a game made. Everything else is detail. But the detail matters, because the detail is where the actual work lives.
The core responsibility
A game producer owns the delivery of a project. That ownership covers the schedule, the budget, the team’s ability to do their work, the communication between disciplines, and the relationship with anyone outside the team who has a stake in the outcome.
That last group can be large. On a mid-sized project it might include a publisher, a platform holder, a licensor, one or two outsource studios, a localisation vendor, and a QA partner. On a smaller project it might just be the studio head. On a service game that’s been live for several years, it can include all of those plus a live operations team, a community team, and customer support.
The producer owns the space between disciplines: the agreements about what gets made, when, to what standard, and with what resources. Direction of art, design decisions, and code belong to other people. The producer owns the conditions that make those things possible.
“The producer owns the space between disciplines: the agreements about what gets made, when, to what standard, and with what resources.”
That framing matters because it tells you what the job actually requires. The requirement is understanding how artists and programmers work well enough to know when something is on track, when it’s slipping, and what’s actually causing the problem.
The two broad types of production work
Most production work falls into one of two categories: internal and external.
Internal production is about running the team. That means planning the schedule, tracking progress, identifying risks before they become delays, managing dependencies between disciplines, and making sure everyone knows what they’re supposed to be building. It also means running the meetings that need to happen and cancelling the ones that don’t. A significant part of the internal producer’s job is clearing the path so that developers can spend as much time as possible actually developing.
External production is about managing relationships and obligations outside the team. That could mean working directly with a publisher, a platform holder like Sony or Microsoft or Apple, a licensor whose intellectual property appears in the game, or one or more external studios doing outsource work. An external producer tracks deliverables, reviews milestones, writes and negotiates statements of work, and carries the quality bar from the internal team into those external relationships.
In practice, producers do both. On smaller teams, one person might own all of it. On larger productions, you’ll see these responsibilities split across multiple producers at different levels. But understanding the distinction helps you understand why the job description looks different from studio to studio. A job ad that emphasises milestone management and third-party relationships is describing external production work. One that emphasises sprint planning and team coordination is describing internal production work.
What specialisation looks like in practice
As studios have grown more complex, so have the specialist tracks within production. A producer who spends their career on the same game for several years often develops deep knowledge in a specific area, and that knowledge becomes a professional identity in its own right.
Server and online production is one common specialisation. Multiplayer games and live service titles require backend infrastructure that has to be planned, built, tested, and operated in parallel with everything else. The producer working in this space understands how online systems are architected and where the production risks live: capacity planning, certification requirements, the difference between a soft launch and a hard launch, what happens when something goes wrong at scale.
Analytics and data production is another. Modern games generate enormous amounts of behavioural data, and that data needs to be planned for, instrumented correctly, and then used. A producer working in this space owns the relationship between design intent and measurement: what are we trying to learn, how are we going to learn it, and what decisions will we make with the results.
Localisation production is a specialism that gets underestimated until something goes wrong. Adapting a game for different languages and regions requires planning from the beginning, integration into content pipelines, and management as an ongoing production stream with its own schedule and quality bar. Handing it to a vendor at the end of development is a reliable way to end up with a late, expensive, and inconsistent localisation.
Outsource production, sometimes called vendor management, is the coordination of work done by external studios or freelancers. This involves writing clear briefs, setting up review pipelines, managing feedback loops efficiently, and keeping outsourced work integrated with in-house development. Studios that depend heavily on outsourcing often have producers who do almost nothing else.
“Handing localisation to a vendor at the end of development is a reliable way to end up with a late, expensive, and inconsistent result.”
Publishing production sits at the intersection of development and release. A publishing producer manages the relationship with platform holders, which means understanding certification requirements, submission windows, and the specific demands of each storefront. It also often means managing relationships with licensors when a game includes third-party IP, which adds a layer of approval and compliance obligations on top of the development schedule.
None of these specialisations are separate professions. They’re concentrations within a single profession. A specialist producer still understands the full production context; they’ve simply developed enough depth in one area to own it without being supervised.
What senior producers add
Seniority in production changes the job, and the change is more substantial than simply doing the same things with more confidence.
A junior or mid-level producer typically executes within a structure that someone else designed. They run sprints, track tasks, manage a vendor relationship, or coordinate a team. That’s valuable and necessary work, and doing it well is harder than it looks.
A senior producer designs the structure. They look at a project and decide how it should be organised, what processes are appropriate for this team and this game, and where the production model needs to adapt as the project moves through different phases. They make architectural decisions about process rather than just executing process.
Beyond that, senior producers often carry financial responsibility. They own the budget, negotiate with external partners, and are accountable for the gap between what was budgeted and what was spent. They’re also frequently people managers, responsible for the professional development of more junior producers on the team.
At the most senior levels, the work starts to look like leadership in a broader sense: setting direction, defining culture, making hiring decisions, and representing production in conversations with studio leadership, publishers, and investors.
“A junior producer executes within a structure. A senior producer designs the structure.”
How people get into production
There’s no single path into game production, and I’d be suspicious of anyone who told you there was.
The most common routes I’ve seen across thirty years in the industry all share one thing: the person arrived with transferable skills and then spent time learning the industry. The route itself matters less than that combination.
QA is the most frequently cited entry point, and it makes a certain kind of sense. QA builds familiarity with the full game, with the development pipeline, and with the disciplines involved. A good QA lead already does a lot of production-adjacent work: tracking issues, coordinating with multiple teams, managing a schedule. The step into production can be a natural one. The risk is that QA experience, on its own, gives you a detailed picture of what breaks and a limited picture of why decisions were made the way they were. The producers I’ve seen come from QA who did well were those who spent their QA time asking questions about design and production intent, not just recording defects.
Other development disciplines are another route. Programmers, artists, and designers who develop an interest in the whole project rather than just their part of it sometimes move into production. They bring technical or craft depth that can be genuinely useful, particularly when producing in areas adjacent to their original discipline. A producer who was previously a programmer tends to have a more realistic model of technical risk. One who came from design tends to have sharper instincts about scope and feature complexity.
Product management from outside games is increasingly common as the industry has grown and professionalised. People with experience running software products, consumer apps, or digital services bring planning and stakeholder management skills that transfer well. The gap is usually games knowledge, which can be closed.
Some producers come from marketing, community management, or project management in adjacent industries. The common thread across all of these routes is that they had already developed the underlying skills before making the move: organising work, communicating clearly across different kinds of people, thinking about the project as a system rather than a set of individual tasks.
The skills that matter are planning, communication, and a genuine understanding of how games are made. The last one takes time to build. You can learn planning frameworks from a book. You learn how games are made by being on development teams, paying attention, and making mistakes.
What the job actually feels like day to day
Most of the writing about game production focuses on the big picture: the structure, the frameworks, the career paths. Less gets written about what the job actually feels like when you’re doing it.
Most days, production is a coordination problem. Someone needs information they don’t have. Two teams have made different assumptions about the same thing. A dependency that looked manageable last week has become urgent. A milestone is approaching and three things that were supposed to be done aren’t.
The job is largely about staying ahead of those problems. You need to know what the problems are, who needs to be involved in solving them, and whether the overall picture is still on track or whether something needs to change. The solving is often someone else’s job. Knowing which problems exist is yours.
That requires a certain tolerance for ambiguity. In early production, large amounts of the project are undefined. The producer creates enough structure that the team can make progress while the uncertainty resolves, and keeps track of which uncertainties need to be resolved before other decisions can be made. The worst thing you can do in pre-production is force every decision too early. The second worst thing is leave every decision too late.
It also requires relationships. Production is a people job. The technical skills matter, but the limiting factor is almost always whether you can build enough trust with the people you’re working with that they tell you the real status of things rather than the status they think you want to hear.
I’ve found that the producers who struggle most are those who try to manage from a distance: read the reports, attend the standups, keep the spreadsheet up to date. Those things are necessary but they’re not sufficient. The information in a status report is filtered, condensed, and delayed. The information you get from a twenty-minute conversation with the person doing the work is richer, faster, and far more likely to include the thing that actually matters. You have to be present enough that people tell you things before they become problems, not after.
“The information in a status report is filtered, condensed, and delayed. The information you get from a twenty-minute conversation is richer, faster, and far more likely to include the thing that actually matters.”
The other thing that catches people out is context-switching. In a single day, a producer on a mid-sized project might move between a design review, a technical dependency discussion, a vendor call, a budget query, and a conversation about whether someone on the team is burning out. Each of those requires a completely different kind of attention. The ability to shift between them without letting any of them bleed into the others is a skill you develop over time, and it’s one that doesn’t show up in any job description I’ve ever read.
Where this series goes next
The next post in the Production 101 series goes into more detail on the specific roles and levels within a studio’s production structure, from Associate Producer through to Executive Producer, and what’s expected at each level.
