There is no single way to make a game
Every game starts differently. One might begin as a sketch on paper, another as a technical experiment, another as a request from a publisher. Teams range from one person working evenings to hundreds of people spread across several countries. Because of that, the process described here is a general pattern, not a rulebook. Real projects skip steps, repeat them, or run several at once.
Still, most projects pass through recognisable stages: an idea, early experiments, a long production period, testing, release, and support afterwards. Understanding these stages makes it easier to see why games take as long as they do, and why they sometimes change a great deal along the way.
Stage one: the idea and the pitch
A game usually begins with a short statement of what the player does and why it might be enjoyable. This can be a sentence or a page. Early thinking tends to cover the core activity (exploring, building, fighting, solving puzzles), the intended audience, the platforms in mind, and a rough sense of scope.
Scope is often the hardest question. An idea that sounds small can hide a great deal of work, and experienced teams are usually cautious about promising too much too early. If the project needs outside money, this stage often includes a pitch to a publisher or investor. Many ideas stop here, which is normal and cheaper than stopping later.
Stage two: pre-production
Pre-production is where a team tests whether the idea can become a real project. Typical work includes:
- building rough versions to see whether the core activity is enjoyable, which is the purpose of a game prototype
- writing down the vision and rules in a design document so everyone shares the same picture
- choosing tools, including one of the game engines available to teams
- estimating the people, time and money needed
- setting a visual style and trying out sample art
The aim is to reduce uncertainty before the expensive part begins. A team that discovers a problem now only loses weeks. A team that discovers it in the middle of production may lose months.
Stage three: production
Production is the longest stage and where most people are employed. Many disciplines work in parallel:
- Designers define rules, challenges and how the parts of the game connect, including how game systems such as combat, inventory and progression interact. Some focus on spaces, which is the craft of level design.
- Programmers build the game’s code, tools and the connections between them. Some features, such as online multiplayer or game physics, need specialists.
- Artists create characters, environments, effects and the interface. Turning concepts into playable characters involves 3D modeling, rigging and animation.
- Audio staff create music, voices and effects. Good sound design often shapes how a game feels more than players consciously notice.
- Writers produce dialogue, text and story material where the game needs them, which ties into game storytelling.
- Producers and managers track schedules, budgets and communication.
Work is commonly built in pieces. Teams often aim for a first version in which everything exists in rough form, then improve it in passes. Developers sometimes call the first playable stretch of the game a vertical slice, because it shows the intended quality of the whole in a small portion.
Stage four: testing and polish
Testing runs alongside production but becomes the main focus near the end. Dedicated testers look for crashes, broken features and unclear moments, a discipline known as quality assurance. Separate playtests put the game in front of people who did not build it, because the team members are too familiar with it to notice what confuses a newcomer.
Polish is the long final stretch of fixing, tuning and smoothing. It includes performance work, since a game that runs poorly on its target hardware has to be adjusted. Matters such as frame rate and loading behaviour are usually checked against the platforms the game will ship on.
Many games also need approval from the platform holder before they can be published, which adds checks of its own.
Stage five: release
Release means putting the game in front of players, through physical copies, stores or both. Today digital distribution is the common route for many games, though practices vary by platform and region. Alongside the game itself come store pages, trailers, ratings information, and press and community outreach.
A launch day is rarely the end. Early player reports often reveal problems that testing missed, and teams commonly respond with fixes soon afterwards.
Stage six: after release
Many games continue to be worked on well after launch. That can mean bug fixes, balance patches for games with competitive modes, new content, support for additional platforms, or tools that let players create their own material, as with game mods. The way a game earns money, including any game monetization it uses, affects how long and how heavily a team supports it.
Some teams move on to a new project once support winds down. Others keep a game in service for years.
Why plans change
It is common for a finished game to differ from its first pitch. Features turn out not to be fun, technology proves harder than expected, or testers show that something the designers loved does not work for players. Good teams treat this as part of the process and keep their early decisions flexible.
Large and small studios approach these stages with different resources and different risks, which is covered under indie development. The stages themselves, though, look broadly similar whether the team is two people or two thousand.