Yes—according to Shigeru Miyamoto’s recollection as reported by GamesRadar+. Development on Super Mario Bros. began shortly before work on The Legend of Zelda started in 1984, so the projects advanced together. The difficult part was not simply having two games in production: Nintendo had to finish Mario and then move Mario’s programmers into Zelda’s final push while Zelda was still an unusually open-ended design problem.
What happened when Mario and Zelda overlapped?
GamesRadar+ reported on May 4, 2026, that Shigeru Miyamoto described the two projects as progressing simultaneously. His recollection places the start of The Legend of Zelda in 1984 and says work on Super Mario Bros. had begun shortly beforehand. That sequence matters because it turns the familiar pair of early Nintendo classics into a production story: one project was already underway when the other began, rather than the second game waiting for the first to be completely finished.
| # | Preview | Product | Price | |
|---|---|---|---|---|
| 1 |
|
Minecraft - Nintendo Switch | $29.82 | Buy on Amazon |
| 2 |
|
Super Smash Bros. Ultimate - US Version | $52.99 | Buy on Amazon |
| 3 |
|
Mario Kart™ World (Nintendo Switch 2) | $79.00 | Buy on Amazon |
| 4 |
|
Super Mario Galaxy™ + Super Mario Galaxy™ 2 | $64.99 | Buy on Amazon |
As an Amazon Associate I earn from qualifying purchases.
“We had started development on Super Mario Bros shortly before [starting on LoZ in 1984], so we were extremely busy with planning, with the two projects progressing simultaneously,” Miyamoto said, in the wording quoted by GamesRadar+ from a Q&A. The statement establishes concurrent planning pressure, but it does not provide a week-by-week schedule, staffing chart or account of every Nintendo project active at the time.
The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Mario started first, but not by much
The chronology in the report is deliberately narrow. Miyamoto remembered Mario development beginning shortly before Zelda development. It is therefore safest to describe the games as closely overlapping projects, not to assign an exact number of months between their starts. The available report does not independently verify a complete production timeline, and it does not give a precise date for Mario’s beginning beyond the relative order in Miyamoto’s recollection.
#1 Best Overall
- Minecraft is a game about placing blocks and going on adventures
- Explore randomly generated worlds and build amazing things from the simplest of homes to the grandest of castles
- Play in creative mode with unlimited resources or mine deep into the world in survival mode, crafting weapons and armor to fend off the dangerous mobs
- Play on the go in handheld or tabletop modes
- Includes Super Mario Mash-Up, Natural Texture Pack, Biome Settlers Skin Pack, Battle & Beasts Skin Pack, Campfire Tales Skin Pack; Compatible with Nintendo Switch only
The overlap created a staffing problem
The most concrete operational difficulty came near the end. “It was very difficult to finish Mario and then get the Mario programmers involved in the final push to finish The Legend of Zelda,” Miyamoto said, as quoted by GamesRadar+. In practical terms, Nintendo had to protect Mario’s finishing work while preparing the people who knew that game’s technology and systems to contribute to Zelda’s closing phase. The report characterizes both games as directed by Miyamoto and made by many of the same developers, which helps explain why a handoff was consequential.
This was not a clean relay in which one team crossed a finish line and immediately became available. Mario still needed to be completed, while Zelda needed additional work at the moment when design decisions, implementation and testing could collide. Miyamoto’s wording identifies the transition itself as difficult; it does not claim that every programmer moved at once or that all staff worked on both games for the entire production.
Why call the period a “madhouse”?
“Early Nintendo was a madhouse” is a vivid editorial framing of the workload described in the report. The evidence supports two projects being planned and developed at the same time, plus a difficult effort to bring Mario programmers into Zelda’s final push. It does not document every part of Nintendo’s workplace, establish a measured level of overtime, or justify claims about a particular number of employees, hours or budget.
That distinction keeps the anecdote useful. The chaos was a coordination problem: different kinds of work had to be sequenced around shared people, and Zelda’s needs became more urgent as it approached completion. Calling the whole company a madhouse would go beyond what the quoted recollection establishes. The narrower conclusion is stronger because it is tied to a specific overlap and a specific handoff.
What Miyamoto wanted the first Zelda to feel like
The staffing story makes more sense when paired with Miyamoto’s description of Zelda’s design goal. He did not present the game as merely another linear action title. “I wanted to create a game where the player understands the history and nature of the land, and it feels like they’re exploring,” he said, according to the GamesRadar+ report.
A land to understand, not just a route to follow
That sentence describes exploration as a form of learning. The player is meant to build an understanding of the setting through movement and discovery, rather than receive all of the game’s meaning in a fixed sequence. “History and nature” can be read as the identity of the world—what its spaces imply, how they connect and what the player learns by moving through them—but the report does not supply a formal design document defining those terms.
Rank #2
- New stages and fighters are joined by the combined rosters of every past Super Smash Bros. Game
- Challenge others anytime, anywhere, whether you're on the couch or on the go
- Play any way you want—locally, online, in TV mode, Tabletop mode, Handheld mode, or even with GameCube Controllers
- Fight faster and smarter with new and returning techniques, like the perfect shield and directional air dodge
- Face off in 2-4 player battles, or play against the computer
The important production consequence is that an exploratory game asks its creators to account for many possible player choices. A linear path can assume that most players encounter the same obstacle in the same order. Zelda’s intended appeal required the team to think about what happens when a player wanders, experiments, misses a clue or reaches a dangerous place early. That is an interpretation of the design ambition Miyamoto described, not a claim that the source lists a particular workflow or testing method.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Scan for outdated or missing drivers - takes under a minute3Clear out junk files and repair common Windows errorsInteraction through the controller
Miyamoto contrasted Zelda with a traditional role-playing structure: “In traditional RPGs, the game progresses solely through dialogue, but we wanted the player to interact with the game world using the controller, and conquer dungeons using a simple mapping system.” GamesRadar+ presents this as part of the same Q&A.
The contrast is about where progress comes from. Dialogue can tell a player what the world means; controller-based interaction asks the player to discover meaning by acting in it. The mention of a simple mapping system also points to dungeons as spaces the player gradually comprehends. The map is not just a record of rooms. In the design Miyamoto describes, it supports the player’s own process of orienting themselves and deciding where to go next.
Why was the beginning of Zelda especially risky?
Open-ended design creates a problem before the player has learned the game’s rules. Miyamoto said the team worried that “people wouldn’t know what to do, even at the beginning of the game, and the game wouldn’t be well received,” as quoted by GamesRadar+.
The first-screen concern
The report gives a specific illustration: a player could take a wrong turn on the first screen and be left without a sword. Treat that as the report’s explanation of the concern, not as a newly verified gameplay test. Its value is conceptual. If the game expects players to explore and infer its systems, the opening must still provide enough direction for experimentation to feel possible rather than arbitrary.
Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchPC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11A player who lacks the sword may not know whether they have made an intentional discovery, missed an essential step or simply chosen an unproductive route. That uncertainty is exactly the tension in Zelda’s ambition: freedom is exciting only when the player can form a working theory about the world. The team therefore had to make a world that invited curiosity without making the first decision incomprehensible.
Rank #3
- Race from one course to another through interconnected paths that span the world
- Traverse mountains, forests, cities, and more—with shifting weather patterns and a day/night cycle
- Ride on rails, jump off walls, skim across water, and more as you race for the finish line
- Take on the adrenaline-packed Knockout Tour—a fierce 24-driver elimination mode
- Explore courses at your own pace and wander the world to discover fun surprises in Free Roam
Freedom and legibility are linked
Miyamoto’s comments connect the opening problem to the larger goal. The game was supposed to let players understand a land by exploring it, but the team also feared that players might not know how to begin. Exploration is not the absence of guidance; it is guidance delivered through spaces, objects, controls and consequences instead of a purely spoken instruction.
This helps explain why Zelda’s development could require a different kind of final push from Mario’s. The issue was not only whether individual features worked. The team also had to consider whether the world communicated enough for players to make sense of their choices. The source does not name particular revisions or identify which developer solved the opening problem, so those details should not be invented.
Mario and Zelda represented different design pressures
The story does not present two products for a conventional feature comparison. Its useful comparison is between the design approaches described in the report.
Recommended Free Tools
| Design question | Super Mario Bros. | Original The Legend of Zelda |
|---|---|---|
| How the report characterizes the player experience | A comparatively direct game to grasp | A more open-ended world built around exploration |
| How progress is framed | Direct understanding is the relevant contrast in the report | Understanding develops through interacting with the world and mapping dungeons |
| Primary player challenge described | Not detailed in the available report | Knowing what to do while preserving a sense of discovery |
| Production relationship | Its programmers were needed for Zelda’s final push after Mario’s work | Advanced at the same time and depended on the difficult handoff |
The table should not be read as a complete technical comparison. The report does not provide Mario’s team structure, Zelda’s team structure, development budgets or a list of features for either game. It supplies a design contrast: Mario was comparatively direct, while Zelda pursued exploration, interaction and dungeon mapping.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.What the programmer handoff tells us about production
Finishing one game can affect another
Miyamoto’s account shows how a shared team turns release preparation into a scheduling issue for the next project. Mario’s programmers could not simply be reassigned while Mario still needed to be finished. Zelda, meanwhile, was not waiting in a purely conceptual state; it was approaching its own final push. The overlap meant that staffing decisions had to be made across projects with different design demands.
Shared developers carry knowledge as well as labor
The report says many of the same developers worked on both games. That matters because programmers bring knowledge of the project’s existing systems, tools and assumptions. Moving them to Zelda was therefore more than adding extra hands. It meant transferring people whose experience could be valuable at the exact stage when Zelda’s open-ended interactions and dungeon structure needed to be made coherent.
Rank #4
- Journey through space in two Super Mario adventures, now improved for the Nintendo Switch system!
- Travel the stars with enhanced resolution, improved UI, and additional content
- Learn more about the Lumas from additional Storybook chapters, groove to a bit of additional music
- Get additional Health and fall recovery in Assist Mode
- Join Rosalina and the Lumas to restore the Comet Observatory and rescue Princess Peach in Super Mario Galaxy.
Nothing in the available account quantifies that transfer. There is no supported figure for team size, hours worked or productivity. The defensible point is qualitative: the same-developer overlap made the final handoff difficult, and Miyamoto remembered it as a significant part of the period’s pressure.
Where this account comes from—and what remains uncertain
GamesRadar+ published its report on May 4, 2026. It says the remarks came from a Q&A included with the 1994 audio CD The Legend of Zelda: Sound and Drama and later resurfaced in Retro Gamer’s 40 years of The Legend of Zelda issue. The material available here is GamesRadar+’s report of those remarks, not the underlying Q&A transcript, audio or magazine pages independently checked against the quotations.
That source trail affects how confidently the chronology should be stated. Miyamoto’s recollection is evidence for the projects’ close overlap and for the staffing difficulty, but it is not a complete archival production schedule. The exact wording in the original Q&A, full bibliographic details for the magazine issue and any additional context around the answers are not established by the report.
It also explains why broad claims should be avoided. The account does not document Nintendo’s entire workplace, provide a numerical study of development effort or specify how many people moved from Mario to Zelda. What it does provide is a focused first-person recollection: Mario began shortly before Zelda, both projects progressed simultaneously, and bringing Mario programmers into Zelda’s final push was difficult.
The lasting lesson in the anecdote
The “madhouse” line is memorable because it compresses two kinds of uncertainty into one production moment. Nintendo was coordinating overlapping projects with shared developers, and it was trying to make a game whose central promise depended on players learning through exploration. The first challenge was organizational; the second was design-related. They intensified each other when Zelda needed finishing work while Mario was still being completed.
Free tools Windows power users keep installed
One-click scans. No signup required.
Miyamoto’s comments also show that Zelda’s openness was not treated as automatically successful. The team worried that a player could reach the beginning, make an unproductive choice and fail to understand how to proceed. That concern does not contradict the goal of exploration. It defines the design problem: create enough structure for a player to form an understanding, while leaving enough room for discovery to feel like the player’s own achievement.
So, were Mario and Zelda made at the same time? In the qualified sense supported by Miyamoto’s reported recollection, yes. Why was it hard to move Mario’s programmers to Zelda? Because Mario still had to be finished and Zelda needed those developers for its final push. What did Miyamoto want players to do in Zelda? Explore a land, understand its nature through interaction, and conquer dungeons with the help of a simple mapping system. Those three answers are the substance behind the colorful “madhouse” framing.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
