Lesson 20 · Part 6: Sharing It
Making It Together
How a group of people ends up making one game: a shared direction, a shared memory, and arguments that make ideas better.
Making It Together
Four friends decide to make a board game over a weekend. One can draw, one is good with numbers, one writes, and one mostly has opinions. By Saturday lunch, the artist has painted a gloomy haunted forest, the writer has a page of puns about cheese, and the numbers person has built a tight little racing game with a lap counter. Every piece is good. None of them belongs to the same game.
Nobody did anything wrong. Each of them made dozens of small decisions on their own, sensibly, and nobody had said which way the whole thing was supposed to lean. Anyone who’s been in a band, a group project, or a kitchen at Thanksgiving has met this problem. Most games are made by groups, and this is the first thing every group runs into.
A direction, not a destination
Level 2 described design as a walk down a design tree: big decisions near the trunk, tiny ones out at the twigs. What color is this card? How loud is the doorbell sound? Is the dice tray round or square? On a team, most of the twigs get decided by people other than you, usually without asking you first. They should. You’d never get anything done otherwise.
What they need is a design vision: a shared sense of where the game is heading, clear enough that other people can make their own decisions in line with it. It can’t be a complete blueprint, because you don’t know exactly where you’ll end up either. Will Wright, who has led design teams of around a hundred people, puts it neatly:
“It’s more understanding the direction you’re going, not the destination.”
The vision spreads the way a family’s habits do. Someone asks you “A or B?” and you say B. It happens again, and again. Eventually they can guess your answer, so they stop asking and only come to you when they’re genuinely unsure. Without meaning to, you’ve been teaching the whole team what the game is. When your own idea shifts (it will), that’s the moment to go round and tell everyone.
It helps a lot to speak in feelings. “Cozy, like a reading nook during a storm.” “Spooky, but the kind of spooky a five-year-old would enjoy.” A sentence like that can be translated by a painter, a musician, and a rules-writer, each into their own craft. Level 14 called the result cohesion, everything feeling like it belongs to one world. A vision people can interpret is how a game gets there.
Three hats
Whoever leads the design wears different hats over the life of a project.
At the start you’re the person with the idea, giving the pitch from Level 19 to the people you hope will join. The whole message is: doesn’t this sound worth making? Come make it with me.
When things are going well, you’re a traffic cop. The ideas coming from the team are mostly good, and your job is mostly about order. This one now, that one later. Do these two fit together? Let’s build a quick prototype and find out.
Very occasionally, you’re the tiebreaker. Two positions lock into a stalemate, the argument has stopped producing anything new, and somebody has to choose. Avoid it when you can. When you can’t, go with your gut and move on.
Underneath all three hats is a quieter job. You’re also designing how the team decides things: who gets consulted, how disagreements get settled, what a fair argument looks like. Call them the rules of the road. A team that knows them wastes far less energy on every single decision, the same way a soccer team that agrees on the offside rule spends less time yelling.
Design is everyone’s job
On a healthy team, a few people may have “designer” in their job title, and everybody contributes to the design. Call this distributed design: spreading design thinking through the whole group so a good idea can come from anywhere.
The practical argument is about who knows what. The person who builds the scoring track or programs the sound knows far better than you what it can be made to do. They’ll spot possibilities you’d never think to ask for. A chef who leaves the menu entirely to the head chef misses the line cook who knows a trick with the leftover bread.
The same thinking applies when you choose your closest collaborators, like whoever is in charge of the art or the sound. You want someone who listens first, then goes somewhere you couldn’t have gone, using what they know, and comes back with two or three strong options for you to pick from. Watch for the opposite: a collaborator with a fixed agenda, who steers every request back toward their own favorite style. And because you’ll spend a lot of hours beside these people, there’s one plain test worth running: do you enjoy being around them? If you do, the work stops feeling like work.
One more thing to watch for. Plenty of people join a team to draw or build or write while privately hoping to design. If you notice that and make their ideas visible, you may end up with another strong designer beside you.
Group memory
“Design document” sounds like something written once, printed, and filed in a drawer. But a game’s design changes every week, sometimes every day. Nobody should have to hunt you down to ask what the plan is this week.
What works better is a living design doc: shared pages that anyone can read and the designers keep current, like a family’s shared shopping list stuck to the fridge. Think of it as the team’s memory. Three of you decide how scoring works and write it down. Anyone who needs to know reads it there. Anyone who spots a problem comes and says so, and the decision gets reopened.
The alternative to writing things down is meeting about them, and meetings get expensive quickly. Every new person adds conversations with everyone already there, so talking grows much faster than the team does. One designer who has led teams of both sizes kept rough count. On teams of ten or twenty, people spent about three hours working for every hour in meetings. On teams of around a hundred, it had flipped the other way round.
Ideas should survive a fight
People take criticism very differently depending on where they learned their craft. Artists who went through art school are used to having their work pinned on a wall and picked apart. Plenty of others find it painful. Either way, an idea that’s been tested against criticism and survived is worth more than one that sailed through because nobody said anything.
Taking criticism well is a skill, and it goes something like this. Be glad they spoke up, even when you disagree. Expect a defensive twinge in yourself and let it pass. Then deliberately imagine a world where they’re right, and walk around in that world for a minute before deciding.
The critic has a job too. Constructive criticism comes with an alternative. “That’s bad” leaves everyone where they were. “I think this would work better than that” puts a second idea on the table, and now the two can compete. Try both. Whichever is left standing has earned its place, and nobody’s idea, including the leader’s, should win just because of who suggested it.
That contest needs an end, though. At some point someone decides, and a good ending leaves the team feeling the choice was fair rather than handed down.
Some teams even grow a signal for when a discussion has stopped being useful. On one of Wright’s teams, the art director would eventually start asking, during long meetings, “Can I leave now?” The team came to call him the canary, after the birds miners carried underground to warn them of bad air. When he walked out, everyone knew the meeting had run out of steam, and they usually ended it. Every group has a canary if you look. Learn who yours is.
Try it · Pocket Game, step 20Living rules
Put your Pocket Game’s rules in a shared document that someone else can open and comment on. At the very top, write one line describing the feeling you’re going for. Send it to someone and ask for exactly one criticism, on one condition: it has to come with an alternative. Whatever they suggest, play one round their way before you decide. Then update the document so it shows the current rules and the date you changed them.
Carry forward: Tell people the direction, write down what you decided, and let any idea, yours included, be beaten by a better one.