Japanese game studios structure development teams as long-lived cross-functional project groups, typically 10 to 40 people, led by a game director who owns the creative vision and a producer who owns schedule and budget. Discipline groups such as planning, design, art, programming, QA and localisation staff those teams from underneath.
That two-headed leadership model is the single most misunderstood thing about working in Japan. Ask ten developers what a producer does and you will get ten answers, usually from studios in different countries.
This guide maps the structure as it actually operates at Nintendo, Bandai Namco Entertainment, Capcom, Sega, Square Enix, Konami, Koei Tecmo and mobile operators like DeNA, then translates it into something an international team can actually use. Structures vary by company and by project, so treat this as a map rather than a single chart.
Table of Contents
- 1What Is the Typical Japanese Game Studio Structure?
- 2How Japanese Game Studios Structure Development Teams
- 3How Japanese Game Studios Structure Development Teams in Practice
- 4Which Roles Usually Form the Development Core?
- 5How Are Small, Mid-Sized, and Large Teams Different?
- 6How Do Producers Keep Cross-Functional Teams Aligned?
- 7What Leadership Styles Are Common in Japanese Studios?
- 8How Do Team Structures Change by Game Genre and Platform?
- 9How Do Japanese Studios Handle Outsourcing and External Partners?
- 10What Can International Teams Learn from These Structures?
- 11Frequently Asked Questions
- 12How many people are usually on a Japanese game development team?
- 13Does a producer in a Japanese game studio make final creative decisions?
- 14Are Japanese game development teams organized by discipline or by project?
- 15How do Japanese studios communicate when developers work remotely?
- 16What team structure should a small international game studio use?
- 17Start by Mapping Decisions, Not Just Job Titles
What Is the Typical Japanese Game Studio Structure?
The typical Japanese game studio structure has four layers: the company, a business unit or division, a project team, and an individual contributor reporting to a discipline lead. Most people only ever see layers three and four.
At the top sits the company, run by an executive team and a studio or business-unit leadership group. Below that, large publishers split into product divisions. Nintendo’s Software Planning and Development division is the clearest published example: reference material describes it as two departments, one handling internal development and another co-producing with external studios.
Bandai Namco Entertainment publishes its own organisation chart on its corporate overview page, and Sega, Square Enix and Konami all run multiple production divisions under a shared corporate centre. The shared centre holds functions a project team should never build for itself: HR, finance, legal, corporate communications, and business planning.
Here is the layering in short form.
| Layer | Who sits there | What they decide |
|---|---|---|
| Company executive | President, executive officers, business-unit heads | Which projects get funded at all |
| Division or studio | Division head, discipline managers, general managers | Permanent staffing, headcount, standards |
| Project team | Game director, producer, planners, designers, artists, engineers, QA | What the game is and when it ships |
| Discipline pool | Senior and mid-level specialists who staff many projects | Craft standards, hiring, career growth |
The fourth layer is the part Western readers rarely anticipate. A senior character artist is not employed by one game. They belong to the art department, and the department lends them to whichever project needs them.
How Japanese Game Studios Structure Development Teams
Inside a project team, responsibilities stack in seven layers: executive and project leadership, creative direction, engineering, art, production, quality assurance, and publishing or business support. Every role in the seventh layer usually sits partly outside the team.
- Leadership: the game director, the producer, and usually a project manager or chief desk under them.
- Creative direction: art director, audio director, scenario or narrative lead.
- Engineering: lead engineer or technical director, gameplay programmers, UI programmers, engine and tooling programmers.
- Art: character, environment, effect and UI artists, plus technical artists who bridge art and engineering.
- Design and planning: planners, system designers, level designers, UX designers.
- Production and quality: production management, QA leads, test coordinators, bug triage.
- Support: localisation, marketing, community management, live-operations analysts, user research.
How Japanese Game Studios Structure Development Teams in Practice
Picture a composite console project of the kind that runs at a company like Capcom or Bandai Namco. The figures below are illustrative, not a real team’s roster, but the shape matches how these projects are usually staffed.
Proposal. Three to five people from the planning group write a proposal. A concept document, a target platform, a rough budget and a schedule window go to the division head. Nothing else happens until a director and producer are named, because a proposal without those two people has nobody accountable.
Pre-production. The director and producer pull specialists from the discipline pools for a few months. Prototypes get built. Milestone dates get fixed. By the end, roughly 15 to 25 people are attached part-time.
Production. The full team forms, usually somewhere between 20 and 40 people, plus a QA group that grows near the end. Work is tracked against a milestone schedule with review gates where the director signs off on builds. Content completion drives headcount: a team asking for one more character concept artist is usually a sign the character milestone slipped.
Release and support. QA peaks, a bug triage group runs daily, and localisation moves through external vendors. After launch most of the team is released back to the pools or reassigned, and a much smaller live-operations or support group stays behind.
That release-back step surprises newcomers most. Teams are built per project and dissolved after it, which is exactly why Japanese studios keep such deep internal discipline pools.
Which Roles Usually Form the Development Core?
The development core of any Japanese project team is about twelve roles. Here is what each one owns, in one line each.
| Role | Japanese term | Owns |
|---|---|---|
| Game director | Game Director | Creative vision, the final call on what the game is |
| Producer | Producer | Schedule, budget, staffing, risk, the publisher relationship |
| Planner | Kikaku | The concept and product plan, plus proposal writing |
| System designer | System Designer | Core rules, progression, combat or economy systems |
| Level designer | Level Designer | Layout, pacing, encounter placement |
| Art director | Art Director | Visual identity and the style guide teams must follow |
| Character artist | Character Artist | Character models, rig setup, animation hand-off |
| Environment artist | Environment Artist | Stages, backgrounds, lighting pass |
| Technical artist | Technical Artist | Shaders, pipeline, art-engine performance |
| Lead engineer | Lead Programmer | Architecture, code standards, build integrity |
| QA engineer | QA | Test plans, regression, bug verification |
| Live-operations planner | Live Ops | Events, balance patches, content cadence after launch |
The planner role has no clean Western equivalent, and it is the most under-covered part of Japanese studio structure. Kikaku covers game design, product planning and the proposal document in a single discipline. A planner who wants to change a core system will first write why, circulate it, and get sign-off, then brief the system designers who build it.
Seniority carries real weight on top of craft. The senpai and kohai relationship is not decoration. A senior planner’s document moves; a new graduate’s document waits. Japanese studios rarely run a flat team where anyone can decide anything, and practitioners on r/gamedev describe the director as holding vision while the producer holds organisation.
How Are Small, Mid-Sized, and Large Teams Different?
Studio size changes how many roles get combined, not which decisions get made. A twelve-person studio has no separate localisation or marketing department, but the localisation decision still happens somewhere.
A concrete anchor: a game director with console and mobile experience told an r/gamedev AMA audience he was leading a team of about 20 people. That is a mid-sized project inside a large company, and it is the figure most often cited for a director-led team.
| Studio size | Typical project team | How roles combine | Outsourcing |
|---|---|---|---|
| Indie, under 30 staff | 5 to 15 | One person holds producer, director and lead engineer | Art and audio, often |
| Mid-sized, 30 to 150 staff | 10 to 25 | Producer and director split; discipline leads part-time | Art, audio, localisation |
| Large publisher, 150+ staff | 20 to 40 plus QA | Full discipline departments, dedicated QA and production | Art, audio, localisation, QA overflow |
| Mobile live-service | 15 to 30 core, plus ops | Analysts, community and ops added post-launch | Art, marketing, localisation, backend |
Management layers thin as teams grow, not thicken. A large company has more layers between a programmer and the president, but the project team itself usually stays small. That is why the project team, not the company, is the unit a Japanese developer thinks of as their team.
How Do Producers Keep Cross-Functional Teams Aligned?
Producers keep cross-functional teams aligned through five mechanisms, and they are the same five whatever the studio size. Milestone scheduling, task ownership, written design documentation, daily coordination, and review gates with scope control.
Milestone scheduling sets fixed dates for content-complete, alpha, beta and submission. Everything else is negotiable until the date locks. Task ownership is written down, so a request to change a weapon design arrives as an assignment with a name on it rather than a hallway conversation.
Daily coordination is short and standing, usually under 20 minutes per discipline. Anything longer moves to a weekly review meeting where the director and producer sit with discipline leads. Review gates are where scope actually gets cut, and they are the producer’s strongest tool.
Two Japanese decision-making practices sit underneath all of it. Nemawashi is the pre-meeting circulation of a proposal so objections surface before a formal meeting, and ringi is the formal sign-off stamp that records who approved it. The pair slows a single decision and speeds up a hundred, because nobody discovers a blocker in the final week of a milestone.
A Japan Online Game Association survey from the early 2020s, widely cited in industry write-ups, found over 70% of surveyed studios using agile workflows. That sits oddly beside ringi and nemawashi, and the honest reading is that studios run agile iteration inside a consensus-heavy decision layer.
What Leadership Styles Are Common in Japanese Studios?
Four leadership styles show up most often in Japanese studios: producer-led, director-led, collaborative and discipline-led. Most projects run a blend, and the blend usually shifts over the project’s life.
Producer-led teams have a producer who effectively runs the project, with the director focused on creative review. You see this more in live-service mobile, where the operating calendar matters as much as the vision. Director-led teams hand the director broader authority over scope as well as content, common on prestige console projects. Collaborative teams push decisions down to discipline leads, which tends to appear on smaller or co-developed titles. Discipline-led teams mean the engineering or art department head holds the final say on anything touching their craft.
The escalation path matters more than the label. When director and producer disagree, the question of who wins is settled before the project starts, usually in the proposal phase. Projects that never resolve it tend to ship late with a resentful team.
Compare this to a Western project manager, whose authority is usually coordination rather than budget ownership. A Japanese producer holds the project’s budget and staffing, which is a genuinely different level of control.
How Do Team Structures Change by Game Genre and Platform?
Console work staffs for craft quality and schedule discipline. Mobile free-to-play and live-service work staffs for cadence and measurement, and the roster looks different within months of launch.
A live-service mobile team built around a Japanese operator such as DeNA adds data analysts, economy designers, community managers and customer support once the game is live. Those roles sit outside the development team and feed back into it, which is a structure console projects do not have at all.
Console projects lean harder on pre-production because content volume is front-loaded and bugs are expensive late. PC and mid-sized titles tend to have smaller teams, earlier prototypes and a heavier outsourcing share. Narrative-driven projects add scenario writers, translators and audio directors earlier than a competitive multiplayer title does, which trades combat systems work for dialogue volume.
The common difference is that console teams are built to a fixed end date, while live-service teams are built for indefinite operation. That single fact changes the hiring mix more than any other.
How Do Japanese Studios Handle Outsourcing and External Partners?
Japanese studios keep core systems, the engine and art direction in house, and outsource everything around them. Art assets, audio, motion capture, localisation, QA overflow and marketing production are the usual outsourced functions.
Nintendo’s Software Planning and Development division is the clearest case: one of its two departments exists specifically to co-produce with external developers. The external studio supplies execution capacity while Nintendo keeps the design, the brand and the ship decision.
Vendor coordination is its own job inside larger publishers, usually under production or a partner management group. Internal ownership stays with a named producer and a discipline lead who reviews every external asset against the internal standard before it enters a build.
Communication is the hard part. Japanese hubs with overseas partners run bilingual documentation as a habit, not an exception, and they rely more on written milestones than on live calls. Time zone spread argues for async by default, with scheduled sync reserved for milestone reviews and escalations.
What Can International Teams Learn from These Structures?
The transferable parts of Japanese studio structure are the boring ones, and they are worth copying. Decide decision rights before staffing the project, not during the first argument.
Keep ownership visible. In Japanese teams, who approves a document is written on the document. A Western team can get the same effect with a decision log and named owners.
Preserve specialist input. The discipline pool means an art director reviews a style question even when the project is mostly programming. Small teams can copy this by paying for a real art and audio review instead of a quick opinion from whoever is free.
Adapt communication to project size. Nemawashi and ringi suit a 40-person console team and are dead weight for a six-person startup. Use pre-circulation when a decision is genuinely hard to reverse, not on everything.
Avoid copying titles and rituals without context. A freelance director track works in Japan because of a specific freelance market. The same label in a five-person team usually means nobody has authority at all.
One honest difference worth knowing: Japanese studios have been widely reported as reluctant to mass-lay-off, a pattern discussed at length on ResetEra. That permanence changes team design, because long project tenures and internal transfers are a real option rather than a theoretical one. It also makes it harder to shed a struggling team, which is a trade-off rather than a free win.
Frequently Asked Questions
How many people are usually on a Japanese game development team?
Most mid-sized Japanese projects run 10 to 25 people, and larger console projects reach 20 to 40 plus a QA group that grows near release. A game director with console and mobile experience described leading a team of about 20 in a public AMA. Indie and small studios compress the same roles into 5 to 15 people.
Does a producer in a Japanese game studio make final creative decisions?
Usually not. The game director owns creative vision and signs off on the game as it is built, while the producer owns schedule, budget, staffing and risk. In live-service mobile projects the producer’s influence often extends to feature scope, because the operating calendar constrains what can ship. Projects that never settle the split in advance tend to argue about it late.
Are Japanese game development teams organized by discipline or by project?
Both, layered. Individuals belong to a discipline department such as art, engineering or planning, and the department lends people to a project team for the length of that project. Once the title ships the core team is released back to the pool. That is why large publishers maintain deep internal departments and why team formation happens at the proposal stage.
How do Japanese studios communicate when developers work remotely?
Written documentation carries most of the load. Decisions, scope changes and design proposals are circulated as documents before meetings, a practice known as nemawashi, and formal sign-off is recorded with ringi. Studios with overseas partners add more async work and fewer live calls, saving synchronous time for milestone reviews and escalations rather than status updates.
What team structure should a small international game studio use?
Keep the decision rights and drop the titles. Name one person who owns the vision, one who owns schedule and budget, and make those two explicit before hiring. Keep specialists as specialists rather than folding art or audio into generalists, and use written decision logs so ownership survives when people are offline. Nemawashi and ringi are worth adopting only for decisions that are hard to reverse.
Start by Mapping Decisions, Not Just Job Titles
If you take one thing from this guide, take the decision map. Japanese game studios structure development teams around a project team of 10 to 40, a director who owns vision, a producer who owns schedule and budget, and discipline departments that staff the project from below.
Before you restructure anything on your own project, write down who owns design, who owns technical decisions, who owns schedule, who owns quality sign-off and who owns the release call. Then check whether anyone outside that list can override them. That is the real Japanese lesson, and it has nothing to do with job titles.
