Sonic producer says Nintendo-sized teams can learn from indie hits

Takashi Iizuka’s message was simple enough to matter in a place like Nintendo: small teams can still ship the ideas people remember, and AAA timelines can get in the way of that clarity. The Sonic producer pointed to lower-budget hits such as Backrooms and Obsession as proof that audiences still respond to fresh concepts, then praised the faster iteration he sees in smaller teams. For Nintendo producers, designers, and QA, the practical takeaway is not to pretend a Mario or Zelda project is an indie game. It is to borrow the habits that make smaller teams move: narrower prototypes, shorter feedback loops, and faster decisions about what should be cut before it grows expensive.

The timing gives the comments extra weight. Sega announced Sonic Pico Park on June 5 as a new indie partnership, said TECOPARK was developing it, and described it as Sega’s first Sonic title licensed out to an indie team. The game was positioned as part of Sonic’s 35th anniversary celebrations during the Summer Game Fest 2026 livestream. That is a clean example of a large brand using a small external team to add energy and variety without turning the project into a sprawling internal program.

Nintendo has been making a similar argument in its own language for years. In a November 6, 2024 investor Q&A, Shigeru Miyamoto said Nintendo’s R&D expenses had been increasing each year and that the rise is, in some respects, inevitable. He added that “what we create is more important than the amount spent on development,” while stressing that Nintendo keeps refining products until it is confident consumers will be satisfied. That is not a call for austerity. It is a reminder that cost is a tool, not a philosophy.

That philosophy is already embedded in Nintendo’s own developer-facing storytelling. The company’s Iwata Asks interviews have long framed development around the time, energy and creative thought behind a product, while Ask the Developer emphasizes the unusual details teams hone in on when building Nintendo software. Read together, those materials and Iizuka’s comments point to the same management lesson for Nintendo-sized teams: greenlight fewer ideas, test them earlier, and let the strongest one survive repeated playtests. In an industry that keeps rewarding focused games, the teams that move fastest without losing polish may have the clearest path to the next standout release.