Game Design - Design Process

Design Process

The design process varies from designer to designer and companies have different formal procedures and philosophies.

The typical "textbook" approach is to start with a concept or a previously completed game and from there create a game design document. This document is intended to map out the complete game design and acts as a central resource for the development team. This document should ideally be updated as the game evolves throughout the production process.

Designers are frequently expected to adapt to multiple roles of widely varying nature: For example, concept prototyping can be assisted with the use of pre-existing engines and tools like Game Maker. Level designs might be done first on paper and again for the game engine using a 3D modelling tool. Scripting languages are used for many elements—AI, cutscenes, GUI, environmental processes, and many other behaviours and effects—that designers would want to tune without a programmer's assistance. Setting, story and character concepts require a research and writing process. Designers may oversee focus testing, write up art and audio asset lists, and write game documentation. In addition to the skillset, designers are ideally clear communicators with attention to detail and ability to delegate responsibilities appropriately.

Design approval in the commercial setting is a continuous process from the earliest stages until the game ships:

When a new project is being discussed (either internally, or as a result of dialogue with potential publishers), the designer may be asked to write a sell-sheet of short concepts, followed by a one or two-page pitch of specific features, audience, platform, and other details. Designers will first meet with leads in other departments to establish agreement on the feasibility of the game given the available time, scope, and budget. If the pitch is approved, early milestones focus on the creation of a fleshed-out design document. Some developers advocate a prototyping phase before the design document is written to experiment with new ideas before they become part of the design.

As production progresses, designers are asked to make frequent decisions about elements missing from the design. The consequences of these decisions are hard to predict and often can only be determined after creating the full implementation. These are referred to as the unknowns of the design, and the faster they are uncovered, the less risk the team faces later in the production process. Outside factors such as budget cuts or changes in milestone expectations also result in cuts to the design, and while overly large cuts can take the heart out of a project, cuts can also result in a streamlined design with only the essential features, polished well.

Towards the end of production, designers take the brunt of responsibility for ensuring that the gameplay remains at a uniform standard throughout the game, even in very long games. This task is made more difficult under "crunch" conditions, as the entire team may begin to lose sight of the core gameplay once pressured to hit a date for a finished and bug-free game.