Hello, let's get started. Most people assume a game goes from a cool idea straight into coding.

It doesn't. A game crawls through five or six distinct phases, and plenty of good ideas die in the second one. Knowing the stages helps you understand why some games take two years and others take eight.

Concept starts with one clear hook

The concept phase is where you answer a single question: what does the player actually do, and why is it fun? Teams write a one-page pitch before touching any engine. Hades started as a single idea, a roguelike where dying is part of the story, and that hook shaped every decision afterward. Most studios abandon three or four concepts for every one they greenlight, because a pitch that can't explain its core loop in two sentences usually can't survive production.

Prototypes prove the loop works

This is the stage people skip and regret. A prototype is a rough, unpolished build that tests whether the core mechanic is actually enjoyable. Valve reportedly built dozens of prototypes for Portal before the portal device felt right. You don't need art here. You need a playable slice, even if it's grey boxes and placeholder sound. If the loop isn't fun at this stage, more polish won't fix it later.

Pre-production locks the plan

Once the prototype holds up, pre-production begins. This is where you write the design document, define the art style, plan the level list, and estimate the schedule. A studio making a mid-size indie title might spend three to six months here. The goal isn't a perfect plan. It's catching the expensive mistakes on paper instead of in code. Teams that rush this phase often rebuild core systems halfway through production.

Production is the long middle

Production is where the game actually gets built, and it takes the most time. Artists, programmers, and designers work in parallel while a producer tracks dependencies. For a small team, this might run twelve to eighteen months. For a large studio, two to four years is normal. This is also when scope creep hits hardest, so most producers cut features here rather than add them. A level that took two weeks to design might take two months to build and test.

Polish and testing tighten everything

After the game is content-complete, the focus shifts to bugs, balance, and feel. QA testers play the same section hundreds of times looking for crashes and soft locks. A single boss fight in a major release might get over a thousand logged bug reports. This phase also covers localisation, accessibility options, and performance tuning so the game runs on lower-end hardware. It's unglamorous work and it decides whether players remember the game fondly or complain about it for years.

Launch is not the finish line

Shipping day feels like the end, but it's really the start of live support. Day-one patches are standard now because certification builds get locked weeks before release. After launch, teams watch crash reports, review scores, and player feedback. Some studios ship a patch within the first week. Others plan content updates months ahead. A game that launches rough can still recover, but it takes a committed team and a clear roadmap.

The whole process comes down to one thing: each stage exists to catch problems before they get expensive. Concept filters bad ideas, prototypes test the fun, pre-production catches planning gaps, production builds it, polish makes it hold up, and launch support keeps it alive. Next time you load up a new game, take a second to think about the two to four years of decisions behind that title screen.