Nintendo on taking risks, approach to development, hiring process, union between hardware and software teams, surprising players
Today, a new interview with Nintendo’s Shinya Takahashi was published on The Guardian. As one of the leaders at the company, he spoke about taking risks, Nintendo’s approach to development and its hiring process, the union between hardware and software teams, and trying to surprise players.
We’ve rounded up the interesting comments from the piece below. You can find The Guardian’s original article here.
On taking risks…
“People always ask us whether we take risks on purpose. But to us, we don’t really take risks – we just keep trying new things. The thinking that guides us is: what can we do to pleasantly surprise players? It’s not that we’re consciously trying to innovate; we’re trying to find ways to make people happy. The result is that we come up with things other people have not done.”
On how Nintendo approaches development…
“In many cases, we begin by assigning a small group to a project; not necessarily senior staff, but developers, to try and come up with ideas. Those lead to the end product. Super Mario Odyssey is a good example to explain this: we actually had several small groups and as a result we had many different ideas, which we then put together to make a single product. Naturally during the course of early development, we find the right mission for each project. I believe every game has a different mission. With [Nintendo Switch launch game] 1-2 Switch, for example, the mission was to make a party game where players would not have to look at the screen – where people would face each other.”
On Nintendo’s hiring process…
“The Japanese hiring system is different from western companies. Typically in Japan, we hire people straight out of college. We have many candidates applying to Nintendo, and in many cases, the ones we hire are the ones who really understand what they have accomplished through their college years. If we see an artist who was very focused and determined about creating a single large-scale project, and they accomplished this over many years, or if we see a person who worked on a single movie from the beginning to the end of their course – that type of person needs a lot of determination and knowledge to accomplish such a thing. That’s what we’re looking for.
“The bottom line is, the quality of the end product that those students created doesn’t really matter to me. How they kept their focus, what they thought throughout those years … that’s what important to me. We like our staff members to be as creative as possible – and creative people should not just listen to their bosses saying ‘Yes sir’, or ‘Yes ma’am’. I want them to always ask themselves, ‘Is this direction correct?’”
On the union of software and hardware teams…
“We have the software team and the hardware team working very closely together. From the hardware perspective, they will sometimes come to the software group and say, ‘We have this particular chipset that we’re thinking about using in our next system, can you take advantage of this?’ But sometimes, the software team goes to hardware team and says, ‘We’re working with this theme, can you look into the technical possibilities, and see if you can come up with hardware features to accommodate it?’
“This is the advantage we have at Nintendo as a software/hardware integrated organisation – when we do research for our new hardware systems, our software developers, our artists, our programmers and our hardware engineers all get together and decide what we should aim for. We’ve been doing that for many years.”
On wanting to make “new and surprising things”…
“We want to make new and surprising things, so we always keep an eye on new technology. That said, in order for us to create surprising things, we also look at older technologies to see if we can leverage them in new ways. New technologies tend to be a bit too advanced – we try to find ways to make technology more approachable.”
