In March 2011, Satoru Iwata stood in front of a room of investors and explained why Nintendo's earnings had fallen. The 3DS had launched poorly. The Wii had stopped selling. The press had called him a failure. Someone in the room asked whether he would step down as president. Iwata said no. Then he said something else — something that, at the time, seemed unremarkable but would later define him: he announced that he would cut his own salary in half for six months. Not to appease investors. Not for show. Because the failure had happened on his watch, and he believed that accountability begins at the top.
This was not strategy. It was character. And character, for Iwata, had been shaped by something simple: he had always been a programmer, and programmers fix things by understanding them directly.
He was born in Sapporo on December 6, 1959. As a teenager, he programmed games on a desktop calculator and showed them to classmates. He enrolled in the Tokyo Institute of Technology to study computer science, and while still a student in 1980, he began working part-time at a small game developer in Tokyo called HAL Laboratory. When he graduated, he joined HAL full-time, not because he wanted to build a company but because he wanted to keep writing code. For over a decade, that is what he did.
Then HAL collapsed. By 1992, the company had accumulated debts totaling approximately fifty billion yen. Under the recovery plan, the obligations were restructured to approximately fifteen billion yen, and over roughly the next six years the company repaid what it owed. Nintendo, a longstanding partner, agreed to support the recovery — but on a condition. Iwata, who had been a programmer and then a manager, would need to become president and take personal liability. He was thirty-two years old. According to accounts from that period, his response was something close to: if I run away from this, I will regret it for the rest of my life.
He could have said no. He could have walked away. He did not. For six years, he rebuilt the company one decision at a time. During this period, he was also working directly on games. His most discussed contribution came not from within HAL but as a favor to an outsider. The writer Shigesato Itoi had been working for years on a game called MOTHER 2. Development had stalled. When Iwata was brought in to assess the situation, he examined the existing codebase and told Itoi plainly: if we continue with what exists now, it will take two years to finish. If we start from scratch, we can do it in six months. They started from scratch. According to Itoi, the game was finished in roughly that time. Itoi later said that Iwata had given each programmer something like a mechanical shovel where before they had all been digging with their hands.
In 2000, Iwata joined Nintendo as head of corporate planning. Two years later, when Hiroshi Yamauchi stepped down after more than fifty years as president, Iwata became Nintendo's fourth president — the first in the company's history who was not related to the founding Yamauchi family, and the first whose career had been built entirely in software. He ran the company through the Wii era, when Nintendo reached audiences who had never touched a game controller. He gave talks at industry conferences in which he dissected his own mistakes in public with an engineer's dispassion. He launched a video series called 'Iwata Asks' in which he interviewed the developers of Nintendo games — not from above, as a president interviewing employees, but as someone who understood what they had done and wanted to know how.
At the Game Developers Conference in 2005, he opened his presentation by holding up his business card and reading it aloud: 'On my business card, I am a corporate president. In my mind, I am a game developer. In my heart, I am a gamer.' The line became famous. But the truth behind it was quieter. Iwata did not simply love games. He had spent his entire adult life making them, fixing them, understanding them from the inside. When he spoke to developers, he spoke as someone who knew what a compiler does, who knew what it means to lose six months of work to a single architectural decision. He did not need to be told what was hard. He had already done it.
In June 2014, he disclosed that he had undergone surgery to remove a bile duct tumor. He returned to work and continued making public appearances. On July 11, 2015, he died. He was fifty-five years old. The condolences that arrived over the following days came from competitors, from developers who had worked with him, and from players who had never known his name until then and who only now were finding out what he had built.
Among the things he had said, the one that traveled farthest in those days was the simplest: that the purpose of a game is to make someone smile. But perhaps the deeper truth was this — he believed that the person who makes the game should understand it all the way down. Not as a metaphor. As code. As structure. As decisions made one line at a time. And if you understand it that way, you carry something with you that cannot be faked: the humility of someone who knows exactly how hard the work is, because you have done it with your own hands. When the company he led stumbled, he did not ask others to pay the cost alone. He stood in front of the room and said: this happened on my watch. I will bear it first.
— The road you are on now, where no one is standing over your shoulder telling you what to do — is that unkindness, or did someone decide to trust you?