Eiji Aonuma Says Long-Term Nintendo Teams Help Zelda Preserve Its Identity

For a series that has reinvented itself repeatedly across four decades, The Legend of Zelda has maintained an unusually recognizable creative identity. Its settings, mechanics and structures may shift dramatically from one release to the next, but there is still a thread connecting the earliest adventures to modern entries. Zelda producer Eiji Aonuma believes one important reason for that consistency is Nintendo's ability to retain experienced developers for the long term.

Aonuma, a Nintendo veteran of 38 years who most recently worked on the Ocarina of Time remake, discussed the value of keeping employees through multiple projects in a recent interview. His comments arrive during a period when layoffs have become a major concern across the games business, particularly among Western publishers and studios. Microsoft's plans to cut 3,200 employees at Xbox are among the prominent examples from this year.

Rather than treating staffing as something that must be rebuilt from project to project, Aonuma described the advantages of having people who have accumulated shared experience together. In his view, a stable core of developers makes later decisions easier because the team has a common understanding of the work that came before.

"I think you see a real benefit to having some very long-term-tenured staff members around who have shared the same experiences over time because every time you get to the next step, it's easier to discuss how to proceed, or if you're going to do something new," Aonuma said.

For useful background on this topic, read Sonic Pico Park Makes Co-Op Puzzle Solving a Chaotic Test of Friendship.

Shared history can support ambitious changes

That perspective is especially relevant to Zelda, a franchise that has often balanced tradition against experimentation. A new game can introduce a drastically different visual style, a major structural departure or unfamiliar systems, yet still needs to feel connected to the series players know. The team does not have to begin every discussion by defining the franchise's foundations when veterans are present who remember why earlier choices were made.

Aonuma's point is not simply that experienced staff can repeat established processes faster. He emphasized the value of shared context when teams are considering a new direction. A developer who has lived through previous successes, compromises and design challenges can offer more than institutional memory. They can help colleagues understand whether a familiar idea should be retained, revised or left behind entirely.

That can be vital for a long-running Nintendo property. The best-known Zelda games do not all follow one formula. Ocarina of Time established a hugely influential approach to 3D action-adventure design, while later titles explored the seas, motion controls, stylized worlds, open-air exploration and new methods of player freedom. Continuity, in this sense, does not necessarily mean refusing to change. It means carrying knowledge forward while being confident enough to reshape it.

Aonuma said Zelda's teams do change over time, but the presence of a continuing core between projects gives the group a base to develop from. This also creates an environment where newer employees can be introduced to the work without losing the momentum built by the previous team.

"You do see the Zelda team change over time, but there is a continuity of core staff, certainly at least from one project to the next, so that we have that base that we can build from and bring up new staff within it," Aonuma said.

New hires need explanation, not just instructions

While Aonuma praised the benefits of a long-serving staff, he did not argue that experience alone is enough. Bringing in new developers is still essential, particularly for a franchise that needs fresh ideas and perspectives. But he suggested that onboarding requires meaningful investment from the studio.

New team members need time to learn the reasons behind a project's methods, terminology and standards. They need to understand not only what to do, but why a process exists and how it connects to the history of the team and the series. Without that understanding, a developer may be able to follow a routine without having the knowledge needed to improve it or challenge it productively.

Aonuma described this as a matter of balance. Experienced developers must share their knowledge, but a studio should not expect newcomers to merely imitate the way things have always been done. The goal is to help them participate fully in the team's creative decision-making.

"When you have new staff coming in, of course you want to make sure that you're bringing everyone up with a lot of discussion, explaining how to do things, why you're doing things certain ways, as well as the language that you're using, but that takes some more time as well," Aonuma explained.

For players, this sort of process may sound far removed from a dungeon layout, sidequest or control option. Yet those details are shaped by the discussions happening inside a development team. If a studio has the time and stability to explain its design philosophy, new employees can understand the intent behind established ideas while also identifying opportunities to update them.

That is different from a team working under constant disruption, where departures can take knowledge with them and incoming developers may be asked to adapt immediately. Aonuma's comments frame employee retention as a creative issue as well as a workplace issue. Long-term continuity can preserve production knowledge, communication habits and familiarity with a series' particular design language.

The Ocarina of Time remake reflects that generational mix

Aonuma recently discussed how the Ocarina of Time remake was shaped by both established experience and younger developers. Not every member of the remake team had played the Nintendo 64 original, a fact he said was part of why the project became what it is. That viewpoint is notable for a remake of one of Nintendo's most celebrated games: reverence for the original is important, but a project cannot only look backward.

The result of that balance can be seen in the remake's additions and adjustments. Alongside the classic adventure's familiar foundation, the game includes new sidequests and altered dungeon elements. It also incorporates a UI-toggle option associated with Breath of the Wild, as well as a jump button. Those changes illustrate how a newer generation of developers can bring modern expectations and different play habits to a landmark older game, while colleagues with a deeper history in Zelda help maintain the qualities that made the original endure.

For Nintendo, Aonuma suggested, this blend of voices is not an accidental outcome. It is part of a longstanding approach that reaches back to the era when Shigeru Miyamoto was first working on projects at the company. The aim is not to freeze a team in place forever. It is to maintain enough continuity that knowledge can be passed forward, while allowing new staff to become genuine contributors rather than outsiders following a template.

A creative argument for stability

The wider games industry has spent years discussing consolidation, studio closures and recurring layoffs. Those conversations often focus on the immediate human cost, which remains the most important issue. Aonuma's remarks add another dimension: instability can also affect the creative continuity of games themselves.

When experienced employees leave, a studio may lose familiarity with its internal tools, production lessons, failed experiments and hard-won solutions. Those things are not always written down in a document that can be handed to the next team. They often live in the collective memory of people who worked through a project together. Preserving that knowledge can make future development discussions more informed and potentially more efficient.

At the same time, Zelda's history shows why a stable staff should not be confused with a creatively static staff. The series has survived because it has not simply repeated one successful game. Its teams have repeatedly found ways to reinterpret exploration, puzzles, combat and discovery for new hardware and new audiences. Aonuma's comments suggest that this evolution works best when it is supported by people who understand the franchise's past, alongside colleagues who are willing to see it differently.

That combination may be one reason Zelda can make major changes without entirely losing its sense of self. Veterans provide a frame of reference, newcomers introduce questions that may not have been asked before, and the team uses discussion to decide what should remain and what deserves to be reimagined.

For Aonuma, the payoff is clear. Maintaining a core group from one project to the next gives Nintendo a platform for training new staff and pursuing the next idea with greater shared understanding. In a business frequently marked by disruption, his view presents long-term investment in people as more than a matter of continuity on an organizational chart. It can be part of how a beloved game series continues to grow.