
The Art of Game Design
One hundred lenses to master
Description
Jesse Schell has designed theme-park rides for Disney, taught at Carnegie Mellon, and run a studio that builds everything from virtual worlds to educational games. When he sat down in 2008 to write down what he actually knew about making games, he made a strange choice for a technical field: he barely mentioned technology. His book, The Art of Game Design, opens instead with the claim that a game designer needs no programming, no art degree, no engine expertise. What the job requires, he argues, is the ability to see clearly what an experience feels like from the inside — and most people, most of the time, cannot.
That premise reframes the whole discipline. If the fundamentals of Monopoly and the fundamentals of a sprawling video game are the same, then the interesting questions are not about hardware. They are about attention, fairness, surprise, the small ache of wanting to win — the psychology that makes a card game at a kitchen table just as gripping as anything on a screen. Schell's bet is that this psychology can be studied, and that a designer who studies it can improve any game, in any medium, without touching a line of code.
The trouble is that experiences are slippery. We can't hold one in our hands, take it apart, and see why it isn't working. Schell's answer is a tool — actually a hundred of them — borrowed from architecture, music, film, anthropology, and a dozen other fields that spent centuries learning to design for human beings. The book has become a fixture in studios and classrooms precisely because it gives the fuzziest craft imaginable something to hold onto.
The question we’re asking : If game design needs no technology, what does it actually need — and can that be taught?What we’ll see : How a theme-park designer turned an unteachable craft into a set of practical questions anyone can learn to ask.
Table of contents
01Chapter 1 — The job nobody trained for
Schell begins with a confession most working designers would recognize: nobody grows up trained for this. There is no clean pipeline, no single credential, no obvious major. The people who end up designing games arrive from writing, from math, from music, from psychology, from theater — and Schell's point is that this is a feature, not an accident. Game design sits at the crossing of all those fields because a game is not one thing. It is rules and story and space and rhythm and feeling, all at once, and no single discipline owns the whole.
So he defines the designer's real material carefully. A game is not the box, the board, or the screen. Those are artifacts. The game is the experience that arises when a player engages with them — and the experience lives only in the player's head. This is the uncomfortable truth at the center of the book. We can build the artifact with precision, but we cannot build the experience directly. We can only build a machine and hope the experience we intended comes out the other side. The designer works one step removed from the thing they actually care about.
02Chapter 2 — A hundred ways to look at the same thing
Schell's solution is the idea that gives the book its subtitle: the lens. A lens is not a rule and not a formula. It is a short set of questions you hold up to your game to see it from one particular angle. The lens of fun asks what parts of your game are pleasurable and why, and which parts could use more. The lens of surprise asks where your game will surprise the player, and whether you've surprised yourself. Each one is small, portable, and deliberately incomplete — a single perspective, nothing more.
The reason there are a hundred is that no single view tells the truth about a design. A game that looks balanced through the lens of fairness might look lifeless through the lens of challenge. A story that reads beautifully on paper might collapse the moment you view it through the lens of the player's freedom to act. Schell's claim is that good design happens in the switching — the constant rotation between viewpoints, catching the problems that any one angle would hide. A designer with one favorite lens makes the same mistake over and over. A designer with a hundred keeps finding new things wrong, which is another way of saying keeps finding ways to make it better.
03Chapter 3 — The player is the only judge
For all the lenses drawn from other fields, Schell keeps returning the reader to a single fact: the player decides. A designer can love a mechanic, defend it in meetings, and build a beautiful version of it — and none of that matters if players don't feel what was intended. The experience is the verdict, and the only place the experience exists is inside someone else's head. So the designer's job is not to be right in the abstract. It is to keep checking, against real people, whether the machine is producing what they hoped.
This is why the book takes playtesting so seriously, and why it treats it as harder than it looks. Watching someone play your game is emotionally difficult; the instinct is to explain, to defend, to point out what they missed. Schell argues for the opposite discipline — say nothing, watch everything. The confusion on a tester's face is not a failure of the player; it is data about the design. A tester who quits early is telling you something you need to hear more than any praise. The designer who can absorb that without flinching learns faster than the one who argues.
04Chapter 4 — What listening actually looks like
Step back from games entirely, and Schell's method turns out to be a manual for a broader craft: designing experiences by paying disciplined attention to the people who will live inside them. The reason the lenses come from architecture, film, music, and theme-park design is that all of these are, at bottom, the same job. Someone builds a structure — a building, a scene, a ride, a rule set — and hopes it produces a particular feeling in a stranger. The builder never gets to install the feeling directly. They can only shape the conditions and then watch what happens. Game design just makes this ancient problem unusually visible, because a game fails so quickly and so obviously when the feeling doesn't arrive.
Seen this way, the hundred lenses are not really about games; they are about the humility the work demands. Each lens is a small admission that your own point of view is not enough, that the thing you built will be experienced by someone who is not you, and that the only way to know if it works is to look through as many eyes as you can borrow. Schell keeps naming this quality — the willingness to be told you are wrong by a confused eleven-year-old at a playtest table, and to treat that as the most valuable thing that happened all week.
05Conclusion
Schell set out to write down what he knew about a job with no obvious training, and ended up describing something larger than games. His designer is not a technologist but an unusually careful observer — someone who treats an experience as real material, accepts that it lives out of reach inside another person, and builds anyway, checking constantly against the only judge that counts. The hundred lenses are the working form of that patience: a hundred ways to distrust your first impression and look again.













