This document discusses game development methodology, specifically focusing on the pre-production phase. Some key points made: 1. Pre-production is for experimenting with prototypes and designing the game at a macro level before full production begins. This includes defining core gameplay and the first "publishable" playable build. 2. Many common beliefs around milestones, technology development, and design documentation are debunked. Instead, the document advocates for minimal documentation, parallel technology and gameplay development, and canceling projects if the first playable is unsatisfactory. 3. Production properly begins after pre-production delivers a "publishable" first playable build and macro design document defining the overall game structure at a high level in 5

1. ““METHOD”METHOD”
Cerny Games, Inc.
Mark Cerny

2. ““METHOD”METHOD”
1.Pre-Production vs. Production
2.“Publishable” First Playable
3.Macro vs Micro Design
4.Gameplay Testing

3. Method, part 1:Method, part 1:
Preproduction vs. ProductionPreproduction vs. Production
“Capturing Lightning”
Pre-Production
“Building the game”
Production

4. “IT IS POSSIBLE TO
PLAN AND SCHEDULE
THE CREATION OF
YOUR GAME”
MYTH #1: PLANNING

5. Pre-Production:Pre-Production:
Managing ChaosManaging Chaos
• assemble core team
• create successive prototypes
• prototypes become like game levels

6. “WORKING
PRODUCTIVELY MEANS
THROWING OUT
NOTHING.”
MYTH #2: PRODUCTIVITY

7. Pre-ProductionPre-Production
• you are not making a game
 3 C's: character, camera, control
 game look
 key technology
 holistic game design (if appropriate)
• you are making a game design

8. Pre-ProductionPre-Production
• take chances
• build without knowledge of moveset
• build without knowledge of tech limits
• don’t know the context of what you’re
working on
• etc…

9. “cutting edge technology is
important, so build your
technology first.”
MYTH #3: TECHNOLOGY

10. TECHNOLOGYTECHNOLOGY
STANDARD PRACTICESTANDARD PRACTICE
Create Design Document
↓
Create “Required Technology” Document
↓
Build Technology
↓
Build Game

11. DOUBLE-TRACK IT!DOUBLE-TRACK IT!
• Build, borrow or buy “Quick and Dirty”
Tech for rapid prototyping
• Build “Cutting Edge” Tech for actual game

12. “FREQUENT PROJECT
REVIEW IS IS ESSENTIAL
TO GOOD MANAGEMENT.”
MYTH #4: MILESTONES

13. Pre-production and milestonesPre-production and milestones
• negotiated term for Pre-Production
• strict deliverables for Pre-Production
 first playable
 macro design
• results of experiments are visible externally
• no “stench of failure”
• “offline” status for team during Pre-Production

14. Deliverables at end of Pre-Production
• “Publishable” First Playable
• Macro Game Design

15. MYTH #5:
“ALPHA =
FIRST PLAYABLE”

16. Method, Part 2:Method, Part 2:
The First PlayableThe First Playable
OVERVIEW
• two levels
• all local features, global features as appropriate
• publishable quality

17. First Playable ChecklistFirst Playable Checklist
Two levels of publishable quality, with:
__ player behavior fully defined __ basic technology done
__ enemy/obstacle behavior fully
defined
__ art direction in place
__ all local features included,
global features included as
required
__ a touch of variety
__ scope of game defined

18. “A cancelled project is a sign of bad
management or a bad team.”
MYTH #6: KILLING GAMES

19. Canceling ProjectsCanceling Projects
• Team cannot create “Publishable” First
Playable
• First Playable shows game not worth
publishing
• Your project will not miraculously get
better during Production!

20. Method, Part 3:Method, Part 3:
Macro vs Micro DesignMacro vs Micro Design
• Macro in hand at start of Production
• Micro created during Production

21. “THE MORE DEFINED YOUR
INITIAL VISION, THE BETTER”
MYTH #7: DESIGN DOCUMENTS

22. “I NEED A 100-PAGE DOCUMENT
DESCRIBING MY GAME.”
MYTH #7: DESIGN DOCUMENTS

23. Why no 100-page design document?Why no 100-page design document?
• waste of resources
• deceptive and misleading
• sets direction prior to verification of fundamentals

24. Method, Part 3:Method, Part 3:
Macro vs Micro DesignMacro vs Micro Design
Macro Design
__ five pages
__ character and moveset
__ exotic mechanics
__ level structure, size and count
__ level contents
__ overarching structure – linear, hub
__ macro chart

25. Macro ChartMacro Chart
locale level
structure
exotic
gameplay
required for
level entry
received
in level
1 Jungle 3-D Egg
2 Volcano 3-D run from lava Egg
3 Snow 2-D ice (training) Egg
4 Desert 3-D motorcycle 1 egg Egg
5 Locale A 2-D - 2 eggs Egg
6 Snow 2-D ice 4 eggs Key
7 Locale B BOSS - Key open hub 2

26. Benefits of aBenefits of a
Macro DesignMacro Design
• can accurately schedule Production
• can track progress during Production
• prevents feature creep and feature drop
• properly circumscribes creativity

27. [Macro Design extras][Macro Design extras]
• brief story
• conceptual art
• acquired abilities or inventory
(holistic games only)

28. Micro DesignMicro Design
Micro Design
• script
• level maps
• enemy descriptions, behaviors
• puzzle descriptions
• special gameplay descriptions
• and much more

29. “If you want to make a hit, listen to the
consumer.”
MYTH #8: THE CONSUMER

30. What You'll Learn from a Focus TestWhat You'll Learn from a Focus Test
• What's popular as of ten minutes ago
• How not to stand out
• The feature list of every recent game that
was pretty good

31. Gameplay TestingGameplay Testing
• two to five times
• watch what they do
• quantitative analysis

32. SETTING IT UPSETTING IT UP
• preproduction-based funding
• greenlight is at first playable
• best and brightest
• ‘housekeeping’ deal during preproduction
• production as usual

33. SETTING IT UPSETTING IT UP
• In the event of cancellation…
• Publisher owns IP, but cannot develop it
with another team
• Developer may purchase IP at cost of
development to date

34. Developer RisksDeveloper Risks
• Lack of full-term publisher commitment
• Full team not employed during pre-
production
• Uncomfortable level of transparency to
publisher

35. Publisher RisksPublisher Risks
• Start projects with only a rough release
date
• Preproduction is expensive
• No milestones = no pressure?

36. Publisher BenefitsPublisher Benefits
• Low cost of entry for projects
• Very close publisher/developer relationship
• Accurate production schedule and budget

37. Thank YouThank You