Source metadata
- Type: Textbook / practitioner’s guide
- Author: Jai Kristjan
- Publisher: CRC Press / Taylor & Francis
- Year: 2019 (copyright 2020)
- Structure: 10 chapters (Preparation → Blue Sky → Pre-production → Production → Alpha → Beta → Final → Post-release → Live → Miscellaneous)
What this book is
A practitioner’s survival guide structured around the game development lifecycle. Each chapter covers one production phase with short, punchy sections offering concrete advice from Kristjan’s 15+ years of industry experience. The tone is deliberately informal, motivational, and experience-based — the author explicitly positions it as “tribal knowledge” that is not being passed on to new designers.
Unlike most design theory textbooks in this wiki, this book is concerned with how to survive and behave on a development team, not just design principles. Its central design argument is that enemies and antagonists in games are consistently underdesigned, and that fixing this requires intention, not just time.
Key takeaways
- The development lifecycle as the central frame. Kristjan’s nine phases — Preparation, Blue Sky, Pre-production, Production, Alpha, Beta, Final, Post-release, Live — provide a practitioner’s mental model for where you are in any project and what your priorities should be at each phase.
- Blue Sky = ideation. The Blue Sky phase (also called high concept or concept phase) is where game ideas are born. The output is the elevator pitch: a phrase, sentence, or paragraph that sells the soul of the game. Rushing through Blue Sky is a common failure mode.
- The Goblin Encounter problem. The book’s title concept: enemies and bosses in most games are cardboard cutouts — present to fill space, not because they serve the game. The fix is giving every encounter a reason to exist, a motivation, and the possibility of being memorable.
- Make villains vibrant. Enemies, including the lowest-level mobs, should have motivation, context, and presence. The boss encounter is a “closed loop” where every variable can be played with to create a more fulfilling experience.
- Three levels of complexity (Good/Bad/Ugly). Every design should be written in three tiers: the best-case full implementation, the stripped-down core version, and the bare-bones minimum that still contributes to the game. This allows scope to flex without losing design intent.
- CTRL-X. Feature cutting is an essential designer skill — knowing what to cut (and having a pre-prepared list) converts a painful loss into a managed decision.
- Never stop prototyping. Prototyping is not just a pre-production activity. Continuous prototyping throughout development can pivot a failing game and should be scheduled throughout the project cycle, not just at the beginning.
- Visual storytelling. Art should be designed as a character that evolves through gameplay, not as a decorative layer. Players can be guided through environments entirely through visual cues without explicit instruction.
- Evoking emotions deliberately. Design a primary emotion for the game, secondary emotions per act/section, and tertiary micro-emotions per level. “Make it fun” is one-note; emotional variety makes games memorable.
- The generalist designer ideal. Kristjan argues against designer specialisation as an industry norm — the best designers are “jack of all trades, master of none, but better than everyone else at a wide array of skills.” Large AAA production is fracturing this ideal.
- “What are you doing right now to make the game better?” Kristjan’s central professional mantra — borrowed from an early mentor — as a constant self-check for designers.
Notable claims
“We deserve better everything in video games… games are routinely starting again from scratch, destined to repeat the same mistakes. This practical or tribal knowledge is not being passed along.” — Kristjan, Preface
“The greatest designer in the room is not the person with all of the best ideas or the greatest experience or even technical know-how. They are the person who can tell a story better than anyone else in that room.” — Kristjan, Ch. 2
“The boss encounter is a closed loop where you can play with all of the variables to make it a better and more fulfilling adventure for the player to go through.” — Kristjan, Ch. 4
“Old designers tend to focus on smaller games, because that way they get to offer everything of themselves to the job they love.” — Kristjan, Ch. 10
Relevance
This source primarily informs:
- villain-design — the Goblin Encounter, making enemies vibrant, boss design, meaningful encounters (created from this source)
- game-design-documentation — elevator pitch / Blue Sky phase; three levels of complexity (Good/Bad/Ugly)
- level-design — encounter-based level structure (beginning/middle/end); level as mixtape
- prototyping — continuous prototyping throughout development, not just at the start
It also connects to:
- narrative-design — backstory, evoking emotions deliberately, primary/secondary/tertiary emotional structure
- game-industry-realities — practitioner experience of crunch, team dynamics, production phase realities
- scrum-in-game-development — parallel view of the development lifecycle from a designer’s (rather than Scrum practitioner’s) perspective
Open questions raised
- The book’s generalist-designer argument conflicts with the industry trend toward specialisation. Is this a genuine tension or a scale problem — does Kristjan’s model apply to small/indie teams but break at AAA scale?
- “Make villains vibrant” is argued from a design quality perspective. Is there a commercial or player research case for the same claim — do players demonstrably respond better to enemies with motivation?