The Morning Miyamoto Said 'No'

The rain was coming down in sheets. Through the floor-to-ceiling glass of the conference room you could see the Kamo River swelling brown, the willows along its banks whipping in a wind that smelled of wet stone and diesel. The room itself was the kind of understated, expensive quiet that Kyoto specializes in: a single long table of pale birch, six chairs, a whiteboard that had been wiped clean so many times its surface had the polish of old ice. At the head of the table sat a man in a charcoal sweater, reading glasses pushed up onto his forehead, an untouched cup of green tea at his right hand. He was not looking at the slides.

It was a Tuesday in the spring of 2014. The man at the table was Shigeru Miyamoto, then in his early sixties, with thirty-three years at Nintendo behind him and a quiet reputation as the most stubborn product thinker in the global games industry. Across from him stood a young engineer, perhaps thirty, who had flown in from the hardware division that morning. Behind the engineer, on the wall-mounted display, a series of slides marched through specifications with the confident, technical swagger of the era: teraflops, ray-tracing, 4K output, memory bandwidth, AAA parity with the PlayStation 4. The deck was beautiful. The deck had been workshopped for weeks. The deck, the engineer believed, was the future.

He was pitching a 4K-capable successor to the Wii U. He clicked to a chart that placed Nintendo's theoretical machine ahead of every competitor on the market. He clicked to a render of the device in cross-section, annotated with arrows that said *here*, *here*, *here*, in the breathless typography of engineering triumph. He talked about frametimes. He talked about unified shading architectures. He talked, with genuine passion, about the demos he had running on a prototype in the lab downstairs: a *Zelda* scene lit with physically accurate global illumination, a *Mario Kart* track reflected in chrome bumpers that actually reflected the world back.

Miyamoto listened. He asked three questions, each one short. *Who is this for? What does the player do that they could not do before? And after the second hour of playing, will they still be smiling?* The engineer answered the first two competently. On the third, he hesitated, then offered an answer that was essentially a restatement of the slide: *the framerate is so high, the lighting so real, that immersion itself becomes the smile*. Miyamoto did not argue. He thanked him, stood, picked up his tea, and said a sentence that would, by the end of the week, end the project.

*"Will it make the player smile?"*

The engineer, suddenly aware that this had been the actual test the entire time, tried again. He talked about delight, about presence, about how the technology itself could be a kind of magic. Miyamoto waited him out the way a carpenter waits out a nail that has not yet found its wood. Then he said, very gently, *I am not sure. So we wait.* The slides went dark. The meeting ended. The prototype in the lab was, within the quarter, dismantled for parts. The engineer went back to his bench, certain that the company had just cost itself the next console generation.

He was wrong. Three years later, on a soundstage in Tokyo, Nintendo would unveil a small, slate-gray device with detachable controllers that looked nothing like the machine in those slides. It would go on to sell more than 140 million units. It would be called the Switch, and it would be the most successful home console Nintendo had ever shipped — not because it had the most teraflops, but because, in the words of one internal memo that later leaked, *"the player smiles within ninety seconds of turning it on, and we have measured this."*

That sentence is the subject of this book.

The Smile Test

What Miyamoto asked in that rainy room is the modern, verbal form of a question that has been asked at Nintendo, in one phrasing or another, since the company was a single craftsman's workshop in the Higashiyama district of Kyoto. It is not a slogan. It is not a line in a brand book. It is what you might call an *operating constraint* — a single sentence that has to be answered in the affirmative before any other question about a product is allowed to matter. Specifications, schedules, manufacturing tolerances, even compatibility with prior hardware: all of these are downstream concerns. Upstream, at the source of every decision, sits a much smaller, much harder question: *will a real human being, holding this thing in their hands, in the conditions in which it will actually be used, find this fun?*

This is the *smile test*, and it is the practical backbone of this book. We will revisit it in nearly every chapter, in different costumes, under different pressures. But it is worth pausing here, in the very first chapter, to give it a shape that any product team — at a startup, at a multinational, in a school, in a garage — can actually use.

The test has four parts. They are deceptively simple, and they are easy to perform badly. Done honestly, they take about fifteen minutes and they tend to kill more projects than they approve.

Part one: Who smiles. This is a question of audience, but a more particular one than the usual marketing persona. *Who, specifically,* is the person whose smile you are trying to earn? Not a demographic. Not a TAM. A real human, ideally named, with a real morning and a real commute and a real reason to be tired by the time they pick up whatever you are making. The Wii U project failed this part of the test because the engineer in that meeting could not name the person. He could describe the screen they would look at, the console they would put under their television, the demo disc they might play. But he could not, when pressed, picture their face.

Part two: When. This is the hardest part. The moment of the smile has to occur at a specific point in the user's experience with the product. *When* is not *always*. *Always* is the language of engagement metrics, and engagement metrics are how a smile test gets quietly abandoned in favor of a session-length test. A real smile is an event. It has a before and an after. The Wii, famously, placed its smile in the first ninety seconds — the moment a player realized that swinging the remote actually swung something on screen. The Switch placed it in the moment a player undocked the device and walked away from the television with it. The DS placed it in the moment the second screen revealed something the first screen had hidden. In each case, the smile was engineered to arrive early, before the player had to earn it.

Part three: Why. Not *why will they smile in general* but *why this smile, and not another.* What is the precise mechanism of delight? If the answer is *because the graphics are realistic*, the smile is borrowed from another product, and it will not last. If the answer is *because the player discovered something the system did not tell them about*, the smile is structural, and it can be replicated across the product. Miyamoto's discipline is to insist on the second kind of answer, even when — especially when — the first kind would be commercially easier to defend in a slide deck.

Part four: At what cost. This is the part most teams forget, and it is the part that separates Nintendo from almost every other company in entertainment technology. The smile test is not allowed to be free. Every smile has to be paid for, and the payment has to come from somewhere in the rest of the experience. The Wii traded raw resolution for physical play. The DS traded a slimmer form factor for a second screen. The Switch traded raw teraflops for portability and a haptic joystick. The cost is not a footnote. It is the central architectural decision. A product team that cannot articulate what their smile is going to *cost* them has not really passed the test. They have just described a wish.

Run these four parts in a room before you greenlight a