Game production is the work of turning a creative vision into a shipped, and often still-running, game: deciding what to build, in what order, with whom, by when and for how much, and then keeping all of that honest as reality arrives. This guide organizes everything on GameDevProducer into the order you need it, from the first pitch to running a live game, with the tools that do the arithmetic along the way.

Each section starts with the ideas that matter most, then points to the deeper guides. If you are new to production, read it top to bottom. If you are in the middle of a project, jump to the stage you are in.

1. What producers actually do

Producers own the “how” and the “when” of a game, not the “what”. The job is part planner, part translator between disciplines, part risk manager and part early-warning system. The best producers make decisions easier for everyone else.

2. The phases of development

Every studio names its phases differently, but the logic is the same: prove the game is fun and feasible before you spend production money, then build content against milestones with clear exit criteria. Most expensive failures come from skipping or blurring a gate.

3. Planning: scope, schedule and budget

A plan is a set of constraints made explicit: the date, the money, the team and the scope, with honest buffer before every gate. Scope it small enough to finish, estimate with the people doing the work, and compare estimates with actuals.

4. Running production week to week

Process exists to make problems visible early and decisions cheap. Use sprints where the work is predictable, flow where it is not, and protect the rituals that change behavior, like retrospectives with owned actions.

5. Risk, scope and quality

Most projects that fail saw it coming and did not say so. Name risks early, give each one an owner, stop scope from growing silently, and decide your bug bar before certification pressure decides it for you.

6. Documentation and pipelines

Documents exist to get everyone building the same game; pipelines exist so that anyone can produce a playable build. Keep both lean, owned and current.

7. Leading the team

Schedules do not ship games; people do. Give feedback against agreed criteria, treat conflict as information, protect motivation through the long middle of production, and treat crunch as a planning failure rather than a culture.

8. Shipping: launch, certification and Steam

The final months are about gates you do not control: platform certification, store review, festival deadlines and launch timing. Put them in the schedule early, with time to fail and resubmit.

9. Live operations

A live game is operated, not finished. It needs a content cadence players can rely on, on-call and rollback plans, metrics that decide what to build next, and capacity protected from constant interruption.

10. Funding and the business

Every production plan is also a financial plan. Know how your game will make money, what you will give up for funding, and what you are signing.

11. Learning from other projects

Game postmortems are the closest thing the industry has to a public failure database, and the research on them is remarkably consistent: most problems are about people and planning, not technology.

12. Your producer career

Producers come from everywhere. What gets you hired is evidence: shipped work, documented process and the ability to explain your trade-offs.

Everything here is free. The full set of calculators and templates lives on the tools page.