THE READING ROOM / BOOK GUIDE
The Art of Game Design
A working designer's book about the decisions behind playable systems, built around a set of questions that ask you to look at a game from many angles before committing to a choice.
About the book
Jesse Schell writes about game design as a craft of judgment rather than a formula. The book addresses the people who make games and the choices they face: what a player should feel, how rules and feedback shape that feeling, and how a designer tests whether the intended experience actually arrives. Schell draws on his background in interactive entertainment and theme-park design, and the book reflects that range, treating games as experiences assembled from mechanics, interface, story, sound and space.
The organizing device is the lens: a short set of questions a designer can hold up to a project to see it differently. Each lens isolates one concern, such as the player's motivation, the clarity of feedback, or the balance between challenge and skill. The approach suits readers who want prompts for thinking rather than a single prescribed method. Schell moves between principle and practical example, and the book's scope is broad enough to cover tabletop and digital games without treating them as separate disciplines.
The result is part reference and part argument about how design work gets done. Schell treats prototyping, playtesting and iteration as central to the job, and he returns often to the gap between what a designer intends and what a player perceives. That emphasis gives the book a practical spine even where the discussion turns philosophical about play, pleasure and meaning.
How to read it
Read the lenses as tools, not commandments. Each one is a prompt for inspection, and the useful move is to apply several to the same design problem and notice where they disagree. The book rewards selective reading: a designer stuck on a specific issue can go to the relevant lens rather than working front to back.
The prose is conversational and example-heavy, which makes the material approachable for newcomers but can leave experienced designers wanting more depth on any single topic. Treat the examples as illustrations of a way of thinking rather than as templates to copy. Keep a current project in mind while reading; the questions land harder when there is something concrete to test them against.
Who it suits
This suits people starting out in game design who want a structured way to think about player experience, and developers from other software backgrounds who need to shift from building features to shaping how those features feel. Teachers and workshop leaders will find the lens format easy to adapt for exercises. Designers working on tabletop games, interactive installations or educational games will recognize concerns that cross those formats. Readers who want a technical manual on engines or programming will need to look elsewhere.
Reading considerations
The book is a broad survey rather than a deep treatment of any one area, and its examples date from the late 2000s, so some platform and business references will feel of their time. Later editions expand the material, so check which version you have before relying on a page reference. The lens framework is persuasive but untested as a guarantee; the real question is whether its questions sharpen your own judgment on a live project.
Follow the HN conversation
35 different recommenders are recorded in the upstream dataset. These are AI-classified source counts, not an independent rating.
Search HN comments about this book ↗
Explore videos on the same subject ↗
Book notes prepared with DeepSeek, using catalogue records and Open Library subject information. They are reading guidance, not a personal review or a verified chapter-by-chapter account. Book details can vary by edition. HN data methodology · Book metadata and covers.
