A Machine Can Build You a Thousand Rooms. It Can't Tell You Which Ones to Cut.

Shigeru Miyamoto has spent about four decades measuring things. His own garden, which turned into Pikmin. His own bathroom scale, which turned into Wii Fit. The woods and caves around Sonobe, outside Kyoto, where he grew up — those turned into the first Zelda. A dog. A remote control sitting on a coffee table.

That habit didn't come from nowhere. He studied industrial design before he ever touched a game. Industrial design is the discipline of taking a physical object and asking where a person's hand is going to land on it.

I bring this up because he said something recently about generative AI that's getting passed around as a kind old man's reassurance: even if gen-AI "were to eventually handle everything, there will always be a role left" for human designers. People are reading that as "don't worry, a machine can't make Mario." That's not what he said, and it's not the interesting part.

Here's what I hear in it. A generative tool is a machine for producing options. Design is a machine for producing refusals. Those are different jobs, and only one of them scales.

Anyone who has made anything knows this feeling. You don't get stuck because you can't think of anything. You get stuck because you thought of forty things and thirty-nine of them are fine. Fine is the enemy. Fine is what fills the map with the same enemy camp four hundred times. Fine is what a system will hand you forever — cheaply, politely, and without the faintest interest in whether you're still awake.

I've played a lot of games that were assembled rather than designed. You know the feeling. You walk into the room and you can see the seam where a rule got applied. Every chest has three items. Every vendor has the same six lines. Every dungeon is built from a palette of rooms that snap together like a rail kit. None of it is broken. All of it is fine. You put it down after eight hours and never think about it again.

Then I think about the Deku Tree in Ocarina of Time, which is a tutorial that spends half its runtime teaching you to be curious and then quietly checks whether you were paying attention. Or the simple cruelty of a block you can see and cannot reach yet. The designer's decision there isn't "what should be in this room." It's "what should not be in this room, so the player leans forward." You can't prompt your way to withholding. Withholding is a stance.

That's the role Miyamoto is describing. Not the ability to make the thing. The authority to say no to the thing.

There's a larger point about how games teach, and it's the one that makes me certain he's right. Machines are extremely good at learning systems. They will get better at absorbing the rules — the type chart, the damage formula, the pacing curve, the way a level teaches you a mechanic and then charges you interest on it three hours later. They can learn the rules. Somebody still has to decide which rules are worth teaching, and to whom, and why.

I learned type matchups in Pokémon before I was ten. When I met resistance and weakness systems again in Dragon Age in my teens, it clicked in about a minute — because a person had made the first one legible, and a person had made the second one teachable. Neither chart needed to be clever. Both needed to be decided.

So no, I don't read this as a "don't worry" quote. I read it as a job listing, and a demanding one. The role that's left sits at the top of the stack: the person who looks at a thousand generated rooms and knows — instantly, in the gut, from having died in bad rooms and good ones — which of them belongs and which of them lands on the cutting room floor.

That's not a consolation prize. That's the whole job. It was always the whole job. We just used to hide it behind the fact that building the thousand rooms was expensive.

Miyamoto has been doing it since before the rooms were cheap.