Short answer: A producer (or project manager) oversees schedules, resources, and communication—ensuring that a game is delivered on time, within budget, and aligned with the team’s goals.
Who is NOT a Producer?
- A person who only defines the creative vision (that’s a Game Director) is not a Producer.
- A person who only writes code or mechanics (that’s a Programmer/Game Designer) is not a Producer.
- A person who only tests for bugs (that’s a QA Tester) is not a Producer.
- A person who only markets or publishes the game (that’s Marketing & Publishing) is not a Producer.
What does a Producer do?
- Scheduling & planning: build timelines, milestones, and sprints.
- Resource management: allocate team members and tools efficiently.
- Communication hub: keep designers, artists, and programmers aligned.
- Risk management: identify delays, bottlenecks, or scope creep.
- Reporting: update stakeholders, publishers, or executives.
- Problem-solving: remove blockers so the team can focus on their work.
Why it matters
Producers keep chaos under control. Without them, projects can spiral into missed deadlines, burnout, and unfinished games.
Common misconceptions
- “Producers don’t make the game.” → They enable the team to make the game efficiently.
- “They just nag people.” → They remove obstacles and support collaboration.
- “Producer = Director.” → Directors own creative vision; producers manage time, scope, and resources.
Core skills & tools
- Project management software: Jira, Trello, Asana, Notion.
- Methodologies: Agile, Scrum, Kanban, Waterfall.
- Knowledge: scope management, risk analysis, budgeting.
- Soft skills: leadership, communication, negotiation, conflict resolution.
- Documentation: roadmaps, sprint reports, production logs.
Practical frameworks
- Agile Sprint Cycle: Plan → Execute → Review → Retrospective.
- Critical path method (CPM): identify tasks that control overall schedule.
- Burn-down charts: visualize workload and progress.
- Post-mortems: reflect on successes and failures after milestones.
Portfolio tips
- Highlight projects shipped under your coordination.
- Show roadmaps, sprint boards, or burn-down charts.
- Include case studies: how you handled risks, delays, or scope changes.
- Demonstrate team management skills with references or testimonials.
Quick example
Think of massive AAA studios like Ubisoft or Naughty Dog—producers coordinate hundreds of people across multiple departments to hit release deadlines.
In indie teams, a producer might double as a designer or programmer while still managing scope.
Author: Pouria Mojdeh
References:
- Heather Maxwell Chandler – The Game Production Handbook (CRC Press, 2020)
- Jennifer Brandes Hepler – Agile Game Development (Addison-Wesley, 2010)
- Jason Schreier – Blood, Sweat, and Pixels (HarperCollins, 2017)
- Will Luton – Free-to-Play: Making Money From Games You Give Away (New Riders, 2013)
- Game Developer (formerly Gamasutra) – www.gamedeveloper.com