Chapter 31 — Further Reading

The literature on playtesting splits across three traditions: game-design craft (designers writing for designers), usability research (academics and practitioners writing about user testing of software in general), and games user research / GUR (a hybrid field that emerged in the last fifteen years to apply usability methods to games specifically). The strongest practitioners draw from all three.

The list below mixes books, talks, and online resources. Read at least two from outside your usual diet — if you mostly read GDC talks, pick up a book; if you mostly read academic papers, watch a talk.

1. Jesse Schell, The Art of Game Design: A Book of Lenses (3rd edition, CRC Press, 2019). Chapters on playtesting and prototyping.

Schell's chapters on playtesting are widely assigned and for good reason. He frames testing as an iterative discipline embedded in the design process from day one, not as a phase that begins after development ends. The "Lens of the Playtester" lens — one of the book's hundred design lenses — asks the designer to imagine the test before designing the prototype. The book's strength is its breadth across all of design; its weakness is that the playtest material does not go as deep as a specialist book would. A good first read for designers who haven't formally studied testing before.

2. Steve Krug, Rocket Surgery Made Easy: The Do-It-Yourself Guide to Finding and Fixing Usability Problems (New Riders, 2009).

Krug is not a games writer; he is a software-usability practitioner. Rocket Surgery is a short, opinionated, deeply practical guide to running cheap, frequent usability tests on a budget. Almost everything in it transfers directly to games. The chapter on "the morning after" — what you do with findings the day after a session — is particularly strong. Krug's larger book Don't Make Me Think (3rd edition, 2014) is the more famous work, but Rocket Surgery is the one to read for the testing practice itself. If you read only one source on this list, read this one.

3. Anders Drachen, Pejman Mirza-Babaei, and Lennart Nacke, eds., Games User Research (Oxford University Press, 2018).

The current standard academic reference for the games user research field. Twenty-plus chapters by working researchers covering methods (think-aloud, biometrics, retrospective protocols, A/B testing), specific contexts (mobile, VR, multiplayer), and case studies. Denser than Krug or Schell; more rigorous on method. If you are building a testing program at studio scale or considering hiring a researcher, this is the book to ground your practice in. If you are a solo developer running occasional sessions, you can skim — most of the book is more apparatus than you need, but the methods chapters reward careful reading.

4. Robin Walker, "The Cabal: Valve's Design Process for Creating Half-Life" (Gamasutra, 1999, archived widely).

A primary-source description of Valve's cabal process for Half-Life, written by one of its lead developers. Predates the company's later refinements but captures the originating spirit: small, cross-functional review groups responsible for evaluating playtest data and making design decisions together. The article is short, free online, and central to understanding modern playtest culture. Valve's later practice elaborates on what this article describes; the foundations are here.

5. Erik Wolpaw, Chet Faliszek, et al., GDC talks on Valve's playtest practice (multiple years, available on the GDC Vault and YouTube).

Across many GDC sessions over the years, various Valve developers have spoken about the studio's playtest culture. Specific talks worth seeking out: the Portal postmortem (Kim Swift and Erik Wolpaw, GDC 2008), various Left 4 Dead talks on the Director system (Mike Booth, Kerry Davis), and Gabe Newell's occasional keynote-style remarks on the studio's culture. The talks are uneven — some are thirty minutes of war stories, some are deeply structural — but together they form a corpus of public documentation that, with some patience, paints a clear picture of what the studio actually does.

6. Ilkka Paananen, public talks and writings on Supercell's culture (multiple, including SuperCell's blog "the kill rate" essays).

Paananen, Supercell's CEO, has written and spoken at length about the company's celebrate-killed-projects culture. His Slush talks (Helsinki's tech conference) are the longest-form sources; shorter pieces appear on the Supercell blog and in industry interviews. The discussion of the soft-launch protocol and the kill thresholds is publicly opaque (the actual numbers are secret), but the framing — why the practice exists, what it is meant to accomplish, why the cultural ritual matters — is well documented. Read at least one Paananen piece if you want to understand the institutional layer that makes Supercell's analytics-driven testing actually work.

7. Jakob Nielsen, "Why You Only Need to Test with 5 Users" (Nielsen Norman Group, 2000). And the broader NN/g body of work.

The classic article that established the rule of thumb that 5 users will surface roughly 80 percent of major usability issues in an interface. Frequently cited, sometimes misapplied (it is about interfaces, not full games, and games typically need more testers per round than 5 because of higher experiential variance). The article and Nielsen's other writings on usability heuristics are foundational to modern UX testing and worth reading in original form rather than through second-hand summaries. Free on nngroup.com; the broader Nielsen Norman Group archive contains decades of accessible practitioner writing.

8. Tracy Fullerton, Game Design Workshop: A Playcentric Approach to Creating Innovative Games (4th edition, CRC Press, 2018).

Fullerton's book is the standard textbook in many game design programs and includes substantial material on iterative playtesting embedded throughout the design process. The book's "playcentric" framing is essentially a pedagogy of playtesting — every prototype, every iteration, every chapter ends with a "test it" exercise. Read alongside Schell for breadth, and pay particular attention to the prototyping chapters, which present the testing rationale for why each kind of prototype exists.

9. PlaytestCloud's blog and case-study library (playtestcloud.com/blog).

PlaytestCloud, the major paid playtesting service for games, maintains a blog with practitioner-facing articles on running effective sessions, recruiting testers, interpreting results, and avoiding common pitfalls. The blog is partly marketing for the service and partly a genuine knowledge base; the case studies (where they document specific findings from their tests for client games) are particularly valuable for seeing what real playtest reports look like. Free, publicly accessible, and updated regularly.

10. Mike Ambinder, GDC talks on biometric playtesting at Valve.

Ambinder, Valve's experimental psychologist, has given several GDC talks on the studio's experiments with biometric data — heart rate, galvanic skin response, eye tracking — as supplementary signal alongside traditional observation. The talks document a more advanced testing infrastructure than most studios will ever build, but they illustrate where the field is heading and what questions biometric data can answer that traditional methods cannot. Watch as future-looking speculation; do not feel obligated to install eye trackers tomorrow.

11. Daniel Cook, "Loops and Arcs" and other essays at Lost Garden (lostgarden.com).

Cook's blog has been one of the most thoughtful long-form game design resources for two decades. His writing on loops, arcs, and player progression is not strictly about playtesting, but the underlying analytical framework — how to think structurally about what a game is doing for the player — is essential context for designing tests that ask the right questions. Read several of his foundational essays alongside the explicit playtesting literature; together, they sharpen your instinct for what to test for.

12. Game Developer magazine post-mortems (archived at gamedeveloper.com).

For decades, Game Developer (formerly Game Developer Magazine and Gamasutra) ran a regular post-mortem feature in which shipped games' lead developers wrote essays on what went right and what went wrong. Hundreds are archived. Read several from games you know — the post-mortems for Diablo II, Civilization II, Thief: The Dark Project, Portal, Bastion, Spelunky, Minecraft, and many others are public. Pay attention to what each team says about playtesting: when they did it, how, what they learned, what they failed to catch. The patterns across post-mortems are themselves a curriculum in playtest practice.

Suggested Reading Path

For a focused first pass: Krug's Rocket Surgery Made Easy (compact, transformative), then Schell's playtesting chapters (broader context), then two or three GDC talks on Valve's practice, then a half-dozen post-mortems from games you have played. Total time: roughly 12-15 hours. You will be operating at a different level afterward.

For deeper specialization: add Drachen et al.'s Games User Research and Fullerton's Game Design Workshop in full. Subscribe to the GDC Vault for searchable access to industry talks. Consider attending a GDC summit on Games User Research if your career is moving in that direction; the field has small, accessible, generous practitioners who are unusually willing to share methodology.

For studio leads: read all of the above plus Paananen's Supercell writings and as many post-mortems as you can stomach. Pay close attention to the cultural-layer commentary in each. Building a playtest practice in your studio will be 30% methodology and 70% culture; the methodology is the easy part.

The reading is not a substitute for running sessions. The reading speeds up your sessions. Do both.