Lesson 17 · Part 5: Making It
Iterate, Tune, Cut
How a design gets better through lots of quick loops, a few brave leaps, and the nerve to cut things you love.
Iterate, Tune, Cut
You taste the soup, and it needs something. You add a pinch of salt, stir, and taste again. Better. Then a squeeze of lemon. Worse, so next time you’ll leave that out. Nobody writes a soup down in advance and gets it perfect. You get there by changing one thing, tasting, and deciding.
Games are made the same way, just with a longer spoon. One famous team built fifty or sixty little prototypes on the way to a single game, and most of them were never used. That wasn’t waste. That was the process doing its job. This level is about the loop that produces all those discarded attempts, and about the harder question of what belongs in the finished game at all.
Loop, don’t plan
Iteration means going around a short cycle again and again: change something, try it, judge the result, repeat. Every prototype from Level 16 is one trip around that cycle. So is every draft of an essay, every run-through at band practice, and every Sunday a family spends tweaking the house rules of a board game until they’re just right.
The speed of the loop matters more than how clever any single guess is. A comedian doesn’t write the perfect joke at a desk. They try it at a small club on Tuesday, change two words, try it again on Wednesday, and by Friday it kills. Fifty quick tries beat one slow, careful one, because each try teaches you something you couldn’t have figured out by thinking.
This matters even more in games, because games are full of surprises. Level 12 introduced emergence, where simple rules produce behavior nobody wrote down. The designer of one city-building game describes sketching, by hand, the traffic he expected to see on a pattern of roads, then running the simulation and getting something completely different, with no obvious way to nudge it toward his sketch. His conclusion was that he couldn’t reason his way to the right rules. What he could do was make rules very easy to change, then change them a great many times, very fast.
Do the scary thing first
With limited time, you need a way to choose which loop to run next. A habit many teams use could be called risk triage, borrowing the word hospitals use for deciding who gets seen first. Once a week, list the biggest risks to the project. Some are about building it: can this even be made? Some are about design: will this be any fun? Some are about time: can we draw all those cards before the deadline? Then go after whatever’s at the top of the list, usually with a prototype, until it drops down and something else takes its place.
Why the scariest first? Because risk gets more expensive with age. A problem you could fix this month for ten dollars might cost a hundred in three months, because by then other work has been piled on top of the wobbly part, and all of that has to change too. It’s like a builder noticing a cracked foundation. Fix it before the walls go up and it’s an afternoon’s work. Fix it after the roof’s on and it’s a disaster. The temptation is always to say “Oh, I’m sure it’ll work” and move on to something more pleasant. Checking early costs less, and it lets you trust the ground you’re standing on.
Big moves before small ones
A lot of iteration is tuning: adjusting the numbers in a game, such as how far a piece moves, how much a thing costs, how many cards you draw, or how often an event happens. Tuning sounds delicate, and beginners treat it that way. They nudge a number up by ten percent, try it, and nudge again.
There’s a rule of thumb from the designer Sid Meier, passed along by Will Wright, that points the opposite way. Call it double or halve. When you first tune a number, don’t move it by ten or twenty percent. Double it, or cut it in half. Your first guess is probably miles off, and big jumps get you into the right neighborhood fast. Then you can fine-tune. Archery coaches teach something similar: first get your arrows onto the target at all, and only then start worrying about the bullseye. Wright adds a bonus round. Every so often, double something for no reason at all, just to see. Sometimes the surprise is better than anything you were aiming for.
Bold moves matter even more when a design gets stuck. Sometimes a game reaches a point where it feels pretty good, and every small change makes it worse. In Level 11 this was called a local maximum: the top of a small hill, with taller hills out of sight in the fog. Little steps can’t get you off it, because every direction leads downhill.
The way off is a big change, like ripping out a feature or adding a new one, and it nearly always makes the game worse at first. Only after some iteration in the new spot do you find out whether you’ve landed on the slope of a taller hill. Think of it as dropping scouts by parachute: each drop is expensive, and each one reports back on whether the ground there slopes up. One veteran designer says every hit he ever worked on went through this several times. It’s also stressful, because a team has spent months climbing the hill you’re proposing to leave. Writers know the feeling well. Sometimes the only way to fix a story is to throw out the draft you’ve polished for weeks and start again from a different first page.
Deciding what the game is not
Every design has to be finished at some point, which means deciding its scope: how much game you’re going to make. Scope is a hunt for a sweet spot. Reach too far and you never finish. Aim too low and there’s nothing worth finishing. What makes the hunt tricky is that effort and payoff don’t line up. Something you threw in during an afternoon may turn out to be the thing everyone loves, and something elaborate that took months may land with a thud.
Players sense scope quickly. Put a cat in a new room and the first thing it does is walk the edges, sniffing every corner, to learn how big its world is. A player does the same thing within a few minutes of starting a game: they figure out how much freedom they’ve got, then judge everything else against that.
For choosing among features, a simple method works well. Call it feature triage. List everything you’d love the game to have, and grade each item A, B, or C for how much it would add. Then have whoever’s building it score each item from one to ten for how hard it’ll be. Put the two columns side by side and sort. An A that costs two is an easy yes. An A that costs ten needs a good argument. This is the trade off from Level 2 with numbers attached, and it tells you what to build first too, since the cheap, valuable features get you something playable soonest. Sometimes one feature is so central that it’s worth almost any cost, because without it there’s no game. That’s allowed. Just make sure you’re saying so on purpose.
Two warnings go with this. First, never judge a feature on its own. The best additions are force multipliers that make everything already in the game richer. A new card that combines with five old ones is worth far more than a new card that just sits there. Second, watch out for over engineering: building something far more elaborate than the game needs, “just in case.” It’s like pouring skyscraper foundations for a garden shed. It’s tempting, it feels responsible, and it eats time you could’ve spent on the game you’re actually making.
Letting go
The hardest part of scope isn’t the math. It’s your feelings. While building Spore, a big game about evolution, Wright’s team made a gorgeous model of how galaxies form stars, with gas cooling into clouds and waves of new stars sweeping around a spiral. Wright loved it. It just had no place in the game players would actually be playing.
“That’s a cool game, but it’s not Spore.”
Writers have an old name for this, kill your darlings: cut the part you’re fondest of when it doesn’t serve the whole. It’s the pruning of the design tree from Level 2 again, applied to a branch you happen to adore. A good question to ask yourself is whether you’re designing to please your own taste or to reach the people who’ll play it.
Here’s the cheerful part: a cut darling often gets a second life. Wright’s first game had players flying a helicopter over islands. To make those islands, he built himself a little tool for laying out the map. He found he was having more fun building the world than flying over it, and that throwaway tool grew into SimCity, a game where building the city is the game. Keep a “next game” envelope. Your darlings can wait in there.
Try it · Pocket Game, step 17Tune and trim
Three small jobs. First, write down the three things most likely to make your Pocket Game not fun, scariest at the top, and decide how you could test that one this week. Second, pick one number in your rules (pieces per player, moves per turn, points to win). Double it and play a round. Then halve the original and play another. Keep whichever direction was better. Third, cut one rule or piece entirely and play without it. If you don’t miss it, leave it out. If you do, write it on a slip of paper and start your “next game” envelope.
Carry forward: Change it boldly, test it quickly, and cut what the game doesn’t need.