The pre-production phase in game development, explained

The pre-production phase in game development is the structured planning stage where a studio defines its concept, writes the game design document, validates core mechanics through prototypes, establishes art and technical direction, and builds a production plan before full-scale development begins. It ends when the project passes a formal greenlight review.

The standard deliverables are a vision package, a game design document, a validated prototype, a technical assessment, an art direction package, and a production plan. These are living documents, not finished paperwork. The goal is a credible decision that the game is fun, technically feasible, and appropriately scoped. Industry guides and producer experience indicate that catching scope problems before a single full-production dollar is spent costs a fraction of catching them mid-development.

What does the pre-production phase actually include?

The minimum useful set covers six deliverables. The game design document is the most critical: it covers design pillars, the core loop, mechanics, progression, content plan, UI/UX, and monetization. It is a shared source of truth, not a finished manuscript. The technical assessment documents engine and platform choices, performance targets, middleware, architecture decisions, and a risk register for unresolved technical unknowns. The art direction package, covering concept art, mood boards, a style bible, and character and environment references, sets the visual bar the team will hold for the rest of development.

This planning stage runs on a small, senior team. The core group for most projects is a game director, lead game designer, technical director, art director, and producer. This is not the moment to staff up; it is the moment to align before you staff up. Studios that lack depth in one of these roles pay a real cost: the gap surfaces during full production, when it is far more expensive to address.

How long does pre-production realistically take?

Planning typically represents 10–20% of total development time, and the phase ends when exit criteria are met, not when a calendar date arrives.

Project scaleTypical durationWhat it must establish
Small indie2–8 weeksCore concept, playable prototype, basic scope, initial art direction
Mid-sized / AA2–6 monthsValidated game loop, technical plan, repeatable art pipeline, credible budget
AAA / large-scale6–18 monthsVertical slice, engine and tooling decisions, staffing plans for large teams

Scope and content volume matter most: more levels, characters, and game modes require longer planning regardless of how simple the core mechanic is. Technical risk adds investigation time that cannot be compressed. Scope stability is the single most controllable variable, every major design pivot resets planning work, so locking scope early has an outsized effect on the final timeline.

Which prototypes should you build first?

Core-mechanic prototype

Start here: build the game’s defining verb, movement, combat, building, dialogue, in a greybox environment with placeholder assets. The question at this stage is “is this fun?” not “is this polished?” Responsiveness, game feel, and repeatability are what you are testing.

Core-loop prototype

The second priority connects explore, encounter, fail, and progress in the simplest possible chain to test pacing and player motivation.

Technical proof of concept

Third is the highest-risk technical question. Whatever could invalidate the entire project, a networking model, procedural system, streaming world, or platform performance target, must be tested on real hardware under realistic conditions before production begins.

Vertical slice

The vertical slice comes last, not first. One short, complete section at near-final quality sets the quality bar, validates end-to-end production, and produces the data needed to estimate cost and schedule for the rest of the game. Every prototype should carry a written success criterion and a stop condition.

How do you know when pre-production is done?

The greenlight review is a structured decision, not a formality. A production-ready project meets five criteria:

  • The GDD reflects an agreed, locked scope with must-have features separated from nice-to-haves.
  • The core mechanic is fun and the riskiest technical question has been answered on real hardware.
  • The team has produced representative assets within the intended quality bar and knows how long that process takes.
  • The production plan is built from validated data, not pre-prototype estimates.
  • The game director, technical director, art director, and lead designer are identified and available for full production.

Common reasons projects fail greenlight: core loop not validated, technical risk still open, scope still in flux, or budget built on assumptions made before prototyping began. A soft greenlight, where limited preparation continues while open items resolve, is preferable to a hard greenlight with unresolved critical dependencies.

Why bring in an external studio during pre-production?

Internal teams close to an idea often underestimate technical risk and overestimate the scope they can deliver. A co-development studio with full-cycle experience can run the technical assessment, prototype risky systems, structure the art pipeline, and pressure-test the production plan before any of these decisions become expensive to change. Studios on tight timelines benefit from embedding a dedicated external team immediately rather than hiring, onboarding, and later making redundant full-time staff.

Kokku is a full-cycle co-development studio with offices in Latin America and Europe, with proven partnerships across AAA and AA titles with publishers including Electronic Arts, Activision and Guerrilla Games. A studio can bring Kokku in at day one of planning and carry the same embedded team all the way through production, spanning concept and prototype through vertical slice, demo, and final release. For studios that need art direction validated without building a full internal art department, Kokku provides 2D/3D art production across realistic and stylized styles, covering characters, environments, and props, which can be used to validate art direction during pre-production.

Pre-production checklist: what to confirm before you greenlight

  • Vision and pitch document written and shared with key stakeholders
  • Game design document drafted, with must-have features locked and nice-to-haves separated
  • Core-mechanic prototype built and tested for fun, responsiveness, and repeatability
  • Core-loop prototype validated for pacing and player motivation
  • Highest-risk technical proof of concept tested on real hardware
  • Vertical slice completed at near-final quality
  • Art direction package finalized (concept art, mood boards, style bible, character and environment references)
  • Technical assessment complete, including engine and platform choices, middleware, and risk register
  • Production plan built from prototype-validated data, not early estimates
  • Core leadership team (game director, technical director, art director, lead designer, producer) identified and committed

Plan the phase, then scale the team

Pre-production is where you prove the game is fun, feasible, and appropriately scoped. The deliverables, GDD, prototypes, vertical slice, technical assessment, art direction, and production plan, are the evidence that each of those questions has been answered with real data rather than optimistic guesses.

Industry guidance consistently shows that studios investing seriously in this stage ship faster and spend less in full production. Those that rush it spend the same time fixing problems later, under higher pressure and at greater cost. If your studio is entering a new project and pre-production resources are thin, get in touch with our team: an experienced co-development partner can help compress the timeline without compromising the work.

Frequently Asked Questions

Who should be on the small senior team during pre-production if we want to be minimally effective?

The core small senior team should be a game director, lead game designer, technical director, art director, and producer. These roles align direction, design, technical decisions, and production planning before you staff up, and lacking depth in any of them creates expensive gaps later in production.

When should we bring in an external co-development studio instead of hiring full-time staff?

You should bring in an external co-development studio when pre-production resources are thin or when you need to compress the timeline without compromising work. An external studio can run technical assessments, prototype risky systems, and validate art direction faster and cheaper than hiring and onboarding full-time staff, and can embed a dedicated team from day one through production if needed.

What are the most common reasons projects fail their greenlight review?

Projects most often fail greenlight because the core loop isn’t validated, technical risk is still open, scope is in flux, or the budget is based on pre-prototype assumptions. These unresolved items mean the project lacks the validated data required for a credible decision that the game is fun, feasible, and appropriately scoped.

How should we define success criteria for prototypes so we know when to stop them?

Each prototype should carry a written success criterion and a stop condition that define what counts as validation and when to end work. That ensures prototypes focus on testing the right question, fun for core mechanics, pacing for core loop, and feasibility for technical proofs, so you only advance when those specific risks are resolved.