Lesson 22 · Part 6: Sharing It
The Designer's Eye
The last level: ten questions an experienced designer asks of any game in progress, how to ask them kindly, and what to make next.
The Designer’s Eye
A friend slides a homemade card game across the kitchen table. “I made this. Be honest.” You play two rounds. Somebody wins, sort of. You hand the cards back and say, “It’s fun! Maybe add more cards?”
Your friend learned nothing, and you both know it. You’ve just spent twenty-one levels collecting ideas, and none of them came out of your mouth. The problem isn’t that you don’t know enough. You just don’t have a quick way to point what you know at a real game. This last level fixes that, and then it sends you off to make another one.
How an expert looks at a game
A cooking-show judge doesn’t just say “tasty.” They ask what you were going for, notice the one thing that’s working, and tell you the two things to try next. Good game critique works the same way.
A design critique is a structured look at a game in progress, meant to work out where the designer’s effort should go next. It isn’t a review and it doesn’t hand out stars. It’s a conversation with someone who’s still building.
We’ll borrow from one example the whole way through. A veteran designer once sat down, one after the other, with two new designers to look at what they were making. The first had a game where you explore an abandoned space station in the dark and can flip the direction of gravity: up, down, left, or right. The second had a turn-based game about buying and selling houses in a coastal city while the sea rises and swallows it, street by street.
Before the questions, notice his manners, because they’re worth copying. He let each designer explain their game, then asked to see it, then played it himself. He said what he liked, specifically: the opening screen of one, the look of the other’s world. He asked far more than he told. And he finished with two or three priorities, not twenty notes, offered lightly. One suggestion he ended with “maybe, maybe not, it’s just a thought.”
Questions about the idea
What’s the hook? The first designer introduced her game by its genre, a side-scrolling platformer (a game where you run and jump across a world that scrolls past sideways). The reviewer admitted that the label made him picture a very familiar kind of game, and that the real thing, once he saw it running, looked much cooler than the description. His advice was to open with the hook from Level 19 instead: it’s a game about gravity, and you choose which way is down. The second designer did this without being told. He named the topic and what you do, never mentioned a genre, and the reviewer said he was already playing it in his head.
What’s the core mechanic? Level 9 called the core mechanic the thing the player does most, and the thing that makes this game this game. The reviewer asked the first designer whether flipping gravity really was what set her game apart. She said yes. That answer tells you where most of the remaining effort belongs.
How much of its space have you explored? She’d just finished a vertical slice from Level 16, a small piece of the game built to near-final quality. A slice proves the game can exist. It says much less about how much the core mechanic can do.
That’s where level design comes in: the craft of arranging spaces and challenges so they put the mechanics to work. Think of it as the difference between owning a set of chess pieces and composing a really good chess puzzle. Flipping gravity opens a huge possibility space, and she’d barely stepped into it. His advice was to build lots of rough levels quickly, find the arrangements that make the flip most interesting, and lean into those. A plain, ugly editor that lets you try ten layouts an hour beats a beautiful one that takes a day per room.
Questions about the senses
Where’s the sound? The gravity game was dark, and the player carries a small light. It was also silent, because the sound hadn’t been started. The reviewer stopped right there. When you can barely see, hearing becomes a main sense. A creak in the dark could be a door or a monster, and not knowing is the whole experience. Without sound, he reckoned, she was missing something like a third of the game. Level 14 explained why sound design changes how everything else feels. In a critique, missing sound is one of the easiest things to spot and one of the most often overlooked.
What happens when I fail? While playing, the reviewer flipped gravity the wrong way and squashed his character, then did it again, laughing. That’s Level 5’s interesting failure from the player’s chair. He added that humor is one of the most underused tools a designer has, and that people often chase a complicated fix for a problem a small joke would solve. Hopscotch has been getting this right for centuries: wobbling on one foot and falling over is half the fun.
Questions about the player
What confuses a new player first? Before giving any advice of his own, the reviewer asked whether other people had played it, and what tripped them up. She already knew from her first playtest: the early puzzles were harder than they needed to be. A designer who can answer this question has been testing. One who can’t has just been handed their homework.
How long is it, and how much do you have to build? She was aiming for three hours. The reviewer thought that was long for this kind of puzzle game and asked how many rooms it would take to fill. That’s scope from Level 17, asked in the simplest possible way.
One path or many? Her game unlocked abilities in a strict order, each opening the next area. He asked whether it would always go A, then B, then C, or whether combinations could open shortcuts and other routes. More routes mean more replayability, the quality that makes a game worth playing again. Think of the difference between a jigsaw (lovely, but you only really do it once) and a deck of cards (endless). More routes also cost more to build and test, and he was clear that this is a trade-off to weigh, not a rule. A game someone enjoys once, start to finish, is a perfectly good thing to make.
What did players feel that you didn’t plan? The second designer reported something unexpected from testing. Players treated the houses in the flooding city almost like people, each with its own story, and some felt uneasy about profiting from a disaster. He raised it as a possible problem. The reviewer thought it was one of the most promising things about the game, because discomfort means people are emotionally involved. Level 4 described the emotional palette that games have and films don’t. Guilt is on it.
Questions about time
How do a beginner and an expert share a pace? Pacing is how a game spreads its demands over time: how long a turn lasts, how quickly decisions arrive, how much waiting there is. Anyone who’s played a board game with one very slow thinker knows exactly what bad pacing feels like.
In the flooding-city game, a turn lasted about thirty-five seconds. The designer had already hit one wall: back when players could own as many houses as they liked, he once had forty properties and forty-five seconds to manage them all, so he capped it at five. The reviewer spotted a second wall. A newcomer gets thirty-five seconds and no idea what to do, surrounded by people who know exactly what to do. And the opposite hurts too: finish your move in half a minute and then wait out a five-minute turn, and you’re bored stiff.
So he floated an idea he said he’d never seen before. Give newcomers a turn twice as long, with one of their turns spanning two of an expert’s, so everyone stays in step. The designer ran with it on the spot, suggesting cheaper houses on the slow clock and pricier ones on the fast clock. That’s player-paced difficulty from Level 5, applied to the clock, and it’s half of onboarding.
The clinic questions
Here’s the whole list. Keep it somewhere you’ll find it.
- What’s the hook? Say it without naming a genre.
- What’s the core mechanic, and is it what makes this game different?
- How much of that mechanic’s space has been explored, and how cheaply can more be tried?
- Where’s the sound?
- What happens when I fail? Is it clear? Is it funny?
- What confuses a brand-new player first?
- How long is the whole thing, and how much has to be built to fill it?
- One path through, or many? Would anyone play twice?
- What did players feel that the designer didn’t plan?
- How do a beginner and an expert share the same pace?
When you use the list on someone else’s game, borrow the manners too. Play before you speak. Say one specific thing you liked. Ask questions and let the designer find the answers. Then name the two or three things you’d work on next, and keep the rest to yourself.
When you use it on your own game, answer in writing. The question you can’t answer is the one to work on next.
Go make something
That’s the course. Here’s what you’ve got. You started twenty-two levels ago with ten objects from a drawer, a coin spinning on a café table. Since then your Pocket Game has been constrained, modeled, looped, given a secret, made fair, broken on purpose, dressed up, prototyped, tuned, tested on silent friends, pitched in thirty seconds, and now put through a clinic. It’s small. That’s fine. Small games you actually make teach more than big ones you only imagine.
Wright ended his own lectures by pointing at the biggest possibility space of all: every game you might make next.
“The possibility space for your next game is huge. So find something you’re passionate about and start exploring.”
He meant it practically. Pick a subject you can’t stop poking at: ants, tides, traffic, your grandmother’s card table, how bread rises. Level 15 made research the start of every project, and one of the nicest perks of being a game designer is that it gives you an excuse to get curious about absolutely anything. Look around. The next idea is usually somewhere close by, waiting for somebody to notice it’s a toy.
Try it · Pocket Game, step 22Hand it over
First, hold a clinic. Pick a game you didn’t make: a board game from the shelf, a card game, a playground game, a game on a phone. Play it for ten minutes, then write one line for each of the ten clinic questions. Do the same for your Pocket Game, and circle the two weakest answers. Then give your Pocket Game to someone who has never seen it. Hand over the pieces and the written rules and leave the room. Come back in ten minutes and ask them to tell you what happened, as a story. Finally, take a blank card and write three lines: a subject you can’t stop thinking about, the idea from this course you most want to try again, and the first object you’d pick up to make a toy out of it. Put the card where you’ll see it tomorrow.
Carry forward: Play first, praise something specific, ask good questions, leave with two priorities, and then go make the next one.