Game development takes time—unless you’re Ryu Ga Gotoku Studio. Then it just takes guts, a bit of chaos, and a team that somehow thrives under pressure. At GDC 2025, Ryosuke Horii (Chief Director and Producer at Sega) and Eiji Hamatsu (Design Manager, 1st Business Unit) hosted a panel walking attendees through how the Like a Dragon series continues to deliver story-rich, visually ambitious RPGs on a surprisingly short production cycle.
Joining Horii was Hamatsu, a longtime design lead at RGG whose career with the series goes back to the original Yakuza. His insight into the studio’s world-building and background art helped round out the talk, offering a rare look at how RGG balances creativity with efficiency.
Narrative is a System, Not a Script
Horii kicked things off by clarifying a common misconception: narrative does not equal story. For RGG, narrative is the entire experience—the emotional rhythm players feel as they move through the world. “We’re not writing novels or movies; we’re crafting experiences that unfold through gameplay,” he said.
Rather than forcing story and gameplay into separate silos, the team develops both together. Story beats influence mechanics; mechanics inform story beats. Horii emphasized the importance of “margins”—built-in flexibility that allows writers and designers to pivot or expand ideas mid-development.
Take Yakuza: Like a Dragon as an example. The story of a homeless ex-yakuza rising from rock bottom created a rags-to-riches scenario that affected everything from job mechanics to the tone of side quests. “This narrative theme—rising from rock bottom—allowed for unique character progression, story beats, and emotional resonance with the player,” Horii explained.
The studio also uses side content strategically. He mentions how the team uses substories that deepen character development, balance emotional pacing, and sometimes explore themes too risky for the main plot, yea, we’ve all spent too much time in the cabaret club. This modular structure makes it easier to produce dense, engaging content at speed without overloading the core development pipeline.
How to Build a Game in Half the Time
If there’s a secret sauce to RGG’s speed, it comes down to three core ideas: parallel development, asset efficiency, and real-world continuity.
1. Parallel Development
Hamatsu explained that RGG doesn’t wait for every detail to be finalized before building. Once they have the bare minimum information—like knowing a boss fight will happen in a certain area—teams begin prototyping environments, combat flow, and even minigame frameworks.
This method, called simultaneous parallel development, is risky but effective. Artists, designers, and writers work concurrently, sharing a rough vision and refining as they go. As Hamatsu put it, the alternative—waiting for upstream approvals—would “drastically extend” production time.
Horii added, “This term refers to you having different sections or roles on the team progressing work on a project at the same time in order to complete rapid schedule.” But he acknowledged that this method requires constant oversight: “The slightest wrong decision can bring confusion and the risk of not finishing that portion.”
A good example is when the team began designing a convenience store for the Dragon Engine transition before all narrative details were in place. “We aimed to have this area ready in time for the demo version,” Hamatsu said, which helped the team test graphics benchmarks and build internal standards early.
2. Real-Time World Progression
Unlike many franchises that reboot or rehash, Like a Dragon lets its world age with the players. Characters grow older. Cities change slightly. This grounded continuity means the team can reuse environments like Kamurocho or Sotenbori without them feeling static. Familiarity becomes a feature, not a flaw.
“This is a series without having to reboot the protagonist, characters, and universe every time,” said Horii. “Players can feel a sense of comfort when they see coming at you similar to your hometown after a long time.”
3. Smart Asset Reuse
Hamatsu broke down how spaces like Kamurocho are built to do more with less. A single building can contain a karaoke bar, a loan office, and a shady club—stacked vertically to create spatial complexity in a small footprint. Even stairwells get special attention to alter flow and feeling.
Reusing maps doesn’t mean laziness. It means refinement. “We alter assets, change lighting, and design new gameplay flows to make each appearance feel fresh,” Hamatsu said. This allows the team to push resources toward what is new—like boss encounters or elaborate set pieces.
For Like a Dragon: Gaiden, a repurposed base map was used so the team could focus resources on the castle area, elevating its detail without spreading the team too thin.
Leadership and Taste-Driven Decision Making
Rapid development requires tight leadership. Horii described his role as one of constant judgment calls—dozens per day—and admitted that not every decision has a clear answer. In those moments, he leans on what he calls “artistic authorship.”
“When logic runs out, trust taste,” he said. That mindset, paired with clear communication and an honest understanding of team strengths and limits, helps RGG stay agile without derailing projects.
Horii believes clarity in creative identity is critical: “This means having a clear understanding of what is right and what is important within the context of the Like a Dragon series.” Deviating from that sense of identity, he said, risks making the game feel off.
He also stressed the value of learning from the past. “Being aware of successful and unsuccessful practices… helps us avoid risks to prevent similar failures recurring.”
In case you missed it, check out our review of Like a Dragon: Pirate Yakuza in Hawaii. Like a Dragon: Pirate Yakuza in Hawaii, is now available worldwide on PlayStation 4, PlayStation 5, Xbox One, Xbox Series X|S, and PC via Steam.
How do you feel about this inside look at the Like a Dragon dev process? Let us know in the comments below, and stay tuned to Noisy Pixel for more coverage.



























