Lesson 2 · Part 1: Play
Thinking Like a Designer
How designers think: trading one good thing for another, starting from limits, cutting most of what they try, and knowing when to stop.
Thinking Like a Designer
You need a chair for your desk, and the shop has forty of them. One is cheap and makes your back ache after an hour. One is a cloud you could sink into, and it costs a month’s rent. One folds flat and wobbles. One would survive a house fire and takes two people to lift. You walk the aisle twice, looking for the chair that’s cheap and comfy and light and solid, and it isn’t there.
Nobody forgot to make it. It can’t be made. Every chair in that shop is somebody’s decision about what to give up.
Game designers stand in that aisle every day, except their chairs haven’t been built yet. This lesson is about how they choose what to give up, and why the limits they grumble about are usually where the good ideas start.
Everything pulls on everything else
Pick a driver in Mario Kart, the cartoon racing game, and you’re making a deal. Heavy drivers reach a higher top speed but take longer to get going. Light ones shoot off the line and get knocked about in a crash. Fighting games make the same deal with their characters: the big wrestler hits hard and moves slowly, and the small, quick fighter hits lightly and is gone before you can swing back.
That deal is a trade off: getting more of one thing you want by accepting less of another. The qualities are tied together with invisible string. Pull one up and another comes down.
Whole games are built out of trade-offs like this. Easy to learn or deep enough to play for years. Short enough for a bus ride or long enough to get lost in. Lots of luck, so a beginner can win, or lots of skill, so practice pays off. Mario Kart leans toward luck on purpose: players near the back get handed stronger items, so a beginner can still beat their big sister. A chess player would hate that. Neither game is wrong. They settled the same trade-off at opposite ends.
A beginner’s instinct is to add: one more power, one more weapon, one more rule. A designer’s first question about any addition is what it will cost somewhere else, because it always costs something.
Limits are where you start
Charles and Ray Eames, a husband-and-wife team who designed some of the best-known chairs of the last century, believed that design depends largely on constraints. A constraint is a limit you have to work inside: a budget, a deadline, a screen size, a rule you can’t break.
Video games are full of famous constraints. When Shigeru Miyamoto drew Mario for the arcade game Donkey Kong in 1981, the hero had to fit in a tiny grid of pixels with only a few colors. A mouth didn’t show up at that size, so Mario got a big mustache. Hair was hard to draw and animate, so he got a cap. Overalls in a second color made his arms easy to see as he ran. The limits did a lot of the designing.
“Within this constraint, what can I do that’s really cool?”
It’s tempting to treat limits as the enemy. Usually they’re the opposite. With no limits there’s nothing to solve, only a daydream. Accept a limit and the question gets sharp, and sharp questions are the ones you can answer. That’s why game jams, where people make a game in a weekend, hand everyone a theme at the start. A blank page is the hardest place to begin.
Some constraints are technical, like the size of the screen or the speed of the machine. Others are human and easy to forget: what your players already know, what their hands can do, how long they can sit still. A phone game played on a crowded bus has to work with one thumb, in short bursts, with the sound off. Whole kinds of game grew out of exactly that.
This is good news if you’re starting with no budget, no team, and no idea how to code. “A game for two people, played with ten coins, done in five minutes” is a much easier thing to begin than “a game.”
The tree, and the cutting
Every finished game sits at the end of a long chain of decisions. The early ones are huge. What’s it about? Do you see the world from the side or from above? Do you play alone or with friends? The later ones are tiny: the color of a coin, the sound of a door. Each answer opens up questions that wouldn’t exist if you’d answered differently.
Picture it as a design tree. Your first idea is the trunk. Every decision splits it into branches, every branch splits again, and out at the tips are all the games you could possibly end up making. There are more tips than you could ever visit, and you’re going to arrive at one of them.
On a team, those decisions are spread across lots of people, often without anyone noticing. The artist drawing the hero is choosing branches. So is the person writing the music. That’s why everyone needs a shared design vision, a common sense of where the game is heading, so that small choices made far apart still point the same way. Level 20 comes back to this.
You can’t walk down every branch to see what’s at the end, so the practical skill is pruning: ruling out branches as early and as cheaply as you can. Gardeners do this to rose bushes. Cut the plant back hard and it puts everything into the stems that are left.
The best pruning tool is the prototype: a small, rough version of one piece of a game, built to answer one question. Should the hero jump or dash? Build both in an afternoon, play each for ten minutes, and cut one. A prototype that can’t tell you which way to go hasn’t done its job, however nice it looks. Level 16 is all about these.
If you’re pruning well, most of what you try ends up on the floor. A desk covered in crossed-out ideas is what the process looks like when it’s working.
Knowing when to stop
There’s an end to all this, and recognizing it is a skill of its own. Many action games shake the screen a little when you land a hit, which makes the blow feel solid. Shake it a lot and players feel seasick and can’t see what’s coming. A little was good. More wasn’t better.
The place to stop is the sweet spot: the point where the parts are in balance, and pushing further in any direction makes the whole thing worse. Think of salting soup. Too little and it’s flat. Too much and it’s ruined. Somewhere in between it’s just right, and you only find it by tasting. Every game has a sweet spot, and so does every rule and every number inside it. It isn’t always in the middle, either. Sometimes the right amount of something is none at all.
Nobody can hand you a formula for finding it. You learn it by finishing things, noticing which ones you overcooked, and adjusting next time. That goes much faster if the things you finish are small, so make lots of tiny games. Draw one on a napkin, or invent a contest with the toothpicks on the table. That’s play from Level 1, pointed at design: cheap, quick, and every mistake teaches you something.
Try it · Pocket Game, step 2Three limits and a tree
Take the objects and the goal from step 1. Accept three constraints: the game is for two players, it lasts five minutes, and everything fits in one pocket. On a sheet of paper, write your goal at the bottom as the trunk. Draw three branches for three different ways two people could chase that goal, such as taking turns, racing at the same time, or working together. Under each, write one sentence about how a round would go. Play each version for a minute, moving for both sides if nobody’s around. Cross out two branches. Keep the paper with the crossings-out visible, because they’re part of the work.
Carry forward: Accept your limits, know what each choice costs, try lots of small things, and expect to cut most of them.
Check
Pack the pocket
Pack a game for Mia and Leo. It has to fit in a pocket and be over in five minutes, and both of them have to want to play.